From: Marc Zyngier <marc.zyngier@arm.com>
To: "Radim Krčmář" <rkrcmar@redhat.com>,
"Eric Auger" <eric.auger@redhat.com>
Cc: kvm@vger.kernel.org, andre.przywara@arm.com, pbonzini@redhat.com,
kvmarm@lists.cs.columbia.edu, eric.auger.pro@gmail.com
Subject: Re: [RFC v9 0/6] KVM: arm/arm64: gsi routing support
Date: Fri, 22 Jul 2016 18:33:52 +0100 [thread overview]
Message-ID: <57925900.8020104@arm.com> (raw)
In-Reply-To: <20160722171354.GC11512@potion>
On 22/07/16 18:13, Radim Krčmář wrote:
> 2016-07-22 16:20+0000, Eric Auger:
>> With the advent of GICv3 ITS in-kernel emulation, KVM MSI routing
>> becomes mandated for proper VIRTIO-PCI vhost integration.
>
> Changes to interfaces and common code look ok,
>
> Acked-by: Radim Krčmář <rkrcmar@redhat.com>
I'll let it sink into -next for a few days, so that I can rerun my
non-reg stuff, and will send another PR if everything turns green.
Thanks you both for the quick turnaround!
M.
--
Jazz is not dead. It just smells funny...
_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
next prev parent reply other threads:[~2016-07-22 17:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-22 16:20 [RFC v9 0/6] KVM: arm/arm64: gsi routing support Eric Auger
2016-07-22 16:20 ` [RFC v9 1/6] KVM: api: Pass the devid in the msi routing entry Eric Auger
2016-07-22 16:20 ` [RFC v9 2/6] KVM: Add devid in kvm_kernel_irq_routing_entry Eric Auger
2016-07-22 16:20 ` [RFC v9 3/6] KVM: irqchip: Convey devid to kvm_set_msi Eric Auger
2016-07-22 16:20 ` [RFC v9 4/6] KVM: Move kvm_setup_default/empty_irq_routing declaration in arch specific header Eric Auger
2016-07-22 16:20 ` [RFC v9 5/6] KVM: arm/arm64: Enable irqchip routing Eric Auger
2016-07-22 16:20 ` [RFC v9 6/6] KVM: arm/arm64: Enable MSI routing Eric Auger
2016-07-22 17:13 ` [RFC v9 0/6] KVM: arm/arm64: gsi routing support Radim Krčmář
2016-07-22 17:33 ` Marc Zyngier [this message]
2016-07-25 7:22 ` Auger Eric
2016-07-28 22:31 ` André Przywara
2016-07-29 6:51 ` Auger Eric
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=57925900.8020104@arm.com \
--to=marc.zyngier@arm.com \
--cc=andre.przywara@arm.com \
--cc=eric.auger.pro@gmail.com \
--cc=eric.auger@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@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