From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Stefan Raspl <raspl@linux.ibm.com>
Cc: Thomas Richter <tmricht@linux.ibm.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
brueckner@linux.vnet.ibm.com, schwidefsky@de.ibm.com,
heiko.carstens@de.ibm.com, stable@vger.kernel.org
Subject: Re: [PATCH] perf kvm: Fix subcommands on s390
Date: Mon, 16 Jul 2018 16:43:01 -0400 [thread overview]
Message-ID: <20180716204301.GB13669@kernel.org> (raw)
In-Reply-To: <de10696f-0fc3-4e34-d6dc-f9e669adc568@linux.ibm.com>
Em Thu, Jul 12, 2018 at 04:17:14PM +0200, Stefan Raspl escreveu:
> On 12.07.2018 09:09, Thomas Richter wrote:
> > With commit eca0fa28cd0d ("perf record: Provide detailed information on s390 CPU")
> > s390 platform provides detailed type/model/capacitiy information
> > in the CPU indentifier string instead of just "IBM/S390".
> > This breaks perf kvm support which uses hard coded string IBM/S390 to
> > compare with the CPU identifier string. Fix this by changing the comparison.
> > Fixes: eca0fa28cd0d ("perf record: Provide detailed information on s390 CPU")
> > Cc: Stefan Raspl <raspl@linux.ibm.com>
> > Cc: <stable@vger.kernel.org> # 4.17
> > Signed-off-by: Thomas Richter <tmricht@linux.ibm.com>
> > Reviewed-by: Hendrik Brueckner <brueckner@linux.ibm.com>
> Reported-and-tested-by: Stefan Raspl <raspl@linux.ibm.com>
Thanks, applied together with Christian's Acked-by,
- Arnaldo
next prev parent reply other threads:[~2018-07-16 20:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-12 7:09 [PATCH] perf kvm: Fix subcommands on s390 Thomas Richter
2018-07-12 7:15 ` Christian Borntraeger
2018-07-12 14:17 ` Stefan Raspl
2018-07-16 20:43 ` Arnaldo Carvalho de Melo [this message]
2018-07-25 20:44 ` [tip:perf/core] " tip-bot for Thomas Richter
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=20180716204301.GB13669@kernel.org \
--to=acme@kernel.org \
--cc=brueckner@linux.vnet.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=raspl@linux.ibm.com \
--cc=schwidefsky@de.ibm.com \
--cc=stable@vger.kernel.org \
--cc=tmricht@linux.ibm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.