lkml.org 
[lkml]   [2007]   [Sep]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    SubjectRE: [kvm-devel] [PATCH] Refactor hypercall infrastructure
    Date
    From
    Jeremy Fitzhardinge wrote:
    > Nakajima, Jun wrote:
    > > Today, 3 CPUID leaves starting from 0x4000_0000 are defined in a
    generic
    > > fashion (hypervisor detection, version, and hypercall page), and
    those
    > > are the ones used by Xen today. We should extend those leaves (e.g.
    > > starting from 0x4000_0003) for the vmm-independent features as well.
    > >
    > > If Xen needs additional Xen-specific features, we need to allocate
    some
    > > leaves for those (e.g. 0x4000_1000)
    >
    > But the signature is "XenVMMXenVMM", which isn't very generic. If
    we're
    > presenting a generic interface, it needs to have a generic signature,
    > otherwise guests will need to have a list of all hypervisor signatures
    > supporting their interface. Since 0x40000000 has already been
    > established as the base leaf of the hypervisor-specific interfaces,
    the
    > generic interface will have to be elsewhere.

    The hypervisor detection machanism is generic, and the signature
    returned is implentation specific. Having a list of all hypervisor
    signatures sounds fine to me as we are detecting vendor-specific
    processor(s) in the native. And I don't expect the list is large.

    >
    > J

    Jun
    ---
    Intel Open Source Technology Center
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2007-09-15 03:07    [W:4.435 / U:0.008 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site