From: erik quanstrom <quanstro@quanstro.net>
To: Andre.G@gmx.de, 9fans@9fans.net
Subject: Re: [9fans] porting p9p to Google's NaCl
Date: Sat, 13 Jun 2009 11:53:58 -0400 [thread overview]
Message-ID: <123caf6f89b75dba06a6dbe4c40f0f23@quanstro.net> (raw)
> This is how TLS is done. Either %gs or %fs are setup so that a
> prefixed instruction will use the TLS address range.
all the world's a vax. er, wrong century. all the world's
an x86.
> The basic idea is: when segment translation is done anyway, let's
> exploit it and get guest code memory translation/access restriction
> for free)
i think you misspelled "for the cost of portability".
- erik
next reply other threads:[~2009-06-13 15:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-13 15:53 erik quanstrom [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-06-12 20:04 Skip Tavakkolian
2009-06-13 1:04 ` Roman V Shaposhnik
2009-06-13 4:07 ` Skip Tavakkolian
2009-06-13 11:08 ` André Günther
2009-06-13 14:36 ` David Leimbach
2009-06-13 15:13 ` André Günther
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=123caf6f89b75dba06a6dbe4c40f0f23@quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
--cc=Andre.G@gmx.de \
/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).