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>] [day] [month] [year] [list]
Message-ID: <20160618082422.GA4065@x1.redhat.com>
Date:	Sat, 18 Jun 2016 16:24:22 +0800
From:	Baoquan He <bhe@...hat.com>
To:	tglx@...utronix.de
Cc:	linux-kernel@...r.kernel.org
Subject: The difference between x86_cpu_to_apicid and x86_bios_cpu_apicid

Hi Thomas,

Sorry to bother you. I am always wondering what's the difference between
x86_cpu_to_apicid and x86_bios_cpu_apicid. Or in other words, I don't
know why x86_bios_cpu_apicid is required. From code both
x86_cpu_to_apicid and x86_bios_cpu_apicid stores the apicid correspond
to a certain logic cpu number. With my understanding x86_cpu_to_apicid
can do what x86_bios_cpu_apicid is doing except for its usage in below
commit.

commit 1f12e32f4cd5243ae46d8b933181be0d022c6793
Author: Thomas Gleixner <tglx@...utronix.de>
Date:   Mon Feb 22 22:19:15 2016 +0000

    x86/topology: Create logical package id

Could you please help to explain when it's convenient to you?

Thanks
Baoquan

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ