From: Sean Christopherson <seanjc@google.com>
To: Zeng Guang <guang.zeng@intel.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Maxim Levitsky <mlevitsk@redhat.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Wanpeng Li <wanpengli@tencent.com>,
Jim Mattson <jmattson@google.com>, Joerg Roedel <joro@8bytes.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H . Peter Anvin" <hpa@zytor.com>,
kvm@vger.kernel.org, x86@kernel.org,
linux-kernel@vger.kernel.org, Gao Chao <chao.gao@intel.com>
Subject: Re: [PATCH] KVM: x86: Inhibit APICv/AVIC when changing apic id/base from the defaults
Date: Fri, 20 May 2022 15:26:20 +0000 [thread overview]
Message-ID: <YoezHLoQ3J2mjv1n@google.com> (raw)
In-Reply-To: <20220520144656.25579-1-guang.zeng@intel.com>
On Fri, May 20, 2022, Zeng Guang wrote:
> From: Maxim Levitsky <mlevitsk@redhat.com>
>
> Neither of these settings should be changed by the guest and it is a burden
> to support it in the acceleration code, so just inhibit APICv/AVIC in case
> such rare cases happen.
>
> Signed-off-by: Maxim Levitsky <mlevitsk@redhat.com>
> Signed-off-by: Zeng Guang <guang.zeng@intel.com>
> ---
All of my comments on Maxim's posting still apply[*]. At this point, unless Paolo
wants wield his hammer of authority and do a bunch of fixup, the fastest way forward
will be to wait for Maxim to respond and post patches 1-3 of that series separately.
[*] https://lore.kernel.org/all/YoZrG3n5fgMp4LQl@google.com
prev parent reply other threads:[~2022-05-20 15:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-20 14:46 [PATCH] KVM: x86: Inhibit APICv/AVIC when changing apic id/base from the defaults Zeng Guang
2022-05-20 15:26 ` 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=YoezHLoQ3J2mjv1n@google.com \
--to=seanjc@google.com \
--cc=bp@alien8.de \
--cc=chao.gao@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=guang.zeng@intel.com \
--cc=hpa@zytor.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mlevitsk@redhat.com \
--cc=pbonzini@redhat.com \
--cc=tglx@linutronix.de \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
--cc=x86@kernel.org \
/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