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

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

Dan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [patch 05/21] Xen-paravirt: paravirt_ops: allocate a fixmap slot
    • From: Jeremy Fitzhardinge <[email protected]>

• Prev by Date: Re: [patch 10/21] Xen-paravirt: Name: dont export paravirt_ops structure, do individual functions
• Next by Date: Re: AHCI - remove probing of ata2
• Previous by thread: Re: [patch 10/21] Xen-paravirt: Name: dont export paravirt_ops structure, do individual functions
• Next by thread: Re: [patch 05/21] Xen-paravirt: paravirt_ops: allocate a fixmap slot
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]