mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Natarajan, Janakarajan" <Janakarajan.Natarajan@amd.com>
To: kvm@vger.kernel.org, x86@kernel.org, linux-kernel@vger.kernel.org
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H . Peter Anvin" <hpa@zytor.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Radim Krcmar <rkrcmar@redhat.com>,
	Len Brown <len.brown@intel.com>, Kyle Huey <me@kylehuey.com>,
	Tom Lendacky <thomas.lendacky@amd.com>,
	Borislav Petkov <bp@suse.de>,
	Grzegorz Andrejczuk <grzegorz.andrejczuk@intel.com>,
	Kan Liang <Kan.liang@intel.com>
Subject: Re: [PATCH v3 0/3] Support Perf Extension on AMD KVM guests
Date: Tue, 2 Jan 2018 17:55:32 -0600	[thread overview]
Message-ID: <f695227a-699e-0e0b-12cb-bf238935ce72@amd.com> (raw)
In-Reply-To: <cover.1512771421.git.Janakarajan.Natarajan@amd.com>

On 12/8/2017 4:39 PM, Janakarajan Natarajan wrote:
> This patchset adds support for Perf Extension on AMD KVM guests.
>
> When perf runs on a guest with family = 15h || 17h, the MSRs that are
> accessed, when the Perf Extension flag is made available, differ from
> the existing K7 MSRs. The accesses are to the AMD Core Performance
> Extension counters which provide 2 extra counters and new MSRs for both
> the event select and counter registers.
>
> Since the new event select and counter MSRs are interleaved and K7 MSRs
> are contiguous, the logic to map them to the gp_counters[] is changed.
>
> This patchset has been tested with Family 17h and Opteron G1 guests.
>
> v1->v2:
> * Rearranged MSR #defines based on Boris's suggestion.
>
> v2->v3:
> * Changed the logic of mapping MSR to gp_counters[] index based on
>    Boris's feedback.
> * Removed use of family checks based on Radim's feedback.
> * Removed KVM bugfix patch since it is already applied.
>
> Janakarajan Natarajan (3):
>    x86/msr: Add AMD Core Perf Extension MSRs
>    x86/kvm: Add support for AMD Core Perf Extension in guest
>    x86/kvm: Expose AMD Core Perf Extension flag to guests

Are there any concerns regarding this patchset?

>
>   arch/x86/include/asm/msr-index.h |  14 ++++
>   arch/x86/kvm/cpuid.c             |   8 ++-
>   arch/x86/kvm/pmu_amd.c           | 140 +++++++++++++++++++++++++++++++++++----
>   arch/x86/kvm/x86.c               |   1 +
>   4 files changed, 148 insertions(+), 15 deletions(-)
>

      parent reply	other threads:[~2018-01-02 23:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-08 22:39 Janakarajan Natarajan
2017-12-08 22:39 ` [PATCH v3 1/3] x86/msr: Add AMD Core Perf Extension MSRs Janakarajan Natarajan
2017-12-08 22:39 ` [PATCH v3 2/3] x86/kvm: Add support for AMD Core Perf Extension in guest Janakarajan Natarajan
2017-12-08 22:39 ` [PATCH v3 3/3] x86/kvm: Expose AMD Core Perf Extension flag to guests Janakarajan Natarajan
2018-01-02 23:55 ` Natarajan, Janakarajan [this message]

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=f695227a-699e-0e0b-12cb-bf238935ce72@amd.com \
    --to=janakarajan.natarajan@amd.com \
    --cc=Kan.liang@intel.com \
    --cc=bp@suse.de \
    --cc=grzegorz.andrejczuk@intel.com \
    --cc=hpa@zytor.com \
    --cc=kvm@vger.kernel.org \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=me@kylehuey.com \
    --cc=mingo@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=rkrcmar@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=thomas.lendacky@amd.com \
    --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®