From: Sean Christopherson <seanjc@google.com>
To: Sean Christopherson <seanjc@google.com>,
kvm@vger.kernel.org,
Alejandro Jimenez <alejandro.j.jimenez@oracle.com>
Cc: pbonzini@redhat.com, linux-kernel@vger.kernel.org,
joao.m.martins@oracle.com, boris.ostrovsky@oracle.com,
suravee.suthikulpanit@amd.com, mlevitsk@redhat.com
Subject: Re: [PATCH v2 0/2] APICv-related fixes for inhibits and tracepoint
Date: Fri, 3 May 2024 14:32:14 -0700 [thread overview]
Message-ID: <171469178174.1010245.3908365461241095071.b4-ty@google.com> (raw)
In-Reply-To: <20240418021823.1275276-1-alejandro.j.jimenez@oracle.com>
On Thu, 18 Apr 2024 02:18:21 +0000, Alejandro Jimenez wrote:
> v2: Add Sean's changes to [PATCH 1/2].
>
> --
>
> Patch 1 fixes an issue when avic=0 (current default) where
> APICV_INHIBIT_REASON_ABSENT remains set even after an in-kernel local APIC has
> been created. e.g. tracing the inhibition tracepoint shows:
>
> [...]
Applied to kvm-x86 misc, with the previously mentioned fixups, thanks!
[1/2] KVM: x86: Only set APICV_INHIBIT_REASON_ABSENT if APICv is enabled
https://github.com/kvm-x86/linux/commit/6982b34c21cb
[2/2] KVM: x86: Remove VT-d mention in posted interrupt tracepoint
https://github.com/kvm-x86/linux/commit/51937f2aae18
--
https://github.com/kvm-x86/linux/tree/next
prev parent reply other threads:[~2024-05-03 21:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-18 2:18 [PATCH v2 0/2] APICv-related fixes for inhibits and tracepoint Alejandro Jimenez
2024-04-18 2:18 ` [PATCH v2 1/2] KVM: x86: Only set APICV_INHIBIT_REASON_ABSENT if APICv is enabled Alejandro Jimenez
2024-05-02 23:21 ` Sean Christopherson
2024-04-18 2:18 ` [PATCH v2 2/2] KVM: x86: Remove VT-d mention in posted interrupt tracepoint Alejandro Jimenez
2024-05-03 21:32 ` 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=171469178174.1010245.3908365461241095071.b4-ty@google.com \
--to=seanjc@google.com \
--cc=alejandro.j.jimenez@oracle.com \
--cc=boris.ostrovsky@oracle.com \
--cc=joao.m.martins@oracle.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mlevitsk@redhat.com \
--cc=pbonzini@redhat.com \
--cc=suravee.suthikulpanit@amd.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 read-only IMAP folder(s) and NNTP newsgroup(s).