Re: [Xen-devel] Re: [patch 05/21] Xen-paravirt: paravirt_ops: allocate a fixmap slot

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 > >>

[Xen-devel] Re: [patch 05/21] Xen-paravirt: paravirt_ops: allocate a fixmap slot

>>> 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

[Xen-devel] Re: [patch 05/21] Xen-paravirt: paravirt_ops: allocate a fixmap slot

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

Re: [Xen-devel] Re: [patch 05/21] Xen-paravirt: paravirt_ops: allocate a fixmap slot

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.