Re: [RFC/PATCH, 2/4] readX_check() performance evaluation

From: David S. Miller <davem_at_redhat.com>
Date: 2004-01-29 09:15:24
On Wed, 28 Jan 2004 13:43:54 -0800 (PST)
Linus Torvalds <torvalds@osdl.org> wrote:

> On Wed, 28 Jan 2004, Andi Kleen wrote:
> >
> > On Wed, 28 Jan 2004 12:28:56 -0800 (PST)
> > Linus Torvalds <torvalds@osdl.org> wrote:
> > 
> > > 
> > > Alternatively, if you get a lot of information at MCE time (CPU that did
> > > the access + some device data), just queue up the information in a per-CPU
> > > queue. You don't have to worry about overflow - you can just drop if if 
> > 
> > That assumes that the access happened with preempt off ?
> 
> Yes. I assume you want _some_ locking anyway, at least within that 
> particular device driver (you don't want to have an irq handler touch the 
> device at the same time you are doing this thing), so any such spinlock 
> would have disabled preemption anyway.

I am rather certain you are going to need to do a per-controller lock
the driver will need to grab during such sequences.  It is the only way
I can see, if the state sits in some controller register or resetting
that status must be done in the controller, to keep two driver inits
or resets or whatever from bumping into each other.
-
To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Received on Wed Jan 28 17:21:19 2004

This archive was generated by hypermail 2.1.8 : 2005-08-02 09:20:21 EST