All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bilbao, Carlos" <carlos.bilbao@amd.com>
To: Josh Marshall <joshua.r.marshall.1991@gmail.com>, ngn <ngn@ngn.tf>
Cc: linux-newbie@vger.kernel.org,
	"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
	Jonathan Corbet <corbet@lwn.net>,
	pranjal.singh4370@gmail.com, "bilbao@vt.edu" <bilbao@vt.edu>
Subject: Re: Feedback on my development setup
Date: Tue, 23 Apr 2024 11:39:59 -0500	[thread overview]
Message-ID: <7ba7cff1-8d9d-4bc3-a74c-6f6828c9195e@amd.com> (raw)
In-Reply-To: <CAFkJGRdjvebW6u6pyyA_MeHsoecRgYjiVrxoWYWsREdYH9iOFQ@mail.gmail.com>

Hello Josh,

On 4/23/2024 10:34 AM, Josh Marshall wrote:
> I have a draft document which I would like broader review on, which
> currently lives here:
> https://gitlab.com/anadon/getting-started-on-kernel-dev-guide-workspace.
> This document is to ease the setup of Kernel Development.  I intend to
> send this in as a patch to the mainline doc tree once it gets by a
> suitable number of reviewers.

It's great that you're interested in improving the documentation. I've CCed
linux-doc list for visibility.

However, please note that we already have existing documentation, and it
might be better to extend what's already there rather than creating
something entirely new. You can refer to:

https://www.kernel.org/doc/html/latest/process/development-process.html

If you still feel the need to start a new document and host it remotely, I
suggest updating:

https://www.kernel.org/doc/html/v6.1/process/kernel-docs.html

If I may offer a suggestion, focusing on documenting the challenges you've
encountered with KVM, etc., could be more valuable that trying to cover
everything.

> 
> On Fri, Apr 19, 2024 at 12:15 PM ngn <ngn@ngn.tf> wrote:
>>
>> On Thu, Apr 18, 2024 at 05:40:20PM -0400, Josh Marshall wrote:
>>> Looks like breakpoints aren't working?  https://paste.debian.net/1314501/
>>>
>>
>> This maybe caused by Kernel Address Space Randomization (KASLR), try
>> disabling it by adding nokaslr option to the boot options.

Thanks,
Carlos

  parent reply	other threads:[~2024-04-23 16:40 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-16 12:38 Feedback on my development setup Josh Marshall
2024-04-16 14:56 ` ngn
2024-04-16 15:03   ` Josh Marshall
2024-04-16 15:21     ` ngn
2024-04-17 16:11       ` Josh Marshall
     [not found]         ` <CAPzh0z8RySn429XYQHoP_c9UA+pb6SLHGhH40vQDhc3P2xiysQ@mail.gmail.com>
2024-04-17 21:18           ` Josh Marshall
2024-04-18 15:35             ` ngn
2024-04-18 19:15               ` Josh Marshall
2024-04-18 19:27                 ` Josh Marshall
2024-04-18 19:52                   ` Josh Marshall
2024-04-18 21:40                     ` Josh Marshall
2024-04-19 16:14                       ` ngn
2024-04-23 15:34                         ` Josh Marshall
2024-04-23 16:08                           ` Pranjal Singh
2024-04-23 16:39                           ` Bilbao, Carlos [this message]
2024-04-23 17:43                             ` Josh Marshall
2024-04-25  5:37                               ` Josh Marshall
2024-04-25 14:36                                 ` Bilbao, Carlos
2024-04-25 14:54                                   ` Josh Marshall
2024-04-25 15:14                                     ` Jonathan Corbet
     [not found]                                       ` <CAFkJGReoq2s+LR1kj1hj8QvsKsEhk+CLYtCXV=DQTjTqan3DOg@mail.gmail.com>
2024-04-25 16:59                                         ` Carlos Bilbao
2024-04-25 17:08                                       ` Josh Marshall
2024-04-25 20:14                                         ` Theodore Ts'o
2024-04-25 20:02                             ` Theodore Ts'o
2024-04-25 14:32                           ` Thomas Bertschinger

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=7ba7cff1-8d9d-4bc3-a74c-6f6828c9195e@amd.com \
    --to=carlos.bilbao@amd.com \
    --cc=bilbao@vt.edu \
    --cc=corbet@lwn.net \
    --cc=joshua.r.marshall.1991@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-newbie@vger.kernel.org \
    --cc=ngn@ngn.tf \
    --cc=pranjal.singh4370@gmail.com \
    /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: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.