From: Cornelia Huck <cornelia.huck@de.ibm.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Paul Mackerras <paulus@ozlabs.org>,
Alexander Graf <agraf@suse.de>,
David Gibson <david@gibson.dropbear.id.au>,
alex.williamson@redhat.com, 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, kvm-ppc <kvm-ppc@vger.kernel.org>
Subject: Re: [PATCH] vfio: Enable VFIO device for powerpc
Date: Thu, 11 Aug 2016 15:19:57 +0200 [thread overview]
Message-ID: <20160811151957.0f113a7c.cornelia.huck@de.ibm.com> (raw)
In-Reply-To: <ef52152a-0009-137d-69c2-5ddd149054c0@redhat.com>
On Thu, 11 Aug 2016 14:57:24 +0200
Paolo Bonzini <pbonzini@redhat.com> wrote:
> On 26/08/2015 20:54, Paul Mackerras wrote:
> > On Wed, Aug 26, 2015 at 11:34:26AM +0200, Alexander Graf wrote:
> >> On 13.08.15 03:15, 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>
> >>> Reviewed-by: Eric Auger <eric.auger@linaro.org>
>
> This patch (commit 178a787502123) did not select CONFIG_KVM_VFIO, so the
> patch did nothing---except causing build failures which I fixed in
> commit 0af574be32cdd ("KVM: PPC: do not compile in vfio.o
> unconditionally", 2016-03-21) by making the patch a total no-op.
>
> Is KVM_VFIO really needed, and if so can this patch be fixed?
FWIW, we enabled building vfio.o on s390 in 14b0b4a ("KVM: s390: Enable
the KVM-VFIO device") with the rationale "while we don't need it, be
like everybody else".
Should powerpc (and every other architecture supporting kvm and vfio)
select KVM_VFIO so that really everybody does the same thing?
next prev parent reply other threads:[~2016-08-11 13:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-13 1:15 [PATCH] vfio: Enable VFIO device for powerpc 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 [this message]
2016-08-11 14:04 ` Alexey Kardashevskiy
2016-08-12 6:46 ` David Gibson
-- strict thread matches above, loose matches on Subject: below --
2015-12-21 0:54 David Gibson
2015-07-20 6:12 David Gibson
2015-07-31 7:27 ` Eric Auger
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=20160811151957.0f113a7c.cornelia.huck@de.ibm.com \
--to=cornelia.huck@de.ibm.com \
--cc=agraf@suse.de \
--cc=aik@ozlabs.ru \
--cc=alex.williamson@redhat.com \
--cc=benh@kernel.crashing.org \
--cc=david@gibson.dropbear.id.au \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mdroth@linux.vnet.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=paulus@ozlabs.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).