From: cinap_lenrek@felloff.net
To: 9fans@9fans.net
Subject: Re: [9fans] extern register
Date: Sun, 20 Jul 2014 03:42:51 +0200 [thread overview]
Message-ID: <534b8febdabb6c739739c1e172dcb816@felloff.net> (raw)
In-Reply-To: <CAOw7k5hi4bL=rVMi2Tkhtet6J_VjuD0VVMtyjCJNx0aNUBQ1og@mail.gmail.com>
ok, i preserve user R14 and R15 now. also removed the saving and restoring
of DS/ES/FS/GS segment registers... they have no effect in long mode and
there are no 32 bit tasks.
someone write a proof of concept program that communicates with another
process by morsing data on the segment registers by loading them with
NULLSEL and UDSEL :)
--
cinap
next prev parent reply other threads:[~2014-07-20 1:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-19 1:57 cinap_lenrek
2014-07-19 2:04 ` erik quanstrom
2014-07-19 2:19 ` erik quanstrom
2014-07-19 2:33 ` cinap_lenrek
2014-07-19 2:37 ` erik quanstrom
2014-07-19 2:27 ` cinap_lenrek
2014-07-19 2:41 ` erik quanstrom
2014-07-19 12:29 ` Aram Hăvărneanu
2014-07-19 12:42 ` Charles Forsyth
2014-07-19 14:38 ` Aram Hăvărneanu
2014-07-19 14:55 ` erik quanstrom
2014-07-19 15:53 ` Aram Hăvărneanu
2014-07-20 1:42 ` cinap_lenrek [this message]
2014-07-20 10:12 ` Aram Hăvărneanu
2014-07-20 16:35 ` cinap_lenrek
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=534b8febdabb6c739739c1e172dcb816@felloff.net \
--to=cinap_lenrek@felloff.net \
--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).