public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Anshuman Khandual <khandual@linux.vnet.ibm.com>
To: Stephane Eranian <eranian@google.com>
Cc: linux-kernel@vger.kernel.org, acme@redhat.com,
	peterz@infradead.org, mingo@elte.hu
Subject: Re: [PATCH] perf record: fix branch_stack type in perf_record_opts
Date: Mon, 28 May 2012 20:40:42 +0530	[thread overview]
Message-ID: <4FC39572.6010709@linux.vnet.ibm.com> (raw)
In-Reply-To: <20120525211344.GA7729@quad>

On Saturday 26 May 2012 02:43 AM, Stephane Eranian wrote:

> 
> The attr.branch_sample_type field is defined as u64 by the API.
> As such, we need to ensure the variable holding the value of the
> branch stack filters is also u64 otherwise we may lose bits in
> the future.
> 
> Note also that the bogus definition of the field in
> perf_record_opts caused problems on big-endian PPC systems.
> Thanks to Anshuman Khandual for tracking the problem on PPC.
> 
> Signed-off-by: Stephane Eranian <eranian@google.com>


Acked-by: Anshuman Khandual <khandual@linux.vnet.ibm.com>

> ---
> 
> diff --git a/tools/perf/perf.h b/tools/perf/perf.h
> index 14f1034..f960ccb 100644
> --- a/tools/perf/perf.h
> +++ b/tools/perf/perf.h
> @@ -227,7 +227,7 @@ struct perf_record_opts {
>  	unsigned int freq;
>  	unsigned int mmap_pages;
>  	unsigned int user_freq;
> -	int	     branch_stack;
> +	u64          branch_stack;
>  	u64	     default_interval;
>  	u64	     user_interval;
>  };
> 



  reply	other threads:[~2012-05-28 15:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-25 21:13 [PATCH] perf record: fix branch_stack type in perf_record_opts Stephane Eranian
2012-05-28 15:10 ` Anshuman Khandual [this message]
2012-05-30  7:47 ` [tip:perf/urgent] perf record: Fix " tip-bot for Stephane Eranian

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=4FC39572.6010709@linux.vnet.ibm.com \
    --to=khandual@linux.vnet.ibm.com \
    --cc=acme@redhat.com \
    --cc=eranian@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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