From: Yan Zhao <yan.y.zhao@intel.com>
To: Sean Christopherson <seanjc@google.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>, <kvm@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, Peter Xu <peterx@redhat.com>,
Maxim Levitsky <mlevitsk@redhat.com>
Subject: Re: [PATCH 0/5] KVM: Dirty ring fixes and cleanups
Date: Mon, 13 Jan 2025 17:51:20 +0800 [thread overview]
Message-ID: <Z4TiGLp/91vJjZh9@yzhao56-desk.sh.intel.com> (raw)
In-Reply-To: <20250111010409.1252942-1-seanjc@google.com>
On Fri, Jan 10, 2025 at 05:04:04PM -0800, Sean Christopherson wrote:
> Yan's series to fix a flaw where a buggy/malicious userspace could coerce
> KVM into corrupting TDX SPTEs
> [*] https://lore.kernel.org/all/20241220082027.15851-1-yan.y.zhao@intel.com
Hi Sean,
Here's the v2
https://lore.kernel.org/kvm/20241223070427.29583-1-yan.y.zhao@intel.com.
FYI, in case you didn't catch it as it was sent close to Christmas :)
Thanks
Yan
prev parent reply other threads:[~2025-01-13 9:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-11 1:04 Sean Christopherson
2025-01-11 1:04 ` [PATCH 1/5] KVM: Bound the number of dirty ring entries in a single reset at INT_MAX Sean Christopherson
2025-01-13 6:48 ` Yan Zhao
2025-01-13 6:57 ` Yan Zhao
2025-01-11 1:04 ` [PATCH 2/5] KVM: Bail from the dirty ring reset flow if a signal is pending Sean Christopherson
2025-01-13 9:31 ` Yan Zhao
2025-01-13 15:48 ` Sean Christopherson
2025-01-14 7:29 ` Yan Zhao
2025-01-14 17:16 ` Sean Christopherson
2025-01-11 1:04 ` [PATCH 3/5] KVM: Conditionally reschedule when resetting the dirty ring Sean Christopherson
2025-01-13 7:04 ` Yan Zhao
2025-01-13 16:28 ` Sean Christopherson
2025-01-14 7:58 ` Yan Zhao
2025-01-11 1:04 ` [PATCH 4/5] KVM: Check for empty mask of harvested dirty ring entries in caller Sean Christopherson
2025-01-13 10:30 ` Yan Zhao
2025-01-13 16:48 ` Sean Christopherson
2025-01-14 8:13 ` Yan Zhao
2025-01-11 1:04 ` [PATCH 5/5] KVM: Use mask of harvested dirty ring entries to coalesce dirty ring resets Sean Christopherson
2025-01-13 9:51 ` Yan Zhao [this message]
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=Z4TiGLp/91vJjZh9@yzhao56-desk.sh.intel.com \
--to=yan.y.zhao@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mlevitsk@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=seanjc@google.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®