From: Charles Forsyth <charles.forsyth@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] magic number
Date: Mon, 7 Nov 2011 20:35:38 +0000 [thread overview]
Message-ID: <CAOw7k5gTQFcWaXi+eNiNn6XM9DWwC=FtvdsWkXE2s6vrdi8G-A@mail.gmail.com> (raw)
This is just a note to ensure that the values below appear in the archives.
If you're wondering why a register contains 0xfaf0f1fe (or 0xFAF0F1FE)
or 0xFEF1F0FA on big-endian machines, and you think "I can guess
that's a marker, and I'm sure I've seen that somewhere"
but can't find it with grep, you'll find it in the place you first
thought of: /sys/src/libc/port/pool.c
where it appears as separate bytes as the "datamagic" data sequence
0xFE, 0xF1, 0xF0, 0xFA
(which you might also see written that way in a memory dump).
next reply other threads:[~2011-11-07 20:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-07 20:35 Charles Forsyth [this message]
2011-11-07 20:47 ` ron minnich
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='CAOw7k5gTQFcWaXi+eNiNn6XM9DWwC=FtvdsWkXE2s6vrdi8G-A@mail.gmail.com' \
--to=charles.forsyth@gmail.com \
--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).