From: Sean Christopherson <seanjc@google.com>
To: kvm@vger.kernel.org, vasant.hegde@amd.com,
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] Print names of apicv inhibit reasons in traces
Date: Wed, 5 Jun 2024 08:10:04 -0700 [thread overview]
Message-ID: <ZmB_zGGqhwMh2jOH@google.com> (raw)
In-Reply-To: <171754374489.2780783.15684128983475310982.b4-ty@google.com>
On Tue, Jun 04, 2024, Sean Christopherson wrote:
> On Mon, 06 May 2024 22:53:19 +0000, Alejandro Jimenez wrote:
> > v2:
> > - Use Sean's implementation/patch from v1: https://lore.kernel.org/all/ZjVQOFLXWrZvoa-Y@google.com/
> > - Fix typo in commit message (s/inhbit/inhibit).
> > - Add patch renaming APICV_INHIBIT_REASON_DISABLE to APICV_INHIBIT_REASON_DISABLED.
> > - Drop Vasant's R-b from v1 since implementation was refined, even though the
> > general approach and behavior remains the same.
> >
> > [...]
>
> Applied to kvm-x86 misc, thanks!
>
> [1/2] KVM: x86: Print names of apicv inhibit reasons in traces
> https://github.com/kvm-x86/linux/commit/8b5bf6b80eb3
> [2/2] KVM: x86: Keep consistent naming for APICv/AVIC inhibit reasons
> https://github.com/kvm-x86/linux/commit/f9979c52eb02
FYI, hashes changed due to dropping an unrelated commit.
[1/2] KVM: x86: Print names of apicv inhibit reasons in traces
https://github.com/kvm-x86/linux/commit/69148ccec679
[2/2] KVM: x86: Keep consistent naming for APICv/AVIC inhibit reasons
https://github.com/kvm-x86/linux/commit/f992572120fb
prev parent reply other threads:[~2024-06-05 15:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-06 22:53 [PATCH v2 0/2] Print names of apicv inhibit reasons in traces Alejandro Jimenez
2024-05-06 22:53 ` [PATCH v2 1/2] KVM: x86: " Alejandro Jimenez
2024-05-08 11:20 ` Vasant Hegde
2024-05-06 22:53 ` [PATCH v2 2/2] KVM: x86: Keep consistent naming for APICv/AVIC inhibit reasons Alejandro Jimenez
2024-06-04 23:29 ` [PATCH v2 0/2] Print names of apicv inhibit reasons in traces Sean Christopherson
2024-06-05 15:10 ` 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=ZmB_zGGqhwMh2jOH@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 \
--cc=vasant.hegde@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