From: Eric Auger <eric.auger@linaro.org>
To: David Gibson <david@gibson.dropbear.id.au>,
alex.williamson@redhat.com, pbonzini@redhat.com
Cc: paulus@samba.org, aik@ozlabs.ru, mdroth@linux.vnet.ibm.com,
benh@kernel.crashing.org, mpe@ellerman.id.au,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] vfio: Enable VFIO device for powerpc
Date: Fri, 31 Jul 2015 09:27:53 +0200 [thread overview]
Message-ID: <55BB2379.8070809@linaro.org> (raw)
In-Reply-To: <1437372731-11097-1-git-send-email-david@gibson.dropbear.id.au>
Hi David,
As noticed we did the same on ARM (4.2) for the same reason.
Reviewed-by: Eric Auger <eric.auger@linaro.org>
Best Regards
Eric
On 07/20/2015 08:12 AM, David Gibson wrote:
> ec53500f "kvm: Add VFIO device" added a special KVM pseudo-device which is
> used to handle any necessary interactions between KVM and VFIO.
>
> Currently that device is built on x86 and ARM, but not powerpc, although
> powerpc does support both KVM and VFIO. This makes things awkward in
> userspace
>
> Currently qemu prints an alarming error message if you attempt to use VFIO
> and it can't initialize the KVM VFIO device. We don't want to remove the
> warning, because lack of the KVM VFIO device could mean coherency problems
> on x86. On powerpc, however, the error is harmless but looks disturbing,
> and a test based on host architecture in qemu would be ugly, and break if
> we do need the KVM VFIO device for something important in future.
>
> There's nothing preventing the KVM VFIO device from being built for
> powerpc, so this patch turns it on. It won't actually do anything, since
> we don't define any of the arch_*() hooks, but it will make qemu happy and
> we can extend it in future if we need to.
>
> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
> ---
> arch/powerpc/kvm/Makefile | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/powerpc/kvm/Makefile b/arch/powerpc/kvm/Makefile
> index 0570eef..7f7b6d8 100644
> --- a/arch/powerpc/kvm/Makefile
> +++ b/arch/powerpc/kvm/Makefile
> @@ -8,7 +8,7 @@ ccflags-y := -Ivirt/kvm -Iarch/powerpc/kvm
> KVM := ../../../virt/kvm
>
> common-objs-y = $(KVM)/kvm_main.o $(KVM)/coalesced_mmio.o \
> - $(KVM)/eventfd.o
> + $(KVM)/eventfd.o $(KVM)/vfio.o
>
> CFLAGS_e500_mmu.o := -I.
> CFLAGS_e500_mmu_host.o := -I.
>
next prev parent reply other threads:[~2015-07-31 7:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-20 6:12 [PATCH] vfio: Enable VFIO device for powerpc David Gibson
2015-07-31 7:27 ` Eric Auger [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-08-13 1:15 David Gibson
2015-08-26 9:34 ` Alexander Graf
2015-08-26 18:54 ` Paul Mackerras
2015-09-07 11:06 ` Paolo Bonzini
2016-08-11 12:57 ` Paolo Bonzini
2016-08-11 13:19 ` Cornelia Huck
2016-08-11 14:04 ` Alexey Kardashevskiy
2016-08-12 6:46 ` David Gibson
2015-12-21 0:54 David Gibson
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=55BB2379.8070809@linaro.org \
--to=eric.auger@linaro.org \
--cc=aik@ozlabs.ru \
--cc=alex.williamson@redhat.com \
--cc=benh@kernel.crashing.org \
--cc=david@gibson.dropbear.id.au \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mdroth@linux.vnet.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=pbonzini@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).