From: losemyheaven@qq.com (=?gb18030?B?wuS62w==?=)
To: kernelnewbies@lists.kernelnewbies.org
Subject: where is __percpu_seg initialized?
Date: Wed, 28 Mar 2018 11:06:55 +0800 [thread overview]
Message-ID: <tencent_C31BFF8CE6F949F85BFCB712D8FD641F4209@qq.com> (raw)
In-Reply-To: <181C899F-91C2-4A27-ACE6-E924B5444234@gmail.com>
setup_per_cpu_areas just prepare a per-cpu area for each
possible cpu, and it doesn't try to start up other possible cpu(s).
The address of a per-cpu area corresponding to this cpu will be
written to its per-cpu-area register , before starting up.
Starting up other non-boot cpu happens in start_secondary function.
Larry
------------------ Original ------------------
From: "Dave Tian"<dave.jing.tian@gmail.com>;
Date: Sat, Apr 23, 2016 10:02 PM
To: "??"<losemyheaven@qq.com>;
Cc: "kernelnewbies"<kernelnewbies@kernelnewbies.org>;
Subject: Re: where is __percpu_seg initialized?
load_percpu_segment, which is called by switch_to_new_gdt in setup_per_cpu_areas.
-daveti
> On Apr 23, 2016, at 3:24 AM, ?? <losemyheaven@qq.com> wrote:
>
> Hi all:
> I knew the kernel implement the per-cpu variable via __percpu_seg. For example on x86 architecture, it's defined as:
>
> #ifdef CONFIG_X86_64
> #define __percpu_seg gs
> #define __percpu_mov_op movq
> #else
> #define __percpu_seg fs
> #define __percpu_mov_op movl
> #endif
>
> But I'm curious where __percpu_seg is initialized?? I fail to find the relative code. Thanks.
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20180328/af86be6a/attachment.html>
prev parent reply other threads:[~2018-03-28 3:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-23 7:24 where is __percpu_seg initialized? =?gb18030?B?wuS62w==?=
2016-04-23 14:02 ` Dave Tian
2018-03-28 3:06 ` =?gb18030?B?wuS62w==?= [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=tencent_C31BFF8CE6F949F85BFCB712D8FD641F4209@qq.com \
--to=losemyheaven@qq.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).