From: Radim Krcmar <rkrcmar@redhat.com>
To: "Natarajan, Janakarajan" <Janakarajan.Natarajan@amd.com>
Cc: kvm@vger.kernel.org, x86@kernel.org,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H . Peter Anvin" <hpa@zytor.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Len Brown <len.brown@intel.com>, Borislav Petkov <bp@suse.de>,
Kyle Huey <me@kylehuey.com>,
Tom Lendacky <thomas.lendacky@amd.com>
Subject: Re: [PATCH v5 0/3] Support Perf Extension on AMD KVM guests
Date: Tue, 6 Mar 2018 22:02:31 +0100 [thread overview]
Message-ID: <20180306210231.GC12128@flask> (raw)
In-Reply-To: <7d5fbe31-e24c-8ec6-631e-6909bcef3430@amd.com>
2018-02-16 13:26-0600, Natarajan, Janakarajan:
> On 2/5/2018 1:24 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.
> >
> > v3->v4:
> > * Rebased to latest KVM tree.
> >
> > v4->v5:
> > * Removed conditional check when exposing Perf Extension flag to
> > guests based on Radim's feedback.
> >
> > 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?
No, looks ok!
I have squashed the last patch, added a sanity BUILD_BUG_ON and applied
to kvm/queue (until we're sure that [1/3] goes through the kvm tree),
thanks.
prev parent reply other threads:[~2018-03-06 21:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-05 19:24 [PATCH v5 0/3] Support Perf Extension on AMD KVM guests Janakarajan Natarajan
2018-02-05 19:24 ` [PATCH v5 1/3] x86/msr: Add AMD Core Perf Extension MSRs Janakarajan Natarajan
2018-03-06 21:03 ` Radim Krcmar
2018-03-16 14:50 ` Paolo Bonzini
2018-03-16 19:22 ` Thomas Gleixner
2018-02-05 19:24 ` [PATCH v5 2/3] x86/kvm: Add support for AMD Core Perf Extension in guest Janakarajan Natarajan
2018-02-05 19:24 ` [PATCH v5 3/3] x86/kvm: Expose AMD Core Perf Extension flag to guests Janakarajan Natarajan
2018-02-16 19:26 ` [PATCH v5 0/3] Support Perf Extension on AMD KVM guests Natarajan, Janakarajan
2018-03-06 21:02 ` Radim Krcmar [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=20180306210231.GC12128@flask \
--to=rkrcmar@redhat.com \
--cc=Janakarajan.Natarajan@amd.com \
--cc=bp@suse.de \
--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=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