Phil,
Did you accidentally miss this in your pull request [1] or did you
leave it out intentionally?
It's still missing the Reviewed bit after the atomic cmpxchg change
prompted by the size_t switch, so that might be the reason - I'm just
trying to figure out what the next step is for this patch.
On Tue, May 7, 2024 at 4:46 PM Philippe Mathieu-Daudé wrote:
>
> On 7/5/24 16:04, Mattias Nissler wrote:
> > On Tue, May 7, 2024 at 2:57 PM Philippe Mathieu-Daudé
> > wrote:
> >>
> >> On 7/5/24 11:42, Mattias Nissler wrote:
> >>> When DMA memory can't be directly accessed, as is the case when
>
On 7/5/24 16:04, Mattias Nissler wrote:
On Tue, May 7, 2024 at 2:57 PM Philippe Mathieu-Daudé wrote:
On 7/5/24 11:42, Mattias Nissler wrote:
When DMA memory can't be directly accessed, as is the case when
running the device model in a separate process without shareable DMA
file descriptors, b
On Tue, May 7, 2024 at 2:57 PM Philippe Mathieu-Daudé wrote:
>
> On 7/5/24 11:42, Mattias Nissler wrote:
> > When DMA memory can't be directly accessed, as is the case when
> > running the device model in a separate process without shareable DMA
> > file descriptors, bounce buffering is used.
> >
On 7/5/24 11:42, Mattias Nissler wrote:
When DMA memory can't be directly accessed, as is the case when
running the device model in a separate process without shareable DMA
file descriptors, bounce buffering is used.
It is not uncommon for device models to request mapping of several DMA
regions
When DMA memory can't be directly accessed, as is the case when
running the device model in a separate process without shareable DMA
file descriptors, bounce buffering is used.
It is not uncommon for device models to request mapping of several DMA
regions at the same time. Examples include:
* net
