linux-kernel - RE: [PATCH] ia64: default the NUMA node distance when there is no ACPI SLIT

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Wed, 15 Aug 2007 09:34:50 -0700
From:	"Luck, Tony" <tony.luck@...el.com>
To:	"Andy Whitcroft" <apw@...dowen.org>
Cc:	<linux-ia64@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH] ia64: default the NUMA node distance when there is no ACPI SLIT

+	printk(KERN_INFO "Building NUMA distance from ACPI 2.0 SLIT\n");

This printk just looks like noise during boot.  Surely this
is normal behavior on a NUMA system?

+	printk(KERN_INFO "No SLIT table, defaulting NUMA distance\n");

But this one deserves more prominence than just KERN_INFO.  I'd
say that it deserves a KERN_ERR rating (without accurate information
we'll make some highly questionable scheduling and memory placement
decisions).  On the other hand the only way for the end-user to fix
this is to complain to their system vendor to fix firmware.  So perhaps
it is just a KERN_NOTICE.

-Tony
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/