From: Paolo Bonzini <pbonzini@redhat.com>
To: zhenwei pi <pizhenwei@bytedance.com>,
Maxim Levitsky <mlevitsk@redhat.com>,
Kele Huang <huangkele@bytedance.com>
Cc: chaiwen.cc@bytedance.com, xieyongji@bytedance.com,
dengliang.1214@bytedance.com, wanpengli@tencent.com,
seanjc@google.com, Vitaly Kuznetsov <vkuznets@redhat.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>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC] KVM: x86: SVM: don't expose PV_SEND_IPI feature with AVIC
Date: Mon, 8 Nov 2021 12:18:11 +0100 [thread overview]
Message-ID: <c3c84251-44b0-cff1-9607-b3686f1196b0@redhat.com> (raw)
In-Reply-To: <ad6b3ef5-4928-681c-a0cf-5a1095654566@bytedance.com>
On 11/8/21 12:14, zhenwei pi wrote:
> I don't yet know if there is a solution to this which doesn't
> involve some management software decision (e.g libvirt or higher).
If we use a new hint, there's no problems with migration from/to older
QEMU and libvirt's host-model/host-passthrough would pick up the bit
automatically.
(I'm not sure if libvirt knows that hints can change across migration,
though).
Paolo
next prev parent reply other threads:[~2021-11-08 11:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-08 9:59 Kele Huang
2021-11-08 10:30 ` Paolo Bonzini
2021-11-08 11:08 ` Maxim Levitsky
2021-11-08 11:14 ` zhenwei pi
2021-11-08 11:18 ` Paolo Bonzini [this message]
2021-11-16 2:48 ` Wanpeng Li
2021-11-16 2:56 ` zhenwei pi
2021-11-16 9:06 ` Chao Gao
2021-11-16 9:30 ` [External] " 黄科乐
2021-11-16 9:30 ` Wanpeng Li
[not found] ` <CAKUug92xp7mU_KB66jGtdYRhgQpgfCm67r+3kMOMdbrGOrTQcA@mail.gmail.com>
2021-11-16 15:57 ` [External] " Sean Christopherson
2021-11-08 10:45 ` Vitaly Kuznetsov
2021-11-16 2:04 ` Wanpeng Li
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=c3c84251-44b0-cff1-9607-b3686f1196b0@redhat.com \
--to=pbonzini@redhat.com \
--cc=bp@alien8.de \
--cc=chaiwen.cc@bytedance.com \
--cc=dave.hansen@linux.intel.com \
--cc=dengliang.1214@bytedance.com \
--cc=hpa@zytor.com \
--cc=huangkele@bytedance.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=pizhenwei@bytedance.com \
--cc=seanjc@google.com \
--cc=tglx@linutronix.de \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
--cc=x86@kernel.org \
--cc=xieyongji@bytedance.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®