From: Michael Petlan <mpetlan@redhat.com>
To: William Cohen <wcohen@redhat.com>
Cc: Michael Petlan <mpetlan@redhat.com>,
Andreas Arnez <arnez@linux.vnet.ibm.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: Thu, 13 Oct 2016 14:42:01 +0200 (CEST) [thread overview]
Message-ID: <alpine.LRH.2.20.1610131424000.14258@Diego> (raw)
In-Reply-To: <44aa1856-f35d-4077-df94-c588d5b3b1e2@redhat.com>
On Wed, 12 Oct 2016, William Cohen wrote:
> On 10/12/2016 10:01 AM, Michael Petlan wrote:
>> On Wed, 5 Oct 2016, Andreas Arnez wrote:
>>>
>>> IIRC, I just performed a quick smoke test before submitting this patch;
>>> and oprofile didn't crash. Other than that, I don't really know what
>>> works and what doesn't.
>>>
>
> Hi Andreas and Andreas,
>
> Is there support for IBM z13 perf counters in the upstream linux kernel? I didn't see perf support for IBM z13 in the mainline kernel git repository.
>
> There is a difference between the kernel and oprofile is the s390 identification. The kernel is using hex numbers such as 0x2817 and 0x2818 for Z196 identification (http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/arch/s390/kernel/perf_cpum_cf_events.c#n303), but oprofile is reading the numbers as decimal for idenfication (https://sourceforge.net/p/oprofile/oprofile/ci/master/tree/libop/op_cpu_type.c). oprofile should also be using hex numbers like the kernel.
I have looked at this and although it is not ideal, it works OK in OProfile,
since it reads the numbers from string, thus it works with decimals.
I have also checked that zEC12 detection works correctly with 1.1.
Michael
>
> -Will
>>
next prev parent reply other threads:[~2016-10-13 12:42 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 [this message]
2016-10-13 14:15 ` William Cohen
2016-10-14 18:32 ` Andreas Arnez
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=alpine.LRH.2.20.1610131424000.14258@Diego \
--to=mpetlan@redhat.com \
--cc=arnez@linux.vnet.ibm.com \
--cc=krebbel@linux.vnet.ibm.com \
--cc=linux-perf-users@vger.kernel.org \
--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).