On Tue, Jul 20, 2021, Brijesh Singh wrote:
>
> On 7/19/21 5:50 PM, Sean Christopherson wrote:
> ...
> >
> > IIUC, this snippet in the spec means KVM can't restrict what requests are made
> > by the guests. If so, that makes it difficult to detect/ratelimit a misbehaving
> > guest, and also limits our options if there are firmware issues (hopefully there
> > aren't). E.g. ratelimiting a guest after KVM has explicitly requested it to
> > migrate is not exactly desirable.
> >
>
> The guest message page contains a message header followed by the encrypted
> payload. So, technically KVM can peek into the message header format to
> determine the message request type. If needed, we can ratelimit based on the
> message type.
Ah, I got confused by this code in snp_build_guest_buf():
data->req_paddr = __sme_set(req_pfn << PAGE_SHIFT);
I was thinking that setting the C-bit meant the memory was guest private, but
that's setting the C-bit for the HPA, which is correct since KVM installs guest
memory with C-bit=1 in the NPT, i.e. encrypts shared memory with the host key.
Tangetially related question, is it correct to say that the host can _read_ memory
from a page that is assigned=1, but has asid=0? I.e. KVM can read the response
page in order to copy it into the guest, even though it is a firmware page?
/* Copy the response after the firmware returns success. */
rc = kvm_write_guest(kvm, resp_gpa, sev->snp_resp_page, PAGE_SIZE);
> In the current series we don't support migration etc so I decided to
> ratelimit unconditionally.
Since KVM can peek at the request header, KVM should flat out disallow requests
that KVM doesn't explicitly support. E.g. migration requests should not be sent
to the PSP.
One concern though: How does the guest query what requests are supported? This
snippet implies there's some form of enumeration:
Note: This guest message may be removed in future versions as it is redundant
with the CPUID page in SNP_LAUNCH_UPDATE (see Section 8.14).
But all I can find is a "Message Version" in "Table 94. Message Type Encodings",
which implies that request support is all or nothing for a given version. That
would be rather unfortunate as KVM has no way to tell the guest that something
is unsupported :-(
> > Is this exposed to userspace in any way? This feels very much like a knob that
> > needs to be configurable per-VM.
>
> It's not exposed to the userspace and I am not sure if userspace care about
> this knob.
Userspace definitely cares, otherwise the system would need to be rebooted just to
tune the ratelimiting. And userspace may want to disable ratelimiting entirely,
e.g. if the entire system is dedicated to a single VM.
> > Also, what are the estimated latencies of a guest request? If the worst case
> > latency is >200ms, a default ratelimit frequency of 5hz isn't going to do a whole
> > lot.
> >
>
> The latency will depend on what else is going in the system at the time the
> request comes to the hypervisor. Access to the PSP is serialized so other
> parallel PSP command execution will contribute to the latency.
I get that it will be variable, but what are some ballpark latencies? E.g. what's
the latency of the slowest command without PSP contention?
> > Question on the VMPCK sequences. The firmware ABI says:
> >
> > Each guest has four VMPCKs ... Each message contains a sequence number per
> > VMPCK. The sequence number is incremented with each message sent. Messages
> > sent by the guest to the firmware and by the firmware to the guest must be
> > delivered in order. If not, the firmware will reject subsequent messages ...
> >
> > Does that mean there are four independent sequences, i.e. four streams the guest
> > can use "concurrently", or does it mean the overall freshess/integrity check is
> > composed from four VMPCK sequences, all of which must be correct for the message
> > to be valid?
> >
>
> There are four independent sequence counter and in theory guest can use them
> concurrently. But the access to the PSP must be serialized.
Technically that's not required from the guest's perspective, correct? The guest
only cares about the sequence numbers for a given VMPCK, e.g. it can have one
in-flight request per VMPCK and expect that to work, even without fully serializing
its own requests.
Out of curiosity, why 4 VMPCKs? It seems completely arbitrary.
> Currently, the guest driver uses the VMPCK0 key to communicate with the PSP.
>
>
> > If it's the latter, then a traditional mutex isn't really necessary because the
> > guest must implement its own serialization, e.g. it's own mutex or whatever, to
> > ensure there is at most one request in-flight at any given time.
>
> The guest driver uses the its own serialization to ensure that there is
> *exactly* one request in-flight.
But KVM can't rely on that because it doesn't control the guest, e.g. it may be
running a non-Linux guest.
> The mutex used here is to protect the KVM's internal firmware response
> buffer.
Ya, where I was going with my question was that if the guest was architecturally
restricted to a single in-flight request, then KVM could do something like this
instead of taking kvm->lock (bad pseudocode):
if (test_and_set(sev->guest_request)) {
rc = AEAD_OFLOW;
goto fail;
}
<do request>
clear_bit(...)
I.e. multiple in-flight requests can't work because the guest can guarantee
ordering between vCPUs. But, because the guest can theoretically have up to four
in-flight requests, it's not that simple.
The reason I'm going down this path is that taking kvm->lock inside vcpu->mutex
violates KVM's locking rules, i.e. is susceptibl to deadlocks. Per kvm/locking.rst,
- kvm->lock is taken outside vcpu->mutex
That means a different mutex is needed to protect the guest request pages.
> > And on the KVM side it means KVM can simpy reject requests if there is
> > already an in-flight request. It might also give us more/better options
> > for ratelimiting?
>
> I don't think we should be running into this scenario unless there is a bug
> in the guest kernel. The guest kernel support and CCP driver both ensure
> that request to the PSP is serialized.
Again, what the Linux kernel does is irrelevant. What matters is what is
architecturally allowed.
> In normal operation we may see 1 to 2 quest requests for the entire guest
> lifetime. I am thinking first request maybe for the attestation report and
> second maybe to derive keys etc. It may change slightly when we add the
> migration command; I have not looked into a great detail yet.
