Received: by 2002:a05:6a11:4021:0:0:0:0 with SMTP id ky33csp403522pxb; Wed, 29 Sep 2021 01:34:41 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzeRhq4FgwMQ/3+yHEBbu6eDYaX10Fwft6kuRxHltM//7Vs5uFKyXnsXk9GcwlTMoyuMSOD X-Received: by 2002:a17:906:340f:: with SMTP id c15mr12077671ejb.437.1632904481086; Wed, 29 Sep 2021 01:34:41 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1632904481; cv=none; d=google.com; s=arc-20160816; b=Uv6yrY5Ys3DqrgOwLe4H3e+9dGzzr6mklmUnnEAyvnvtXNrRZXjSi2IpxiCcG8L08i j0IuGI9RTiFHGQWqT1x1B5VSMHt19Xz970Cje7Qvxu78yQRANsaMoGi1Iambc8KrsXyA aornYmu0UTkQe7Z5qVBUvfgiq5RAsMhuHOcZO1V00AFkQ3yy4MVpPYE2/ev5rm7TFg2S w6iJVI7dKMGII1+igzQOvyYctcKWjlppJzSIPJMbY/JlRrfw47V+rdXaYvEpa37gvHdg U26OIWqxSmbPXNqnOuBSgLtu05edlEBkUOKodwlGZKZd6cqaGS0Hd/XPpIui7aieqh3y +NEw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=5B+J6ikPYVeFKKWzNbZvG5IpNmejBbX+SUEbN/ObqLg=; b=WeZnH/YwTFhQ+1Uyp1b35KDc7/ZiynnzKjMagoSC5vt9bbDNbn9vMeHL5ioQGD+qrQ VgJJjjNh4nGcD9CkQAH2Um3gqE9luknQtCKshszhdQRhjJT9pRa6lEXjr6pZjNHswhsE rIEhA61Q80yrfjt9MBK/Wlu4AuKME7zUk4wfQXm84E7KOW+dq4959mtm41lvLcK11nBI Stx/oSzcaNL31L/+XA0gVLHYmSwbGKRrYJc45AtgKEpC1pNa3deQUJyWaf72gv/QXmf8 Bbg6XM0oztVB3NXsrmQ+ARdwLECAaC6oS+35mQT0qa1lKcJaG4ArzHJ89r+jb8H37ZeP dIrA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=SdTlwGp0; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id r24si2377269ejy.194.2021.09.29.01.34.03; Wed, 29 Sep 2021 01:34:41 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=SdTlwGp0; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S244627AbhI2I3c (ORCPT + 99 others); Wed, 29 Sep 2021 04:29:32 -0400 Received: from us-smtp-delivery-124.mimecast.com ([170.10.133.124]:30832 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S240284AbhI2I3b (ORCPT ); Wed, 29 Sep 2021 04:29:31 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1632904070; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=5B+J6ikPYVeFKKWzNbZvG5IpNmejBbX+SUEbN/ObqLg=; b=SdTlwGp03Z1shgJGaLIB0MBiONp/GvYVvVcrdwT8sHa0g69DylJjLYuX+GInrch7ZKpL0x BJOpThU+YIlc4+7v8tZQ2mD06f8FRInkBOPNLsIRGMbL54QDJSXTu8H/UuyXWqQm8tDbMU BtKCwZcui3rzlACLqKYhI48gLsGMZgQ= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-324-_CN3CUe6NlKkYioyzTbRmw-1; Wed, 29 Sep 2021 04:27:46 -0400 X-MC-Unique: _CN3CUe6NlKkYioyzTbRmw-1 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 0D6179127B; Wed, 29 Sep 2021 08:27:22 +0000 (UTC) Received: from piliu.users.ipa.redhat.com (ovpn-8-24.pek2.redhat.com [10.72.8.24]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 62538101E1C5; Wed, 29 Sep 2021 08:27:16 +0000 (UTC) Date: Wed, 29 Sep 2021 16:27:11 +0800 From: Pingfan Liu To: Marc Zyngier Cc: Mark Rutland , Pingfan Liu , linux-arm-kernel@lists.infradead.org, Catalin Marinas , Will Deacon , Joey Gouly , Sami Tolvanen , Julien Thierry , Thomas Gleixner , Yuichi Ito , linux-kernel@vger.kernel.org Subject: Re: [PATCHv2 4/5] irqchip/GICv3: let gic_handle_irq() utilize irqentry on arm64 Message-ID: References: <20210924132837.45994-1-kernelfans@gmail.com> <20210924132837.45994-5-kernelfans@gmail.com> <20210928091053.GD1924@C02TD0UTHF1T.local> <87mtnvu9to.wl-maz@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87mtnvu9to.wl-maz@kernel.org> X-Scanned-By: MIMEDefang 2.84 on 10.5.11.22 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Sep 29, 2021 at 08:20:35AM +0100, Marc Zyngier wrote: > On Wed, 29 Sep 2021 04:10:11 +0100, > Pingfan Liu wrote: > > > > On Tue, Sep 28, 2021 at 10:10:53AM +0100, Mark Rutland wrote: > > > On Fri, Sep 24, 2021 at 09:28:36PM +0800, Pingfan Liu wrote: > > > > The call to rcu_irq_enter() originated from gic_handle_irq() is > > > > redundant now, since arm64 has enter_from_kernel_mode() akin to > > > > irqenter_entry(), which has already called rcu_irq_enter(). > > > > > > Here I think you're referring to the call in handle_domain_irq(), but > > > that isn't clear from the commit message. > > > > > Yes, and I will make it clear in V2. > > > > > > Based on code analysis, the redundant can raise some mistake, e.g. > > > > rcu_data->dynticks_nmi_nesting inc 2, which causes > > > > rcu_is_cpu_rrupt_from_idle() unexpected. > > > > > > > > So eliminate the call to irq_enter() in handle_domain_irq(). And > > > > accordingly supplementing irq_enter_rcu(). > > > > > > We support many more irqchips on arm64, and GICv3 can be used on regular > > > 32-bit arm, so this isn't right. Moving the irq_enter_rcu() call > > > into the GICv3 driver specifically breaks other drivers on arm64 by > > > removing the call, and breaks the GICv3 driver on arm by adding a > > > duplicate call. > > > > > Oops. I forgot to protect the code in GICv3 with CONFIG_HAVE_ARCH_IRQENTRY > > > > > It looks like this should live in do_interrupt_handler() in > > > arch/arm64/kernel/entry-common.c, e.g. > > > > > > | static void do_interrupt_handler(struct pt_regs *regs, > > > | void (*handler)(struct pt_regs *)) > > > | { > > > | irq_enter_rcu(); > > > | if (on_thread_stack()) > > > | call_on_irq_stack(regs, handler); > > > | else > > > | handler(regs); > > > | irq_exit_rcu(); > > > | } > > > > > > ... unless there's some problem with that? > > > > > Yeah, do_interrupt_handler() is a more suitable place. But to resolve > > the performance regression of rescheduling IPI [1], it is badly demanded to > > distinguish irqnr before calling irq_enter_rcu() (please see 5/5 and [2] > > for the context). So it is a compromise to host the code in GICv3. > > > > Any good idea? > > There is no way we are going to single out a particular interrupt > controller. As for the "regression", we'll have to look at the numbers > once we have fixed the whole infrastructure. > But I just realize that at present, gic_handle_nmi() sits behind gic_handle_irq(). So it will make an mistaken for accounting of normal interrupt if calling irq_enter_rcu() in do_interrupt_handler(). And going through drivers/irqchip/irq-chip-gic*, I think there are only two files should be handled: irq-gic.c and irq-gic-v3.c. Thanks, Pingfan