From: Eric Auger <eric.auger@linaro.org>
To: Cornelia Huck <cornelia.huck@de.ibm.com>,
Paul Mackerras <paulus@samba.org>
Cc: kvm@vger.kernel.org, kvm-ppc@vger.kernel.org,
"Michael S. Tsirkin" <mst@redhat.com>,
Alexander Graf <agraf@suse.de>
Subject: Re: [PATCH 0/6] IRQFD without IRQ routing, enabled for XICS
Date: Thu, 24 Jul 2014 17:47:26 +0200 [thread overview]
Message-ID: <53D12A8E.6050407@linaro.org> (raw)
In-Reply-To: <20140714161842.052bb423.cornelia.huck@de.ibm.com>
Hi Paul,
I also confirm your patch works fine on my ARM test environment. I was
able to run
- with irqchip without regression
- without irqchip (ie removing routing totally), just implementing
identity kvm_irq_map_gsi and kvm_irq_map_chip_pin and proper
kvm_set_irq. The overall integration becomes much simpler :-)
Many thanks
Best Regards
Eric
On 07/14/2014 04:18 PM, Cornelia Huck wrote:
> On Mon, 30 Jun 2014 20:51:08 +1000
> Paul Mackerras <paulus@samba.org> wrote:
>
>> I would like to see this go into 3.17.
>
> FWIW: I've given this a whirl on s390 (with a dataplane disk), and
> everything seems to work as before.
>
> The only thing which is I think worth mentioning is that embedding the
> routing entry into the irqfd struct will grow it a bit, which might be
> noticable on large installations with hundreds of devices. OTOH, the
> routing entry isn't too large, so I don't think it will become a
> problem.
>
>>
>> arch/ia64/kvm/Kconfig | 1 +
>> arch/powerpc/kvm/Kconfig | 3 +
>> arch/powerpc/kvm/book3s_hv_rm_xics.c | 5 ++
>> arch/powerpc/kvm/book3s_xics.c | 55 +++++++++++---
>> arch/powerpc/kvm/book3s_xics.h | 2 +
>> arch/powerpc/kvm/mpic.c | 4 +-
>> arch/s390/kvm/Kconfig | 1 +
>> arch/s390/kvm/interrupt.c | 3 +-
>> arch/x86/kvm/Kconfig | 1 +
>> include/linux/kvm_host.h | 43 ++++-------
>> virt/kvm/Kconfig | 3 +
>> virt/kvm/eventfd.c | 134 ++++++++++++++++++++++++++---------
>> virt/kvm/irq_comm.c | 24 +++----
>> virt/kvm/irqchip.c | 98 ++++++++++---------------
>> virt/kvm/kvm_main.c | 2 +-
>> 15 files changed, 227 insertions(+), 152 deletions(-)
>
next prev parent reply other threads:[~2014-07-24 15:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-30 10:51 [PATCH 0/6] IRQFD without IRQ routing, enabled for XICS Paul Mackerras
2014-06-30 10:51 ` [PATCH 1/6] KVM: Don't keep reference to irq routing table in irqfd struct Paul Mackerras
2014-06-30 10:51 ` [PATCH 2/6] KVM: irqchip: Provide and use accessors for irq routing table Paul Mackerras
2014-06-30 10:51 ` [PATCH 3/6] KVM: Move all accesses to kvm::irq_routing into irqchip.c Paul Mackerras
2014-06-30 10:51 ` [PATCH 4/6] KVM: Move irq notifier implementation into eventfd.c Paul Mackerras
2014-06-30 10:51 ` [PATCH 5/6] KVM: Give IRQFD its own separate enabling Kconfig option Paul Mackerras
2014-06-30 10:51 ` [PATCH 6/6] KVM: PPC: Enable IRQFD support for the XICS interrupt controller Paul Mackerras
2014-06-30 12:43 ` [PATCH 0/6] IRQFD without IRQ routing, enabled for XICS Alexander Graf
2014-06-30 21:25 ` Paul Mackerras
2014-07-13 22:30 ` Paul Mackerras
2014-07-14 14:18 ` Cornelia Huck
2014-07-24 15:47 ` Eric Auger [this message]
2014-08-05 12:27 ` Paolo Bonzini
2014-08-06 12:35 ` Paolo Bonzini
2014-08-07 9:49 ` Paul Mackerras
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=53D12A8E.6050407@linaro.org \
--to=eric.auger@linaro.org \
--cc=agraf@suse.de \
--cc=cornelia.huck@de.ibm.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=paulus@samba.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