linux-kernel - Re: [PATCH v2][TRIVIAL] x86/smpboot: fix cpu bootup message

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: <CAE9FiQV401-fC=aTAfvkz3e3nUmJtXTTLGjnwR9innXwU13TmA@mail.gmail.com>
Date:	Mon, 23 Dec 2013 22:09:24 -0800
From:	Yinghai Lu <yinghai@...nel.org>
To:	Xie XiuQi <xiexiuqi@...wei.com>
Cc:	Borislav Petkov <bp@...e.de>, Ingo Molnar <mingo@...hat.com>,
	Ingo Molnar <mingo@...e.hu>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Li Bin <huawei.libin@...wei.com>
Subject: Re: [PATCH v2][TRIVIAL] x86/smpboot: fix cpu bootup message

On Mon, Dec 23, 2013 at 7:52 PM, Xie XiuQi <xiexiuqi@...wei.com> wrote:
> [    0.000000] ACPI: Local APIC address 0xfee00000
> [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
> [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
> [    0.000000] SRAT: PXM 0 -> APIC 0x12 -> Node 0
> [    0.000000] SRAT: PXM 0 -> APIC 0x14 -> Node 0
> [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
> [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
> [    0.000000] SRAT: PXM 0 -> APIC 0x13 -> Node 0
> [    0.000000] SRAT: PXM 0 -> APIC 0x15 -> Node 0
> [    0.000000] SRAT: PXM 1 -> APIC 0x20 -> Node 1
> [    0.000000] SRAT: PXM 1 -> APIC 0x22 -> Node 1
> [    0.000000] SRAT: PXM 1 -> APIC 0x32 -> Node 1
> [    0.000000] SRAT: PXM 1 -> APIC 0x34 -> Node 1
> [    0.000000] SRAT: PXM 1 -> APIC 0x21 -> Node 1
> [    0.000000] SRAT: PXM 1 -> APIC 0x23 -> Node 1
> [    0.000000] SRAT: PXM 1 -> APIC 0x33 -> Node 1
> [    0.000000] SRAT: PXM 1 -> APIC 0x35 -> Node 1
> [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x0009ffff]
> [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00100000-0xbfffffff]
> [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x63fffffff]
> [    0.000000] SRAT: Node 1 PXM 1 [mem 0x640000000-0xc3fffffff]
...
> [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x20] enabled)
> [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x22] enabled)
> [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x32] enabled)
> [    0.000000] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x34] enabled)
> [    0.000000] ACPI: LAPIC (acpi_id[0x05] lapic_id[0x00] enabled)
> [    0.000000] ACPI: LAPIC (acpi_id[0x06] lapic_id[0x02] enabled)
> [    0.000000] ACPI: LAPIC (acpi_id[0x07] lapic_id[0x12] enabled)
> [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x14] enabled)
> [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x21] enabled)
> [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x23] enabled)
> [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x33] enabled)
> [    0.000000] ACPI: LAPIC (acpi_id[0x0c] lapic_id[0x35] enabled)
> [    0.000000] ACPI: LAPIC (acpi_id[0x0d] lapic_id[0x01] enabled)
> [    0.000000] ACPI: LAPIC (acpi_id[0x0e] lapic_id[0x03] enabled)
> [    0.000000] ACPI: LAPIC (acpi_id[0x0f] lapic_id[0x13] enabled)
> [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x15] enabled)
> [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x90] disabled)
> [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x91] disabled)
> [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x92] disabled)
> [    0.000000] ACPI: LAPIC (acpi_id[0x14] lapic_id[0x93] disabled)
> [    0.000000] ACPI: LAPIC (acpi_id[0x15] lapic_id[0x94] disabled)
> [    0.000000] ACPI: LAPIC (acpi_id[0x16] lapic_id[0x95] disabled)
> [    0.000000] ACPI: LAPIC (acpi_id[0x17] lapic_id[0x96] disabled)
> [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x97] disabled)

Amazing!

Your BIOS engineers really have different idea about building MADT.

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/