On 2017年07月12日 15:26, Julien Grall wrote:
> Hi,
>
> On 07/12/2017 04:09 AM, Lan Tianyu wrote:
>> On 2017年07月08日 00:08, Julien Grall wrote:
Because we now just have onE vIOMMU, all virtual interrupt will be
bound
to it. If need to support mult-vIOMMU, we can add device-scope
fie
Hi,
On 07/12/2017 04:09 AM, Lan Tianyu wrote:
On 2017年07月08日 00:08, Julien Grall wrote:
Because we now just have onE vIOMMU, all virtual interrupt will be bound
to it. If need to support mult-vIOMMU, we can add device-scope
field(sbdf array or some thing like that) in the structure and specify
On 2017年07月08日 00:16, Julien Grall wrote:
> Hi,
>
> On 06/07/17 07:20, Lan Tianyu wrote:
>> On 2017年07月05日 21:25, Julien Grall wrote:
>>> Furthermore, on ARM we would be able to create the vIOMMU but it would
>>> be unusable. Indeed, IOMMU are only used to protect devices. But you
>>> don't see an
On 2017年07月08日 00:08, Julien Grall wrote:
>> Because we now just have onE vIOMMU, all virtual interrupt will be bound
>> to it. If need to support mult-vIOMMU, we can add device-scope
>> field(sbdf array or some thing like that) in the structure and specify
>> what devices should be under one vIOMM
Hi,
On 06/07/17 07:20, Lan Tianyu wrote:
On 2017年07月05日 21:25, Julien Grall wrote:
Furthermore, on ARM we would be able to create the vIOMMU but it would
be unusable. Indeed, IOMMU are only used to protect devices. But you
don't see any way to say "This device is protected by the IOMMU". Did I
Hi,
On 06/07/17 04:10, Lan Tianyu wrote:
On 2017年07月05日 21:25, Julien Grall wrote:
+
+- XEN_DOMCTL_create_viommu
+Create vIOMMU device with vIOMMU_type, capabilities, MMIO
+base address and length. Hypervisor returns viommu_id. Capabilities
should
+be in range of value returned by que
On 2017年07月05日 21:25, Julien Grall wrote:
> Furthermore, on ARM we would be able to create the vIOMMU but it would
> be unusable. Indeed, IOMMU are only used to protect devices. But you
> don't see any way to say "This device is protected by the IOMMU". Did I
> miss anything?
The "device protectio
On 2017年07月05日 21:25, Julien Grall wrote:
>
>
> On 05/07/17 04:15, Lan Tianyu wrote:
>> Hi Julien:
>
> Hi Tianyu Lan,
>
>> Thanks for your review.
>>
>> On 2017年07月04日 18:39, Julien Grall wrote:
+vIOMMU hypercall
+
+Introduce new domctl hypercall "xen_domctl_v
On 05/07/17 04:15, Lan Tianyu wrote:
Hi Julien:
Hi Tianyu Lan,
Thanks for your review.
On 2017年07月04日 18:39, Julien Grall wrote:
+vIOMMU hypercall
+
+Introduce new domctl hypercall "xen_domctl_viommu_op" to create/destroy
+vIOMMU and query vIOMMU capabilities that
Hi Julien:
Thanks for your review.
On 2017年07月04日 18:39, Julien Grall wrote:
>> +vIOMMU hypercall
>> +
>> +Introduce new domctl hypercall "xen_domctl_viommu_op" to create/destroy
>> +vIOMMU and query vIOMMU capabilities that device model can support.
>> +
>> +* vIOMMU hyper
Hi,
On 06/29/2017 06:50 AM, Lan Tianyu wrote:
This patch is to add Xen virtual IOMMU doc to introduce motivation,
framework, vIOMMU hypercall and xl configuration.
Signed-off-by: Lan Tianyu
---
docs/misc/viommu.txt | 129 +++
1 file changed, 1
This patch is to add Xen virtual IOMMU doc to introduce motivation,
framework, vIOMMU hypercall and xl configuration.
Signed-off-by: Lan Tianyu
---
docs/misc/viommu.txt | 129 +++
1 file changed, 129 insertions(+)
create mode 100644 docs/misc/viom
12 matches
Mail list logo
