linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Anshuman Khandual <khandual@linux.vnet.ibm.com>
To: Rashmica Gupta <rashmicy@gmail.com>, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] powerpc: Add rN aliases to the pt_regs_offset table.
Date: Mon, 23 Nov 2015 13:54:34 +0530	[thread overview]
Message-ID: <5652CD42.5010008@linux.vnet.ibm.com> (raw)
In-Reply-To: <1448086096-3117-1-git-send-email-rashmicy@gmail.com>

On 11/21/2015 11:38 AM, Rashmica Gupta wrote:
> It is common practice with powerpc to use 'rN' to refer to register 'N'. However
> when using the pt_regs_offset table we have to use 'gprN'.
> 
> So add aliases such that both 'rN' and 'gprN' can be used.
> 
> For example, we can currently do:
> $ su -
> $ echo "p:probe/sys_fchownat .sys_fchownat %gpr3:s32 +0(%gpr4):string %gpr5:s32
> %gpr6:s32 %gpr7:s32" > /sys/kernel/debug/tracing/kprobe_events
> $ echo 1 > /sys/kernel/debug/tracing/events/probe/sys_fchownat/enable
> $ touch /tmp/foo
> $ chown root /tmp/foo
> $ echo 0 > /sys/kernel/debug/tracing/events/enable
> $ cat /sys/kernel/debug/tracing/trace
>            chown-5040  [001] d... 24800.047211: sys_fchownat:
> (.SyS_fchownat+0x0/0x190) arg1=-100 arg2="foo" arg3=0 arg4=-1 arg5=0
> 
> Instead we'd like to be able to use:
> $ echo "p:probe/sys_fchownat sys_fchownat %r3:s32 +0(%r4):string %r5:s32
> %r6:s32 %r7:s32" > /sys/kernel/debug/tracing/kprobe_events

This makes sense and works for me on a LE guest. Just that the symbol
should not have the "." before it. 

  reply	other threads:[~2015-11-23  8:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-21  6:08 [PATCH] powerpc: Add rN aliases to the pt_regs_offset table Rashmica Gupta
2015-11-23  8:24 ` Anshuman Khandual [this message]
2015-11-23 10:15   ` Michael Ellerman
2015-11-26 12:15 ` Michael Ellerman

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=5652CD42.5010008@linux.vnet.ibm.com \
    --to=khandual@linux.vnet.ibm.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=rashmicy@gmail.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).