lkml.org 
[lkml]   [2020]   [Apr]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [PATCH 3/4] x86,module: Detect VMX vs SLD conflicts
From
Date
On 08/04/2020 10:56, Peter Zijlstra wrote:
>>> + case 0xc1: /* VMCALL */
>>> + case 0xc2: /* VMLAUNCH */
>>> + case 0xc3: /* VMRESUME */
>>> + case 0xc4: /* VMXOFF */
>> case 0xd4: /* VMFUNC */
> As per Andrew, VMCALL and VMFUNC are SMV, and I really only need VMX in
> this case. Including SMV is probably harmless, but I'm thinking a
> smaller function is better.

VMCALL and VMFUNC are both VMX instructions.  VMMCALL (count the M's -
yes it is a different instruction) is SVM, and I forgot VMGEXIT from the
list yesterday which is also SVM.

However, searching for them is probably not helpful.  They are all
guest-only instructions and you wouldn't expect to see them in
hypervisor code.

~Andrew

\
 
 \ /
  Last update: 2020-04-08 12:15    [W:0.331 / U:0.828 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site