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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sun, 19 Feb 2012 23:21:23 +0800 From: Cong Wang <xiyou.wangcong@...il.com> To: Tao Jiang <jiangtao.jit@...il.com> CC: linux-kernel@...r.kernel.org Subject: Re: A problem with percpu variable cpu_number On 02/19/2012 08:20 PM, Tao Jiang wrote: > Hi : > > At the beginning of start_kernel() -- init/main.c > boot_cpu_init() is called > > and in boot_cpu_init() will call smp_processor_id() > it's a macro > and it will be expanded as (percpu_read(cpu_number)) and so on > > but i noticed that it's before setup_per_cpu_areas() in start_kernel() > is that mean the percpu areas hadn't be initialized yet > but why smp_processor_id() could be called before setup_per_cpu_areas() It doesn't matter, as the percpu var 'cpu_number' is defined statically: DECLARE_PER_CPU(int, cpu_number);. Thanks. -- 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/
Powered by blists - more mailing lists