From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753510AbbHEPfW (ORCPT ); Wed, 5 Aug 2015 11:35:22 -0400 Received: from casper.infradead.org ([85.118.1.10]:37449 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753304AbbHEPfK (ORCPT ); Wed, 5 Aug 2015 11:35:10 -0400 Date: Wed, 5 Aug 2015 17:35:07 +0200 From: Peter Zijlstra To: Alexander Shishkin Cc: Ingo Molnar , linux-kernel@vger.kernel.org, adrian.hunter@intel.com, Arnaldo Carvalho de Melo , Vince Weaver , Stephane Eranian Subject: Re: [PATCH RFC v1 1/4] perf: Introduce extended syscall error reporting Message-ID: <20150805153507.GM19282@twins.programming.kicks-ass.net> References: <1437738359-23920-1-git-send-email-alexander.shishkin@linux.intel.com> <1437738359-23920-2-git-send-email-alexander.shishkin@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1437738359-23920-2-git-send-email-alexander.shishkin@linux.intel.com> User-Agent: Mutt/1.5.21 (2012-12-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jul 24, 2015 at 02:45:56PM +0300, Alexander Shishkin wrote: > +#define __perf_err(__e, __c, __m) ({ \ > + static struct perf_err_site \ > + __attribute__ ((unused,__section__("__perf_err"))) \ > + __err_site = { \ > + .message = (__m), \ > + .owner = PERF_MODNAME, \ > + .code = __builtin_constant_p((__c)) ? \ > + (__c) : 0, \ > + }; \ > + (__e) = &__err_site; \ > +}) Why is __e an argument at all? Why not simply return &__err_site ?