lkml.org 
[lkml]   [2014]   [Apr]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [visorchipset] invalid opcode: 0000 [#1] PREEMPT SMP
    On 04/09/2014 04:01 PM, Fengguang Wu wrote:
    > CC the KVM people: it looks like a KVM problem that can be triggered by
    >
    > qemu-system-x86_64 -cpu Haswell,+smep,+smap

    I'm really confused. First of all, is this a KVM problem or is it a
    Qemu JIT problem?

    Either seems really wonky. It is questionable at best whether or not
    Qemu in JIT mode should set the hypervisor bit IMO. However, even so,
    you *better* not call VMCALL *just* because the hypervisor bit is set.

    The reason for it is that you have absolutely no idea what VMCALL is
    going to do on any one hypervisor... different hypervisors even use
    completely different conventions for VMCALL, and some might not accept
    VMCALL at all and might just terminate your guest with extreme prejudice.

    So what is actually going on here?

    -hpa



    \
     
     \ /
      Last update: 2014-04-10 01:41    [W:6.722 / U:0.008 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site