Received: by 2002:a25:7ec1:0:0:0:0:0 with SMTP id z184csp5672203ybc; Wed, 27 Nov 2019 07:42:12 -0800 (PST) X-Google-Smtp-Source: APXvYqxANGMuE2nGUlV2SNYA765gaXVo6yL9Ns0ax+3Br0Ux4lURuufNeX85orTbInsE/ROCzYAd X-Received: by 2002:aa7:c756:: with SMTP id c22mr32223196eds.25.1574869332444; Wed, 27 Nov 2019 07:42:12 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1574869332; cv=none; d=google.com; s=arc-20160816; b=f1gaoNeZhLxU9CvNUMcWxjyIWCEiMX2dlR1Jn7Kt7XxWqLMEGOeYtWPJxAWlaoHfVt kdKhjdACywEyQmnZnNZ/d70a7oms6gJeihbf+RjMAgMfs+qODwP9RP1L3P338naI6Xf7 0hmAzW3LQ0c3Y7zOR6rU1PjC9YOV+dwuQCzmMyiD+jLGYZdoCQ5THDdesDgqD6QcOhDI 3B63VKj4VfyTALGGjZOuEOl2lSBoPfOcAzI3FG8yPgQW2K+fXrbc1DQOxtALgs0O+9Gc UtBXNS7/BCd5v21wv8hTpiBGom7EprKvKv5S7/i8zhAt15K9DjdwZe0H5lLeD6TsHr6P D0qQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=iKViV7dFY7n4WNMW/SfDiS/fv5pzKYZlqbzqFAgPrSk=; b=EpuScVmJh+EGvuvCZ1PHHEJ3bUI2sckGCM7ut1Bl4u+lFfEmH34XrXM6KyiIveWnTO 5jWDOgvwMbK2ZvAtZiPrpl0eVs8AmkxOJH7VP+p8AuSKhxbclbl0OPi3VzlW8kgs3blF hGo1lt9eT3UotBWpR4s60vHAq+RFw3qK1jWrxZyr5gUgp1ucvveOi8FebQCk49NTTAb1 nBLJeprBm7eEIHoSkLCoNYPmpcYfAYYx7w60nGC/OCZIqY6AEYjhDEVJJbwNmaQmQWTy U1alU73lu1q60qb1iOjpQxmY/E7VIfm0j54SaC+98jZg7d4HmMGViSgO19Wv7LleGoxK o04w== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id dc21si9646317ejb.101.2019.11.27.07.41.48; Wed, 27 Nov 2019 07:42:12 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726983AbfK0PAY (ORCPT + 99 others); Wed, 27 Nov 2019 10:00:24 -0500 Received: from gate.crashing.org ([63.228.1.57]:47841 "EHLO gate.crashing.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726514AbfK0PAY (ORCPT ); Wed, 27 Nov 2019 10:00:24 -0500 Received: from gate.crashing.org (localhost.localdomain [127.0.0.1]) by gate.crashing.org (8.14.1/8.14.1) with ESMTP id xARF00sE025427; Wed, 27 Nov 2019 09:00:00 -0600 Received: (from segher@localhost) by gate.crashing.org (8.14.1/8.14.1/Submit) id xARExxVi025420; Wed, 27 Nov 2019 08:59:59 -0600 X-Authentication-Warning: gate.crashing.org: segher set sender to segher@kernel.crashing.org using -f Date: Wed, 27 Nov 2019 08:59:58 -0600 From: Segher Boessenkool To: Christophe Leroy Cc: Michael Ellerman , Benjamin Herrenschmidt , Paul Mackerras , linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org Subject: Re: [PATCH v4 2/2] powerpc/irq: inline call_do_irq() and call_do_softirq() Message-ID: <20191127145958.GG9491@gate.crashing.org> References: <5ca6639b7c1c21ee4b4138b7cfb31d6245c4195c.1570684298.git.christophe.leroy@c-s.fr> <877e3tbvsa.fsf@mpe.ellerman.id.au> <20191121101552.GR16031@gate.crashing.org> <87y2w49rgo.fsf@mpe.ellerman.id.au> <20191125142556.GU9491@gate.crashing.org> <5fdb1c92-8bf4-01ca-f81c-214870c33be3@c-s.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5fdb1c92-8bf4-01ca-f81c-214870c33be3@c-s.fr> User-Agent: Mutt/1.4.2.3i Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Nov 27, 2019 at 02:50:30PM +0100, Christophe Leroy wrote: > So what do we do ? We just drop the "r2" clobber ? You have to make sure your asm code works for all ABIs. This is quite involved if you do a call to an external function. The compiler does *not* see this call, so you will have to make sure that all that the compiler and linker do will work, or prevent some of those things (say, inlining of the function containing the call). > Otherwise, to be on the safe side we can just save r2 in a local var > before the bl and restore it after. I guess it won't collapse CPU time > on a performant PPC64. That does not fix everything. The called function requires a specific value in r2 on entry. So all this needs verification. Hopefully you can get away with just not clobbering r2 (and not adding a nop after the bl), sure. But this needs to be checked. Changing control flow inside inline assembler always is problematic. Another problem in this case (on all ABIs) is that the compiler does not see you call __do_irq. Again, you can probably get away with that too, but :-) Segher