From: Ravi Bangoria <ravi.bangoria@linux.vnet.ibm.com>
To: Masami Hiramatsu <mhiramat@kernel.org>
Cc: acme@redhat.com, alexis.berlemont@gmail.com,
linux-kernel@vger.kernel.org, peterz@infradead.org,
mingo@redhat.com, alexander.shishkin@linux.intel.com,
naveen.n.rao@linux.vnet.ibm.com, mpe@ellerman.id.au,
hemant@linux.vnet.ibm.com,
Ravi Bangoria <ravi.bangoria@linux.vnet.ibm.com>
Subject: Re: [PATCH v2 1/3] perf/sdt/x86: Add renaming logic for (missing) 8 bit registers
Date: Tue, 28 Mar 2017 12:24:44 +0530 [thread overview]
Message-ID: <58DA08B4.9000503@linux.vnet.ibm.com> (raw)
In-Reply-To: <20170327231715.cf9a6e2571347157d6266d98@kernel.org>
Hi Masami, Thanks for the review.
On Monday 27 March 2017 07:47 PM, Masami Hiramatsu wrote:
> On Mon, 27 Mar 2017 13:28:27 +0530
> Ravi Bangoria <ravi.bangoria@linux.vnet.ibm.com> wrote:
>
>> I found couple of events using al, bl, cl and dl registers for
>> argument. These are not directly accepted by uprobe_events and
>> thus needs to be mapped to ax, bx, cx and dx respectively.
>>
>> Few ex,
>>
>> /usr/bin/qemu-system-s390x
>> css_adapter_interrupt: 1@%bl
>> css_chpid_add: 1@%cl 1@%sil 1@%dl
>> dma_bdrv_io: 8@%rbx 8@%rbp -8@%r14 1@%al
>>
>> /usr/bin/postgres
>> buffer__read__done: ... -1@-bash -1@%al
>> buffer__read__start: ... -1@%al
> Of course, it should be suppoted. BTW, wouldn't we take care about ah, bh ... too?
I thought about them while preparing this patch, but I couldn't find any
events using those registers. So I ignored them.
But I think no one stops compiler to use those registers for sdt argument.
And if so, they should get included.
Will send v3 for this.
Thanks,
Ravi
next prev parent reply other threads:[~2017-03-28 6:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-27 7:58 [PATCH v2 0/3] perf/sdt: Hardening argument support Ravi Bangoria
2017-03-27 7:58 ` [PATCH v2 1/3] perf/sdt/x86: Add renaming logic for (missing) 8 bit registers Ravi Bangoria
2017-03-27 14:17 ` Masami Hiramatsu
2017-03-28 6:54 ` Ravi Bangoria [this message]
2017-03-27 7:58 ` [PATCH v2 2/3] perf/sdt/x86: Move OP parser to tools/perf/arch/x86/ Ravi Bangoria
2017-03-27 14:56 ` Masami Hiramatsu
2017-03-27 7:58 ` [PATCH v2 3/3] perf/sdt/powerpc: Add argument support Ravi Bangoria
2017-03-27 15:10 ` Masami Hiramatsu
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=58DA08B4.9000503@linux.vnet.ibm.com \
--to=ravi.bangoria@linux.vnet.ibm.com \
--cc=acme@redhat.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=alexis.berlemont@gmail.com \
--cc=hemant@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=naveen.n.rao@linux.vnet.ibm.com \
--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