On Mon, May 13, 2024 at 04:48:25PM -0700, Sean Christopherson wrote:
> On Wed, May 01, 2024, Michael Roth wrote:
> > Version 2 of GHCB specification added support for the SNP Extended Guest
> > Request Message NAE event. This event serves a nearly identical purpose
> > to the previously-added SNP_GUEST_REQUEST event, but allows for
> > additional certificate data to be supplied via an additional
> > guest-supplied buffer to be used mainly for verifying the signature of
> > an attestation report as returned by firmware.
> >
> > This certificate data is supplied by userspace, so unlike with
> > SNP_GUEST_REQUEST events, SNP_EXTENDED_GUEST_REQUEST events are first
> > forwarded to userspace via a KVM_EXIT_VMGEXIT exit structure, and then
> > the firmware request is made after the certificate data has been fetched
> > from userspace.
> >
> > Since there is a potential for race conditions where the
> > userspace-supplied certificate data may be out-of-sync relative to the
> > reported TCB or VLEK that firmware will use when signing attestation
> > reports, a hook is also provided so that userspace can be informed once
> > the attestation request is actually completed. See the updates to
> > Documentation/ for more details on these aspects.
> >
> > Signed-off-by: Michael Roth <michael.roth@xxxxxxx>
> > ---
> > Documentation/virt/kvm/api.rst | 87 ++++++++++++++++++++++++++++++++++
> > arch/x86/kvm/svm/sev.c | 86 +++++++++++++++++++++++++++++++++
> > arch/x86/kvm/svm/svm.h | 3 ++
> > include/uapi/linux/kvm.h | 23 +++++++++
> > 4 files changed, 199 insertions(+)
> >
> > diff --git a/Documentation/virt/kvm/api.rst b/Documentation/virt/kvm/api.rst
> > index f0b76ff5030d..f3780ac98d56 100644
> > --- a/Documentation/virt/kvm/api.rst
> > +++ b/Documentation/virt/kvm/api.rst
> > @@ -7060,6 +7060,93 @@ Please note that the kernel is allowed to use the kvm_run structure as the
> > primary storage for certain register types. Therefore, the kernel may use the
> > values in kvm_run even if the corresponding bit in kvm_dirty_regs is not set.
> >
> > +::
> > +
> > + /* KVM_EXIT_VMGEXIT */
> > + struct kvm_user_vmgexit {
>
> LOL, it looks dumb, but maybe kvm_vmgexit_exit to avoid confusing about whether
> the struct refers to host userspace vs. guest userspace?
>
> Actually, I vote to punt on naming until more exits need to be kicked to userspace,
> and just do (see below for details on how I got here):
>
> /* KVM_EXIT_VMGEXIT */
> struct {
> __u64 exit_code;
> union {
> struct {
> __u64 data_gpa;
> __u64 data_npages;
> __u64 ret;
> } req_certs;
> };
> } vmgexit;
>
> > + #define KVM_USER_VMGEXIT_REQ_CERTS 1
> > + __u32 type; /* KVM_USER_VMGEXIT_* type */
>
> Regardless of whether or not requesting a certificate is vendor specific enough
> to justify its own exit reason, I don't think KVM should have a #VMGEXIT that
> adds its own layer. Structuring the user exit this way will make it weird and/or
> difficult to handle #VMGEXITs that _do_ fit a generic pattern, e.g. a user might
> wonder why PSC #VMGEXITs don't show up here.
>
> And defining an exit reason that is, for all intents and purposes, a regurgitation
> of the raw #VMGEXIT reason, but with a different value, is also confusing. E.g.
> it wouldn't be unreasonable for a reader to expect that "type" matches the value
> defined in the GHCB (or whever the values are defined).
The type in this case is actually "extended guest request". You'd rightly
pointed out that that is miles away from describing what KVM wants
userspace to do, so I named it "request certificate". And now with PSC being
handled as seperate KVM_HC_MAP_GPA_RANGE event with no exposure of GHCB/etc
to userspace, it made further sense to not lean too heavily on the GHCB for
defining the types.
But continuing to name it KVM_EXIT_VMGEXIT sort of goes against that
decoupling, so I can see some potential for confusion there. KVM_EXIT_SNP is
probably a better generic name for what this exit is meant to cover. But I'm
not aware of anything specific that would involve requiring extending this in
the near-term, though maybe there's some potential with live migration. So a
renaming to something more generic and less specific to VMGEXIT/GHCB,
like KVM_EXIT_SNP, or something more specific like KVM_EXIT_SNP_REQ_CERTS,
both seem warranted, but I don't think moving to something more coupled to
VMGEXIT/GHCB would provide much benefit long-term.
>
> Ah, you copied what KVM does for Hyper-V and Xen emulation. Hrm. But only
> partially.
>
> Assuming it's impractical to have a generic user exit for this, and we think
> there is a high likelihood of needing to punt more #VMGEXITs to userspace, then
> we should more closely (perhaps even exactly) follow the Hyper-V and Xen models.
> I.e. for all values and whanot that are controlled/defined by a third party
> (Hyper-V, Xen, the GHCB, etc.) #define those values in a header that is clearly
> "owned" by the third party.
>
> E.g. IIRC, include/xen/interface/xen.h is copied verbatim from Xen documentation
> (source?). And include/asm-generic/hyperv-tlfs.h is the kernel's copy of the
> TLFS, which dictates all of the Hyper-V hypercalls.
>
> If we do that, then my concerns/objections largely go away, e.g. KVM isn't
> defining magic values, there's less chance for confusion about what "type" holds,
> etc.
>
> Oh, and if we go that route, the sizes for all fields should follow the GHCB,
> e.g. I believe the "type" should be a __u64.
>
> > + union {
> > + struct {
> > + __u64 data_gpa;
> > + __u64 data_npages;
> > + #define KVM_USER_VMGEXIT_REQ_CERTS_ERROR_INVALID_LEN 1
> > + #define KVM_USER_VMGEXIT_REQ_CERTS_ERROR_BUSY 2
> > + #define KVM_USER_VMGEXIT_REQ_CERTS_ERROR_GENERIC (1 << 31)
>
> Hopefully it won't matter, but are BUSY and GENERIC actually defined somewhere?
> I don't see them in GHCB 2.0.
BUSY is defined in 4.1.7:
It is not expected that a guest would issue many Guest Request NAE
events. However, access to the SNP firmware is a sequential and
synchronous operation. To avoid the possibility of a guest creating a
denial-of-service attack against the SNP firmware, it is recommended
that some form of rate limiting be implemented should it be detected
that a high number of Guest Request NAE events are being issued. To
allow for this, the hypervisor may set the SW_EXITINFO2 field to
0x0000000200000000, which will inform the guest to retry the request
INVALID_LEN in 4.1.8.1:
The hypervisor must validate that the guest has supplied enough pages
to hold the certificates that will be returned before performing the SNP
guest request. If there are not enough guest pages to hold the certificate
table and certificate data, the hypervisor will return the required number
of pages needed to hold the certificate table and certificate data in the
RBX register and set the SW_EXITINFO2 field to 0x0000000100000000.
and GENERIC chosen to provide an non-zero error code that doesn't
conflict with that above (or future) GHCB-defined values. But KVM isn't
trying to expose the actual GHCB details, like how these values are to be in
the upper 32-bits of SW_EXITINFO2, it just re-uses the values to avoid
purposefully obfuscating the GHCB return codes they relate to.
>
> In a perfect world, it would be nice for KVM to not have to care about the error
> codes. But KVM disallows KVM_{G,S}ET_REGS for guest with protected state, which
> means it's not feasible for userspace to set registers, at least not in any sane
> way.
>
> Heh, we could abuse KVM_SYNC_X86_REGS to let userspace specify RBX, but (a) that's
> gross, and (b) KVM_SYNC_X86_REGS and KVM_SYNC_X86_SREGS really ought to be rejected
> if guest state is protected.
>
> > + __u32 ret;
> > + #define KVM_USER_VMGEXIT_REQ_CERTS_FLAGS_NOTIFY_DONE BIT(0)
>
> This has no business being buried in a VMGEXIT_REQ_CERTS flags. Notifying
> userspace that KVM completed its portion of a userspace exit is completely generic.
>
> And aside from where the notification flag lives, _if_ we add a notification
> mechanism, it belongs in a separate patch, because it's purely a performance
> optimization. Userspace can use immediate_exit to force KVM to re-exit after
> completing an exit.
>
> Actually, I take that back, this isn't even an optimization, it's literally a
> non-generic implementation of kvm_run.immediate_exit.
Relying on a generic -EINTR response resulting from kvm_run.immediate_exit
doesn't seem like a very robust way to ensure the attestation request
was made to firmware. It seems fully possible that future code changes
could result in EINTR being returned for other reasons. So how do you
reliably detect that the EINTR is a result of immediate_exit being called
after the attestation request is made to firmware? We could squirrel something
away in struct kvm_run to probe for, but delivering another
KVM_EXIT_SNP_REQ_CERT with an extra flag set seems to be reasonably
userspace-friendly.
>
> If this were an optimization, i.e. KVM truly notified userspace without exiting,
> then it would need to be a lot more robust, e.g. to ensure userspace actually
> received the notification before KVM moved on.
Right, this does rely on exiting via , not userspace polling for flags or
anything along that line.
>
> > + __u8 flags;
> > + #define KVM_USER_VMGEXIT_REQ_CERTS_STATUS_PENDING 0
> > + #define KVM_USER_VMGEXIT_REQ_CERTS_STATUS_DONE 1
>
> This is also a weird reimplementation of generic functionality. KVM nullifies
> vcpu->arch.complete_userspace_io _before_ invoking the callback. So if a callback
> needs to run again on the next KVM_RUN, it can simply set complete_userspace_io
> again. In other words, literally doing nothing will get you what you want :-)
We could just have the completion callback set complete_userspace_io
again, but then you'd always get 2 userspace exit events per attestation
request. There could be some userspaces that don't implement the
file-locking scheme, in which case they wouldn't need the 2nd notification.
That's why the KVM_USER_VMGEXIT_REQ_CERTS_FLAGS_NOTIFY_DONE flag is provided
as an opt-in.
The pending/done status bits are so userspace can distinguish between the
start of a certificate request and the completion side of it after it gets
bound a completed attestation request and the filelock can be released.
Thanks,
Mike
>
> > + __u8 status;
> > + } req_certs;
> > + };
> > + };
