From: Andi Kleen <andi@firstfloor.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: "Liang\, Kan" <kan.liang@intel.com>,
"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"kvm\@vger.kernel.org" <kvm@vger.kernel.org>, "Kleen\,
Andi" <andi.kleen@intel.com>
Subject: Re: [PATCH 1/2] perf: ignore LBR and offcore_rsp.
Date: Wed, 18 Jun 2014 09:04:02 -0700 [thread overview]
Message-ID: <87lhsu8arx.fsf@tassilo.jf.intel.com> (raw)
In-Reply-To: <20140618155916.GZ6758@twins.programming.kicks-ass.net> (Peter Zijlstra's message of "Wed, 18 Jun 2014 17:59:16 +0200")
Peter Zijlstra <peterz@infradead.org> writes:
>
> This order indicates Andi is the author; but there's no corresponding
> From.
I wrote an early version of the patch, but Kan took it over and extended
it. So both are authors.
BTW Kan you may want to use git send-email to get standard format.
>
>> Signed-off-by: Kan Liang <kan.liang@intel.com>
>
> And here I thought that Andi was of the opinion that if you set CPUID to
> indicate a particular CPU you had better also handle all its MSRs.
Yes, philosophically that would be the right way,
but we needed a short term fix to stop things from crashing, and that
was the simplest.
-Andi
--
ak@linux.intel.com -- Speaking for myself only
next prev parent reply other threads:[~2014-06-18 16:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <37D7C6CF3E00A74B8858931C1DB2F0770148F513@SHSMSX103.ccr.corp.intel.com>
2014-06-18 15:59 ` [PATCH 1/2] perf: ignore LBR and offcore_rsp Peter Zijlstra
2014-06-18 16:04 ` Andi Kleen [this message]
2014-06-19 17:52 ` Andi Kleen
2014-06-23 9:19 ` Peter Zijlstra
2014-06-23 9:29 ` Peter Zijlstra
2014-06-23 15:56 ` Andi Kleen
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=87lhsu8arx.fsf@tassilo.jf.intel.com \
--to=andi@firstfloor.org \
--cc=andi.kleen@intel.com \
--cc=kan.liang@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.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