All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: Tiwei Bie <tiwei.bie@intel.com>,
	cunming.liang@intel.com, qemu-devel@nongnu.org,
	peterx@redhat.com, zhihong.wang@intel.com, dan.daly@intel.com
Subject: Re: [Qemu-devel] [RFC] vhost-user: introduce F_NEED_ALL_IOTLB protocol feature
Date: Thu, 12 Apr 2018 07:19:38 +0300	[thread overview]
Message-ID: <20180412071805-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <9314ebd5-8e92-41b1-efd1-4371177075a0@redhat.com>

On Thu, Apr 12, 2018 at 11:43:41AM +0800, Jason Wang wrote:
> 
> 
> On 2018年04月12日 11:35, Michael S. Tsirkin wrote:
> > > There are more advantages to using request with PASID:
> > > 
> > > You can use hardware support for nesting, having guest supply 1st level
> > > translation and host second level translation.
> > > 
> > > I actually had an idea to do something like this for AMD
> > > and ARM which support nesting even for requests with PASID,
> > > having intel benefit too would be nice.
> > Something else to consider is implementing PRS capability.
> > 
> > 
> > In theory this could then go like this:
> > 
> > - get page request from device
> > - fetch request from VTD page tables
> > - use response to issue a page response message
> > 
> > 
> > This would match the current vhost-user model.
> 
> This requires IOMMU driver can forward this to VFIO and then VFIO can
> forward it to userspace. Looks like a lot of changes and it would be even
> slower than what is proposed in this patch.
> 
> Thanks


It would work better for a static table as only accessed pages would
need to be sent.  Slower for the dynamic case but dynamic case needs
hardware support to work properly in any case.

-- 
MST

  reply	other threads:[~2018-04-12  4:19 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-11  7:20 [Qemu-devel] [RFC] vhost-user: introduce F_NEED_ALL_IOTLB protocol feature Tiwei Bie
2018-04-11  8:00 ` Peter Xu
2018-04-11  8:25   ` Tiwei Bie
2018-04-11  8:37     ` Peter Xu
2018-04-11  8:55       ` Tiwei Bie
2018-04-11  9:16         ` Peter Xu
2018-04-11  9:25           ` Tiwei Bie
2018-04-11  8:01 ` Jason Wang
2018-04-11  8:38   ` Tiwei Bie
2018-04-11 13:41     ` Jason Wang
2018-04-11 17:00       ` Michael S. Tsirkin
2018-04-12  3:23         ` Jason Wang
2018-04-12  3:37           ` Michael S. Tsirkin
2018-04-12  3:56             ` Jason Wang
2018-04-11 17:37     ` Michael S. Tsirkin
2018-04-12  1:44       ` Tiwei Bie
2018-04-12  7:38         ` Jason Wang
2018-04-12  8:10           ` Tiwei Bie
2018-04-12  9:40             ` Jason Wang
2018-04-11 13:22 ` Michael S. Tsirkin
2018-04-11 13:42   ` Jason Wang
2018-04-12  1:10   ` Tiwei Bie
2018-04-12  1:29     ` Michael S. Tsirkin
2018-04-12  1:39       ` Tiwei Bie
2018-04-12  1:57         ` Michael S. Tsirkin
2018-04-12  2:35           ` Tiwei Bie
2018-04-12  3:20             ` Michael S. Tsirkin
2018-04-12  3:35               ` Michael S. Tsirkin
2018-04-12  3:43                 ` Jason Wang
2018-04-12  4:19                   ` Michael S. Tsirkin [this message]
2018-04-12  3:37           ` Jason Wang
2018-04-12  3:41             ` Michael S. Tsirkin
2018-04-12  7:24               ` Jason Wang
2018-04-16  7:47 ` Stefan Hajnoczi
2018-04-17  2:14   ` Jason Wang
2018-04-17  2:35   ` Tiwei Bie

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=20180412071805-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=cunming.liang@intel.com \
    --cc=dan.daly@intel.com \
    --cc=jasowang@redhat.com \
    --cc=peterx@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=tiwei.bie@intel.com \
    --cc=zhihong.wang@intel.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 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.