All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joerg Roedel <joro@8bytes.org>
To: Jean-Philippe Brucker <jean-philippe.brucker@arm.com>
Cc: virtio-dev@lists.oasis-open.org, kevin.tian@intel.com,
	lorenzo.pieralisi@arm.com, tnowicki@caviumnetworks.com,
	mst@redhat.com, marc.zyngier@arm.com, linux-pci@vger.kernel.org,
	jasowang@redhat.com, will.deacon@arm.com, robin.murphy@arm.com,
	virtualization@lists.linux-foundation.org,
	iommu@lists.linux-foundation.org, robh+dt@kernel.org,
	bhelgaas@google.com, frowand.list@gmail.com,
	kvmarm@lists.cs.columbia.edu, devicetree@vger.kernel.org
Subject: Re: [PATCH v6 0/7] Add virtio-iommu driver
Date: Wed, 12 Dec 2018 11:35:45 +0100	[thread overview]
Message-ID: <20181212103545.GV16835@8bytes.org> (raw)
In-Reply-To: <20181211182104.18241-1-jean-philippe.brucker@arm.com>

Hi,

to make progress on this, we should first agree on the protocol used
between guest and host. I have a few points to discuss on the protocol
first.

On Tue, Dec 11, 2018 at 06:20:57PM +0000, Jean-Philippe Brucker wrote:
> [1] Virtio-iommu specification v0.9, sources and pdf
>     git://linux-arm.org/virtio-iommu.git virtio-iommu/v0.9
>     http://jpbrucker.net/virtio-iommu/spec/v0.9/virtio-iommu-v0.9.pdf

Looking at this I wonder why it doesn't make the IOTLB visible to the
guest. the UNMAP requests seem to require that the TLB is already
flushed to make the unmap visible.

I think that will cost significant performance for both, vfio and
dma-iommu use-cases which both do (vfio at least to some degree),
deferred flushing.

I also wonder whether the protocol should implement a
protocol version handshake and iommu-feature set queries.

> [3] git://linux-arm.org/linux-jpb.git virtio-iommu/v0.9.1
>     git://linux-arm.org/kvmtool-jpb.git virtio-iommu/v0.9

Unfortunatly gitweb seems to be broken on linux-arm.org. What is missing
in this patch-set to make this work on x86?

Regards,

	Joerg

WARNING: multiple messages have this Message-ID (diff)
From: Joerg Roedel <joro@8bytes.org>
To: Jean-Philippe Brucker <jean-philippe.brucker@arm.com>
Cc: iommu@lists.linux-foundation.org, linux-pci@vger.kernel.org,
	devicetree@vger.kernel.org,
	virtualization@lists.linux-foundation.org,
	virtio-dev@lists.oasis-open.org, mst@redhat.com,
	jasowang@redhat.com, robh+dt@kernel.org, mark.rutland@arm.com,
	bhelgaas@google.com, frowand.list@gmail.com,
	kvmarm@lists.cs.columbia.edu, eric.auger@redhat.com,
	tnowicki@caviumnetworks.com, kevin.tian@intel.com,
	marc.zyngier@arm.com, robin.murphy@arm.com, will.deacon@arm.com,
	lorenzo.pieralisi@arm.com, bharat.bhushan@nxp.com
Subject: Re: [PATCH v6 0/7] Add virtio-iommu driver
Date: Wed, 12 Dec 2018 11:35:45 +0100	[thread overview]
Message-ID: <20181212103545.GV16835@8bytes.org> (raw)
In-Reply-To: <20181211182104.18241-1-jean-philippe.brucker@arm.com>

Hi,

to make progress on this, we should first agree on the protocol used
between guest and host. I have a few points to discuss on the protocol
first.

On Tue, Dec 11, 2018 at 06:20:57PM +0000, Jean-Philippe Brucker wrote:
> [1] Virtio-iommu specification v0.9, sources and pdf
>     git://linux-arm.org/virtio-iommu.git virtio-iommu/v0.9
>     http://jpbrucker.net/virtio-iommu/spec/v0.9/virtio-iommu-v0.9.pdf

Looking at this I wonder why it doesn't make the IOTLB visible to the
guest. the UNMAP requests seem to require that the TLB is already
flushed to make the unmap visible.

I think that will cost significant performance for both, vfio and
dma-iommu use-cases which both do (vfio at least to some degree),
deferred flushing.

I also wonder whether the protocol should implement a
protocol version handshake and iommu-feature set queries.

> [3] git://linux-arm.org/linux-jpb.git virtio-iommu/v0.9.1
>     git://linux-arm.org/kvmtool-jpb.git virtio-iommu/v0.9

Unfortunatly gitweb seems to be broken on linux-arm.org. What is missing
in this patch-set to make this work on x86?

Regards,

	Joerg

  parent reply	other threads:[~2018-12-12 10:35 UTC|newest]

Thread overview: 65+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-11 18:20 [PATCH v6 0/7] Add virtio-iommu driver Jean-Philippe Brucker
2018-12-11 18:20 ` [virtio-dev] " Jean-Philippe Brucker
2018-12-11 18:20 ` Jean-Philippe Brucker
2018-12-11 18:20 ` [PATCH v6 1/7] dt-bindings: virtio-mmio: Add IOMMU description Jean-Philippe Brucker
2018-12-11 18:20 ` Jean-Philippe Brucker
2018-12-11 18:20   ` [virtio-dev] " Jean-Philippe Brucker
2018-12-11 18:20 ` [PATCH v6 2/7] dt-bindings: virtio: Add virtio-pci-iommu node Jean-Philippe Brucker
2018-12-11 18:20 ` Jean-Philippe Brucker
2018-12-11 18:20   ` [virtio-dev] " Jean-Philippe Brucker
2018-12-11 18:20   ` Jean-Philippe Brucker
2018-12-11 18:21 ` [PATCH v6 3/7] of: Allow the iommu-map property to omit untranslated devices Jean-Philippe Brucker
2018-12-11 18:21 ` Jean-Philippe Brucker
2018-12-11 18:21   ` [virtio-dev] " Jean-Philippe Brucker
2018-12-11 18:21 ` [PATCH v6 4/7] PCI: OF: Initialize dev->fwnode appropriately Jean-Philippe Brucker
2018-12-11 18:21 ` Jean-Philippe Brucker
2018-12-11 18:21   ` [virtio-dev] " Jean-Philippe Brucker
2018-12-11 18:21 ` [PATCH v6 5/7] iommu: Add virtio-iommu driver Jean-Philippe Brucker
2018-12-11 18:21 ` Jean-Philippe Brucker
2018-12-11 18:21   ` [virtio-dev] " Jean-Philippe Brucker
2018-12-11 18:21 ` [PATCH v6 6/7] iommu/virtio: Add probe request Jean-Philippe Brucker
2018-12-11 18:21   ` [virtio-dev] " Jean-Philippe Brucker
2018-12-11 18:21 ` Jean-Philippe Brucker
2018-12-11 18:21 ` [PATCH v6 7/7] iommu/virtio: Add event queue Jean-Philippe Brucker
2018-12-11 18:21   ` [virtio-dev] " Jean-Philippe Brucker
2018-12-11 18:21 ` Jean-Philippe Brucker
2018-12-11 18:31 ` [PATCH v6 0/7] Add virtio-iommu driver Christoph Hellwig
     [not found] ` <20181211182104.18241-1-jean-philippe.brucker-5wv7dgnIgG8@public.gmane.org>
2018-12-11 18:31   ` Christoph Hellwig
2018-12-11 18:31     ` Christoph Hellwig
2018-12-11 19:07     ` Jean-Philippe Brucker
2018-12-11 19:07       ` [virtio-dev] " Jean-Philippe Brucker
2018-12-11 19:07     ` Jean-Philippe Brucker
2018-12-12  0:39     ` Michael S. Tsirkin
2018-12-12  0:39     ` Michael S. Tsirkin
2018-12-12  0:39       ` [virtio-dev] " Michael S. Tsirkin
2018-12-12 10:35 ` Joerg Roedel
2018-12-12 10:35 ` Joerg Roedel [this message]
2018-12-12 10:35   ` Joerg Roedel
2018-12-12 14:35   ` Michael S. Tsirkin
2018-12-12 14:35   ` Michael S. Tsirkin
2018-12-12 14:35     ` [virtio-dev] " Michael S. Tsirkin
2018-12-13 12:50   ` Jean-Philippe Brucker
2018-12-13 12:50     ` [virtio-dev] " Jean-Philippe Brucker
2018-12-13 12:50     ` Jean-Philippe Brucker
2018-12-13 14:17     ` Christoph Hellwig
2018-12-13 14:17     ` Christoph Hellwig
2018-12-13 14:17       ` Christoph Hellwig
2018-12-19 23:09     ` Michael S. Tsirkin
2018-12-19 23:09     ` Michael S. Tsirkin
2018-12-19 23:09       ` [virtio-dev] " Michael S. Tsirkin
2018-12-19 23:09       ` Michael S. Tsirkin
2018-12-20 17:59       ` Jean-Philippe Brucker
2018-12-20 17:59       ` Jean-Philippe Brucker
2018-12-20 17:59         ` [virtio-dev] " Jean-Philippe Brucker
2018-12-20 18:17         ` Michael S. Tsirkin
2018-12-20 18:17         ` Michael S. Tsirkin
2018-12-20 18:17           ` [virtio-dev] " Michael S. Tsirkin
2018-12-20 18:17           ` Michael S. Tsirkin
2019-01-11 12:28     ` Joerg Roedel
2019-01-11 12:28       ` Joerg Roedel
2019-01-11 13:00       ` Jean-Philippe Brucker
2019-01-11 13:00       ` Jean-Philippe Brucker
2019-01-11 13:00         ` [virtio-dev] " Jean-Philippe Brucker
2019-01-11 13:00         ` Jean-Philippe Brucker
2019-01-11 12:28     ` Joerg Roedel
2018-12-13 12:50   ` Jean-Philippe Brucker

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=20181212103545.GV16835@8bytes.org \
    --to=joro@8bytes.org \
    --cc=bhelgaas@google.com \
    --cc=devicetree@vger.kernel.org \
    --cc=frowand.list@gmail.com \
    --cc=iommu@lists.linux-foundation.org \
    --cc=jasowang@redhat.com \
    --cc=jean-philippe.brucker@arm.com \
    --cc=kevin.tian@intel.com \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=linux-pci@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=marc.zyngier@arm.com \
    --cc=mst@redhat.com \
    --cc=robh+dt@kernel.org \
    --cc=robin.murphy@arm.com \
    --cc=tnowicki@caviumnetworks.com \
    --cc=virtio-dev@lists.oasis-open.org \
    --cc=virtualization@lists.linux-foundation.org \
    --cc=will.deacon@arm.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.