From: Martin Waitz <tali@admingilde.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org
Subject: weird semantics of cpu/*/msr
Date: Fri, 11 Oct 2002 00:52:21 +0200 [thread overview]
Message-ID: <20021010225221.GA1552@admingilde.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1281 bytes --]
hi :)
the i386 msr driver is a bit strange:
* when reading/writing, it does not update the file position/msr register
* file position is used directly as msr register
that is, reads with count>8 do read from the same register multiple
times, and writes overwrite themselves.
i would expect the following semantics:
* file position is (msr register * 8). position%8!=0 is invalid
* read/write updating file position.
that would make it possible to write/read multiple MSRs with one
syscall, which is very handy when initializing P4 performance counters.
should i implement that behaviour?
of course it would break binary compatibility with existing
uses of that drivers.
perhaps we would need a new location for the new api.
comments?
--
CU, / Friedrich-Alexander University Erlangen, Germany
Martin Waitz // [Tali on IRCnet] [tali.home.pages.de] _________
______________/// - - - - - - - - - - - - - - - - - - - - ///
dies ist eine manuell generierte mail, sie beinhaltet //
tippfehler und ist auch ohne grossbuchstaben gueltig. /
-
Wer bereit ist, grundlegende Freiheiten aufzugeben, um sich
kurzfristige Sicherheit zu verschaffen, der hat weder Freiheit
noch Sicherheit verdient.
Benjamin Franklin (1706 - 1790)
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2002-10-10 22:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-10 22:52 Martin Waitz [this message]
2002-10-10 22:55 ` weird semantics of cpu/*/msr 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=20021010225221.GA1552@admingilde.org \
--to=tali@admingilde.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox