From: ron minnich <rminnich@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] πp
Date: Fri, 15 Oct 2010 10:49:22 -0700 [thread overview]
Message-ID: <AANLkTin248RkUG83nAgqPN79-0RnwCXFgT_XDbu=JRMi@mail.gmail.com> (raw)
In-Reply-To: <EB9547BD-D480-4C38-A601-9E839B22C92E@gmail.com>
2010/10/15 Nemo <nemo.mbox@gmail.com>:
> So, when I hear migration, I just tend to see what happens after it has
> been implemented and faces the spaghethy phase.
And even if you get that right, it may not work well on hardware. We
saw cases with linux migration, while migrating from one x86 to
another, where valid FP values would cause the target to get an FP
trap. Made no sense, but it's what happened, because the two x86's
were different *implementations* of the same architecture. So,
migration works well for all the really easy cases -- CPU you migrate
to was fabbed by the same vendor in the same place with the same mask
and microcode as the one you migrate from -- and can fail on anything
tricky. That's why I don't like it either :-)
ron
next prev parent reply other threads:[~2010-10-15 17:49 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-13 19:46 Eric Van Hensbergen
2010-10-13 22:13 ` David Leimbach
2010-10-13 22:36 ` roger peppe
2010-10-13 23:15 ` David Leimbach
2010-10-14 4:25 ` blstuart
2010-10-13 23:24 ` Venkatesh Srinivas
2010-10-14 21:12 ` Latchesar Ionkov
2010-10-14 21:48 ` erik quanstrom
2010-10-14 22:14 ` dorin bumbu
2010-10-15 14:07 ` erik quanstrom
2010-10-15 14:45 ` Russ Cox
2010-10-15 15:41 ` Latchesar Ionkov
2010-10-15 21:13 ` dorin bumbu
2010-10-15 22:13 ` erik quanstrom
2010-10-15 23:30 ` dorin bumbu
2010-10-15 23:45 ` cinap_lenrek
2010-10-15 23:54 ` dorin bumbu
2010-10-15 7:24 ` Sape Mullender
2010-10-15 10:41 ` hiro
2010-10-15 12:11 ` Jacob Todd
2010-10-15 13:06 ` Iruatã Souza
2010-10-15 13:23 ` Sape Mullender
2010-10-15 14:57 ` David Leimbach
2010-10-15 14:54 ` David Leimbach
2010-10-15 14:59 ` Francisco J Ballesteros
2010-10-15 16:19 ` cinap_lenrek
2010-10-15 16:28 ` Lyndon Nerenberg
2010-10-15 17:54 ` Nemo
2010-10-15 17:49 ` ron minnich [this message]
2010-10-15 18:56 ` erik quanstrom
2010-10-15 16:31 ` Latchesar Ionkov
2010-10-15 16:40 ` cinap_lenrek
2010-10-15 16:43 ` Latchesar Ionkov
2010-10-15 17:11 ` cinap_lenrek
2010-10-15 17:15 ` Latchesar Ionkov
2010-10-15 19:10 ` erik quanstrom
2010-10-15 19:16 ` Latchesar Ionkov
2010-10-15 21:43 ` Julius Schmidt
2010-10-15 22:02 ` David Leimbach
2010-10-15 22:05 ` John Floren
2010-10-15 16:45 ` ron minnich
2010-10-15 17:26 ` Eric Van Hensbergen
2010-10-15 17:45 ` Charles Forsyth
2010-10-15 17:45 ` ron minnich
2010-10-15 18:03 ` Bakul Shah
2010-10-15 18:45 ` David Leimbach
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='AANLkTin248RkUG83nAgqPN79-0RnwCXFgT_XDbu=JRMi@mail.gmail.com' \
--to=rminnich@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).