From: losemyheaven@qq.com (=?gb18030?B?wuS62w==?=)
To: kernelnewbies@lists.kernelnewbies.org
Subject: where is __percpu_seg initialized?
Date: Sat, 23 Apr 2016 15:24:33 +0800 [thread overview]
Message-ID: <tencent_56B238C1379AEEAF6FB608F3@qq.com> (raw)
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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20160423/2c2d99ff/attachment.html
next reply other threads:[~2016-04-23 7:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-23 7:24 =?gb18030?B?wuS62w==?= [this message]
2016-04-23 14:02 ` where is __percpu_seg initialized? Dave Tian
2018-03-28 3:06 ` =?gb18030?B?wuS62w==?=
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_56B238C1379AEEAF6FB608F3@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).