From: Kurt Garloff <garloff@suse.de>
To: Linux kernel list <linux-kernel@vger.kernel.org>
Subject: [PATCH 1/3] Resend: [PATCH 1/3]: Store SRAT revision
Date: Tue, 14 Jul 2009 18:57:22 +0200 [thread overview]
Message-ID: <20090714165722.GE31657@tpkurt2.suse.de> (raw)
In-Reply-To: <20090714165508.GD31657@tpkurt2.suse.de>
[-- Attachment #1.1: Type: text/plain, Size: 535 bytes --]
Hi,
In SRAT v1, we had 8bit proximity domain (PXM) fields; SRAT v2 provides
32bits for these. The new fields were reserved before.
According to the ACPI spec, the OS must disregard reserved fields.
In order to know whether to disregard or not, we must know what
version the SRAT table has.
This patch stores the SRAT table revision for later consumption
by arch specific __init functions.
This is patch 1/3.
Signed-off-by: Kurt Garloff <garloff@suse.de>
--
Kurt Garloff, VP OPS Partner Engineering -- Novell Inc.
[-- Attachment #1.2: 01_srat-pxm-rev-store.diff --]
[-- Type: text/x-patch, Size: 1491 bytes --]
From: Kurt Garloff <garloff@suse.de>
Subject: Store SRAT table revision
In SRAT v1, we had 8bit proximity domain (PXM) fields; SRAT v2 provides
32bits for these. The new fields were reserved before.
According to the ACPI spec, the OS must disregard reserved fields.
In order to know whether to disregard or not, we must know what
version the SRAT table has.
This patch stores the SRAT table revision for later consumption
by arch specific __init functions.
This is patch 1/3.
Signed-off-by: Kurt Garloff <garloff@suse.de>
diff -r a28eb89d1fe1 drivers/acpi/numa.c
--- a/drivers/acpi/numa.c Tue Jul 14 02:00:45 2009 +0000
+++ b/drivers/acpi/numa.c Tue Jul 14 16:44:35 2009 +0200
@@ -42,6 +42,8 @@
static int node_to_pxm_map[MAX_NUMNODES]
= { [0 ... MAX_NUMNODES - 1] = PXM_INVAL };
+unsigned char acpi_srat_revision __initdata;
+
int pxm_to_node(int pxm)
{
if (pxm < 0)
@@ -266,6 +268,7 @@
return -EINVAL;
srat = (struct acpi_table_srat *)table;
+ acpi_srat_revision = srat->header.revision;
return 0;
}
diff -r a28eb89d1fe1 include/acpi/acpi_numa.h
--- a/include/acpi/acpi_numa.h Tue Jul 14 02:00:45 2009 +0000
+++ b/include/acpi/acpi_numa.h Tue Jul 14 16:44:35 2009 +0200
@@ -15,6 +15,7 @@
extern int node_to_pxm(int);
extern void __acpi_map_pxm_to_node(int, int);
extern int acpi_map_pxm_to_node(int);
+extern unsigned char acpi_srat_revision;
#endif /* CONFIG_ACPI_NUMA */
#endif /* __ACP_NUMA_H */
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2009-07-14 16:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-18 9:33 [PATCH 0/3]: Discard reserved PXM bits for SRAT v1 Kurt Garloff
2009-05-18 9:46 ` [PATCH 1/3]: Store SRAT revision Kurt Garloff
2009-05-18 9:47 ` [PATCH 2/3]: x86-64: Handle SRAT v1 and v2 consistently Kurt Garloff
2009-05-18 20:04 ` Yinghai Lu
2009-05-18 9:49 ` [PATCH 3/3]: Consider SRAT rev on ia64 Kurt Garloff
2009-05-18 15:33 ` [PATCH 0/3]: Discard reserved PXM bits for SRAT v1 Greg KH
2009-05-19 9:01 ` xb
2009-06-22 14:05 ` Erik Jacobson
2009-07-14 16:55 ` [PATCH 0/3] Resend: " Kurt Garloff
2009-07-14 16:57 ` Kurt Garloff [this message]
2009-07-14 16:58 ` [PATCH 2/3] Resend: x86-64: Handle SRAT v1 and v2 consistently Kurt Garloff
2009-07-17 22:10 ` Yinghai Lu
2009-07-14 16:59 ` [PATCH 3/3] Resend: Consider SRAT rev on ia64 Kurt Garloff
2009-08-13 13:38 ` [PATCH 0/3]: Discard reserved PXM bits for SRAT v1 Chuck Ebbert
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=20090714165722.GE31657@tpkurt2.suse.de \
--to=garloff@suse.de \
--cc=linux-kernel@vger.kernel.org \
/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
Powered by JetHome