* Jeremy Fitzhardinge <[EMAIL PROTECTED]> wrote:
> Allocate a fixmap slot for use by a paravirt_ops implementation. This
> is intended for early-boot bootstrap mappings. Once the zones and
> allocator have been set up, it would be better to use get_vm_area() to
> allocate some virtual
* Jeremy Fitzhardinge [EMAIL PROTECTED] wrote:
Allocate a fixmap slot for use by a paravirt_ops implementation. This
is intended for early-boot bootstrap mappings. Once the zones and
allocator have been set up, it would be better to use get_vm_area() to
allocate some virtual space.
Allocate a fixmap slot for use by a paravirt_ops implementation. This
is intended for early-boot bootstrap mappings. Once the zones and
allocator have been set up, it would be better to use get_vm_area() to
allocate some virtual space.
Xen uses this to map the hypervisor's shared info page,
Allocate a fixmap slot for use by a paravirt_ops implementation. This
is intended for early-boot bootstrap mappings. Once the zones and
allocator have been set up, it would be better to use get_vm_area() to
allocate some virtual space.
Xen uses this to map the hypervisor's shared info page,
Ingo Molnar wrote:
> fair enough. Please rename it to FIX_PARAVIRT_BOOTUP - you can still
> rely on it being available later on too, but we'd like to give everyone
> the right fundamental idea about this: it's meant to be a limited,
> inflexible interface for bootstrap only.
>
Will do.
* Jeremy Fitzhardinge <[EMAIL PROTECTED]> wrote:
> > Yes. vmalloc would have the annoying side-effect of actually
> > allocating some pages which would be shadowed by the remapping, but
> > I guess get_vm_area would do the job. I'll give it a go.
>
> Hm, this is a bit awkward. We need to
* Jeremy Fitzhardinge [EMAIL PROTECTED] wrote:
Yes. vmalloc would have the annoying side-effect of actually
allocating some pages which would be shadowed by the remapping, but
I guess get_vm_area would do the job. I'll give it a go.
Hm, this is a bit awkward. We need to map the
Ingo Molnar wrote:
fair enough. Please rename it to FIX_PARAVIRT_BOOTUP - you can still
rely on it being available later on too, but we'd like to give everyone
the right fundamental idea about this: it's meant to be a limited,
inflexible interface for bootstrap only.
Will do.
J
-
Jeremy Fitzhardinge wrote:
> Ingo Molnar wrote:
>
>> why not vmalloc it on the guest side? fixmaps are bad for this purpose
>> for a general paravirt implementation, it limits the size of the shared
>> info page, etc.
>>
>
> Yes. vmalloc would have the annoying side-effect of actually
Ingo Molnar wrote:
> * Jeremy Fitzhardinge <[EMAIL PROTECTED]> 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
>>
* Jeremy Fitzhardinge <[EMAIL PROTECTED]> 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 not vmalloc it on
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.
Signed-off-by: Jeremy Fitzhardinge <[EMAIL PROTECTED]>
---
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.
Signed-off-by: Jeremy Fitzhardinge [EMAIL PROTECTED]
---
* Jeremy Fitzhardinge [EMAIL PROTECTED] 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 not vmalloc it on the
Ingo Molnar wrote:
* Jeremy Fitzhardinge [EMAIL PROTECTED] 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.
Jeremy Fitzhardinge wrote:
Ingo Molnar wrote:
why not vmalloc it on the guest side? fixmaps are bad for this purpose
for a general paravirt implementation, it limits the size of the shared
info page, etc.
Yes. vmalloc would have the annoying side-effect of actually allocating
16 matches
Mail list logo
