Received: by 2002:a05:6a10:5bc5:0:0:0:0 with SMTP id os5csp3699300pxb; Sun, 24 Oct 2021 08:52:31 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxxI1+9oGaqhHlFrVUSeD0pVLxZ6+gHfg+XLIveHEI0VfQxzWw3LXx/RqRC79f40Ndrg3lE X-Received: by 2002:a17:90b:1004:: with SMTP id gm4mr3482155pjb.32.1635090750956; Sun, 24 Oct 2021 08:52:30 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1635090750; cv=none; d=google.com; s=arc-20160816; b=uKSgoLMPaCkInOMXqKn+Lq2xAoOczUjDGXVbxyDQjMTrE5T8HxJESI5+3HJsZsnFcv wUEyXR2m+JhquBVeY5Kn9Y0nxbbxTlnKSJC0zrYfIZdX1/Q/zIvuoV5C5/HQ/cGHVQiX 5hv2uhQ08hLT8WtaXTQxnbrGsxF5PMijaZBlSoVBEGSTkU54xBPa1q9fWMIOmnBvZRG0 sVzgXykg36D1SE3HovAJXwN4TLnPMHq7gHtZUTOMBXPpkyy3s2cD+uUtXy7o2yY5Yp/9 B/ZEwlx/rAZY9ra5KlxjdSfMeKFMJSXAqR/yl5lCYx+LjUkUutXpWnQ/IKQBJUJdkKEb grQg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:message-id:date:references :in-reply-to:subject:cc:to:from; bh=nvfhYArOSOSR7rL7bpWQgdLfIRcLTC/2yOu4yjgNIBc=; b=KxeXATEdUcAi6yCSKbOQNuaKTVz7n+bEtTMPmnCrRD+ytPFOICXeQxdycR+AsDEgyK bU3xtSZHPP60aAQD5kIxoILSyYFLwU6Kf0t5UtChW9kMRueb3RGSWlC4py96SEYMpNne 7bMBsODrJxsv2xOr4pFes3vVSSWkQV4T8ihqBjGZ134aUz4ffyYkVJtiuk0cBuOqZZep mZYoyQz+ZsLWVPKih70l2SaS6yNAmiNupOwKOyEZsOoPtghM2WpQ3jPkH1pUrEvG9R4q LBGY3PYpnLQ5sK4qaehYBNClsoc7I8GWw7ixMN2L1I2ZpUrAGeWNvdAeVVmhmZyA5u4w TbVw== ARC-Authentication-Results: i=1; mx.google.com; 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=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id k3si4040518plk.357.2021.10.24.08.52.17; Sun, 24 Oct 2021 08:52:30 -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; 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=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231394AbhJXPxF (ORCPT + 99 others); Sun, 24 Oct 2021 11:53:05 -0400 Received: from foss.arm.com ([217.140.110.172]:38342 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229755AbhJXPxE (ORCPT ); Sun, 24 Oct 2021 11:53:04 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 6C753D6E; Sun, 24 Oct 2021 08:50:42 -0700 (PDT) Received: from e113632-lin (usa-sjc-imap-foss1.foss.arm.com [10.121.207.14]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 34C5B3F5A1; Sun, 24 Oct 2021 08:50:41 -0700 (PDT) From: Valentin Schneider To: Marc Zyngier Cc: linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Will Deacon , Mark Rutland , Thomas Gleixner , Sebastian Andrzej Siewior , Ard Biesheuvel Subject: Re: [PATCH 1/3] irqchip/gic-v3-its: Give the percpu rdist struct its own flags field In-Reply-To: <87r1cct8cw.wl-maz@kernel.org> References: <20211022103307.1711619-1-valentin.schneider@arm.com> <20211022103307.1711619-2-valentin.schneider@arm.com> <87r1cct8cw.wl-maz@kernel.org> Date: Sun, 24 Oct 2021 16:50:34 +0100 Message-ID: <87bl3ejub9.mognet@arm.com> MIME-Version: 1.0 Content-Type: text/plain Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 23/10/21 10:10, Marc Zyngier wrote: > On Fri, 22 Oct 2021 11:33:05 +0100, > Valentin Schneider wrote: >> -#define RDIST_FLAGS_PROPBASE_NEEDS_FLUSHING (1 << 0) >> -#define RDIST_FLAGS_RD_TABLES_PREALLOCATED (1 << 1) >> +#define RDISTS_FLAGS_PROPBASE_NEEDS_FLUSHING (1 << 0) >> +#define RDISTS_FLAGS_RD_TABLES_PREALLOCATED (1 << 1) >> + >> +#define RDIST_FLAGS_LPI_ENABLED BIT(0) > > Just to reduce the churn and for me not to misread things (because > RDIST/RDISTS is pretty confusing), how about leaving the original > flags as is, and name the per-RD ones like: > > #define RD_LOCAL_LPI_ENABLED BIT(0) > > ? > > Or something else that'd be adequately different from the original > flags? > Aye, sounds like the right thing to do!