From: Borislav Petkov <bp@suse.de>
To: Aravind Gopalakrishnan <aravind.gopalakrishnan@amd.com>
Cc: a.p.zijlstra@chello.nl, paulus@samba.org, mingo@redhat.com,
acme@kernel.org, tglx@linutronix.de, hpa@zytor.com,
x86@kernel.org, linux-kernel@vger.kernel.org,
Paolo Bonzini <pbonzini@redhat.com>,
Jan Kiszka <jan.kiszka@siemens.com>,
Len Brown <len.brown@intel.com>,
Fenghua Yu <fenghua.yu@intel.com>
Subject: Re: [PATCH] perf, amd, ibs: Update IBS MSRs and feature definitions
Date: Sat, 8 Nov 2014 10:03:55 +0100 [thread overview]
Message-ID: <20141108090355.GB14837@pd.tnic> (raw)
In-Reply-To: <545BA884.5040406@amd.com>
On Thu, Nov 06, 2014 at 10:57:40AM -0600, Aravind Gopalakrishnan wrote:
> On 11/6/2014 10:34 AM, Borislav Petkov wrote:
> >On Thu, Nov 06, 2014 at 10:26:22AM -0600, Aravind Gopalakrishnan wrote:
> >>diff --git a/arch/x86/include/uapi/asm/msr-index.h b/arch/x86/include/uapi/asm/msr-index.h
> >>index e21331c..ba7b609 100644
> >>--- a/arch/x86/include/uapi/asm/msr-index.h
> >>+++ b/arch/x86/include/uapi/asm/msr-index.h
> >>@@ -206,6 +206,8 @@
> >> #define MSR_AMD64_IBSOP_REG_MASK ((1UL<<MSR_AMD64_IBSOP_REG_COUNT)-1)
> >> #define MSR_AMD64_IBSCTL 0xc001103a
> >> #define MSR_AMD64_IBSBRTARGET 0xc001103b
> >>+#define MSR_AMD64_IBS_FETCH_EXTD_CTL 0xc001103c
> >>+#define MSR_AMD64_IBSOPDATA4 0xc001103d
> >> #define MSR_AMD64_IBS_REG_COUNT_MAX 8 /* includes MSR_AMD64_IBSBRTARGET */
> >> /* Fam 16h MSRs */
> But Why?
> IBS_CAPS_BRNTRGT and IBS_CAPS_OPDATA4 indicate support for the respective
> MSRs
Ok, I was just making sure.
Btw, MSR_AMD64_IBS_FETCH_EXTD_CTL seems unused. Forgotten?
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next prev parent reply other threads:[~2014-11-08 9:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-06 16:26 Aravind Gopalakrishnan
2014-11-06 16:34 ` Borislav Petkov
2014-11-06 16:57 ` Aravind Gopalakrishnan
2014-11-08 9:03 ` Borislav Petkov [this message]
2014-11-10 16:00 ` Aravind Gopalakrishnan
2014-11-10 16:03 ` Borislav Petkov
2014-11-10 16:17 ` Aravind Gopalakrishnan
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=20141108090355.GB14837@pd.tnic \
--to=bp@suse.de \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=aravind.gopalakrishnan@amd.com \
--cc=fenghua.yu@intel.com \
--cc=hpa@zytor.com \
--cc=jan.kiszka@siemens.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulus@samba.org \
--cc=pbonzini@redhat.com \
--cc=tglx@linutronix.de \
--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
all inboxes | Powered by JetHome®