Zachary Amsden wrote:
George Anzinger wrote:
Nick Piggin wrote:
George Anzinger wrote:
The NMI entry and exit code fiddles with bits in the preempt count.
If an NMI happens while some other code is doing the same, bits will
be lost. This patch removes this modify code from the NMI path t
George Anzinger wrote:
Nick Piggin wrote:
George Anzinger wrote:
The NMI entry and exit code fiddles with bits in the preempt count.
If an NMI happens while some other code is doing the same, bits will
be lost. This patch removes this modify code from the NMI path till
we can come up wit
On Fri, 12 Aug 2005, George Anzinger wrote:
>
> The NMI entry and exit code fiddles with bits in the preempt count. If
> an NMI happens while some other code is doing the same, bits will be
> lost.
Why?
Even if an NMI happens in the middle of a read-modify-write sequence that
is critical, t
Nick Piggin wrote:
George Anzinger wrote:
The NMI entry and exit code fiddles with bits in the preempt count.
If an NMI happens while some other code is doing the same, bits will
be lost. This patch removes this modify code from the NMI path till
we can come up with something better.
Hu
George Anzinger wrote:
The NMI entry and exit code fiddles with bits in the preempt count. If
an NMI happens while some other code is doing the same, bits will be
lost. This patch removes this modify code from the NMI path till we can
come up with something better.
Humour me for a minute
The NMI entry and exit code fiddles with bits in the preempt count. If
an NMI happens while some other code is doing the same, bits will be
lost. This patch removes this modify code from the NMI path till we can
come up with something better.
--
George Anzinger george@mvista.com
HRT (High-r
6 matches
Mail list logo