From: Pavel Machek <pavel@suse.cz>
To: "Perez-Gonzalez, Inaky" <inaky.perez-gonzalez@intel.com>
Cc: Yasunori Goto <ygoto@fsw.fujitsu.com>,
linux-kernel@vger.kernel.org, "Luck, Tony" <tony.luck@intel.com>,
IWAMOTO Toshihiro <iwamoto@valinux.co.jp>,
Hirokazu Takahashi <taka@valinux.co.jp>,
Linux Hotplug Memory Support <lhms-devel@lists.sourceforge.net>
Subject: Re: [Lhms-devel] RE: memory hotremove prototype, take 3
Date: Thu, 4 Dec 2003 12:01:01 +0100 [thread overview]
Message-ID: <20031204110101.GF11044@atrey.karlin.mff.cuni.cz> (raw)
In-Reply-To: <A20D5638D741DD4DBAAB80A95012C0AE0125DD6A@orsmsx409.jf.intel.com>
Hi!
> > > I still think we could use the CPU's virtualization mechanism--of course,
> > > and as you and Tony Luck mention, we'd had to track down and modify the
> > > parts that assume physical memory et al. That they use large pages
> > > or
> >
> > ...which means basically auditing whole kernel, and rewriting half of
> > drivers. Good luck with _that_.
>
> Bingo...just the perfect excuse I need to give to my manager to keep
> a low profile while tinkering around for a long time :)
>
> Okay, so I will play a wee bit more the devil's advocate as an
> exercise of futility, if you don't mind. Just trying to compile a
> (possibly incomplete) quick list of what would be needed, can you
> guys help me? you know way more than I do:
>
> 1) the core kernel needs to be independent of physical memory position
> 1.1) same with drivers/subsystems
> 1.2) filesystems
> [it cannot be really incomplete because I have added all the code
> :/]
...and you have bad problem at any place where physical address is
passed to the hardware. UHCI is going to be "interesting".
Pavel
--
Horseback riding is like software...
...vgf orggre jura vgf serr.
next prev parent reply other threads:[~2003-12-04 11:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-04 10:37 [Lhms-devel] RE: memory hotremove prototype, take 3 Perez-Gonzalez, Inaky
2003-12-04 11:01 ` Pavel Machek [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-04 20:06 Luck, Tony
2003-12-04 16:12 Perez-Gonzalez, Inaky
2003-12-04 4:59 Perez-Gonzalez, Inaky
2003-12-04 9:54 ` Pavel Machek
2003-12-03 5:19 Perez-Gonzalez, Inaky
2003-12-03 21:23 ` [Lhms-devel] " Yasunori Goto
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=20031204110101.GF11044@atrey.karlin.mff.cuni.cz \
--to=pavel@suse.cz \
--cc=inaky.perez-gonzalez@intel.com \
--cc=iwamoto@valinux.co.jp \
--cc=lhms-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=taka@valinux.co.jp \
--cc=tony.luck@intel.com \
--cc=ygoto@fsw.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 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).