[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.20.1610071448590.19804@nanos>
Date: Fri, 7 Oct 2016 14:50:07 +0200 (CEST)
From: Thomas Gleixner <tglx@...utronix.de>
To: Dou Liyang <douly.fnst@...fujitsu.com>
cc: Yinghai Lu <yinghai@...nel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Ingo Molnar <mingo@...nel.org>,
"H. Peter Anvin" <hpa@...or.com>,
"linux-tip-commits@...r.kernel.org"
<linux-tip-commits@...r.kernel.org>,
Tony Luck <tony.luck@...el.com>,
"Rafael J. Wysocki" <rjw@...ysocki.net>,
"lenb@...nel.org" <lenb@...nel.org>,
"Zheng, Lv" <lv.zheng@...el.com>, robert.moore@...el.com,
linux-acpi@...r.kernel.org
Subject: Re: [tip:x86/apic] x86/acpi: Introduce persistent storage for cpuid
<-> apicid mapping
On Fri, 7 Oct 2016, Dou Liyang wrote:
> Is it possible that the "-1/oxffffffff" could appear in the MADT which is one
> of the ACPI tables?
According to the SDM the x2apic id is a 32bit ID, so 0xffffffff is a
legitimate value.
Thanks,
tglx
Powered by blists - more mailing lists