[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <248424c9-04ab-18b1-50f7-b995b6d7b1e2@arm.com>
Date: Tue, 6 Apr 2021 11:54:08 +0530
From: Vivek Kumar Gautam <vivek.gautam@....com>
To: Jean-Philippe Brucker <jean-philippe@...aro.org>
Cc: linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
iommu@...ts.linux-foundation.org,
virtualization@...ts.linux-foundation.org, joro@...tes.org,
will.deacon@....com, mst@...hat.com, robin.murphy@....com,
eric.auger@...hat.com, alex.williamson@...hat.com,
kevin.tian@...el.com, jacob.jun.pan@...ux.intel.com,
yi.l.liu@...el.com, lorenzo.pieralisi@....com,
shameerali.kolothum.thodi@...wei.com
Subject: Re: [PATCH RFC v1 15/15] iommu/virtio: Update fault type and reason
info for viommu fault
On 3/29/21 9:53 PM, Jean-Philippe Brucker wrote:
> On Fri, Mar 12, 2021 at 06:39:05PM +0530, Vivek Kumar Gautam wrote:
>> To complete the page request we would also need to send the response back to
>> the host from virtio backend when handling page request. So the virtio
>> command should also be accompanied with a vfio api to send the page request
>> response back to the host. Isn't it?
>> This is where the host smmuv3 can send PRI_RESP command to the device to
>> complete the page fault.
>
> It looks like Eric already has this in the VFIO series:
> https://lore.kernel.org/linux-iommu/20210223210625.604517-14-eric.auger@redhat.com/
Right, I have taken this change to work on getting the vSVA with
virtio-iommu.
For this I am adding a new request for virtio-iomm -
VIRTIO_IOMMU_T_PAGE_RESP, and related struct virtio_iommu_req_page_resp
that would contain information such as, pasid, grpid, response_code,
flags, and endpoint. This is inline with struct iommu_page_response.
I will post out the patches for this soon.
Thanks & regards
Vivek
>
> Thanks,
> Jean
>
Powered by blists - more mailing lists