On 19/06/15 16:15, Ross Lagerwall wrote:
> When a CPU is offlined, there may be unprocessed events on a port for
> that CPU. If the port is subsequently reused on a different CPU, it
> could be in an unexpected state with the link bit set, resulting in
> interrupts being missed. Fix this by consum
On 30/06/15 13:26, Boris Ostrovsky wrote:
> On 06/30/2015 05:51 AM, Ross Lagerwall wrote:
>> On 06/29/2015 02:32 PM, Boris Ostrovsky wrote:
>>> On 06/29/2015 06:19 AM, Ross Lagerwall wrote:
On 06/19/2015 05:06 PM, David Vrabel wrote:
> On 19/06/15 17:02, Boris Ostrovsky wrote:
>> On 06
On 06/30/2015 05:51 AM, Ross Lagerwall wrote:
On 06/29/2015 02:32 PM, Boris Ostrovsky wrote:
On 06/29/2015 06:19 AM, Ross Lagerwall wrote:
On 06/19/2015 05:06 PM, David Vrabel wrote:
On 19/06/15 17:02, Boris Ostrovsky wrote:
On 06/19/2015 11:15 AM, Ross Lagerwall wrote:
When a CPU is offlined
On 06/29/2015 02:32 PM, Boris Ostrovsky wrote:
On 06/29/2015 06:19 AM, Ross Lagerwall wrote:
On 06/19/2015 05:06 PM, David Vrabel wrote:
On 19/06/15 17:02, Boris Ostrovsky wrote:
On 06/19/2015 11:15 AM, Ross Lagerwall wrote:
When a CPU is offlined, there may be unprocessed events on a port fo
On 06/29/2015 06:19 AM, Ross Lagerwall wrote:
On 06/19/2015 05:06 PM, David Vrabel wrote:
On 19/06/15 17:02, Boris Ostrovsky wrote:
On 06/19/2015 11:15 AM, Ross Lagerwall wrote:
When a CPU is offlined, there may be unprocessed events on a port for
that CPU. If the port is subsequently reused
On 06/19/2015 05:06 PM, David Vrabel wrote:
On 19/06/15 17:02, Boris Ostrovsky wrote:
On 06/19/2015 11:15 AM, Ross Lagerwall wrote:
When a CPU is offlined, there may be unprocessed events on a port for
that CPU. If the port is subsequently reused on a different CPU, it
could be in an unexpecte
On 19/06/15 17:02, Boris Ostrovsky wrote:
> On 06/19/2015 11:15 AM, Ross Lagerwall wrote:
>> When a CPU is offlined, there may be unprocessed events on a port for
>> that CPU. If the port is subsequently reused on a different CPU, it
>> could be in an unexpected state with the link bit set, result
On 06/19/2015 11:15 AM, Ross Lagerwall wrote:
When a CPU is offlined, there may be unprocessed events on a port for
that CPU. If the port is subsequently reused on a different CPU, it
could be in an unexpected state with the link bit set, resulting in
interrupts being missed. Fix this by consumi
When a CPU is offlined, there may be unprocessed events on a port for
that CPU. If the port is subsequently reused on a different CPU, it
could be in an unexpected state with the link bit set, resulting in
interrupts being missed. Fix this by consuming any unprocessed events
for a particular CPU w
