From: Christian Koenig
1. It is really dangerous to have more than one
spinlock protecting the same information.
2. radeon_irq_set sometimes wasn't called with lock
protection, so it can happen that more than one
CPU would tamper with the irq regs at the same
From: Christian Koenig christian.koe...@amd.com
1. It is really dangerous to have more than one
spinlock protecting the same information.
2. radeon_irq_set sometimes wasn't called with lock
protection, so it can happen that more than one
CPU would tamper with the irq regs at the same
From: Christian Koenig
1. It is really dangerous to have more than one
spinlock protecting the same information.
2. radeon_irq_set sometimes wasn't called with lock
protection, so it can happen that more than one
CPU would tamper with the irq regs at the same
On 31.05.2012 20:15, Alex Deucher wrote:
> On Thu, May 24, 2012 at 11:35 AM, Alex Deucher
> wrote:
>> On Thu, May 24, 2012 at 3:49 AM, Christian K?nig
>> wrote:
>>> From: Christian Koenig
>>>
>>> 1. It is really dangerous to have more than one
>>>spinlock protecting the same information.
On Thu, May 31, 2012 at 4:16 PM, Christian K?nig
wrote:
> From: Christian Koenig
>
> 1. It is really dangerous to have more than one
> ? spinlock protecting the same information.
>
> 2. radeon_irq_set sometimes wasn't called with lock
> ? protection, so it can happen that more than one
> ? CPU
On Thu, May 31, 2012 at 2:15 PM, Alex Deucher wrote:
> On Thu, May 24, 2012 at 11:35 AM, Alex Deucher
> wrote:
>> On Thu, May 24, 2012 at 3:49 AM, Christian K?nig
>> wrote:
>>> From: Christian Koenig
>>>
>>> 1. It is really dangerous to have more than one
>>> ? spinlock protecting the same
On Thu, May 24, 2012 at 11:35 AM, Alex Deucher wrote:
> On Thu, May 24, 2012 at 3:49 AM, Christian K?nig
> wrote:
>> From: Christian Koenig
>>
>> 1. It is really dangerous to have more than one
>> ? spinlock protecting the same information.
>>
>> 2. radeon_irq_set sometimes wasn't called with
On Thu, May 24, 2012 at 11:35 AM, Alex Deucher alexdeuc...@gmail.com wrote:
On Thu, May 24, 2012 at 3:49 AM, Christian König
deathsim...@vodafone.de wrote:
From: Christian Koenig christian.koe...@amd.com
1. It is really dangerous to have more than one
spinlock protecting the same
On Thu, May 31, 2012 at 2:15 PM, Alex Deucher alexdeuc...@gmail.com wrote:
On Thu, May 24, 2012 at 11:35 AM, Alex Deucher alexdeuc...@gmail.com wrote:
On Thu, May 24, 2012 at 3:49 AM, Christian König
deathsim...@vodafone.de wrote:
From: Christian Koenig christian.koe...@amd.com
1. It is
On 31.05.2012 20:15, Alex Deucher wrote:
On Thu, May 24, 2012 at 11:35 AM, Alex Deucheralexdeuc...@gmail.com wrote:
On Thu, May 24, 2012 at 3:49 AM, Christian König
deathsim...@vodafone.de wrote:
From: Christian Koenigchristian.koe...@amd.com
1. It is really dangerous to have more than one
From: Christian Koenig christian.koe...@amd.com
1. It is really dangerous to have more than one
spinlock protecting the same information.
2. radeon_irq_set sometimes wasn't called with lock
protection, so it can happen that more than one
CPU would tamper with the irq regs at the same
On Thu, May 24, 2012 at 11:35:15AM -0400, Alex Deucher wrote:
> On Thu, May 24, 2012 at 3:49 AM, Christian K?nig
> wrote:
> > From: Christian Koenig
> >
> > 1. It is really dangerous to have more than one
> > ? spinlock protecting the same information.
> >
> > 2. radeon_irq_set sometimes wasn't
On Thu, May 24, 2012 at 3:49 AM, Christian K?nig
wrote:
> From: Christian Koenig
>
> 1. It is really dangerous to have more than one
> ? spinlock protecting the same information.
>
> 2. radeon_irq_set sometimes wasn't called with lock
> ? protection, so it can happen that more than one
> ? CPU
From: Christian Koenig
1. It is really dangerous to have more than one
spinlock protecting the same information.
2. radeon_irq_set sometimes wasn't called with lock
protection, so it can happen that more than one
CPU would tamper with the irq regs at the same
From: Christian Koenig christian.koe...@amd.com
1. It is really dangerous to have more than one
spinlock protecting the same information.
2. radeon_irq_set sometimes wasn't called with lock
protection, so it can happen that more than one
CPU would tamper with the irq regs at the same
On Thu, May 24, 2012 at 3:49 AM, Christian König
deathsim...@vodafone.de wrote:
From: Christian Koenig christian.koe...@amd.com
1. It is really dangerous to have more than one
spinlock protecting the same information.
2. radeon_irq_set sometimes wasn't called with lock
protection, so it
On Thu, May 24, 2012 at 11:35:15AM -0400, Alex Deucher wrote:
On Thu, May 24, 2012 at 3:49 AM, Christian König
deathsim...@vodafone.de wrote:
From: Christian Koenig christian.koe...@amd.com
1. It is really dangerous to have more than one
spinlock protecting the same information.
2.
17 matches
Mail list logo