public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Michael Ellerman <patch-notifications@ellerman•id.au>
To: Michael Ellerman <mpe@ellerman•id.au>, linuxppc-dev@ozlabs•org
Cc: anton@samba•org
Subject: Re: powerpc/pseries: hcall_exit tracepoint retval should be signed
Date: Fri, 11 May 2018 00:06:40 +1000 (AEST)	[thread overview]
Message-ID: <40hZlj2K0dz9s1b@ozlabs.org> (raw)
In-Reply-To: <20180507130355.25115-1-mpe@ellerman.id.au>

On Mon, 2018-05-07 at 13:03:55 UTC, Michael Ellerman wrote:
> The hcall_exit() tracepoint has retval defined as unsigned long. That
> leads to humours results like:
> 
>   bash-3686  [009] d..2   854.134094: hcall_entry: opcode=24
>   bash-3686  [009] d..2   854.134095: hcall_exit: opcode=24 retval=18446744073709551609
> 
> It's normal for some hcalls to return negative values, displaying them
> as unsigned isn't very helpful. So change it to signed.
> 
>   bash-3711  [001] d..2   471.691008: hcall_entry: opcode=24
>   bash-3711  [001] d..2   471.691008: hcall_exit: opcode=24 retval=-7
> 
> Which can be more easily compared to H_NOT_FOUND in hvcall.h
> 
> Signed-off-by: Michael Ellerman <mpe@ellerman•id.au>
> Acked-by: Anton Blanchard <anton@samba•org>

Applied to powerpc next.

https://git.kernel.org/powerpc/c/8f2133cc0e1f9718f3e2d39b7587f4

cheers

      parent reply	other threads:[~2018-05-10 14:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-07 13:03 [PATCH] powerpc/pseries: hcall_exit tracepoint retval should be signed Michael Ellerman
2018-05-08 11:57 ` Anton Blanchard
2018-05-09  9:46 ` Ravi Bangoria
2018-05-10 14:06 ` 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=40hZlj2K0dz9s1b@ozlabs.org \
    --to=patch-notifications@ellerman$(echo .)id.au \
    --cc=anton@samba$(echo .)org \
    --cc=linuxppc-dev@ozlabs$(echo .)org \
    --cc=mpe@ellerman$(echo .)id.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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