linux-kernel - Re: [PATCH v3 17/22] x86, ACPI, numa, ia64: split SLIT handling out

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAE9FiQW9LsXo7gRvpAUv2ORbe2iuZaYO9nNOP-vTWa-_P450tg@mail.gmail.com>
Date:	Fri, 5 Apr 2013 15:16:48 -0700
From:	Yinghai Lu <yinghai@...nel.org>
To:	Tony Luck <tony.luck@...il.com>
Cc:	Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...e.hu>,
	"H. Peter Anvin" <hpa@...or.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Tejun Heo <tj@...nel.org>, Thomas Renninger <trenn@...e.de>,
	Tang Chen <tangchen@...fujitsu.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	"Rafael J. Wysocki" <rjw@...k.pl>,
	linux-acpi <linux-acpi@...r.kernel.org>,
	Fenghua Yu <fenghua.yu@...el.com>,
	"linux-ia64@...r.kernel.org" <linux-ia64@...r.kernel.org>
Subject: Re: [PATCH v3 17/22] x86, ACPI, numa, ia64: split SLIT handling out

On Fri, Apr 5, 2013 at 2:54 PM, Tony Luck <tony.luck@...il.com> wrote:
> On Thu, Apr 4, 2013 at 4:46 PM, Yinghai Lu <yinghai@...nel.org> wrote:
>> It should not break ia64 by replacing acpi_numa_init with
>> acpi_numa_init_srat/acpi_numa_init_slit/acpi_num_arch_fixup.
>
> You are right - it doesn't break ia64.  All my test configs still
> build.  Machines both with and without NUMA still boot and
> nothing strange happens.
>
> Tested-by: Tony Luck <tony.luck@...el.com>

Great, Thanks a lot for testing them.

Yinghai
--
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/