public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: acme@kernel.org
Cc: mingo@kernel.org, jolsa@kernel.org, linux-kernel@vger.kernel.org,
	Andi Kleen <ak@linux.intel.com>, Andi Kleen <andi@firstfloor.org>
Subject: Re: [PATCH] perf, tools, script: Add brstackinsn for branch stacks
Date: Thu, 16 Mar 2017 13:16:21 +1100	[thread overview]
Message-ID: <87zigmt18q.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <20170223234634.583-1-andi@firstfloor.org>

Hi acme,

Andi Kleen <andi@firstfloor.org> writes:

> diff --git a/tools/perf/builtin-script.c b/tools/perf/builtin-script.c
> index c0783b4f7b6c..b0fdb6c032a5 100644
> --- a/tools/perf/builtin-script.c
> +++ b/tools/perf/builtin-script.c
> @@ -546,6 +555,259 @@ static void print_sample_brstacksym(struct perf_sample *sample,
>  	}
>  }
>  
> +#define MAXBB 16384UL
> +
> +static int grab_bb(u8 *buffer, u64 start, u64 end,
> +		    struct machine *machine, struct thread *thread,
> +		    bool *is64bit, u8 *cpumode, bool last)
> +{
> +	long offset, len;
> +	struct addr_location al;
> +	bool kernel;
> +
> +	if (!start || !end)
> +		return 0;
> +
> +	kernel = machine__kernel_ip(machine, start);
> +	if (kernel)
> +		*cpumode = PERF_RECORD_MISC_KERNEL;
> +	else
> +		*cpumode = PERF_RECORD_MISC_USER;
> +
> +	/*
> +	 * Block overlaps between kernel and user.
> +	 * This can happen due to ring filtering
> +	 * On Intel CPUs the entry into the kernel is filtered,
> +	 * but the exit is not. Let the caller patch it up.
> +	 */
> +	if (kernel != machine__kernel_ip(machine, end)) {
> +		printf("\tblock %" PRIx64 "-%" PRIx64 " transfers between kernel and user\n",
> +				start, end);
> +		return -ENXIO;
> +	}
> +
> +	memset(&al, 0, sizeof(al));
> +	if (end - start > MAXBB - MAXINSN) {
> +		if (last)
> +			printf("\tbrstack does not reach to final jump (%" PRIx64 "-%" PRIx64 ")\n",
> +					start, end);
> +		else
> +			printf("\tblock %" PRIx64 "-%" PRIx64 " (%ld) too long to dump\n",
> +					start, end, end - start);

This looks to be breaking the build on ppc64:

  builtin-script.c: In function ‘grab_bb’:
  builtin-script.c:595:11: error: format ‘%ld’ expects argument of type ‘long int’, but argument 4 has type ‘u64 {aka long long unsigned int}’ [-Werror=format=]
      printf("\tblock %" PRIx64 "-%" PRIx64 " (%ld) too long to dump\n", start, end, end - start);
             ^

cheers

  reply	other threads:[~2017-03-16  2:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-23 23:46 [PATCH] perf, tools, script: Add brstackinsn for branch stacks Andi Kleen
2017-03-16  2:16 ` Michael Ellerman [this message]
2017-03-16  2:22   ` Andi Kleen
2017-03-16 12:25     ` Arnaldo Carvalho de Melo
2017-03-16 16:36 ` [tip:perf/core] perf script: Add 'brstackinsn' " tip-bot for Andi Kleen

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=87zigmt18q.fsf@concordia.ellerman.id.au \
    --to=mpe@ellerman.id.au \
    --cc=acme@kernel.org \
    --cc=ak@linux.intel.com \
    --cc=andi@firstfloor.org \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.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