| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
Re: [Xen-devel] Re: changeset 13403 ...
We're not proposing to change that. This out-of-the-way allocation would be
a very temporary measure to transfer us from the current pagetables to the
builder pagetables. The memory area will be unused by the time the
chain-booted kernel starts to execute.
-- Keir
On 29/1/07 18:36, "Joe Bonasera" <joe.bonasera@xxxxxxx> wrote:
>
> I'm dropping in on this part way through but
> out of context the following sounds dangerous.
>
> For example, Solaris domains assume at start
> of time, that only pages mapped in the start
> area are in use in any way. All other pages
> go immediately in our free lists. If you change
> this protocol, then we'll have backwards
> incompatibility issues to fix.
>
>> Date: Mon, 29 Jan 2007 16:35:48 +0100
>> From: Gerd Hoffmann <kraxel@xxxxxxx>
>> Subject: Re: [Xen-devel] Re: changeset 13403 ...
>> To: Keir Fraser <keir@xxxxxxxxxxxxx>
>> Cc: Xen devel list <xen-devel@xxxxxxxxxxxxxxxxxxx>
>> Message-ID: <45BE1454.9030101@xxxxxxx>
>> Content-Type: text/plain; charset=ISO-8859-1
>>
>> Hi,
>>
>>> You may even know that they only map part of
>>> the guest physical memory and so choose to locate the intermediate
>>> pagetables outside that mapped area.
>>
>> Good point, that solves at least a part of the problem, as the read-only
>> mapping is needed one-way only then ...
>>
>> thanks,
>> Gerd
>>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home