From: Ingo Molnar <mingo@elte.hu>
To: Andreas Herrmann <andreas.herrmann3@amd.com>
Cc: Jaswinder Singh Rajput <jaswinder@kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
x86 maintainers <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [git-pull -tip V2] x86: msr architecture debug code
Date: Thu, 5 Mar 2009 14:32:08 +0100 [thread overview]
Message-ID: <20090305133208.GC4322@elte.hu> (raw)
In-Reply-To: <20090305122157.GA7347@alberich.amd.com>
* Andreas Herrmann <andreas.herrmann3@amd.com> wrote:
> On Thu, Mar 05, 2009 at 02:19:56AM +0530, Jaswinder Singh Rajput wrote:
> > On Thu, 2009-03-05 at 00:46 +0530, Jaswinder Singh Rajput wrote:
> >
> > > The following changes since commit 1d10914bf2c8a1164aef6c341e6c3518a91b8374:
> > > Ingo Molnar (1):
> > > Merge branch 'core/percpu'
> > >
> > > are available in the git repository at:
> > >
> > > git://git.kernel.org/pub/scm/linux/kernel/git/jaswinder/linux-2.6-tip-cpu.git master
> > >
> > > Jaswinder Singh Rajput (1):
> > > x86: msr architecture debug code
>
> Hi,
>
> Why do we need this in-kernel?
> We have already access to MSRs via /dev/cpu/*/msr
>
> Did you have a look at x86info. (see
> http://www.codemonkey.org.uk/projects/x86info/)
> Recent versions contain a tool called lsmsr -- which shows you MSRs
> and also decodes some bits, e.g.
Having debugfs access and a topical splitup of all MSRs (and
possibly other CPU data - not necessarily MSR accessible - such
as the CR bits, etc.) is a nice touch i think and allows the
quick inspection of various properties of a CPU.
> - I've just one directory in debugfs
> x86/cpu/msr/cpu0
> The system has a quad-core CPU. So I guess there should be 4
> directories -- one for each core.
Correct, most MSRs are per core - that needs to be fixed.
Ingo
next prev parent reply other threads:[~2009-03-05 13:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-02 15:42 [git-pull -tip] x86: msr architecture debug code Jaswinder Singh Rajput
2009-03-02 17:25 ` Jaswinder Singh Rajput
2009-03-02 20:54 ` Ingo Molnar
2009-03-04 19:16 ` Jaswinder Singh Rajput
2009-03-04 20:49 ` [git-pull -tip V2] " Jaswinder Singh Rajput
2009-03-05 12:21 ` Andreas Herrmann
2009-03-05 13:10 ` Jaswinder Singh Rajput
2009-03-05 13:32 ` Ingo Molnar [this message]
2009-03-05 13:48 ` Jaswinder Singh Rajput
2009-03-05 14:11 ` Ingo Molnar
2009-03-05 14:31 ` Jaswinder Singh Rajput
2009-03-05 13:54 ` [git-pull -tip] " Andreas Herrmann
2009-03-05 14:08 ` Ingo Molnar
2009-03-05 17:01 ` Andreas Herrmann
2009-03-05 14:12 ` Jaswinder Singh Rajput
2009-03-05 14:37 ` Andreas Herrmann
2009-03-05 15:16 ` Jaswinder Singh Rajput
2009-03-05 15:47 ` Jaswinder Singh Rajput
2009-03-05 18:23 ` Andreas Herrmann
2009-03-05 18:40 ` Jaswinder Singh Rajput
2009-03-06 10:07 ` Andreas Herrmann
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=20090305133208.GC4322@elte.hu \
--to=mingo@elte.hu \
--cc=andreas.herrmann3@amd.com \
--cc=hpa@zytor.com \
--cc=jaswinder@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@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