From: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
To: Christian Limpach <Christian.Limpach@cl.cam.ac.uk>
Cc: Paul Mackerras <paulus@samba.org>,
akpm@osdl.org, "Eric W. Biederman" <ebiederm@xmission.com>,
Jesse Barnes <jbarnes@engr.sgi.com>,
linux-kernel@vger.kernel.org, riel@redhat.com,
Ian.Pratt@cl.cam.ac.uk, kurt@garloff.de
Subject: Re: [PATCH] Xen/i386 cleanups - AGP bus/phys cleanups
Date: Sat, 19 Mar 2005 13:01:31 +0000 [thread overview]
Message-ID: <ca43c5769187191af6e1b3c3e91d4bf8@cl.cam.ac.uk> (raw)
In-Reply-To: <20050319105632.GH31328@cl.cam.ac.uk>
On 19 Mar 2005, at 10:56, Christian Limpach wrote:
>> For this specific case there may be another resolution but could
>> you please, please look at marking the missing pages PG_reserved
>> and not hacking phys_to_virt.
>>
>> At this point anything short of explicitly introducing an intermediate
>> step say virt_to_logical() logical_to_virt() will be extremely
>> confusing and lead to very hard to spot bugs. Silently changing
>> the semantics of functions is bad.
>
> We also use the additional level of indirection to implement suspend/
> resume and relocation of virtual machines between physical machines --
> you won't get the same sparse allocation of memory on the target
> machine.
> Also, this will make it much easier to support hot plug memory at the
> hypervisor level since it will be able to substitute memory with very
> little support from the OS running in the virtual machine.
Also, more generally, I don't believe Linux would deal well with a
highly fragmented memory map. I wonder how far Linux would boot if you
PG_reserved every other page? We'd also need to deal with
virtual<->lowmem not being a 1:1 mapping (at least for kernel code and
data, as at least that obviously needs to be contiguous in virtual
space).
-- Keir
next prev parent reply other threads:[~2005-03-19 13:02 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-16 11:48 Keir Fraser
2005-03-16 14:31 ` Christoph Hellwig
2005-03-16 14:58 ` Keir Fraser
2005-03-16 15:01 ` Rik van Riel
2005-03-16 18:10 ` Christoph Hellwig
2005-03-16 18:35 ` Keir Fraser
2005-03-16 18:42 ` Jesse Barnes
2005-03-16 19:08 ` Keir Fraser
2005-03-16 19:06 ` Christoph Hellwig
2005-03-16 19:11 ` Keir Fraser
2005-03-16 17:40 ` Alan Cox
2005-03-16 17:54 ` Jesse Barnes
2005-03-16 21:24 ` Paul Mackerras
2005-03-16 22:06 ` Jesse Barnes
2005-03-16 23:55 ` Rik van Riel
2005-03-17 0:39 ` Paul Mackerras
2005-03-17 1:05 ` Tupshin Harper
2005-03-17 3:44 ` Rik van Riel
2005-03-17 4:42 ` Christoph Hellwig
2005-03-17 4:58 ` Rik van Riel
2005-03-17 9:16 ` Keir Fraser
2005-03-17 9:34 ` Paul Mackerras
2005-03-17 10:56 ` Keir Fraser
2005-03-19 10:07 ` Eric W. Biederman
2005-03-19 10:56 ` Christian Limpach
2005-03-19 13:01 ` Keir Fraser [this message]
2005-03-17 13:53 ` Alan Cox
2005-03-18 0:16 ` Paul Mackerras
2005-03-18 4:23 ` Rik van Riel
2005-03-18 9:05 ` Keir Fraser
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=ca43c5769187191af6e1b3c3e91d4bf8@cl.cam.ac.uk \
--to=keir.fraser@cl.cam.ac.uk \
--cc=Christian.Limpach@cl.cam.ac.uk \
--cc=Ian.Pratt@cl.cam.ac.uk \
--cc=akpm@osdl.org \
--cc=ebiederm@xmission.com \
--cc=jbarnes@engr.sgi.com \
--cc=kurt@garloff.de \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.org \
--cc=riel@redhat.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
all inboxes | Powered by JetHome®