linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Michael Ellerman <mpe@ellerman.id.au>, linuxppc-dev@ozlabs.org
Subject: Re: powerpc/64: Make sys_switch_endian() traceable
Date: Fri, 22 Feb 2019 20:47:37 +1100 (AEDT)	[thread overview]
Message-ID: <445RMs4hVcz9sBR@ozlabs.org> (raw)
In-Reply-To: <20190115063736.3679-1-mpe@ellerman.id.au>

On Tue, 2019-01-15 at 06:37:36 UTC, Michael Ellerman wrote:
> We weren't using SYSCALL_DEFINE for sys_switch_endian(), which means
> it wasn't able to be traced by CONFIG_FTRACE_SYSCALLS.
> 
> By using the macro we create the right metadata and the syscall is
> visible. eg:
> 
>   # cd /sys/kernel/debug/tracing
>   # echo 1 | tee events/syscalls/sys_*_switch_endian/enable
>   # ~/switch_endian_test
>   # cat trace
>   ...
>   switch_endian_t-3604  [009] ....   315.175164: sys_switch_endian()
>   switch_endian_t-3604  [009] ....   315.175167: sys_switch_endian -> 0x5555aaaa5555aaaa
>   switch_endian_t-3604  [009] ....   315.175169: sys_switch_endian()
>   switch_endian_t-3604  [009] ....   315.175169: sys_switch_endian -> 0x5555aaaa5555aaaa
> 
> Fixes: 529d235a0e19 ("powerpc: Add a proper syscall for switching endianness")
> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>

Applied to powerpc next.

https://git.kernel.org/powerpc/c/81dac817786263bb44cd5a200a07eff3

cheers

      reply	other threads:[~2019-02-22 10:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-15  6:37 [PATCH] powerpc/64: Make sys_switch_endian() traceable Michael Ellerman
2019-02-22  9:47 ` Michael Ellerman [this message]

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=445RMs4hVcz9sBR@ozlabs.org \
    --to=patch-notifications@ellerman.id.au \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=mpe@ellerman.id.au \
    /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).