Re: [PATCH 1/7] hyperv: Detect Nested virtualization support for SVM

[Vineeth Pillai]

On 4/8/21 11:24 AM, Sean Christopherson wrote:
> Technically, you can use normal memory accesses, so long as software guarantees
> the VMCS isn't resident in the VMCS cache and knows the field offsets for the
> underlying CPU.  The lack of an architecturally defined layout is the biggest
> issue, e.g. tacking on dirty bits through a PV ABI would be trivial.
>
> > Yes, you are right. I was referring to the fact that we cant use normal
> > memory accesses, but is a bit mis-worded.
> If you slot in "architectural" it will read nicely, i.e. "VMCB is already an
> architectural datastructure in memory".
Yes, this makes sense. Thanks for the suggestion, will reword as you
suggested.

Thanks,
Vineeth