On Wed, Feb 14, 2007 at 08:37:26AM +, Jan Beulich wrote:
> >>> Jeremy Fitzhardinge <[EMAIL PROTECTED]> 14.02.07 02:36 >>>
> >Dan Hecht wrote:
> >> Why doesn't Xen allocate the shared_info page from the pseudo-physical
> >> space? Doesn't it already have to steal pages from the
> >>
Dan Hecht wrote:
> Right. But that is only because Xen decides to allocate the page from
> the (machine) physical space, rather than from the pseudo-physical
> space. My question is: why doesn't Xen allocate shared_info from the
> pseudo-physical space?
Historical reasons ...
> If it had,
>>> Jeremy Fitzhardinge <[EMAIL PROTECTED]> 14.02.07 02:36 >>>
>Dan Hecht wrote:
>> Why doesn't Xen allocate the shared_info page from the pseudo-physical
>> space? Doesn't it already have to steal pages from the
>> pseudo-physical space for e.g. initial page tables, console, etc? Why
>> not do
Jeremy Fitzhardinge [EMAIL PROTECTED] 14.02.07 02:36
Dan Hecht wrote:
Why doesn't Xen allocate the shared_info page from the pseudo-physical
space? Doesn't it already have to steal pages from the
pseudo-physical space for e.g. initial page tables, console, etc? Why
not do the same for
Dan Hecht wrote:
Right. But that is only because Xen decides to allocate the page from
the (machine) physical space, rather than from the pseudo-physical
space. My question is: why doesn't Xen allocate shared_info from the
pseudo-physical space?
Historical reasons ...
If it had, then
On Wed, Feb 14, 2007 at 08:37:26AM +, Jan Beulich wrote:
Jeremy Fitzhardinge [EMAIL PROTECTED] 14.02.07 02:36
Dan Hecht wrote:
Why doesn't Xen allocate the shared_info page from the pseudo-physical
space? Doesn't it already have to steal pages from the
pseudo-physical space for e.g.
On 02/13/2007 05:36 PM, Jeremy Fitzhardinge wrote:
Dan Hecht wrote:
Why doesn't Xen allocate the shared_info page from the pseudo-physical
space? Doesn't it already have to steal pages from the
pseudo-physical space for e.g. initial page tables, console, etc? Why
not do the same for
Dan Hecht wrote:
> Why doesn't Xen allocate the shared_info page from the pseudo-physical
> space? Doesn't it already have to steal pages from the
> pseudo-physical space for e.g. initial page tables, console, etc? Why
> not do the same for shared_info, and then you don't need a reserve the
>
On 02/13/2007 02:17 PM, Jeremy Fitzhardinge wrote:
Allocate a fixmap slot for use by a paravirt_ops implementation. Xen
uses this to map the hypervisor's shared info page, which doesn't have
a pseudo-physical page number, and therefore can't be mapped
ordinarily.
Why doesn't Xen allocate the
On 02/13/2007 02:17 PM, Jeremy Fitzhardinge wrote:
Allocate a fixmap slot for use by a paravirt_ops implementation. Xen
uses this to map the hypervisor's shared info page, which doesn't have
a pseudo-physical page number, and therefore can't be mapped
ordinarily.
Why doesn't Xen allocate the
Dan Hecht wrote:
Why doesn't Xen allocate the shared_info page from the pseudo-physical
space? Doesn't it already have to steal pages from the
pseudo-physical space for e.g. initial page tables, console, etc? Why
not do the same for shared_info, and then you don't need a reserve the
fixmap
On 02/13/2007 05:36 PM, Jeremy Fitzhardinge wrote:
Dan Hecht wrote:
Why doesn't Xen allocate the shared_info page from the pseudo-physical
space? Doesn't it already have to steal pages from the
pseudo-physical space for e.g. initial page tables, console, etc? Why
not do the same for
12 matches
Mail list logo
