lkml.org 
[lkml]   [2006]   [Mar]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [RFC, PATCH 1/24] i386 Vmi documentation
    * Andi Kleen (ak@suse.de) wrote:
    > On Monday 13 March 2006 18:59, Zachary Amsden wrote:
    >
    > > + The general mechanism for providing customized features and
    > > + capabilities is to provide notification of these feature through
    > > + the CPUID call,
    >
    > How should that work since CPUID cannot be intercepted by
    > a Hypervisor (without VMX/SVM)?

    Yeah, it requires guest kernel cooperation/modification.

    > > + The net result of these choices is that most of the calls are very
    > > + easy to make from C-code, and calls that are likely to be required in
    > > + low level trap handling code are easy to call from assembler. Most
    > > + of these calls are also very easily implemented by the hypervisor
    > > + vendor in C code, and only the performance critical calls from
    > > + assembler paths require custom assembly implementations.
    > > +
    > > + CORE INTERFACE CALLS
    >
    > Did I miss it or do you never describe how to find these entry points?

    It's the ROM interface. For native they are emitted directly inline.
    For non-native, they are emitted as call stubs, which call to the ROM.
    I don't recall if it's in this doc, but the inline patch has all the
    gory details.

    thanks,
    -chris
    -
    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: 2006-03-22 22:37    [W:2.389 / U:0.360 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site