On Thu, 17 Mar 2022 15:34:53 +0100
Eric Auger wrote:
> Hi Alex,
>
> On 3/17/22 3:23 PM, Alex Williamson wrote:
> > On Thu, 17 Mar 2022 14:57:30 +0100
> > Eric Auger wrote:
> >
> >> Hi Alex,
> >>
> >> On 3/17/22 12:08 AM, Alex Williamson wrote:
> >>> On Wed, 16 Mar 2022 21:29:51 +0100
> >>>
Hi Alex,
On 3/17/22 3:23 PM, Alex Williamson wrote:
> On Thu, 17 Mar 2022 14:57:30 +0100
> Eric Auger wrote:
>
>> Hi Alex,
>>
>> On 3/17/22 12:08 AM, Alex Williamson wrote:
>>> On Wed, 16 Mar 2022 21:29:51 +0100
>>> Eric Auger wrote:
>>>
The CRB command buffer currently is a RAM MemoryReg
On Thu, 17 Mar 2022 14:57:30 +0100
Eric Auger wrote:
> Hi Alex,
>
> On 3/17/22 12:08 AM, Alex Williamson wrote:
> > On Wed, 16 Mar 2022 21:29:51 +0100
> > Eric Auger wrote:
> >
> >> The CRB command buffer currently is a RAM MemoryRegion and given
> >> its base address alignment, it causes an
Hi Alex,
On 3/17/22 12:08 AM, Alex Williamson wrote:
> On Wed, 16 Mar 2022 21:29:51 +0100
> Eric Auger wrote:
>
>> The CRB command buffer currently is a RAM MemoryRegion and given
>> its base address alignment, it causes an error report on
>> vfio_listener_region_add(). This region could have bee
On Wed, 16 Mar 2022 21:29:51 +0100
Eric Auger wrote:
> The CRB command buffer currently is a RAM MemoryRegion and given
> its base address alignment, it causes an error report on
> vfio_listener_region_add(). This region could have been a RAM device
> region, easing the detection of such safe sit
The CRB command buffer currently is a RAM MemoryRegion and given
its base address alignment, it causes an error report on
vfio_listener_region_add(). This region could have been a RAM device
region, easing the detection of such safe situation but this option
was not well received. So let's add a he
