All of lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach <baruch@tkos.co.il>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@redhat.com>,
	Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Cc: linux-xtensa@linux-xtensa.org, linux-kernel@vger.kernel.org
Subject: Re: [Linux-Xtensa] [PATCH v2] perf: add support for the xtensa architecture
Date: Mon, 13 Jan 2014 09:55:18 +0200	[thread overview]
Message-ID: <20140113075518.GH4944@tarshish> (raw)
In-Reply-To: <2681fd21a9ee014ffe77c0ec7304157be7209b6f.1388649430.git.baruch@tkos.co.il>

Hi perf maintainers,

Ping?

Anyone taking this for v3.14?

baruch

On Thu, Jan 02, 2014 at 09:57:10AM +0200, Baruch Siach wrote:
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
> ---
> v2: use the "core ID" field from /proc/cpuinfo (Max Filippov)
> ---
>  tools/perf/perf.h | 7 +++++++
>  1 file changed, 7 insertions(+)
> 
> diff --git a/tools/perf/perf.h b/tools/perf/perf.h
> index b079304bd53d..e441864dbe03 100644
> --- a/tools/perf/perf.h
> +++ b/tools/perf/perf.h
> @@ -132,6 +132,13 @@
>  #define CPUINFO_PROC	"CPU"
>  #endif
>  
> +#ifdef __xtensa__
> +#define mb()		asm volatile("memw" ::: "memory")
> +#define wmb()		asm volatile("memw" ::: "memory")
> +#define rmb()		asm volatile("" ::: "memory")
> +#define CPUINFO_PROC	"core ID"
> +#endif
> +
>  #define barrier() asm volatile ("" ::: "memory")
>  
>  #ifndef cpu_relax

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch@tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -

  parent reply	other threads:[~2014-01-13  7:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-02  7:57 [PATCH v2] perf: add support for the xtensa architecture Baruch Siach
2014-01-02  8:11 ` [Linux-Xtensa] " Max Filippov
2014-01-13  7:55 ` Baruch Siach [this message]
2014-01-13 10:02   ` Ingo Molnar

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=20140113075518.GH4944@tarshish \
    --to=baruch@tkos.co.il \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@ghostprotocols.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xtensa@linux-xtensa.org \
    --cc=mingo@redhat.com \
    --cc=paulus@samba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.