From: Marc Zyngier <marc.zyngier@arm.com>
To: Eric Auger <eric.auger@linaro.org>,
"eric.auger@st.com" <eric.auger@st.com>,
"christoffer.dall@linaro.org" <christoffer.dall@linaro.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"patches@linaro.org" <patches@linaro.org>,
"alex.williamson@redhat.com" <alex.williamson@redhat.com>,
"b.reynal@virtualopensystems.com"
<b.reynal@virtualopensystems.com>,
Kim Phillips <kim.phillips@linaro.org>
Subject: Re: [PATCH] KVM: arm/arm64: Enable the KVM-VFIO device
Date: Tue, 09 Jun 2015 18:09:53 +0100 [thread overview]
Message-ID: <55771DE1.7050405@arm.com> (raw)
In-Reply-To: <1433517709-6872-1-git-send-email-eric.auger@linaro.org>
On 05/06/15 16:21, Eric Auger wrote:
> From: Kim Phillips <kim.phillips@linaro.org>
>
> The KVM-VFIO device is used by the QEMU VFIO device. It is used to
> record the list of in-use VFIO groups so that KVM can manipulate
> them.
>
> Signed-off-by: Kim Phillips <kim.phillips@linaro.org>
> Signed-off-by: Eric Auger <eric.auger@linaro.org>
>
> ---
>
> - previously included in KVM-VFIO IRQ forward control v6 series.
> Rationale to put it aside is the unavailability of the kvm-vfio device
> causes produces a warning when launching the QEMU VFIO platform device
> that can puzzle some users (although not blocking):
> "Failed to create KVM VFIO device: No such device"
Applied to queue.
M.
--
Jazz is not dead. It just smells funny...
WARNING: multiple messages have this Message-ID (diff)
From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] KVM: arm/arm64: Enable the KVM-VFIO device
Date: Tue, 09 Jun 2015 18:09:53 +0100 [thread overview]
Message-ID: <55771DE1.7050405@arm.com> (raw)
In-Reply-To: <1433517709-6872-1-git-send-email-eric.auger@linaro.org>
On 05/06/15 16:21, Eric Auger wrote:
> From: Kim Phillips <kim.phillips@linaro.org>
>
> The KVM-VFIO device is used by the QEMU VFIO device. It is used to
> record the list of in-use VFIO groups so that KVM can manipulate
> them.
>
> Signed-off-by: Kim Phillips <kim.phillips@linaro.org>
> Signed-off-by: Eric Auger <eric.auger@linaro.org>
>
> ---
>
> - previously included in KVM-VFIO IRQ forward control v6 series.
> Rationale to put it aside is the unavailability of the kvm-vfio device
> causes produces a warning when launching the QEMU VFIO platform device
> that can puzzle some users (although not blocking):
> "Failed to create KVM VFIO device: No such device"
Applied to queue.
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2015-06-09 17:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-05 15:21 [PATCH] KVM: arm/arm64: Enable the KVM-VFIO device Eric Auger
2015-06-05 15:21 ` Eric Auger
2015-06-09 17:09 ` Marc Zyngier [this message]
2015-06-09 17:09 ` Marc Zyngier
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=55771DE1.7050405@arm.com \
--to=marc.zyngier@arm.com \
--cc=alex.williamson@redhat.com \
--cc=b.reynal@virtualopensystems.com \
--cc=christoffer.dall@linaro.org \
--cc=eric.auger@linaro.org \
--cc=eric.auger@st.com \
--cc=kim.phillips@linaro.org \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.