Re: [Qemu-devel] [Qemu-arm] [RFC v3 0/8] VIRTIO-IOMMU device

On 17/08/17 16:26, Auger Eric wrote: > Hi Linu, Jean, > > On 17/08/2017 15:39, Jean-Philippe Brucker wrote: >> Hi Linu, >> >> On 17/08/17 12:26, Linu Cherian wrote: >>> Hi Eric, >>> >>> On Tue Aug 01, 2017 at 11:33:06AM +0200, Eric Auger wrot

Re: [Qemu-devel] [Qemu-arm] [RFC v3 0/8] VIRTIO-IOMMU device

meoryRegion plus some small fixes. >> >> This is a proof of concept based on the virtio-iommu specification >> written by Jean-Philippe Brucker [1]. >> >> The device gets instantiated using the "-device virtio-iommu-device" >> option. It currently works with ARM virt mac

Re: [Qemu-devel] [RFC PATCH 7/8] VFIO: Add new IOCTL for IOMMU TLB invalidate propagation

On 18/07/17 15:29, Alex Williamson wrote: > On Tue, 18 Jul 2017 10:38:40 +0100 > Jean-Philippe Brucker <jean-philippe.bruc...@arm.com> wrote: > >> On 17/07/17 23:45, Alex Williamson wrote: >> [..] >>>>> >>>>> How does a user learn wh

Re: [Qemu-devel] [RFC PATCH 7/8] VFIO: Add new IOCTL for IOMMU TLB invalidate propagation

On 17/07/17 23:45, Alex Williamson wrote: [..] >>> >>> How does a user learn which model(s) are supported by the interface? >>> How do they learn which ops are supported? Perhaps a good use for one of >>> those >>> flag bits in the outer data structure is "probe". >> >> My initial plan to user

Re: [Qemu-devel] [RFC v2 0/8] VIRTIO-IOMMU device

On 14/07/17 08:20, Tian, Kevin wrote: >> From: Jean-Philippe Brucker [mailto:jean-philippe.bruc...@arm.com] >> Sent: Friday, July 7, 2017 11:15 PM >> >> On 07/07/17 07:21, Tian, Kevin wrote: >>> sorry I didn't quite get this part, and here is my understanding: >

Re: [Qemu-devel] [RFC v2 6/8] virtio-iommu: Implement the translation and commands

Hi Peter, On 14/07/17 03:17, Peter Xu wrote: > > [...] > >> static int virtio_iommu_unmap(VirtIOIOMMU *s, >> @@ -133,10 +227,64 @@ static int virtio_iommu_unmap(VirtIOIOMMU *s, >> uint64_t virt_addr = le64_to_cpu(req->virt_addr); >> uint64_t size = le64_to_cpu(req->size); >>

Re: [Qemu-devel] [RFC v2 0/8] VIRTIO-IOMMU device

On 12/07/17 11:27, Bharat Bhushan wrote: > > >> -Original Message----- >> From: Jean-Philippe Brucker [mailto:jean-philippe.bruc...@arm.com] >> Sent: Wednesday, July 12, 2017 3:48 PM >> To: Bharat Bhushan <bharat.bhus...@nxp.com>; Auger Eric &g

Re: [Qemu-devel] [RFC v2 0/8] VIRTIO-IOMMU device

On 12/07/17 04:50, Bharat Bhushan wrote: [...] >> The size of the virtio_iommu_req_probe structure is variable, and depends >> what fields the device implements. So the device initially computes the size >> it >> needs to fill virtio_iommu_req_probe, describes it in probe_size, and the >> driver

Re: [Qemu-devel] [RFC v2 0/8] VIRTIO-IOMMU device

On 11/07/17 06:54, Bharat Bhushan wrote: > Hi Jean, > >> -Original Message----- >> From: Jean-Philippe Brucker [mailto:jean-philippe.bruc...@arm.com] >> Sent: Friday, July 07, 2017 8:50 PM >> To: Bharat Bhushan <bharat.bhus...@nxp.com>; Auger Eric &g

Re: [Qemu-devel] [Qemu-arm] [RFC v2 0/8] VIRTIO-IOMMU device

generic support > for ATS/PRI extensions needs to be added in VFIO too. That's also in progress. As far as I know the latest version for fault reporting is http://www.spinics.net/lists/kvm/msg146615.html Thanks, Jean > Thanks, > Ashish > > -----Original Message- > From:

Re: [Qemu-devel] [RFC v2 0/8] VIRTIO-IOMMU device

On 07/07/17 12:36, Bharat Bhushan wrote: >>> In this proposal, QEMU reserves a iova-range for guest (not host) and guest >> kernel will use this as msi-iova untranslated (IOMMU_RESV_MSI). While this >> does not change host interface and it will continue to use host reserved >> mapping for actual

Re: [Qemu-devel] [RFC v2 0/8] VIRTIO-IOMMU device

On 06/07/17 22:11, Auger Eric wrote: > Hello Bharat, Jean-Philippe, > On 06/07/2017 12:02, Jean-Philippe Brucker wrote: >> On 05/07/17 09:49, Bharat Bhushan wrote:>>> Also when setup msi-route >> kvm_irqchip_add_msi_route() we needed to >>>> provide the tr

Re: [Qemu-devel] [Qemu-arm] [RFC v2 0/8] VIRTIO-IOMMU device

Hi Ashish, On 07/07/17 00:33, Tian, Kevin wrote: >> From: Kalra, Ashish [mailto:ashish.ka...@cavium.com] >> Sent: Friday, July 7, 2017 7:24 AM >> >> I have a generic question on vIOMMU support, is there any proposal/plan to >> add ATS/PRI extension support to vIOMMUs and allow >> handling for end

Re: [Qemu-devel] [RFC v2 0/8] VIRTIO-IOMMU device

On 07/07/17 07:21, Tian, Kevin wrote: > sorry I didn't quite get this part, and here is my understanding: > > Guest programs vIOMMU to map a gIOVA (used by MSI to a GPA > of doorbell register of virtual irqchip. vIOMMU then > triggers VFIO map/unmap to update physical IOMMU page > table for

Re: [Qemu-devel] [RFC v2 0/8] VIRTIO-IOMMU device

On 06/07/17 12:24, Bharat Bhushan wrote: > > >> -Original Message----- >> From: Jean-Philippe Brucker [mailto:jean-philippe.bruc...@arm.com] >> Sent: Thursday, July 06, 2017 3:33 PM >> To: Bharat Bhushan <bharat.bhus...@nxp.com>; Auger Eric &g

Re: [Qemu-devel] [RFC v2 0/8] VIRTIO-IOMMU device

On 05/07/17 09:49, Bharat Bhushan wrote:>>> Also when setup msi-route kvm_irqchip_add_msi_route() we needed to >> provide the translated address. >>> According to my understanding this is required because kernel does no go >> through viommu translation when generating interrupt, no? >> >> yes this

Re: [Qemu-devel] [RFC v2 0/8] VIRTIO-IOMMU device

On 05/07/17 08:25, Tian, Kevin wrote: >> From: Jean-Philippe Brucker [mailto:jean-philippe.bruc...@arm.com] >> Sent: Tuesday, June 27, 2017 12:13 AM >> >> On 26/06/17 09:22, Auger Eric wrote: >>> Hi Jean-Philippe, >>> >>> On 19/06/2017 12:15,

Re: [Qemu-devel] [RFC v2 0/8] VIRTIO-IOMMU device

On 05/07/17 08:14, Tian, Kevin wrote: >> From: Jean-Philippe Brucker [mailto:jean-philippe.bruc...@arm.com] >> Sent: Monday, June 19, 2017 6:15 PM >> >> On 19/06/17 08:54, Bharat Bhushan wrote: >>> Hi Eric, >>> >>> I started added replay

Re: [Qemu-devel] [RFC PATCH 7/8] VFIO: Add new IOCTL for IOMMU TLB invalidate propagation

On 05/07/17 07:45, Tian, Kevin wrote: >> From: Liu, Yi L >> Sent: Monday, July 3, 2017 6:31 PM >> >> Hi Jean, >> >> >>> 2. Define a structure in include/uapi/linux/iommu.h(newly added header >> file) struct iommu_tlb_invalidate { __u32 scope; /* pasid-selective

Re: [Qemu-devel] [RFC PATCH 7/8] VFIO: Add new IOCTL for IOMMU TLB invalidate propagation

Hi Yi, On 02/07/17 11:06, Liu, Yi L wrote: > On Fri, May 12, 2017 at 01:11:02PM +0100, Jean-Philippe Brucker wrote: > > Hi Jean, > > As we've got a few discussions on it. I'd like to have a conclusion and > make it as a reference for future discussion. > > Currently,

Re: [Qemu-devel] [RFC v2 0/8] VIRTIO-IOMMU device

On 26/06/17 09:22, Auger Eric wrote: > Hi Jean-Philippe, > > On 19/06/2017 12:15, Jean-Philippe Brucker wrote: >> On 19/06/17 08:54, Bharat Bhushan wrote: >>> Hi Eric, >>> >>> I started added replay in virtio-iommu and came across how MSI interrupts

Re: [Qemu-devel] [RFC v2 6/8] virtio-iommu: Implement the translation and commands

On 07/06/17 17:01, Eric Auger wrote: > This patch adds the actual implementation for the translation routine > and the virtio-iommu commands. > > Signed-off-by: Eric Auger > > ---[...] > static int virtio_iommu_attach(VirtIOIOMMU *s, >

Re: [Qemu-devel] [RFC v2 3/8] virtio_iommu: add skeleton

On 06/08/2017 12:09 PM, Bharat Bhushan wrote: >> From: Eric Auger [mailto:eric.au...@redhat.com] >> Sent: Wednesday, June 07, 2017 9:31 PM >> To: eric.auger@gmail.com; eric.au...@redhat.com; >> peter.mayd...@linaro.org; alex.william...@redhat.com; m...@redhat.com; >> qemu-...@nongnu.org;

Re: [Qemu-devel] [RFC v2 0/8] VIRTIO-IOMMU device

On 19/06/17 08:54, Bharat Bhushan wrote: > Hi Eric, > > I started added replay in virtio-iommu and came across how MSI interrupts > with work with VFIO. > I understand that on intel this works differently but vsmmu will have same > requirement. > kvm-msi-irq-route are added using the

Re: [Qemu-devel] [RFC 0/8] VIRTIO-IOMMU device

Hi Jason, On 07/06/17 10:17, Jason Wang wrote: > On 2017年06月07日 16:35, Eric Auger wrote: >> This series implements the virtio-iommu device. This is a proof >> of concept based on the virtio-iommu specification written by >> Jean-Philippe Brucker [1]. This was test

Re: [Qemu-devel] [RFC PATCH 1/8] iommu: Introduce bind_pasid_table API function

On 23/05/17 08:50, Liu, Yi L wrote: > On Fri, Apr 28, 2017 at 01:51:42PM +0100, Jean-Philippe Brucker wrote: [...] >>>> >>>> For the next version of my SVM series, I was thinking of passing group >>>> instead of device to iommu_bind. Since all devices in a gr

Re: [Qemu-devel] [RFC PATCH 5/8] VFIO: Add new IOTCL for PASID Table bind propagation

On 17/05/17 11:27, Liu, Yi L wrote: > On Fri, May 12, 2017 at 03:58:51PM -0600, Alex Williamson wrote: >> On Wed, 26 Apr 2017 18:12:02 +0800 >> "Liu, Yi L" wrote: >>> >>> +/* IOCTL for Shared Virtual Memory Bind */ >>> +struct vfio_device_svm { >>> + __u32 argsz; >>>

Re: [Qemu-devel] [RFC PATCH 7/8] VFIO: Add new IOCTL for IOMMU TLB invalidate propagation

On 14/05/17 11:12, Liu, Yi L wrote: > On Fri, May 12, 2017 at 01:11:02PM +0100, Jean-Philippe Brucker wrote: >> Hi Yi, >> >> On 26/04/17 11:12, Liu, Yi L wrote: >>> From: "Liu, Yi L" <yi.l@linux.intel.com> >>> >>> This patch adds

Re: [Qemu-devel] [RFC PATCH 7/8] VFIO: Add new IOCTL for IOMMU TLB invalidate propagation

Hi Yi, On 26/04/17 11:12, Liu, Yi L wrote: > From: "Liu, Yi L" > > This patch adds VFIO_IOMMU_TLB_INVALIDATE to propagate IOMMU TLB > invalidate request from guest to host. > > In the case of SVM virtualization on VT-d, host IOMMU driver has > no knowledge of caching

Re: [Qemu-devel] [RFC PATCH 1/8] iommu: Introduce bind_pasid_table API function

On 28/04/17 10:04, Liu, Yi L wrote: > On Wed, Apr 26, 2017 at 05:56:45PM +0100, Jean-Philippe Brucker wrote: >> Hi Yi, Jacob, >> >> On 26/04/17 11:11, Liu, Yi L wrote: >>> From: Jacob Pan <jacob.jun@linux.intel.com> >>> >>> Virtual IOMMU w

Re: [Qemu-devel] [RFC PATCH 1/8] iommu: Introduce bind_pasid_table API function

On 27/04/17 07:36, Liu, Yi L wrote: > On Wed, Apr 26, 2017 at 05:56:45PM +0100, Jean-Philippe Brucker wrote: >> Hi Yi, Jacob, >> >> On 26/04/17 11:11, Liu, Yi L wrote: >>> From: Jacob Pan <jacob.jun@linux.intel.com> >>> >>> Virtual IOMMU w

Re: [Qemu-devel] [RFC PATCH 1/8] iommu: Introduce bind_pasid_table API function

On 26/04/17 19:29, jacob pan wrote: > On Wed, 26 Apr 2017 17:56:45 +0100 > Jean-Philippe Brucker <jean-philippe.bruc...@arm.com> wrote: > >> Hi Yi, Jacob, >> >> On 26/04/17 11:11, Liu, Yi L wrote: >>> From: Jacob Pan <jacob.jun@linux.intel.com&g

Re: [Qemu-devel] [RFC PATCH 1/8] iommu: Introduce bind_pasid_table API function

Hi Yi, Jacob, On 26/04/17 11:11, Liu, Yi L wrote: > From: Jacob Pan > > Virtual IOMMU was proposed to support Shared Virtual Memory (SVM) use > case in the guest: > https://lists.gnu.org/archive/html/qemu-devel/2016-11/msg05311.html > > As part of the proposed

Re: [Qemu-devel] [RFC PATCH 5/8] VFIO: Add new IOTCL for PASID Table bind propagation

On 26/04/17 11:12, Liu, Yi L wrote: > From: "Liu, Yi L" > > This patch adds VFIO_IOMMU_SVM_BIND_TASK for potential PASID table > binding requests. > > On VT-d, this IOCTL cmd would be used to link the guest PASID page table > to host. While for other vendors, it may

<    1   2   3   4   5