[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <SJ1PR11MB608359E8F8700DAEC9D4663AFC98A@SJ1PR11MB6083.namprd11.prod.outlook.com>
Date: Fri, 23 May 2025 17:47:56 +0000
From: "Luck, Tony" <tony.luck@...el.com>
To: "Keshavamurthy, Anil S" <anil.s.keshavamurthy@...el.com>,
"rafael@...nel.org" <rafael@...nel.org>
CC: "Chen, Yu C" <yu.c.chen@...el.com>, "lenb@...nel.org" <lenb@...nel.org>,
"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"patches@...ts.linux.dev" <patches@...ts.linux.dev>
Subject: RE: [PATCH] ACPI/MRRM: Fix default max memory region
> Per the spec, the default max memory region must be 1 covering
> all system memory.
>
> When platform does not provide ACPI MRRM table or
> when CONFIG_ACPI is opted out, the acpi_mrrm_max_mem_region() function
> defaults to returning 1 region complying to RDT spec.
>
> Signed-off-by: Anil S Keshavamurthy <anil.s.keshavamurthy@...el.com>
Good (corner case) catch. I was too focused on the assumption that MRRM
table will be present when needed. Always a good plan to have a backup
option if BIOS does something strange.
Reviewed-by: Tony Luck <tony.luck@...el.com>
-Tony
Powered by blists - more mailing lists