From: "Michael S. Tsirkin" <mst@redhat.com>
To: Peter Xu <peterx@redhat.com>
Cc: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
Maxime Coquelin <maxime.coquelin@redhat.com>,
Jason Wang <jasowang@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 3/3] vhost: iommu: cache static mapping if there is
Date: Mon, 5 Jun 2017 18:05:30 +0300 [thread overview]
Message-ID: <20170605180442-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20170605031511.GG4056@pxdev.xzpeter.org>
On Mon, Jun 05, 2017 at 11:15:11AM +0800, Peter Xu wrote:
> On Fri, Jun 02, 2017 at 06:45:05PM +0300, Michael S. Tsirkin wrote:
> > On Fri, Jun 02, 2017 at 07:50:54PM +0800, Peter Xu wrote:
> > > This patch pre-heat vhost iotlb cache when passthrough mode enabled.
> > >
> > > Sometimes, even if user specified iommu_platform for vhost devices,
> > > IOMMU might still be disabled. One case is passthrough mode in VT-d
> > > implementation. We can detect this by observing iommu_list. If it's
> > > empty, it means IOMMU translation is disabled, then we can actually
> > > pre-heat the translation (it'll be static mapping then) by first
> > > invalidating all IOTLB, then cache existing memory ranges into vhost
> > > backend iotlb using 1:1 mapping.
> > >
> > > Reviewed-by: Jason Wang <jasowang@redhat.com>
> > > Signed-off-by: Peter Xu <peterx@redhat.com>
> >
> > This is still a hack I think. What if there's an invalidation?
> > I think the right thing is to send updates only when requested,
> > but sent the largest mapping including the iova, not from iova until end
> > of page. Thoughts?
>
> Indeed it's kind of a hack, but it does not hurt anything but will
> definitely boost performance in most cases...
>
> Yes "sent the largest mapping including the iova" is okay, but the
> first IO on one region would be delayed as well, so IMHO it's not the
> best solution as well. I think the best solution should be (for sure)
> that vhost knows it's PT, then it just skips the translation
> completely. I just don't sure whether there's simple/good way to do
> this.
>
> Thanks,
If you send the whole 64 bit area, then backend can detect this
easily.
> --
> Peter Xu
next prev parent reply other threads:[~2017-06-05 15:05 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-02 11:50 [Qemu-devel] [PATCH 0/3] exec: further refine address_space_get_iotlb_entry() Peter Xu
2017-06-02 11:50 ` [Qemu-devel] [PATCH 1/3] exec: add page_mask for address_space_do_translate Peter Xu
2017-06-02 16:45 ` Michael S. Tsirkin
2017-06-05 2:52 ` Peter Xu
2017-06-02 11:50 ` [Qemu-devel] [PATCH 2/3] exec: simplify address_space_get_iotlb_entry Peter Xu
2017-06-02 16:49 ` Michael S. Tsirkin
2017-06-05 3:07 ` Peter Xu
2017-06-06 14:34 ` Paolo Bonzini
2017-06-06 23:47 ` David Gibson
2017-06-07 3:44 ` Peter Xu
2017-06-07 13:07 ` Michael S. Tsirkin
2017-06-08 6:11 ` Peter Xu
2017-06-08 18:59 ` Michael S. Tsirkin
2017-06-09 1:58 ` Peter Xu
2017-06-09 2:37 ` David Gibson
2017-06-11 10:09 ` Michael S. Tsirkin
2017-06-11 12:10 ` David Gibson
2017-06-12 2:34 ` Peter Xu
2017-06-12 3:07 ` Michael S. Tsirkin
2017-06-12 4:04 ` Peter Xu
2017-06-14 18:34 ` Michael S. Tsirkin
2017-06-15 2:31 ` Peter Xu
2017-06-15 2:57 ` Peter Xu
2017-06-16 15:33 ` Michael S. Tsirkin
2017-06-07 13:01 ` Paolo Bonzini
2017-06-02 11:50 ` [Qemu-devel] [PATCH 3/3] vhost: iommu: cache static mapping if there is Peter Xu
2017-06-02 15:45 ` Michael S. Tsirkin
2017-06-05 3:15 ` Peter Xu
2017-06-05 4:07 ` Jason Wang
2017-06-05 15:05 ` Michael S. Tsirkin [this message]
2017-06-02 16:51 ` Michael S. Tsirkin
2017-06-02 14:51 ` [Qemu-devel] [PATCH 0/3] exec: further refine address_space_get_iotlb_entry() Michael S. Tsirkin
2017-06-05 3:20 ` Peter Xu
2017-06-06 15:29 ` 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=20170605180442-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=jasowang@redhat.com \
--cc=maxime.coquelin@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.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).