From: Andreas Arnez <arnez@linux.vnet.ibm.com>
To: William Cohen <wcohen@redhat.com>
Cc: Michael Petlan <mpetlan@redhat.com>,
Andreas Krebbel <krebbel@linux.vnet.ibm.com>,
oprofile-list@lists.sf.net,
"linux-perf-users@vger.kernel.org"
<linux-perf-users@vger.kernel.org>
Subject: Re: [PATCH] s390: Add support for z13
Date: Fri, 14 Oct 2016 20:32:27 +0200 [thread overview]
Message-ID: <m3wphabx38.fsf@oc1027705133.ibm.com> (raw)
In-Reply-To: <1cb7be99-0b62-3dab-1194-20fe3171ac44@redhat.com> (William Cohen's message of "Thu, 13 Oct 2016 10:15:05 -0400")
On Thu, Oct 13 2016, William Cohen wrote:
> Yes, the s390 processor detection in oprofile is not ideal with the kernel
> outputting the id in hex and the oprofile reading it in as a decimal.
> Good thing that none of the s390 id values have a-f in the digits.
> Attached is a patch that reads in the values as hex to better line up with
> the kernel's handling of the s390 identification. Could one of the IBM
> people try this patch?
Sure. The patch looks good to me, and I've verified it on one of the
affected machines.
--
Andreas
next prev parent reply other threads:[~2016-10-14 18:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m3mvnwu1cy.fsf@oc1027705133.ibm.com>
[not found] ` <bb9acd86-0c7c-7291-00c1-1c6ad8576232@redhat.com>
[not found] ` <m360p8m87d.fsf@oc1027705133.ibm.com>
[not found] ` <d2177055-a1c3-7562-f555-bd239836af3e@redhat.com>
[not found] ` <alpine.LRH.2.20.1610042254100.6819@Diego>
[not found] ` <m3vax6lkon.fsf@oc1027705133.ibm.com>
[not found] ` <alpine.LRH.2.20.1610121546540.14258@Diego>
2016-10-12 20:27 ` [PATCH] s390: Add support for z13 William Cohen
2016-10-13 12:42 ` Michael Petlan
2016-10-13 14:15 ` William Cohen
2016-10-14 18:32 ` Andreas Arnez [this message]
2016-10-13 16:14 ` Andreas Arnez
2016-10-13 18:23 ` William Cohen
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=m3wphabx38.fsf@oc1027705133.ibm.com \
--to=arnez@linux.vnet.ibm.com \
--cc=krebbel@linux.vnet.ibm.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=mpetlan@redhat.com \
--cc=oprofile-list@lists.sf.net \
--cc=wcohen@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).