From: Sunil V L <sunilvl@ventanamicro.com>
To: Haibo Xu <haibo1.xu@intel.com>
Cc: xiaobo55x@gmail.com, ajones@ventanamicro.com,
"Paul Walmsley" <paul.walmsley@sifive.com>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Albert Ou" <aou@eecs.berkeley.edu>,
"Rafael J. Wysocki" <rafael@kernel.org>,
"Len Brown" <lenb@kernel.org>,
"Robert Moore" <robert.moore@intel.com>,
"Conor Dooley" <conor.dooley@microchip.com>,
"Guo Ren" <guoren@kernel.org>,
"Alexandre Ghiti" <alexghiti@rivosinc.com>,
"Greentime Hu" <greentime.hu@sifive.com>,
"Anup Patel" <apatel@ventanamicro.com>,
"Zong Li" <zong.li@sifive.com>,
"Sami Tolvanen" <samitolvanen@google.com>,
"Jisheng Zhang" <jszhang@kernel.org>,
"Baoquan He" <bhe@redhat.com>,
"Clément Léger" <cleger@rivosinc.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Chen Jiahao" <chenjiahao16@huawei.com>,
"Arnd Bergmann" <arnd@arndb.de>,
"James Morse" <james.morse@arm.com>,
"Evan Green" <evan@rivosinc.com>,
"Samuel Holland" <samuel.holland@sifive.com>,
"Tony Luck" <tony.luck@intel.com>,
"Ard Biesheuvel" <ardb@kernel.org>,
"Yuntao Wang" <ytcoode@gmail.com>,
"Dan Williams" <dan.j.williams@intel.com>,
"Alison Schofield" <alison.schofield@intel.com>,
"Dave Hansen" <dave.hansen@linux.intel.com>,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-acpi@vger.kernel.org, acpica-devel@lists.linux.dev
Subject: Re: [PATCH v2 4/6] ACPI: NUMA: Make some NUMA related parse functions common
Date: Mon, 1 Apr 2024 12:30:56 +0530 [thread overview]
Message-ID: <ZgpbqAraGbQqZv5d@sunil-laptop> (raw)
In-Reply-To: <c8b86184d9e6d078e9b9949d4837bc6e392c3f52.1709780590.git.haibo1.xu@intel.com>
On Thu, Mar 07, 2024 at 04:47:56PM +0800, Haibo Xu wrote:
> The acpi_numa_slit_init(), acpi_numa_memory_affinity_init()
> and acpi_parse_cfmws() functions are common enough to be used
> on platforms that support ACPI_NUMA(x86/arm64/loongarch).
> Remove the condition to avoid long defined(CONFIG_ARCH) check
> when new platform(riscv) support was enabled.
>
> Suggested-by: Sunil V L <sunilvl@ventanamicro.com>
> Signed-off-by: Haibo Xu <haibo1.xu@intel.com>
> ---
> drivers/acpi/numa/srat.c | 8 --------
> 1 file changed, 8 deletions(-)
>
> diff --git a/drivers/acpi/numa/srat.c b/drivers/acpi/numa/srat.c
> index 1946431c0eef..938c4adb7ec4 100644
> --- a/drivers/acpi/numa/srat.c
> +++ b/drivers/acpi/numa/srat.c
> @@ -219,7 +219,6 @@ int __init srat_disabled(void)
> return acpi_numa < 0;
> }
>
> -#if defined(CONFIG_X86) || defined(CONFIG_ARM64) || defined(CONFIG_LOONGARCH)
> /*
> * Callback for SLIT parsing. pxm_to_node() returns NUMA_NO_NODE for
> * I/O localities since SRAT does not list them. I/O localities are
> @@ -351,13 +350,6 @@ static int __init acpi_parse_cfmws(union acpi_subtable_headers *header,
> (*fake_pxm)++;
> return 0;
> }
> -#else
> -static int __init acpi_parse_cfmws(union acpi_subtable_headers *header,
> - void *arg, const unsigned long table_end)
> -{
> - return 0;
> -}
> -#endif /* defined(CONFIG_X86) || defined (CONFIG_ARM64) */
>
> static int __init acpi_parse_slit(struct acpi_table_header *table)
> {
LGTM.
Reviewed-by: Sunil V L <sunilvl@ventanamicro.com>
next prev parent reply other threads:[~2024-04-01 7:01 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-07 8:47 [PATCH v2 0/6] Add ACPI NUMA support for RISC-V Haibo Xu
2024-03-07 8:47 ` [PATCH v2 1/6] ACPICA: SRAT: Add RISC-V RINTC affinity structure Haibo Xu
2024-03-07 8:47 ` [PATCH v2 2/6] ACPI: RISCV: Add NUMA support based on SRAT and SLIT Haibo Xu
2024-04-01 7:06 ` Sunil V L
2024-04-01 7:41 ` Haibo Xu
2024-04-02 9:31 ` Alexandre Ghiti
2024-04-07 3:09 ` Haibo Xu
2024-03-07 8:47 ` [PATCH v2 3/6] ACPI: NUMA: Add handler for SRAT RINTC affinity structure Haibo Xu
2024-04-01 6:56 ` Sunil V L
2024-03-07 8:47 ` [PATCH v2 4/6] ACPI: NUMA: Make some NUMA related parse functions common Haibo Xu
2024-04-01 7:00 ` Sunil V L [this message]
2024-03-07 8:47 ` [PATCH v2 5/6] ACPI: NUMA: Remove ARCH depends option in ACPI_NUMA Kconfig Haibo Xu
2024-03-07 8:44 ` Arnd Bergmann
2024-03-07 9:19 ` Haibo Xu
2024-03-07 9:22 ` Arnd Bergmann
2024-03-07 9:28 ` Haibo Xu
2024-03-07 8:47 ` [PATCH v2 6/6] ACPI: RISCV: Enable ACPI based NUMA Haibo Xu
2024-04-01 7:18 ` Sunil V L
2024-04-01 8:04 ` Haibo Xu
2024-04-01 16:57 ` Luck, Tony
2024-04-03 3:54 ` Sunil V L
2024-04-07 2:53 ` Haibo Xu
2024-03-27 12:37 ` [PATCH v2 0/6] Add ACPI NUMA support for RISC-V Haibo Xu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZgpbqAraGbQqZv5d@sunil-laptop \
--to=sunilvl@ventanamicro.com \
--cc=acpica-devel@lists.linux.dev \
--cc=ajones@ventanamicro.com \
--cc=alexghiti@rivosinc.com \
--cc=alison.schofield@intel.com \
--cc=aou@eecs.berkeley.edu \
--cc=apatel@ventanamicro.com \
--cc=ardb@kernel.org \
--cc=arnd@arndb.de \
--cc=bhe@redhat.com \
--cc=chenjiahao16@huawei.com \
--cc=cleger@rivosinc.com \
--cc=conor.dooley@microchip.com \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=evan@rivosinc.com \
--cc=greentime.hu@sifive.com \
--cc=gregkh@linuxfoundation.org \
--cc=guoren@kernel.org \
--cc=haibo1.xu@intel.com \
--cc=james.morse@arm.com \
--cc=jszhang@kernel.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=rafael@kernel.org \
--cc=robert.moore@intel.com \
--cc=samitolvanen@google.com \
--cc=samuel.holland@sifive.com \
--cc=tony.luck@intel.com \
--cc=xiaobo55x@gmail.com \
--cc=ytcoode@gmail.com \
--cc=zong.li@sifive.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox