From: Sean Christopherson <seanjc@google.com>
To: Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Manali Shukla <Manali.Shukla@amd.com>
Subject: Re: [PATCH] KVM: selftests: Add helpers for locally (un)blocking IRQs on x86
Date: Thu, 9 Jan 2025 11:47:15 -0800 [thread overview]
Message-ID: <173645120539.885681.9004596567911167052.b4-ty@google.com> (raw)
In-Reply-To: <20241220012617.3513898-1-seanjc@google.com>
On Thu, 19 Dec 2024 17:26:17 -0800, Sean Christopherson wrote:
> Copy KVM-Unit-Tests' x86 helpers for emitting STI and CLI, comments and
> all, and use them throughout x86 selftests. The safe_halt() and sti_nop()
> logic in particular benefits from centralized comments, as the behavior
> isn't obvious unless the reader is already aware of the STI shadow.
Applied to kvm-x86 selftests, thanks!
[1/1] KVM: selftests: Add helpers for locally (un)blocking IRQs on x86
https://github.com/kvm-x86/linux/commit/983820cb53c0
--
https://github.com/kvm-x86/linux/tree/next
prev parent reply other threads:[~2025-01-09 19:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-20 1:26 Sean Christopherson
2025-01-09 19:47 ` Sean Christopherson [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=173645120539.885681.9004596567911167052.b4-ty@google.com \
--to=seanjc@google.com \
--cc=Manali.Shukla@amd.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®