Stefan Hajnoczi writes:
> Hi Alex,
> I'm waiting for a v4 or a confirmation that you've retested and I can
> just drop this patch.
I've re-ordered and I'll post the up to date series with the dropped
patch tomorrow. I was hoping for r-b's for the other patches.
>
> Thanks!
>
> Stefan
--
Al
On Tue, Nov 29, 2022 at 04:01:25PM -0500, Stefan Hajnoczi wrote:
> Hi Alex,
> I'm waiting for a v4 or a confirmation that you've retested and I can
> just drop this patch.
>
> Thanks!
>
> Stefan
Note things need to be reordered, patch 2 should come last.
So I'd really like to see v4 if possible.
Hi Alex,
I'm waiting for a v4 or a confirmation that you've retested and I can
just drop this patch.
Thanks!
Stefan
On Mon, Nov 28, 2022 at 07:39:29PM +, Alex Bennée wrote:
>
> Stefan Hajnoczi writes:
>
> > On Mon, 28 Nov 2022 at 11:42, Alex Bennée wrote:
> >>
> >> There was a disconnect here because vdev->host_features was set to
> >> random rubbish. This caused a weird negotiation between the driver an
Stefan Hajnoczi writes:
> On Mon, 28 Nov 2022 at 11:42, Alex Bennée wrote:
>>
>> There was a disconnect here because vdev->host_features was set to
>> random rubbish. This caused a weird negotiation between the driver and
>> device that took no account of the features provided by the backend.
On Mon, 28 Nov 2022 at 11:42, Alex Bennée wrote:
>
> There was a disconnect here because vdev->host_features was set to
> random rubbish. This caused a weird negotiation between the driver and
> device that took no account of the features provided by the backend.
> To fix this we must set vdev->ho
There was a disconnect here because vdev->host_features was set to
random rubbish. This caused a weird negotiation between the driver and
device that took no account of the features provided by the backend.
To fix this we must set vdev->host_features once we have initialised
the vhost backend.
[AJ
