public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: William Lee Irwin III <wli@holomorphy.com>
Cc: Dave Hansen <haveblue@us.ibm.com>,
	linux-kernel@vger.kernel.org,
	"Martin J. Bligh" <mbligh@aracnet.com>
Subject: Re: kexec reboot code buffer
Date: 28 Jan 2003 08:21:23 -0700	[thread overview]
Message-ID: <m1el6x5mh8.fsf@frodo.biederman.org> (raw)
In-Reply-To: <20030128073117.GJ780@holomorphy.com>

William Lee Irwin III <wli@holomorphy.com> writes:

> William Lee Irwin III <wli@holomorphy.com> writes:
> >> Seriously, just plop down the fresh zone type and all will be well.
> >> It's really incredibly easy.
> 
> On Tue, Jan 28, 2003 at 12:28:04AM -0700, Eric W. Biederman wrote:
> > I will certainly take a look, tracing through that code can get a little
> > hairy.
> 
> It can really be approached much more cavalierly than that. The only
> extant example aside from the original ZONE_DMA32 implementation I've
> seen is Simon Winwood's MPSS patch, which needed something on the order
> of 10 lines of code for a fresh zone type (for one arch).
> 
> And most of the bulk of the ZONE_DMA32 implementation was stringing up
> the block layer to utilize it, not inserting the new zone type itself.

Primarily it appears that just another ZONE needs to be added, and then
free_area_init needs to be passed the proper parameters.  

I still want to look closely at how the discontig mem case for NUMA is
setup.  It is probably nothing to worry about but I want to make
certain it does not have any perverse behavior and also I want to be
certain I know how to setup a NUMA system properly, since I am looking
at the code anyway.

Eric

      reply	other threads:[~2003-01-28 15:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3E31AC58.2020802@us.ibm.com>
2003-01-25 14:16 ` kexec reboot code buffer Eric W. Biederman
2003-01-27 21:55   ` Dave Hansen
2003-01-27 22:03     ` Martin J. Bligh
2003-01-28  0:10       ` William Lee Irwin III
2003-01-28  7:24       ` Eric W. Biederman
2003-01-28 16:15         ` Martin J. Bligh
2003-01-29 15:41           ` Eric W. Biederman
2003-01-29 16:17             ` Martin J. Bligh
2003-01-28  7:04     ` Eric W. Biederman
2003-01-28  7:18       ` William Lee Irwin III
2003-01-28  7:28         ` Eric W. Biederman
2003-01-28  7:31           ` William Lee Irwin III
2003-01-28 15:21             ` Eric W. Biederman [this message]

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=m1el6x5mh8.fsf@frodo.biederman.org \
    --to=ebiederm@xmission.com \
    --cc=haveblue@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@aracnet.com \
    --cc=wli@holomorphy.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox