On Wed, Feb 09 2022, Eric Auger wrote:
> Hi,
>
> On 2/9/22 12:10 PM, Cornelia Huck wrote:
>> On Tue, Feb 08 2022, "Michael S. Tsirkin" wrote:
>>
>>> On Tue, Feb 08, 2022 at 06:42:57PM +0100, Cornelia Huck wrote:
On Thu, Jan 27 2022, Jean-Philippe Brucker
wrote:
> @@ -988,9 +
Hi,
On 2/9/22 12:10 PM, Cornelia Huck wrote:
> On Tue, Feb 08 2022, "Michael S. Tsirkin" wrote:
>
>> On Tue, Feb 08, 2022 at 06:42:57PM +0100, Cornelia Huck wrote:
>>> On Thu, Jan 27 2022, Jean-Philippe Brucker wrote:
>>>
@@ -988,9 +1025,9 @@ static void virtio_iommu_device_realize(DeviceSt
On Tue, Feb 08 2022, "Michael S. Tsirkin" wrote:
> On Tue, Feb 08, 2022 at 06:42:57PM +0100, Cornelia Huck wrote:
>> On Thu, Jan 27 2022, Jean-Philippe Brucker wrote:
>>
>> > @@ -988,9 +1025,9 @@ static void virtio_iommu_device_realize(DeviceState
>> > *dev, Error **errp)
>> > virtio_add_
On Tue, Feb 08, 2022 at 06:42:57PM +0100, Cornelia Huck wrote:
> On Thu, Jan 27 2022, Jean-Philippe Brucker wrote:
>
> > @@ -988,9 +1025,9 @@ static void virtio_iommu_device_realize(DeviceState
> > *dev, Error **errp)
> > virtio_add_feature(&s->features, VIRTIO_IOMMU_F_INPUT_RANGE);
> >
On Thu, Jan 27 2022, Jean-Philippe Brucker wrote:
> @@ -988,9 +1025,9 @@ static void virtio_iommu_device_realize(DeviceState
> *dev, Error **errp)
> virtio_add_feature(&s->features, VIRTIO_IOMMU_F_INPUT_RANGE);
> virtio_add_feature(&s->features, VIRTIO_IOMMU_F_DOMAIN_RANGE);
> vir
On 1/27/22 3:29 PM, Jean-Philippe Brucker wrote:
> Currently the virtio-iommu device must be programmed before it allows
> DMA from any PCI device. This can make the VM entirely unusable when a
> virtio-iommu driver isn't present, for example in a bootloader that
> loads the OS from storage.
>
>
Currently the virtio-iommu device must be programmed before it allows
DMA from any PCI device. This can make the VM entirely unusable when a
virtio-iommu driver isn't present, for example in a bootloader that
loads the OS from storage.
Similarly to the other vIOMMU implementations, default to DMA
