From: Paolo Bonzini <pbonzini@redhat.com>
To: Vitaly Kuznetsov <vkuznets@redhat.com>, qemu-devel@nongnu.org
Cc: Eduardo Habkost <ehabkost@redhat.com>,
kvm@vger.kernel.org, Marcelo Tosatti <mtosatti@redhat.com>,
Liran Alon <liran.alon@oracle.com>,
Roman Kagan <rkagan@virtuozzo.com>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [PATCH RFC] target/i386: filter out VMX_PIN_BASED_POSTED_INTR when enabling SynIC
Date: Tue, 18 Feb 2020 17:13:26 +0100 [thread overview]
Message-ID: <9b4b46c2-e2cf-a3d5-70e4-c8772bf6734f@redhat.com> (raw)
In-Reply-To: <20200218144415.94722-1-vkuznets@redhat.com>
On 18/02/20 15:44, Vitaly Kuznetsov wrote:
> Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
> ---
> RFC: This is somewhat similar to eVMCS breakage and it is likely possible
> to fix this in KVM. I decided to try QEMU first as this is a single
> control and unlike eVMCS we don't need to keep a list of things to disable.
I think you should disable "virtual-interrupt delivery" instead (which
in turn requires "process posted interrupts" to be zero). That is the
one that is incompatible with AutoEOI interrupts.
The ugly part about fixing this in QEMU is that in theory it would be
still possible to emulate virtual interrupt delivery and posted
interrupts, because they operate on a completely disjoint APIC
configuration than the host's. I'm not sure we want to go there though,
so I'm thinking that again a KVM implementation is better. It
acknowledges that this is just a limitation (workaround for a bug) in KVM.
Paolo
next prev parent reply other threads:[~2020-02-18 16:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-18 14:44 [PATCH RFC] target/i386: filter out VMX_PIN_BASED_POSTED_INTR when enabling SynIC Vitaly Kuznetsov
2020-02-18 16:13 ` Paolo Bonzini [this message]
2020-02-18 17:08 ` Vitaly Kuznetsov
2020-02-18 17:47 ` Paolo Bonzini
2020-02-19 9:54 ` Vitaly Kuznetsov
2020-02-18 16:56 ` no-reply
2020-02-18 17:14 ` Vitaly Kuznetsov
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=9b4b46c2-e2cf-a3d5-70e4-c8772bf6734f@redhat.com \
--to=pbonzini@redhat.com \
--cc=ehabkost@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=liran.alon@oracle.com \
--cc=mtosatti@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rkagan@virtuozzo.com \
--cc=rth@twiddle.net \
--cc=vkuznets@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;
as well as URLs for NNTP newsgroup(s).