Re: [tip:x86/apic] x86/acpi: Introduce persistent storage for cpuid <-> apicid mapping
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [tip:x86/apic] x86/acpi: Introduce persistent storage for cpuid <-> apicid mapping
- From: Yinghai Lu <yinghai@xxxxxxxxxx>
- Date: Fri, 7 Oct 2016 11:55:39 -0700
- Cc: Dou Liyang <douly.fnst@xxxxxxxxxxxxxx>, Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx>, Ingo Molnar <mingo@xxxxxxxxxx>, "H. Peter Anvin" <hpa@xxxxxxxxx>, "linux-tip-commits@xxxxxxxxxxxxxxx" <linux-tip-commits@xxxxxxxxxxxxxxx>, Tony Luck <tony.luck@xxxxxxxxx>, "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>, "lenb@xxxxxxxxxx" <lenb@xxxxxxxxxx>, "Zheng, Lv" <lv.zheng@xxxxxxxxx>, Bob Moore <robert.moore@xxxxxxxxx>, ACPI Devel Maling List <linux-acpi@xxxxxxxxxxxxxxx>
- In-reply-to: <alpine.DEB.2.20.1610071455360.19804@nanos>
- References: <1472114120-3281-4-git-send-email-douly.fnst@cn.fujitsu.com> <tip-8f54969dc8d6704632b42cbb5e47730cd75cc713@git.kernel.org> <CAE9FiQVQx6FRXT-RdR7Crz4dg5LeUWHcUSy1KacjR+JgU_vGJg@mail.gmail.com> <alpine.DEB.2.20.1610041258410.7712@nanos> <CAE9FiQWigWvrZ8JzNDKtZ9FWARh2m0kGoF+VOZdwAdY9vnU3_w@mail.gmail.com> <4608f474-c49e-550b-90e2-c5f4c25e00f5@cn.fujitsu.com> <CAE9FiQVEvoK=TvYyhU6iiLh5FiX3pXXyy53tr2F7BEnRxGk7HA@mail.gmail.com> <e53a9807-2beb-0878-87dc-cc6f93b7c911@cn.fujitsu.com> <alpine.DEB.2.20.1610071448590.19804@nanos> <alpine.DEB.2.20.1610071455360.19804@nanos>
On Fri, Oct 7, 2016 at 6:00 AM, Thomas Gleixner <tglx@xxxxxxxxxxxxx> wrote:
> On Fri, 7 Oct 2016, Thomas Gleixner wrote:
>> 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.
>
> The ACPI spec says that bit 0 of the x2apic flags field tells whether the
> logical processor is present or not. So the proper check for x2apic is that
> flag.
>
> The lapic structure has the same flag, but the kernel ignores the flags for
> both lapic and x2apic.
>
> I'm going to apply the minimal fix of checking for id == 0xff in
> acpi_lapic_parse() for now, but this needs to be revisited and fixed
> proper.
Good to me. Thanks for fixing it.
Yinghai
--
To unsubscribe from this list: send the line "unsubscribe linux-tip-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
[Index of Archives]
[Linux Stable Commits]
[Linux Stable Kernel]
[Linux Kernel]
[Linux USB Devel]
[Linux Video &Media]
[Linux Audio Users]
[Yosemite News]
[Linux SCSI]