From: hpa@zytor.com (H. Peter Anvin)
To: Dave Jones <davej@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Rudolf Marek <r.marek@assembler.cz>,
norsk5@xmission.com, lkml <linux-kernel@vger.kernel.org>,
LM Sensors <lm-sensors@lm-sensors.org>,
bluesmoke-devel@lists.sourceforge.net
Subject: [lm-sensors] [RFC] new MSR r/w functions per CPU
Date: Wed, 13 Dec 2006 22:45:19 +0000 [thread overview]
Message-ID: <4580827F.8080703@zytor.com> (raw)
In-Reply-To: <20061213222616.GJ2418@redhat.com>
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
WARNING: multiple messages have this Message-ID (diff)
From: "H. Peter Anvin" <hpa@zytor.com>
To: Dave Jones <davej@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Rudolf Marek <r.marek@assembler.cz>,
norsk5@xmission.com, lkml <linux-kernel@vger.kernel.org>,
LM Sensors <lm-sensors@lm-sensors.org>,
bluesmoke-devel@lists.sourceforge.net
Subject: Re: [RFC] new MSR r/w functions per CPU
Date: Wed, 13 Dec 2006 14:45:19 -0800 [thread overview]
Message-ID: <4580827F.8080703@zytor.com> (raw)
In-Reply-To: <20061213222616.GJ2418@redhat.com>
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
next prev parent reply other threads:[~2006-12-13 22:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-13 21:45 [lm-sensors] [RFC] new MSR r/w functions per CPU Rudolf Marek
2006-12-13 21:45 ` Rudolf Marek
2006-12-13 22:01 ` [lm-sensors] " H. Peter Anvin
2006-12-13 22:01 ` H. Peter Anvin
2006-12-13 22:10 ` [lm-sensors] " Dave Jones
2006-12-13 22:10 ` Dave Jones
2006-12-13 22:19 ` [lm-sensors] " H. Peter Anvin
2006-12-13 22:19 ` H. Peter Anvin
2006-12-13 22:26 ` [lm-sensors] " Dave Jones
2006-12-13 22:26 ` Dave Jones
2006-12-13 22:45 ` H. Peter Anvin [this message]
2006-12-13 22:45 ` H. Peter Anvin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4580827F.8080703@zytor.com \
--to=hpa@zytor.com \
--cc=bluesmoke-devel@lists.sourceforge.net \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lm-sensors@lm-sensors.org \
--cc=norsk5@xmission.com \
--cc=r.marek@assembler.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.