From: Alex Williamson <alex.williamson@redhat.com>
To: Pavel Fedin <p.fedin@samsung.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] vfio: Fix handling VFIO_IOMMU_GET_INFO results
Date: Thu, 12 Nov 2015 08:33:28 -0700 [thread overview]
Message-ID: <1447342408.3946.54.camel@redhat.com> (raw)
In-Reply-To: <014c01d11d57$5a101a20$0e304e60$@samsung.com>
On Thu, 2015-11-12 at 17:35 +0300, Pavel Fedin wrote:
> Hello!
>
> > > Kernel headers define VFIO_IOMMU_INFO_PGSIZES flag, however it has
> > > actually been never used, probably by mistake which now became a part
> > > of the ABI. The kernel always sets info.flags to 0:
> >
> > I don't see how this implies that it becomes part of the ABI. In fact,
> > as the defacto userspace driver for vfio, QEMU honoring the flag and not
> > using the value the kernel provides implies the ABI is still valid. We
> > should fix the kernel instead.
>
> Well... I intentionally put two links to LXR. From the very
> beginning, this ioctl returned valid page sizes. And it never set this
> flag. We simply cannot have a kernel which does not report page sizes.
Isn't that the state we've been in since the very beginning? QEMU gets
along ok assuming a minimum page size. If that assumption were to be
invalid, DMA map would fail. The fact that this bug has been there
since the very beginning and that QEMU has still been honoring the flag
suggests to me that it's not sufficiently critical to change the ABI.
> If we fix qemu, it will automatically start working with all
> available kernels which are there in the wild. If we fix kernel, older
> versions will still not work, however they can.
> That's why i think that we should adapt qemu to what already exists.
> But, well, you are The Boss, so you can just say "i don't care". So,
> just let me now if you strongly disagree with this.
I do care, in fact I care enough about the ABI that I'm suggesting what
I think is the correct fix rather than taking the quick and dirty
solution. It's an unfortunate bug, but it's not worth changing the ABI
and removing the kernel's ability to indicate whether the pgsize bitmap
field is valid IMO. Thanks,
Alex
next prev parent reply other threads:[~2015-11-12 15:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-12 7:16 [Qemu-devel] [PATCH] vfio: Fix handling VFIO_IOMMU_GET_INFO results Pavel Fedin
2015-11-12 14:16 ` Alex Williamson
2015-11-12 14:35 ` Pavel Fedin
2015-11-12 15:33 ` Alex Williamson [this message]
2015-11-13 9:33 ` Pavel Fedin
2015-11-13 17:23 ` Alex Williamson
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=1447342408.3946.54.camel@redhat.com \
--to=alex.williamson@redhat.com \
--cc=p.fedin@samsung.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).