From: Andi Kleen <andi@firstfloor.org>
To: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
Cc: Vineet Gupta <Vineet.Gupta1@synopsys.com>,
Aabid Rushdi <Aabid.Rushdi@synopsys.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"peterz@infradead.org" <peterz@infradead.org>,
"linux-perf-users@vger.kernel.org"
<linux-perf-users@vger.kernel.org>,
"dvhart@linux.intel.com" <dvhart@linux.intel.com>,
"dsahern@gmail.com" <dsahern@gmail.com>,
"acme@redhat.com" <acme@redhat.com>
Subject: Re: [RFC] perf: fix building for ARCv1
Date: Sun, 18 Oct 2015 16:14:54 -0700 [thread overview]
Message-ID: <87a8rf6a6p.fsf@tassilo.jf.intel.com> (raw)
In-Reply-To: <1445166916.9672.10.camel@synopsys.com> (Alexey Brodkin's message of "Sun, 18 Oct 2015 11:15:16 +0000")
Alexey Brodkin <Alexey.Brodkin@synopsys.com> writes:
>
> So the best we may do is to implement detection of atomics in the toolchain and if there's no atomics hard stop with
> perf building.
If your target is single cpu only you can always simulate them in C.
-Andi
WARNING: multiple messages have this Message-ID (diff)
From: Andi Kleen <andi@firstfloor.org>
To: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
Cc: Vineet Gupta <Vineet.Gupta1@synopsys.com>,
Aabid Rushdi <Aabid.Rushdi@synopsys.com>,
"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"peterz\@infradead.org" <peterz@infradead.org>,
"linux-perf-users\@vger.kernel.org"
<linux-perf-users@vger.kernel.org>,
"dvhart\@linux.intel.com" <dvhart@linux.intel.com>,
"dsahern\@gmail.com" <dsahern@gmail.com>,
"acme\@redhat.com" <acme@redhat.com>
Subject: Re: [RFC] perf: fix building for ARCv1
Date: Sun, 18 Oct 2015 16:14:54 -0700 [thread overview]
Message-ID: <87a8rf6a6p.fsf@tassilo.jf.intel.com> (raw)
In-Reply-To: <1445166916.9672.10.camel@synopsys.com> (Alexey Brodkin's message of "Sun, 18 Oct 2015 11:15:16 +0000")
Alexey Brodkin <Alexey.Brodkin@synopsys.com> writes:
>
> So the best we may do is to implement detection of atomics in the toolchain and if there's no atomics hard stop with
> perf building.
If your target is single cpu only you can always simulate them in C.
-Andi
next prev parent reply other threads:[~2015-10-18 23:14 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1445088959-3058-1-git-send-email-abrodkin@synopsys.com>
2015-10-17 14:19 ` [RFC] perf: fix building for ARCv1 Vineet Gupta
2015-10-18 11:15 ` Alexey Brodkin
2015-10-18 11:15 ` Alexey Brodkin
2015-10-18 23:14 ` Andi Kleen [this message]
2015-10-18 23:14 ` Andi Kleen
2015-10-19 4:58 ` Vineet Gupta
2015-10-19 5:49 ` Andi Kleen
2015-10-19 5:49 ` Andi Kleen
2015-10-19 9:28 ` Vineet Gupta
2015-10-19 9:35 ` Peter Zijlstra
2015-10-19 9:46 ` Vineet Gupta
2015-10-19 9:51 ` Peter Zijlstra
2015-10-19 10:04 ` Vineet Gupta
2015-10-20 8:00 ` Vineet Gupta
2015-10-20 10:11 ` Peter Zijlstra
2015-10-20 10:45 ` Vineet Gupta
2015-10-29 15:58 ` Alexey Brodkin
2015-10-29 15:58 ` Alexey Brodkin
2015-10-29 15:58 ` Alexey Brodkin
2015-10-30 6:19 ` Vineet Gupta
2015-10-30 6:19 ` Vineet Gupta
2016-02-03 16:20 ` Alexey Brodkin
2016-02-03 16:20 ` Alexey Brodkin
[not found] ` <1454516455.2811.4.camel__10775.5710989752$1454516490$gmane$org@synopsys.com>
2016-02-04 4:13 ` Vineet Gupta
2016-02-04 4:13 ` Vineet Gupta
2016-02-04 4:13 ` Vineet Gupta
2016-02-05 11:18 ` Noam Camus
2016-02-05 11:18 ` Noam Camus
2016-02-05 16:10 ` acme
2016-02-05 16:10 ` acme
2016-02-10 3:09 ` Vineet Gupta
2016-02-10 3:09 ` Vineet Gupta
2016-10-18 18:58 ` Vineet Gupta
2016-10-18 18:58 ` Vineet Gupta
2016-10-24 16:17 ` [PATCH-v2] ARC: syscall for userspace cmpxchg assist Vineet Gupta
2016-10-24 16:17 ` Vineet Gupta
2016-11-04 20:16 ` Vineet Gupta
2016-11-04 20:16 ` Vineet Gupta
2016-11-07 18:50 ` [PATCH] ARC: tweak semantics of " Vineet Gupta
2016-11-07 18:50 ` Vineet Gupta
2015-10-30 6:21 ` [RFC] perf: fix building for ARCv1 Vineet Gupta
2015-10-30 6:21 ` Vineet Gupta
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=87a8rf6a6p.fsf@tassilo.jf.intel.com \
--to=andi@firstfloor.org \
--cc=Aabid.Rushdi@synopsys.com \
--cc=Alexey.Brodkin@synopsys.com \
--cc=Vineet.Gupta1@synopsys.com \
--cc=acme@redhat.com \
--cc=dsahern@gmail.com \
--cc=dvhart@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--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 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.