All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yuanhan Liu <yuanhan.liu@linux.intel.com>
To: Jason Wang <jasowang@redhat.com>
Cc: dev@dpdk.org, huawei.xie@intel.com, mst@redhat.com,
	Thomas Monjalon <thomas.monjalon@6wind.com>
Subject: Re: [PATCH 2/2] virtio: support IOMMU platform
Date: Tue, 6 Sep 2016 15:46:18 +0800	[thread overview]
Message-ID: <20160906074618.GB4357@yliu-dev.sh.intel.com> (raw)
In-Reply-To: <20160905071626.GM30752@yliu-dev.sh.intel.com>

Oops, seems I failed to send it out (I happened to know it when
I was checking the patchwork status: I didn't find my comment).

I also happened to find out that I failed to receive quite many
emails, including some patches. Seems something went wrong :(

	--yliu

On Mon, Sep 05, 2016 at 03:16:26PM +0800, Yuanhan Liu wrote:
> On Fri, Sep 02, 2016 at 02:37:00PM +0800, Jason Wang wrote:
> > Virtio pmd doesn't support VFIO in the past since devices bypass IOMMU
> > completely. But recently, the work of making virtio device work with
> > IOMMU is near to complete. So this patch make pmd support IOMMU by:
> > 
> > - Allow VFIO mapping by setting RTE_PCI_DRV_NEED_MAPPING flag
> 
> I think that's not needed, since virtio_read_caps() invokes
> rte_eal_pci_map_device().
> 
> 	--yliu

  parent reply	other threads:[~2016-09-06  7:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-02  6:36 [PATCH 1/2] net/virtio: support modern device id Jason Wang
2016-09-02  6:37 ` [PATCH 2/2] virtio: support IOMMU platform Jason Wang
2016-09-02 13:04   ` Thomas Monjalon
2016-09-02 17:26     ` Michael S. Tsirkin
2016-09-04  8:08       ` Alejandro Lucero
2016-09-05  6:31         ` Jason Wang
2016-09-05  5:15     ` Jason Wang
2016-09-05  6:25     ` Jason Wang
     [not found]   ` <20160905071626.GM30752@yliu-dev.sh.intel.com>
2016-09-06  7:46     ` Yuanhan Liu [this message]
2016-09-07  4:53       ` Jason Wang
2016-09-02 12:57 ` [PATCH 1/2] net/virtio: support modern device id Thomas Monjalon
2016-09-05  6:36   ` Jason Wang

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=20160906074618.GB4357@yliu-dev.sh.intel.com \
    --to=yuanhan.liu@linux.intel.com \
    --cc=dev@dpdk.org \
    --cc=huawei.xie@intel.com \
    --cc=jasowang@redhat.com \
    --cc=mst@redhat.com \
    --cc=thomas.monjalon@6wind.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.