Displaying 2 results from an estimated 2 matches for "73fa21ea4fc6".
2019 Apr 10
0
[RFC PATCH 10/12] virtio/s390: consolidate DMA allocations
...aligned. But I did not look to hard.
>
> The ccw.cda can hold an arbitrary data address AFAIR (for indirect,
> of course we do have alignment requirements).
I think it needs to be doubleword aligned.
>
> Apparently status used to be a normal field, and became a pointer with
> 73fa21ea4fc6 "KVM: s390: Dynamic allocation of virtio-ccw I/O
> data." (Cornelia Huck, 2013-01-07). I could not quite figure out why.
In the beginning, the code used a below-2G-area for all commands.
Rather than adding locking to avoid races there, that commit switches
to allocating the needed str...
2019 Apr 11
0
[RFC PATCH 10/12] virtio/s390: consolidate DMA allocations
...e with a reference that proves me
> wrong if I'm wrong.
Ah, it was the ccw itself, not the cda. Indeed, there do not seem to be
any requirements for direct addressing.
>
> > >
> > > Apparently status used to be a normal field, and became a pointer with
> > > 73fa21ea4fc6 "KVM: s390: Dynamic allocation of virtio-ccw I/O
> > > data." (Cornelia Huck, 2013-01-07). I could not quite figure out why.
> >
> > In the beginning, the code used a below-2G-area for all commands.
> > Rather than adding locking to avoid races there, that co...