From: Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
To: Will Deacon <will.deacon-5wv7dgnIgG8@public.gmane.org>
Cc: kvm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
marc.zyngier-5wv7dgnIgG8@public.gmane.org,
iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [GIT PULL] iommu: KVM PCIe/MSI passthrough on ARM/ARM64 for 4.11
Date: Mon, 30 Jan 2017 15:59:47 +0100 [thread overview]
Message-ID: <20170130145946.GA28129@8bytes.org> (raw)
In-Reply-To: <20170127165021.GC10758-5wv7dgnIgG8@public.gmane.org>
On Fri, Jan 27, 2017 at 04:50:22PM +0000, Will Deacon wrote:
> Hi Joerg,
>
> Please pull Eric's guest-MSI series for 4.11. This has been through
> considerable review and associated rework (including a session at LPC),
> but it has stabilised at last and we all seem to be happy with it. Eric's
> done a great job of respinning these and remaining patient while we
> pulled him in a bunch of different directions.
>
> With these patches applied, it's possible for us to pass PCI devices
> through to KVM guests on arm64 using VFIO and have them signal interrupts
> using MSIs targetting the ITS via the SMMU. Acronym soup, sure, but it's
> much better than legacy wired irqs!
>
> Cheers,
>
> Will
>
> --->8
>
> The following changes since commit a121103c922847ba5010819a3f250f1f7fc84ab8:
>
> Linux 4.10-rc3 (2017-01-08 14:18:17 -0800)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/will/linux.git iommu/guest-msi
Pulled, thanks Will.
prev parent reply other threads:[~2017-01-30 14:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-27 16:50 [GIT PULL] iommu: KVM PCIe/MSI passthrough on ARM/ARM64 for 4.11 Will Deacon
[not found] ` <20170127165021.GC10758-5wv7dgnIgG8@public.gmane.org>
2017-01-30 14:59 ` Joerg Roedel [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=20170130145946.GA28129@8bytes.org \
--to=joro-zlv9swrftaidnm+yrofe0a@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=kvm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=marc.zyngier-5wv7dgnIgG8@public.gmane.org \
--cc=will.deacon-5wv7dgnIgG8@public.gmane.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