On Thu, 26 Feb 2015, Daniel Thompson wrote:
> On Thu, 2015-02-26 at 15:31 -0500, Nicolas Pitre wrote:
> > On Tue, 3 Feb 2015, Daniel Thompson wrote:
> >
> > > Currently gic_raise_softirq() is locked using upon irq_controller_lock.
> > > This lock is primarily used to make register
On Thu, 2015-02-26 at 15:31 -0500, Nicolas Pitre wrote:
> On Tue, 3 Feb 2015, Daniel Thompson wrote:
>
> > Currently gic_raise_softirq() is locked using upon irq_controller_lock.
> > This lock is primarily used to make register read-modify-write sequences
> > atomic but gic_raise_softirq() uses
On Tue, 3 Feb 2015, Daniel Thompson wrote:
> Currently gic_raise_softirq() is locked using upon irq_controller_lock.
> This lock is primarily used to make register read-modify-write sequences
> atomic but gic_raise_softirq() uses it instead to ensure that the
> big.LITTLE migration logic can
On Tue, 3 Feb 2015, Daniel Thompson wrote:
Currently gic_raise_softirq() is locked using upon irq_controller_lock.
This lock is primarily used to make register read-modify-write sequences
atomic but gic_raise_softirq() uses it instead to ensure that the
big.LITTLE migration logic can figure
On Thu, 2015-02-26 at 15:31 -0500, Nicolas Pitre wrote:
On Tue, 3 Feb 2015, Daniel Thompson wrote:
Currently gic_raise_softirq() is locked using upon irq_controller_lock.
This lock is primarily used to make register read-modify-write sequences
atomic but gic_raise_softirq() uses it
On Thu, 26 Feb 2015, Daniel Thompson wrote:
On Thu, 2015-02-26 at 15:31 -0500, Nicolas Pitre wrote:
On Tue, 3 Feb 2015, Daniel Thompson wrote:
Currently gic_raise_softirq() is locked using upon irq_controller_lock.
This lock is primarily used to make register read-modify-write
6 matches
Mail list logo
