From: Eric Lacombe <tuxiko@free.fr>
To: linux-kernel@vger.kernel.org
Cc: goretux@gmail.com
Subject: [x86] fs, gs purpose & multicore prog
Date: Wed, 3 Sep 2008 11:09:45 +0200 [thread overview]
Message-ID: <200809031109.45660.goretux@gmail.com> (raw)
Hello,
I've some questions about IA-32e in Linux.
- What is the FS and GS segments role inside the kernel ?
(I was thinking about thread local storage)
- When I do a "mov %fs ..." instruction (in a module), it seems that %fs is
equal to 0 (idem for %gs). Are these registers not always filled ?
- What is the purpose of MSR_FS_BASE and MSR_GS_BASE ?
(I thought they were filled with "gdt[fs_entry].base")
- My last question is about the kernel programation of multi-core (or
multiprocessor)
architecture. I don't see a lot of documentation about that on Internet.
Do you have some docs/urls about this topic.
Maybe someone can briefly explain how the execution flow are given to the
different cores.
Thanks in advance.
Eric
next reply other threads:[~2008-09-03 9:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-03 9:09 Eric Lacombe [this message]
2008-09-04 16:49 ` [x86] fs, gs purpose & multicore prog Jeremy Fitzhardinge
2008-09-05 11:17 ` Eric Lacombe
2008-09-05 14:51 ` Jeremy Fitzhardinge
2008-09-05 23:09 ` Eric Lacombe
2008-09-06 5:38 ` Jeremy Fitzhardinge
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=200809031109.45660.goretux@gmail.com \
--to=tuxiko@free.fr \
--cc=goretux@gmail.com \
--cc=linux-kernel@vger.kernel.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