All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nigel Cunningham <nigel@nigel.suspend2.net>
To: Yasunori Goto <y-goto@jp.fujitsu.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: x86_64 memory hotplug simulation support?
Date: Thu, 5 Jul 2007 16:44:54 +1000	[thread overview]
Message-ID: <200707051644.55191.nigel@nigel.suspend2.net> (raw)
In-Reply-To: <20070705145527.2798.Y-GOTO@jp.fujitsu.com>

[-- Attachment #1: Type: text/plain, Size: 1628 bytes --]

Hi.

On Thursday 05 July 2007 16:20:18 Yasunori Goto wrote:
> Hello. Nigel-san.
> 
> > I'm wondering whether anyone has patches lying around that might be useful 
for 
> > simulating memory hotplug on x86_64. Goggling has revealed some old x86 
> > patches, but that's all.
> 
> I'm not sure what "simulation" means.
> Could you tell me how/what do you expect memory hotplug
> simulation exactly?
> 
> Memory hot-add code is included in kernel. And, remove(unplug) code
> has developed (and hopefully, it will be merged to -mm after
> some cleanups, I think.)
> 
> I would like to make sure what is necessary.

Thanks for your reply. Please, just call me Nigel :). I saw a patch that Dave 
Hansen had posted, back around the time of 2.6.11 iirc. It was for x86, and 
(so far as I understand) allowed a person who doesn't really have 
hotpluggable memory to make their computer pretend that it does.

Just in case I'm not being clear enough, let me get more concrete. I have had 
some code for a while that uses bitmaps to simulate page flags, without 
needing to take up those precious bits in page->flags. I've begun to add 
support for memory hotplugging, in the hope that I can make it general enough 
that it will be useful for more than just suspend2. To do that, I'd like to 
be able to test the memory hotplugging paths, without needing to actually 
have hotpluggable memory. I do have an x86 desktop I could work on, but would 
prefer to do it on my x86_64 laptop if I can.

Regards,

Nigel
-- 
See http://www.tuxonice.net for Howtos, FAQs, mailing
lists, wiki and bugzilla info.

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2007-07-05  6:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-05  4:30 x86_64 memory hotplug simulation support? Nigel Cunningham
2007-07-05  6:20 ` Yasunori Goto
2007-07-05  6:44   ` Nigel Cunningham [this message]
2007-07-05  8:52     ` Yasunori Goto
2007-07-05  9:31       ` Nigel Cunningham

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=200707051644.55191.nigel@nigel.suspend2.net \
    --to=nigel@nigel.suspend2.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nigel@suspend2.net \
    --cc=y-goto@jp.fujitsu.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.