From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753038AbbJSKEg (ORCPT ); Mon, 19 Oct 2015 06:04:36 -0400 Received: from smtprelay.synopsys.com ([198.182.47.9]:50714 "EHLO smtprelay.synopsys.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751182AbbJSKEe convert rfc822-to-8bit (ORCPT ); Mon, 19 Oct 2015 06:04:34 -0400 From: Vineet Gupta To: Peter Zijlstra CC: Andi Kleen , Alexey Brodkin , Aabid Rushdi , "linux-kernel@vger.kernel.org" , "linux-perf-users@vger.kernel.org" , "dvhart@linux.intel.com" , "dsahern@gmail.com" , "acme@redhat.com" Subject: Re: [RFC] perf: fix building for ARCv1 Thread-Topic: [RFC] perf: fix building for ARCv1 Thread-Index: AQHRCjH5qUIZ06l560WdnGKbYbcPAw== Date: Mon, 19 Oct 2015 10:04:29 +0000 Message-ID: References: <1445088959-3058-1-git-send-email-abrodkin@synopsys.com> <1445166916.9672.10.camel@synopsys.com> <87a8rf6a6p.fsf@tassilo.jf.intel.com> <8761235rwe.fsf@tassilo.jf.intel.com> <20151019093549.GK3816@twins.programming.kicks-ass.net> <20151019095157.GM3816@twins.programming.kicks-ass.net> Accept-Language: en-US, en-IN Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.12.239.237] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8BIT MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Monday 19 October 2015 03:22 PM, Peter Zijlstra wrote: > On Mon, Oct 19, 2015 at 09:46:35AM +0000, Vineet Gupta wrote: >> > On ARC we could use the atomic EXchange to implement a user space only binary >> > semaphore - these atomic ops will be small duration so it is OK to spin wait for a >> > little bit. That's how the old pthread library worked for ARC w/o any atomic support. > That has the obvious problem of lock-holder-preemption and the horrible > performance issues that result from that. > > I think the syscall at least has deterministic behaviour, whereas that > userspace spin loop has this abysmal worst case thing. I agree - we can add that syscall trivially and use it based on build time feature detection for atomics !