[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4580827F.8080703@zytor.com>
Date: Wed, 13 Dec 2006 14:45:19 -0800
From: "H. Peter Anvin" <hpa@...or.com>
To: Dave Jones <davej@...hat.com>, "H. Peter Anvin" <hpa@...or.com>,
Rudolf Marek <r.marek@...embler.cz>, norsk5@...ssion.com,
lkml <linux-kernel@...r.kernel.org>,
LM Sensors <lm-sensors@...sensors.org>,
bluesmoke-devel@...ts.sourceforge.net
Subject: Re: [RFC] new MSR r/w functions per CPU
Dave Jones wrote:
>
> Can you explain this a little further? I'm fairly certain
> there are places in the kernel already doing this (or similar).
> In fact, I cut-n-pasted most of the above from similar code in the
> powernow-k8 driver. What exactly can we deadlock on?
>
I wanted to change the MSR driver to do the above, and Alan Cox objected
that with realtime priority routines and/or user set affinity, that code
might never be executed, so I retained the IPI-based code (which
executes at the target processor at interrupt priority.)
-hpa
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists