From: Robin Murphy Sent: Wednesday, August 28, 2024
12:50 PM
>
> On 2024-08-28 2:03 pm, Petr Tesařík wrote:
> > On Wed, 28 Aug 2024 13:02:31 +0100
> > Robin Murphy wrote:
> >
> >> On 2024-08-22 7:37 pm, mhkelle...@gmail.com wrote:
> >>> From: Michael Kelley
> >>>
> >>> Background
> >>> ===
On 2024-08-28 2:03 pm, Petr Tesařík wrote:
On Wed, 28 Aug 2024 13:02:31 +0100
Robin Murphy wrote:
On 2024-08-22 7:37 pm, mhkelle...@gmail.com wrote:
From: Michael Kelley
Background
==
Linux device drivers may make DMA map/unmap calls in contexts that
cannot block, such as in an inte
On Wed, 28 Aug 2024 16:30:04 +
Michael Kelley wrote:
> From: Petr Tesařík Sent: Wednesday, August 28, 2024 6:04 AM
> >
> > On Wed, 28 Aug 2024 13:02:31 +0100
> > Robin Murphy wrote:
> >
> > > On 2024-08-22 7:37 pm, mhkelle...@gmail.com wrote:
> > > > From: Michael Kelley
> > > >
> >
From: Petr Tesařík Sent: Wednesday, August 28, 2024 6:04 AM
>
> On Wed, 28 Aug 2024 13:02:31 +0100
> Robin Murphy wrote:
>
> > On 2024-08-22 7:37 pm, mhkelle...@gmail.com wrote:
> > > From: Michael Kelley
> > >
> > > Background
> > > ==
> > > Linux device drivers may make DMA map/unmap
On Wed, 28 Aug 2024 13:02:31 +0100
Robin Murphy wrote:
> On 2024-08-22 7:37 pm, mhkelle...@gmail.com wrote:
> > From: Michael Kelley
> >
> > Background
> > ==
> > Linux device drivers may make DMA map/unmap calls in contexts that
> > cannot block, such as in an interrupt handler. Conseq
On 2024-08-22 7:37 pm, mhkelle...@gmail.com wrote:
From: Michael Kelley
Background
==
Linux device drivers may make DMA map/unmap calls in contexts that
cannot block, such as in an interrupt handler. Consequently, when a
DMA map call must use a bounce buffer, the allocation of swiotlb
m
On Tue, 27 Aug 2024 00:26:36 +
Michael Kelley wrote:
> From: Petr Tesařík Sent: Monday, August 26, 2024 12:28 PM
> >
> > On Mon, 26 Aug 2024 16:24:53 +
> > Michael Kelley wrote:
> >
> > > From: Petr Tesařík Sent: Saturday, August 24, 2024
> > > 1:06 PM
> > > >
> > > > On Fri, 23
On Mon, Aug 26, 2024 at 03:27:30PM +, Michael Kelley wrote:
> OK, this makes sense to me. The DMA_ATTR_* symbols are currently
> defined as just values that are not part of an enum or any other higher
> level abstraction, and the "attrs" parameter to the dma_* functions is
> just "unsigned long
From: Petr Tesařík Sent: Monday, August 26, 2024 12:28 PM
>
> On Mon, 26 Aug 2024 16:24:53 +
> Michael Kelley wrote:
>
> > From: Petr Tesařík Sent: Saturday, August 24, 2024 1:06
> > PM
> > >
> > > On Fri, 23 Aug 2024 20:40:16 +
> > > Michael Kelley wrote:
> > >
> > > > From: Petr Te
On Mon, 26 Aug 2024 16:24:53 +
Michael Kelley wrote:
> From: Petr Tesařík Sent: Saturday, August 24, 2024 1:06 PM
> >
> > On Fri, 23 Aug 2024 20:40:16 +
> > Michael Kelley wrote:
> >
> > > From: Petr Tesařík Sent: Thursday, August 22, 2024
> > > 11:45 PM
> > >[...]
> > > > > Dis
From: Petr Tesařík Sent: Saturday, August 24, 2024 1:06 PM
>
> On Fri, 23 Aug 2024 20:40:16 +
> Michael Kelley wrote:
>
> > From: Petr Tesařík Sent: Thursday, August 22, 2024 11:45
> > PM
> >[...]
> > > > Discussion
> > > > ==
> > > > * Since swiotlb isn't visible to device driver
From: Christoph Hellwig Sent: Saturday, August 24, 2024 1:16 AM
>
> On Thu, Aug 22, 2024 at 11:37:11AM -0700, mhkelle...@gmail.com wrote:
> > Because it's not possible to detect at runtime whether a DMA map call
> > is made in a context that can block, the calls in key device drivers
> > must be
On Fri, 23 Aug 2024 20:40:16 +
Michael Kelley wrote:
> From: Petr Tesařík Sent: Thursday, August 22, 2024 11:45 PM
>[...]
> > > Discussion
> > > ==
> > > * Since swiotlb isn't visible to device drivers, I've specifically
> > > named the DMA attribute as MAY_BLOCK instead of MAY_THROT
On Thu, Aug 22, 2024 at 11:37:11AM -0700, mhkelle...@gmail.com wrote:
> Because it's not possible to detect at runtime whether a DMA map call
> is made in a context that can block, the calls in key device drivers
> must be updated with a MAY_BLOCK attribute, if appropriate. When this
> attribute is
On Fri, Aug 23, 2024 at 02:20:41AM +, Michael Kelley wrote:
> Christoph Hellwig, or anyone else who knows the history and current
> reality better than I do, please jump in. :-)
It's not just interrupt context, but any context that does not allow
blocking. There is plenty of that as seen by t
From: Petr Tesařík Sent: Thursday, August 22, 2024 11:45 PM
>
> Hi all,
>
> upfront, I've had more time to consider this idea, because Michael
> kindly shared it with me back in February.
>
> On Thu, 22 Aug 2024 11:37:11 -0700
> mhkelle...@gmail.com wrote:
>
> > From: Michael Kelley
> >
> > B
Hi all,
upfront, I've had more time to consider this idea, because Michael
kindly shared it with me back in February.
On Thu, 22 Aug 2024 11:37:11 -0700
mhkelle...@gmail.com wrote:
> From: Michael Kelley
>
> Background
> ==
> Linux device drivers may make DMA map/unmap calls in context
On Fri, 23 Aug 2024 02:20:41 +
Michael Kelley wrote:
> From: Bart Van Assche Sent: Thursday, August 22, 2024
> 12:29 PM
> >
> > On 8/22/24 11:37 AM, mhkelle...@gmail.com wrote:
> > > Linux device drivers may make DMA map/unmap calls in contexts that
> > > cannot block, such as in an inte
From: Bart Van Assche Sent: Thursday, August 22, 2024
12:29 PM
>
> On 8/22/24 11:37 AM, mhkelle...@gmail.com wrote:
> > Linux device drivers may make DMA map/unmap calls in contexts that
> > cannot block, such as in an interrupt handler.
>
> Although I really appreciate your work, what alternat
On 8/22/24 11:37 AM, mhkelle...@gmail.com wrote:
Linux device drivers may make DMA map/unmap calls in contexts that
cannot block, such as in an interrupt handler.
Although I really appreciate your work, what alternatives have been
considered? How many drivers perform DMA mapping from atomic con
20 matches
Mail list logo
