From: "Michael S. Tsirkin" <mst@redhat.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-kernel@vger.kernel.org, virtualization@lists.linux-foundation.org
Subject: Re: [PATCH v3] virtio: new feature to detect IOMMU device quirk
Date: Mon, 25 Jul 2016 22:13:05 +0300 [thread overview]
Message-ID: <20160725214322-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20160725075009.GA25638@infradead.org>
On Mon, Jul 25, 2016 at 12:50:09AM -0700, Christoph Hellwig wrote:
> On Tue, Jul 19, 2016 at 05:38:23AM +0300, Michael S. Tsirkin wrote:
> >
> > On other systems, including SPARC and PPC64, virtio-pci devices are
> > enumerated as though they are behind an IOMMU, but the virtio host
> > ignores the IOMMU, so we must either pretend that the IOMMU isn't
> > there or somehow map everything as the identity.
> >
> > Add a feature bit to detect that quirk: VIRTIO_F_IOMMU_PLATFORM.
> >
> > Any device with this feature bit set to 0 needs a quirk and has to be
> > passed physical addresses (as opposed to bus addresses) even though
> > the device is behind an IOMMU.
>
> This is the wrong way around.
Well given there are tons of quirky devices out there
and they have this bit set to 0, I don't think we can change this.
New devices will have it set to 1.
> > Note: it has to be a per-device quirk because for example, there could
> > be a mix of passed-through and virtual virtio devices. As another
> > example, some devices could be implemented by an out of process
> > hypervisor backend (in case of qemu vhost, or vhost-user) and so support
> > for an IOMMU needs to be coded up separately.
> >
> > It would be cleanest to handle this in IOMMU core code, but that needs
> > per-device DMA ops. While we are waiting for that to be implemented, use
> > a work-around in virtio core.
> >
> > Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> > ---
> >
> > wanted to use per-device dma ops but that does not
> > seem to be ready. So let's put this in virtio
> > code for now, and move when it becomes possible.
>
> So work on making it ready. We're close to there, and given that
> virtio needs it, finish it off. We now have everyone using the
> operation vectors for DMA, so the only thing you need is a dma_ops
> pointer in struct device initialized to what get_dma_ops returns.
And then pci_dma_configure would have a quirk to
set that for legacy virtio devices?
--
MST
next prev parent reply other threads:[~2016-07-25 19:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-19 2:38 [PATCH v3] virtio: new feature to detect IOMMU device quirk Michael S. Tsirkin
2016-07-23 21:32 ` kbuild test robot
2016-07-23 21:32 ` kbuild test robot
2016-07-24 22:44 ` kbuild test robot
2016-07-24 22:44 ` kbuild test robot
2016-07-25 7:50 ` Christoph Hellwig
2016-07-25 19:13 ` Michael S. Tsirkin
2016-07-25 19:13 ` Michael S. Tsirkin [this message]
2016-07-26 18:50 ` Michael S. Tsirkin
2016-07-26 18:50 ` Michael S. Tsirkin
-- strict thread matches above, loose matches on Subject: below --
2016-07-19 2:38 Michael S. Tsirkin
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=20160725214322-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.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.