LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Borislav Petkov <email@example.com> To: Tor Vic <firstname.lastname@example.org> Cc: "email@example.com" <firstname.lastname@example.org>, "email@example.com" <firstname.lastname@example.org>, "email@example.com" <firstname.lastname@example.org>, "email@example.com" <firstname.lastname@example.org>, "email@example.com" <firstname.lastname@example.org>, Christoph Hellwig <email@example.com>, Greg KH <firstname.lastname@example.org> Subject: Re: [PATCH 2/2] x86, Makefile: Add new generic x86-64 settings v2/v3/v4 Date: Wed, 18 Aug 2021 20:43:04 +0200 [thread overview] Message-ID: <YR1UuJM0GumaTIi2@zn.tnic> (raw) In-Reply-To: <email@example.com> On Wed, Aug 18, 2021 at 06:28:47PM +0000, Tor Vic wrote: > That's something I'd like to help with, hence my (not very good) > submissions. You're one of the kernel colonels, so I'm happy to get > some *useful* feedback which enables noobs like me to get a better > understanding of the kernel stuff. Sure, Greg so happens to have written a reply recently explaining what to do: https://lists.kernelnewbies.org/pipermail/kernelnewbies/2017-April/017765.html Thx Greg! In addition to the above, I'd suggest reading lkml, reading other people's patches, review of those patches by people and trying to understand what they're talking about. And then following through the code to try to see it. What also really helps is setting up a kvm guest, booting the kernel with it and adding printks here and there and dumping interesting information with them. Once you start dealing with this, you might spend a couple of decades figuring it all out in full depth. :-) Oh, and this https://www.kernel.org/doc/html/latest has all of the kernel's documentation formatted nicely. I sincerely hope that helps a bit. -- Regards/Gruss, Boris. https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2021-08-18 18:42 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-17 14:23 [PATCH 1/2] x86, Makefile: Move the CPU-specific 64-bit tuning settings to arch/x86/Makefile.cpu torvic9 2021-08-17 14:24 ` [PATCH 2/2] x86, Makefile: Add new generic x86-64 settings v2/v3/v4 torvic9 2021-08-17 18:17 ` Nick Desaulniers 2021-08-17 18:22 ` Nick Desaulniers 2021-08-17 18:31 ` Tor Vic 2021-08-17 18:47 ` Nick Desaulniers 2021-08-17 18:36 ` Borislav Petkov 2021-08-17 19:12 ` Tor Vic 2021-08-18 15:08 ` torvic9 2021-08-18 17:59 ` Borislav Petkov 2021-08-18 18:28 ` Tor Vic 2021-08-18 18:43 ` Borislav Petkov [this message] 2021-08-18 7:15 ` Christoph Hellwig 2021-08-18 9:46 ` torvic9 2021-08-19 21:58 ` David Laight 2021-08-17 17:58 ` [PATCH 1/2] x86, Makefile: Move the CPU-specific 64-bit tuning settings to arch/x86/Makefile.cpu Nick Desaulniers 2021-08-17 18:28 ` Tor Vic 2021-08-18 7:11 ` Christoph Hellwig 2021-08-18 9:46 ` torvic9 2021-08-18 14:51 ` Masahiro Yamada
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=YR1UuJM0GumaTIi2@zn.tnic \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).