From: Paolo Bonzini <pbonzini@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>, qemu-devel@nongnu.org
Cc: Sergio Lopez <slp@redhat.com>,
kvm@vger.kernel.org, "Michael S. Tsirkin" <mst@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [PATCH 0/3] i386/kvm: Assume IRQ routing is always available
Date: Wed, 23 Sep 2020 14:43:24 +0200 [thread overview]
Message-ID: <68fe355a-10de-0810-f001-46a4f9d8f3f2@redhat.com> (raw)
In-Reply-To: <20200922201922.2153598-1-ehabkost@redhat.com>
On 22/09/20 22:19, Eduardo Habkost wrote:
> KVM_CAP_IRQ_ROUTING is available since 2019 (Linux v2.6.30), so
> we can safely assume it's always present and remove some runtime
> checks.
>
> Eduardo Habkost (3):
> i386/kvm: Require KVM_CAP_IRQ_ROUTING
> i386/kvm: Remove IRQ routing support checks
> i386/kvm: Delete kvm_allows_irq0_override()
>
> target/i386/kvm_i386.h | 1 -
> hw/i386/fw_cfg.c | 2 +-
> hw/i386/kvm/apic.c | 5 ++---
> hw/i386/kvm/ioapic.c | 33 ++++++++++++++++-----------------
> hw/i386/microvm.c | 2 +-
> hw/i386/pc.c | 2 +-
> target/i386/kvm-stub.c | 5 -----
> target/i386/kvm.c | 17 +++++------------
> 8 files changed, 26 insertions(+), 41 deletions(-)
>
Acked-by: Paolo Bonzini <pbonzini@redhat.com>
prev parent reply other threads:[~2020-09-23 12:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-22 20:19 [PATCH 0/3] i386/kvm: Assume IRQ routing is always available Eduardo Habkost
2020-09-22 20:19 ` [PATCH 1/3] i386/kvm: Require KVM_CAP_IRQ_ROUTING Eduardo Habkost
2020-09-22 20:19 ` [PATCH 2/3] i386/kvm: Remove IRQ routing support checks Eduardo Habkost
2020-09-22 20:19 ` [PATCH 3/3] i386/kvm: Delete kvm_allows_irq0_override() Eduardo Habkost
2020-09-23 12:43 ` Paolo Bonzini [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=68fe355a-10de-0810-f001-46a4f9d8f3f2@redhat.com \
--to=pbonzini@redhat.com \
--cc=ehabkost@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=mtosatti@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=slp@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).