From: cinap_lenrek@gmx.de
To: 9fans@9fans.net
Subject: Re: [9fans] some x86 Segment descriptor experiments
Date: Wed, 14 May 2008 02:12:45 +0200 [thread overview]
Message-ID: <0e89aa27f8e0c7383dbb8e2de1054ec6@gmx.de> (raw)
In-Reply-To: <13426df10805131626q1c3775b2hc7957c7e77ed724@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 444 bytes --]
arrrg... i found the problem... of course! Plan9 *does* restore/reload the
segment registers! It does it still in kernel mode. So if a segment
register is set (from usermode) with a selector pointing to my TLS
descriptor, and that descriptor gets changed to {0, 0} again, forkret()
restores/reloads the segment register and *kernel* gets a GP fault.
Now the selector checking in trap() makes sense... arrg >_<
sorry for the noise...
[-- Attachment #2: Type: message/rfc822, Size: 2482 bytes --]
From: "ron minnich" <rminnich@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] some x86 Segment descriptor experiments
Date: Tue, 13 May 2008 16:26:31 -0700
Message-ID: <13426df10805131626q1c3775b2hc7957c7e77ed724@mail.gmail.com>
it seems reasonable on first glance. What's the stack barf look like?
ron
prev parent reply other threads:[~2008-05-14 0:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-13 22:10 cinap_lenrek
2008-05-13 23:26 ` ron minnich
2008-05-14 0:12 ` cinap_lenrek [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=0e89aa27f8e0c7383dbb8e2de1054ec6@gmx.de \
--to=cinap_lenrek@gmx.de \
--cc=9fans@9fans.net \
/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).