From: William Cohen <wcohen@redhat.com>
To: Michael Petlan <mpetlan@redhat.com>
Cc: "linux-perf-users@vger.kernel.org"
<linux-perf-users@vger.kernel.org>,
Andreas Krebbel <krebbel@linux.vnet.ibm.com>,
oprofile-list@lists.sf.net,
Andreas Arnez <arnez@linux.vnet.ibm.com>
Subject: Re: [PATCH] s390: Add support for z13
Date: Thu, 13 Oct 2016 10:15:05 -0400 [thread overview]
Message-ID: <1cb7be99-0b62-3dab-1194-20fe3171ac44@redhat.com> (raw)
In-Reply-To: <alpine.LRH.2.20.1610131424000.14258@Diego>
[-- Attachment #1: Type: text/plain, Size: 1685 bytes --]
On 10/13/2016 08:42 AM, Michael Petlan wrote:
> 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
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?
-Will
[-- Attachment #2: oprofile-s390-hexid.patch --]
[-- Type: text/x-patch, Size: 688 bytes --]
diff --git a/libop/op_cpu_type.c b/libop/op_cpu_type.c
index e70e4f6..ea5ff76 100644
--- a/libop/op_cpu_type.c
+++ b/libop/op_cpu_type.c
@@ -668,20 +668,19 @@ static op_cpu _get_s390_cpu_type(void)
return CPU_NO_GOOD;
ptr += sizeof(prefix) - 1;
- if (sscanf(ptr, "%u", &model) != 1)
- return CPU_NO_GOOD;
+ model = strtol(ptr, NULL, 16);
switch (model) {
- case 2097:
- case 2098:
+ case 0x2097:
+ case 0x2098:
return CPU_S390_Z10;
- case 2817:
- case 2818:
+ case 0x2817:
+ case 0x2818:
return CPU_S390_Z196;
- case 2827:
- case 2828:
+ case 0x2827:
+ case 0x2828:
return CPU_S390_ZEC12;
- case 2964:
+ case 0x2964:
return CPU_S390_Z13;
}
return CPU_NO_GOOD;
[-- Attachment #3: Type: text/plain, Size: 203 bytes --]
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
[-- Attachment #4: Type: text/plain, Size: 170 bytes --]
_______________________________________________
oprofile-list mailing list
oprofile-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oprofile-list
next prev parent reply other threads:[~2016-10-13 14:15 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 [this message]
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=1cb7be99-0b62-3dab-1194-20fe3171ac44@redhat.com \
--to=wcohen@redhat.com \
--cc=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 \
/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).