On Mon, Jan 23, 2017 at 04:59:32PM +0100, Thomas Gleixner wrote:
> On Mon, 23 Jan 2017, Jens Axboe wrote:
>
> > On 01/23/2017 08:33 AM, Chris Wilson wrote:
> > > Allow the user to communicate with the tasklet through the atomic state
> > > field by assigning a bit for their use. This can be used,
On Mon, Jan 23, 2017 at 04:59:32PM +0100, Thomas Gleixner wrote:
> On Mon, 23 Jan 2017, Jens Axboe wrote:
>
> > On 01/23/2017 08:33 AM, Chris Wilson wrote:
> > > Allow the user to communicate with the tasklet through the atomic state
> > > field by assigning a bit for their use. This can be used,
On Mon, 23 Jan 2017, Jens Axboe wrote:
> On 01/23/2017 08:33 AM, Chris Wilson wrote:
> > Allow the user to communicate with the tasklet through the atomic state
> > field by assigning a bit for their use. This can be used, for example,
> > to differentiate between a tasklet called following an
On Mon, 23 Jan 2017, Jens Axboe wrote:
> On 01/23/2017 08:33 AM, Chris Wilson wrote:
> > Allow the user to communicate with the tasklet through the atomic state
> > field by assigning a bit for their use. This can be used, for example,
> > to differentiate between a tasklet called following an
On 01/23/2017 08:33 AM, Chris Wilson wrote:
> Allow the user to communicate with the tasklet through the atomic state
> field by assigning a bit for their use. This can be used, for example,
> to differentiate between a tasklet called following an irq or from
> process context, where some hardware
On 01/23/2017 08:33 AM, Chris Wilson wrote:
> Allow the user to communicate with the tasklet through the atomic state
> field by assigning a bit for their use. This can be used, for example,
> to differentiate between a tasklet called following an irq or from
> process context, where some hardware
Allow the user to communicate with the tasklet through the atomic state
field by assigning a bit for their use. This can be used, for example,
to differentiate between a tasklet called following an irq or from
process context, where some hardware state may only be valid after the
irq.
Allow the user to communicate with the tasklet through the atomic state
field by assigning a bit for their use. This can be used, for example,
to differentiate between a tasklet called following an irq or from
process context, where some hardware state may only be valid after the
irq.
8 matches
Mail list logo