xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Borislav Petkov <borislav.petkov@amd.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Borislav Petkov <bp@amd64.org>, "H. Peter Anvin" <hpa@zytor.com>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	Jacob Shin <jacob.shin@amd.com>,
	Andre Przywara <andre.przywara@amd.com>,
	jeremy@goop.org, xen-devel@lists.xensource.com,
	LKML <linux-kernel@vger.kernel.org>,
	Jan Beulich <JBeulich@suse.com>, Ingo Molnar <mingo@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH 2/4] x86, CPU: Fix show_msr MSR accessing function
Date: Sat, 2 Jun 2012 00:50:30 +0200	[thread overview]
Message-ID: <20120601225030.GC30418@aftab.osrc.amd.com> (raw)
In-Reply-To: <CAE9FiQVad9qWvZeBej31Mw4aEJO3L0L6ZC7mx7VJQwRB_q8fzQ@mail.gmail.com>

On Fri, Jun 01, 2012 at 11:22:03AM -0700, Yinghai Lu wrote:
> can you double check if the range will need special passcode ?
> 
>         { 0x00000000, 0x00000418},
>         { 0xc0000000, 0xc000040b},
>         { 0xc0010000, 0xc0010142},
>         { 0xc0011000, 0xc001103b},
> 
> passcode should be
>        gprs[7] = 0x9c5a203a;

This currently reads the MSRs it can read without the passcode. There's
no reason I'm aware of to access the other MSRs.

-- 
Regards/Gruss,
Boris.

Advanced Micro Devices GmbH
Einsteinring 24, 85609 Dornach
GM: Alberto Bozzo
Reg: Dornach, Landkreis Muenchen
HRB Nr. 43632 WEEE Registernr: 129 19551

  reply	other threads:[~2012-06-01 22:50 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-01 14:52 [PATCH 0/4] x86, CPU, AMD: Cleanup AMD-specific MSR-rw users Borislav Petkov
2012-06-01 14:52 ` [PATCH 1/4] x86, pvops: Remove hooks for {rd, wr}msr_safe_regs Borislav Petkov
2012-06-06 20:06   ` [PATCH 1/4] x86, pvops: Remove hooks for {rd,wr}msr_safe_regs Konrad Rzeszutek Wilk
2012-06-01 14:52 ` [PATCH 2/4] x86, CPU: Fix show_msr MSR accessing function Borislav Petkov
2012-06-01 18:22   ` Yinghai Lu
2012-06-01 22:50     ` Borislav Petkov [this message]
2012-06-06 20:07   ` Konrad Rzeszutek Wilk
2012-06-01 14:52 ` [PATCH 3/4] x86, AMD: Fix crash as Xen Dom0 on AMD Trinity systems Borislav Petkov
2012-06-06 20:07   ` Konrad Rzeszutek Wilk
2012-06-06 22:00   ` H. Peter Anvin
2012-06-07  7:21     ` Borislav Petkov
2012-06-07  7:49       ` Andre Przywara
2012-06-07  8:08         ` Greg KH
2012-06-07  8:18           ` Andre Przywara
2012-06-07 13:25             ` [GIT PULL] x86, CPU, AMD: Cleanup AMD-specific MSR-rw users Borislav Petkov
2012-06-07 16:27           ` [PATCH 3/4] x86, AMD: Fix crash as Xen Dom0 on AMD Trinity systems H. Peter Anvin
2012-06-01 14:52 ` [PATCH 4/4] x86, CPU, AMD: Deprecate AMD-specific MSR variants Borislav Petkov
2012-06-06 20:07   ` Konrad Rzeszutek Wilk
2012-06-01 14:53 ` [PATCH 0/4] x86, CPU, AMD: Cleanup AMD-specific MSR-rw users H. Peter Anvin
2012-06-01 14:57   ` Borislav Petkov
2012-06-01 15:06     ` 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=20120601225030.GC30418@aftab.osrc.amd.com \
    --to=borislav.petkov@amd.com \
    --cc=JBeulich@suse.com \
    --cc=andre.przywara@amd.com \
    --cc=bp@amd64.org \
    --cc=hpa@zytor.com \
    --cc=jacob.shin@amd.com \
    --cc=jeremy@goop.org \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=xen-devel@lists.xensource.com \
    --cc=yinghai@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;
as well as URLs for NNTP newsgroup(s).