From: Sean Christopherson <seanjc@google.com>
To: Manali Shukla <manali.shukla@amd.com>
Cc: kvm@vger.kernel.org, linux-kselftest@vger.kernel.org,
pbonzini@redhat.com, nikunj@amd.com, bp@alien8.de
Subject: Re: [PATCH v5 0/5] Add support for the Bus Lock Threshold
Date: Fri, 16 May 2025 12:01:04 -0700 [thread overview]
Message-ID: <aCeLcLiioNJYXhRh@google.com> (raw)
In-Reply-To: <ff1f0e75-a13c-4f6f-82db-94dc600d6367@amd.com>
On Mon, May 12, 2025, Manali Shukla wrote:
> A gentle reminder to review patches
(a) Trim your replies.
(b) Don't do whatever you did that generated 8 bajillion "prerequisite-patch-id"
lines, which causes b4 to barf.
next prev parent reply other threads:[~2025-05-16 19:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-02 5:03 [PATCH v5 0/5] Add support for the Bus Lock Threshold Manali Shukla
2025-05-02 5:03 ` [PATCH v5 1/5] KVM: x86: Make kvm_pio_request.linear_rip a common field for user exits Manali Shukla
2025-05-02 5:03 ` [PATCH v5 2/5] x86/cpufeatures: Add CPUID feature bit for the Bus Lock Threshold Manali Shukla
2025-05-12 10:46 ` Borislav Petkov
2025-05-02 5:03 ` [PATCH v5 3/5] KVM: SVM: Enable Bus lock threshold exit Manali Shukla
2025-05-02 5:03 ` [PATCH v5 4/5] KVM: SVM: Add support for KVM_CAP_X86_BUS_LOCK_EXIT on SVM CPUs Manali Shukla
2025-05-17 16:46 ` ALOK TIWARI
2025-05-02 5:03 ` [PATCH v5 5/5] KVM: selftests: Add bus lock exit test Manali Shukla
2025-05-16 19:28 ` Sean Christopherson
2025-05-19 11:45 ` Manali Shukla
2025-05-12 4:47 ` [PATCH v5 0/5] Add support for the Bus Lock Threshold Manali Shukla
2025-05-16 19:01 ` Sean Christopherson [this message]
2025-05-19 11:39 ` Manali Shukla
2025-05-20 16:48 ` Sean Christopherson
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=aCeLcLiioNJYXhRh@google.com \
--to=seanjc@google.com \
--cc=bp@alien8.de \
--cc=kvm@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=manali.shukla@amd.com \
--cc=nikunj@amd.com \
--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;
as well as URLs for NNTP newsgroup(s).