From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id CF88E44396; Wed, 27 Dec 2023 11:15:23 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="pP9RBZ+D" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 354F6C433C8; Wed, 27 Dec 2023 11:15:16 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1703675723; bh=Gy+D+S27rQJBs12wlJEa+cumgsdCkF3P6tKjEyxVt5s=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=pP9RBZ+DfqI9ufbs6J2xz/FKM0nY4Pwf02G34GG/l91DTZu2tk+J7E60zTnEhjPL3 qZpNUMit64mYzbAtmwb9KGD6zaz5A40god5gLykenVaCm2sXCYmzeuPBwh81SyO6PE Bmza1w3YIvrK9XpCQ1ll0SBpVNNIbPKuiFHL1di27kuvrOtBBRDVMYxJBl9aC9WXFF MVkAcY36NePVzE7QE5kh7q0qI8bFlVKwHv5Lb87s+QQdATKl+4EzU0nNeZCmAVTbhm BIC374HdlJLWXGEfqtrC7dzBPDecYaAPxTeXEnoldydMWpAyK6aa7O4FdWU6pXS3QV BU1AUG2sovIcQ== Date: Wed, 27 Dec 2023 12:15:14 +0100 From: Lorenzo Pieralisi To: "Rafael J. Wysocki" Cc: "Russell King (Oracle)" , Jonathan Cameron , linux-pm@vger.kernel.org, loongarch@lists.linux.dev, linux-acpi@vger.kernel.org, linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-riscv@lists.infradead.org, kvmarm@lists.linux.dev, x86@kernel.org, acpica-devel@lists.linuxfoundation.org, linux-csky@vger.kernel.org, linux-doc@vger.kernel.org, linux-ia64@vger.kernel.org, linux-parisc@vger.kernel.org, Salil Mehta , Jean-Philippe Brucker , jianyong.wu@arm.com, justin.he@arm.com, James Morse Subject: Re: [PATCH RFC v3 13/21] ACPICA: Add new MADT GICC flags fields Message-ID: References: <20231215162322.00007391@Huawei.com> Precedence: bulk X-Mailing-List: linux-parisc@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: On Mon, Dec 18, 2023 at 02:14:30PM +0100, Rafael J. Wysocki wrote: > On Mon, Dec 18, 2023 at 10:23 AM Lorenzo Pieralisi > wrote: > > > > On Fri, Dec 15, 2023 at 04:53:28PM +0000, Russell King (Oracle) wrote: > > > On Fri, Dec 15, 2023 at 04:23:22PM +0000, Jonathan Cameron wrote: > > > > On Wed, 13 Dec 2023 12:50:18 +0000 > > > > Russell King (Oracle) wrote: > > > > > > > > > From: James Morse > > > > > > > > > > Add the new flag field to the MADT's GICC structure. > > > > > > > > > > 'Online Capable' indicates a disabled CPU can be enabled later. See > > > > > ACPI specification 6.5 Tabel 5.37: GICC CPU Interface Flags. > > > > > > > > > > Signed-off-by: James Morse > > > > > Tested-by: Miguel Luis > > > > > Tested-by: Vishnu Pajjuri > > > > > Tested-by: Jianyong Wu > > > > > Signed-off-by: Russell King (Oracle) > > > > > > > > I see there is an acpica pull request including this bit but with a different name > > > > For reference. > > > > https://github.com/acpica/acpica/pull/914/commits/453a5f67567786522021d5f6913f561f8b3cabf6 > > > > > > > > +CC Lorenzo who submitted that. > > > > > > > > +#define ACPI_MADT_GICC_CPU_CAPABLE (1<<3) /* 03: CPU is online capable */ > > > > > > > > ACPI_MADT_GICC_ONLINE_CAPABLE > > > > > > It's somewhat disappointing, but no big deal. It's easy enough to change > > > "irqchip/gic-v3: Add support for ACPI's disabled but 'online capable' CPUs" > > > to use Lorenzo's name when that patch hits - and it becomes one less > > > patch in this patch set when Lorenzo's change eventually hits mainline. > > > > > > Does anyone know how long it may take for Lorenzo's change to get into > > > mainline? Would it be by the 6.8 merge window or the following one? > > > > I wish I knew. I submitted ACPICA changes for the online capable bit > > since I had to add additional flags on top (ie DMA coherent) and it > > would not make sense to submit the latter without the former. > > > > I'd be great if the ACPICA headers can make it into Linux for the upcoming > > merge window, not sure what I can do to fasttrack the process though > > (I shall ping the maintainers). > > If your upstream pull request has been merged, I can pick up Linux > patches carrying Link: tags pointing to the upstream ACPICA commits in > that pull request. ACPICA PR was merged, sent the Linuxized version along with the GIC changes here: https://lore.kernel.org/lkml/20231227110038.55453-1-lpieralisi@kernel.org Thanks, Lorenzo