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

2017-07-16 Thread Tian, Kevin
> From: Jean-Philippe Brucker [mailto:jean-philippe.bruc...@arm.com] > Sent: Friday, July 14, 2017 7:26 PM > > 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, K

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

2017-07-14 Thread Jean-Philippe Brucker
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: >>> >>> Guest programs vIOMMU to map a

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

2017-07-14 Thread Tian, Kevin
> 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: > > > > Guest programs vIOMMU to map a gIOVA (used by MSI to a GPA > > of doorb

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

2017-07-12 Thread Bharat Bhushan
redhat.com; > qemu-...@nongnu.org; qemu-devel@nongnu.org > Cc: w...@redhat.com; kevin.t...@intel.com; marc.zyng...@arm.com; > t...@semihalf.com; will.dea...@arm.com; drjo...@redhat.com; > robin.mur...@arm.com; christoffer.d...@linaro.org > Subject: Re: [Qemu-devel] [RFC v2 0/8] VIRTIO-IOMMU devi

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

2017-07-12 Thread Jean-Philippe Brucker
gt; peter.mayd...@linaro.org; alex.william...@redhat.com; m...@redhat.com; >> qemu-...@nongnu.org; qemu-devel@nongnu.org >> Cc: w...@redhat.com; kevin.t...@intel.com; marc.zyng...@arm.com; >> t...@semihalf.com; will.dea...@arm.com; drjo...@redhat.com; >> robin.mur...@arm.com;

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

2017-07-12 Thread Bharat Bhushan
redhat.com; > qemu-...@nongnu.org; qemu-devel@nongnu.org > Cc: w...@redhat.com; kevin.t...@intel.com; marc.zyng...@arm.com; > t...@semihalf.com; will.dea...@arm.com; drjo...@redhat.com; > robin.mur...@arm.com; christoffer.d...@linaro.org > Subject: Re: [Qemu-devel] [RFC v2 0/8] VIRTIO-IOMMU devi

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

2017-07-12 Thread Jean-Philippe Brucker
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 a

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

2017-07-11 Thread Bharat Bhushan
; qemu-...@nongnu.org; qemu-devel@nongnu.org > Cc: w...@redhat.com; kevin.t...@intel.com; marc.zyng...@arm.com; > t...@semihalf.com; will.dea...@arm.com; drjo...@redhat.com; > robin.mur...@arm.com; christoffer.d...@linaro.org > Subject: Re: [Qemu-devel] [RFC v2 0/8] VIRTIO-IOMMU devi

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

2017-07-11 Thread Jean-Philippe Brucker
com; christoffer.d...@linaro.org >> Subject: 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 t

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

2017-07-10 Thread Bharat Bhushan
redhat.com; > qemu-...@nongnu.org; qemu-devel@nongnu.org > Cc: w...@redhat.com; kevin.t...@intel.com; marc.zyng...@arm.com; > t...@semihalf.com; will.dea...@arm.com; drjo...@redhat.com; > robin.mur...@arm.com; christoffer.d...@linaro.org > Subject: Re: [Qemu-devel] [RFC v2 0/8] VIRTIO-IO

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

2017-07-07 Thread Jean-Philippe Brucker
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 in

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

2017-07-07 Thread Jean-Philippe Brucker
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 translated address. > According to my und

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

2017-07-07 Thread Jean-Philippe Brucker
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 gIOV

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

2017-07-07 Thread Bharat Bhushan
@semihalf.com; will.dea...@arm.com; drjo...@redhat.com; > >>>> robin.mur...@arm.com; christoffer.d...@linaro.org > >>>> Subject: Re: [Qemu-devel] [RFC v2 0/8] VIRTIO-IOMMU device > >>>> > >>>> On 05/07/17 09:49, Bharat Bhushan wrote:>>

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

2017-07-07 Thread Auger Eric
Hi, On 06/07/2017 23: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 translated address. > According to

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

2017-07-07 Thread Auger Eric
gt;>> qemu-...@nongnu.org; qemu-devel@nongnu.org >>>> Cc: w...@redhat.com; kevin.t...@intel.com; marc.zyng...@arm.com; >>>> t...@semihalf.com; will.dea...@arm.com; drjo...@redhat.com; >>>> robin.mur...@arm.com; christoffer.d...@linaro.org >>>> Subject:

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

2017-07-06 Thread Bharat Bhushan
; qemu-...@nongnu.org; qemu-devel@nongnu.org > Cc: w...@redhat.com; kevin.t...@intel.com; marc.zyng...@arm.com; > t...@semihalf.com; will.dea...@arm.com; drjo...@redhat.com; > robin.mur...@arm.com; christoffer.d...@linaro.org > Subject: Re: [Qemu-devel] [RFC v2 0/8] VIRTIO-IOMMU device &

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

2017-07-06 Thread Tian, Kevin
> From: Jean-Philippe Brucker [mailto:jean-philippe.bruc...@arm.com] > Sent: Wednesday, July 5, 2017 8:45 PM > > 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, Bhara

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

2017-07-06 Thread Auger Eric
.mur...@arm.com; christoffer.d...@linaro.org >> Subject: 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 ad

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

2017-07-06 Thread Auger Eric
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 translated address. According to my understanding this is required because kernel do

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

2017-07-06 Thread Jean-Philippe Brucker
gt; peter.mayd...@linaro.org; alex.william...@redhat.com; m...@redhat.com; >> qemu-...@nongnu.org; qemu-devel@nongnu.org >> Cc: w...@redhat.com; kevin.t...@intel.com; marc.zyng...@arm.com; >> t...@semihalf.com; will.dea...@arm.com; drjo...@redhat.com; >> robin.mur...@arm.com; ch

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

2017-07-06 Thread Bharat Bhushan
; qemu-...@nongnu.org; qemu-devel@nongnu.org > Cc: w...@redhat.com; kevin.t...@intel.com; marc.zyng...@arm.com; > t...@semihalf.com; will.dea...@arm.com; drjo...@redhat.com; > robin.mur...@arm.com; christoffer.d...@linaro.org > Subject: Re: [Qemu-devel] [RFC v2 0/8] VIRTIO-IOMMU devi

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

2017-07-06 Thread Jean-Philippe Brucker
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

2017-07-05 Thread Jean-Philippe Brucker
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, Jean-Philippe Brucker wrote: On 19/06/17 08:54, Bha

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

2017-07-05 Thread Jean-Philippe Brucker
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 in virtio-iommu and came across how MSI interrupts >> with wo

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

2017-07-05 Thread Bharat Bhushan
qemu-devel@nongnu.org; jean-philippe.bruc...@arm.com > Cc: w...@redhat.com; kevin.t...@intel.com; marc.zyng...@arm.com; > t...@semihalf.com; will.dea...@arm.com; drjo...@redhat.com; > robin.mur...@arm.com; christoffer.d...@linaro.org > Subject: Re: [Qemu-devel] [RFC v2 0/8] VIRTIO-IOMMU

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

2017-07-05 Thread Auger Eric
r Eric [mailto:eric.au...@redhat.com] >>>> Sent: Friday, June 09, 2017 5:24 PM >>>> To: Bharat Bhushan ; >>>> eric.auger@gmail.com; peter.mayd...@linaro.org; >>>> alex.william...@redhat.com; m...@redhat.com; qemu-...@nongnu.org; >>>> qemu-

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

2017-07-05 Thread Bharat Bhushan
qemu-devel@nongnu.org; jean-philippe.bruc...@arm.com > Cc: w...@redhat.com; kevin.t...@intel.com; marc.zyng...@arm.com; > t...@semihalf.com; will.dea...@arm.com; drjo...@redhat.com; > robin.mur...@arm.com; christoffer.d...@linaro.org > Subject: Re: [Qemu-devel] [RFC v2 0/8] VIRTIO-IOMMU dev

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

2017-07-05 Thread Tian, Kevin
> 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, Jean-Philippe Brucker wrote: > >> On 19/06/17 08:54, Bharat Bhushan wrote: > >>> Hi Eric, > >>> >

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

2017-07-05 Thread Bharat Bhushan
redhat.com; > qemu-...@nongnu.org; qemu-devel@nongnu.org > Cc: w...@redhat.com; kevin.t...@intel.com; marc.zyng...@arm.com; > t...@semihalf.com; will.dea...@arm.com; drjo...@redhat.com; > robin.mur...@arm.com; christoffer.d...@linaro.org > Subject: Re: [Qemu-devel] [RFC v2 0/8] VIRTIO-IO

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

2017-07-05 Thread Tian, Kevin
> 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 in virtio-iommu and came across how MSI interrupts > with work with VFIO. > > I understand that on int

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

2017-06-27 Thread Auger Eric
Hi, On 27/06/2017 10:46, Will Deacon wrote: > Hi Eric, > > On Tue, Jun 27, 2017 at 08:38:48AM +0200, Auger Eric wrote: >> On 26/06/2017 18:13, Jean-Philippe Brucker wrote: >>> On 26/06/17 09:22, Auger Eric wrote: On 19/06/2017 12:15, Jean-Philippe Brucker wrote: > On 19/06/17 08:54, Bhar

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

2017-06-27 Thread Will Deacon
Hi Eric, On Tue, Jun 27, 2017 at 08:38:48AM +0200, Auger Eric wrote: > On 26/06/2017 18:13, Jean-Philippe Brucker wrote: > > On 26/06/17 09:22, Auger Eric wrote: > >> On 19/06/2017 12:15, Jean-Philippe Brucker wrote: > >>> On 19/06/17 08:54, Bharat Bhushan wrote: > I started added replay in v

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

2017-06-26 Thread Auger Eric
Hi Jean-Philippe, On 26/06/2017 18:13, Jean-Philippe Brucker wrote: > 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 ca

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

2017-06-26 Thread Jean-Philippe Brucker
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 >>> with work with VFIO. >>> I understand that

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

2017-06-26 Thread Auger Eric
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 >> with work with VFIO. >> I understand that on intel this works differently but vsmmu will h

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

2017-06-26 Thread Auger Eric
ill.dea...@arm.com; drjo...@redhat.com; >> robin.mur...@arm.com; christoffer.d...@linaro.org >> Subject: Re: [Qemu-devel] [RFC v2 0/8] VIRTIO-IOMMU device >> >> Hi Bharat, >> >> On 09/06/2017 13:30, Bharat Bhushan wrote: >>> Hi Eric, >>>

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

2017-06-19 Thread Jean-Philippe Brucker
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 msi-addre

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

2017-06-19 Thread Bharat Bhushan
com; > robin.mur...@arm.com; christoffer.d...@linaro.org > Subject: Re: [Qemu-devel] [RFC v2 0/8] VIRTIO-IOMMU device > > Hi Bharat, > > On 09/06/2017 13:30, Bharat Bhushan wrote: > > Hi Eric, > > > >> -Original Message- > >> From: Auger Eric [mail

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

2017-06-09 Thread Auger Eric
Hi, On 09/06/2017 13:30, Bharat Bhushan wrote: > Hi Eric, > >> -Original Message- >> From: Auger Eric [mailto:eric.au...@redhat.com] >> Sent: Friday, June 09, 2017 12:14 PM >> To: Bharat Bhushan ; >> eric.auger@gmail.com; peter.mayd...@linaro.org; >> alex.william...@redhat.com; m...@r

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

2017-06-09 Thread Auger Eric
Hi Bharat, On 09/06/2017 13:30, Bharat Bhushan wrote: > Hi Eric, > >> -Original Message- >> From: Auger Eric [mailto:eric.au...@redhat.com] >> Sent: Friday, June 09, 2017 12:14 PM >> To: Bharat Bhushan ; >> eric.auger@gmail.com; peter.mayd...@linaro.org; >> alex.william...@redhat.com;

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

2017-06-09 Thread Bharat Bhushan
Hi Eric, > -Original Message- > From: Auger Eric [mailto:eric.au...@redhat.com] > Sent: Friday, June 09, 2017 12:14 PM > To: Bharat Bhushan ; > eric.auger@gmail.com; peter.mayd...@linaro.org; > alex.william...@redhat.com; m...@redhat.com; qemu-...@nongnu.org; > qemu-devel@nongnu.org; j

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

2017-06-08 Thread Auger Eric
Hi Bharat, On 09/06/2017 08:16, Bharat Bhushan wrote: > Hi Eric, > >> -Original Message- >> 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

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

2017-06-08 Thread Bharat Bhushan
Hi Eric, > -Original Message- > 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; qemu-devel@nongnu.

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

2017-06-07 Thread Eric Auger
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 tested with a guest using the virtio-iommu driver [2] and exposed with a virtio-net-pci using dma ops. The device gets instantiated usin