From: Sean Christopherson <seanjc@google.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [PATCH 0/7] KVM: SEV fixes for 6.9
Date: Mon, 18 Mar 2024 15:58:49 -0700 [thread overview]
Message-ID: <ZfjHKdx3PNqQfkne@google.com> (raw)
In-Reply-To: <20240318221002.2712738-1-pbonzini@redhat.com>
On Mon, Mar 18, 2024, Paolo Bonzini wrote:
> A small bugfix and documentation extract of my SEV_INIT2 series, plus
> 4 patches from Ashish and Sean that I thought would be in the 6.9 pull
> requests.
Heh, they were in the 6.9 pull requests, but I sent the SVM PR early[1]. Looks
like another small PR for an async #PF ABI cleanup[2] got missed too.
[1] https://lore.kernel.org/all/20240227192451.3792233-1-seanjc@google.com
[2] https://lore.kernel.org/all/20240223211621.3348855-3-seanjc@google.com
next prev parent reply other threads:[~2024-03-18 22:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-18 22:09 Paolo Bonzini
2024-03-18 22:09 ` [PATCH 1/7] KVM: SVM: Set sev->asid in sev_asid_new() instead of overloading the return Paolo Bonzini
2024-03-18 22:09 ` [PATCH 2/7] KVM: SVM: Use unsigned integers when dealing with ASIDs Paolo Bonzini
2024-03-18 22:09 ` [PATCH 3/7] KVM: SVM: Add support for allowing zero SEV ASIDs Paolo Bonzini
2024-03-18 22:09 ` [PATCH 4/7] KVM: SVM: Return -EINVAL instead of -EBUSY on attempt to re-init SEV/SEV-ES Paolo Bonzini
2024-03-18 22:10 ` [PATCH 5/7] KVM: SEV: fix compat ABI for KVM_MEMORY_ENCRYPT_OP Paolo Bonzini
2024-03-18 22:10 ` [PATCH 6/7] Documentation: kvm/sev: separate description of firmware Paolo Bonzini
2024-03-18 22:10 ` [PATCH 7/7] Documentation: kvm/sev: clarify usage of KVM_MEMORY_ENCRYPT_OP Paolo Bonzini
2024-03-18 22:58 ` Sean Christopherson [this message]
2024-03-18 23:04 ` [PATCH 0/7] KVM: SEV fixes for 6.9 Paolo Bonzini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZfjHKdx3PNqQfkne@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®