From: "Steve Simon" <steve@quintile.net>
To: 9fans@9fans.net
Subject: Re: [9fans] why not halt in x86 multicore
Date: Mon, 4 Jul 2011 14:13:22 +0100 [thread overview]
Message-ID: <eb08eafaf7fc967ecae0a0016c499fad@quintile.net> (raw)
In-Reply-To: <dec8fdfc3428edfed2dd35da399c11c1@ladd.quanstro.net>
> so why don't you just give your plan 9 guest 1 processor, either through the vmm
> or *ncpu, and be done with it?
Too much work to port plan9 a cpu server to the mac ppc hardware... :-)
An intel mac would solve many problems I agree.
-Steve
next prev parent reply other threads:[~2011-07-04 13:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-01 14:00 Henning Schild
2011-07-01 17:23 ` erik quanstrom
2011-07-01 17:47 ` Ali Mashtizadeh
2011-07-01 17:51 ` Russ Cox
2011-07-01 18:01 ` erik quanstrom
2011-07-01 18:35 ` Bakul Shah
2011-07-02 5:06 ` Venkatesh Srinivas
2011-07-04 9:24 ` Henning Schild
2011-07-04 9:54 ` Sape Mullender
2011-07-04 13:02 ` erik quanstrom
2011-07-04 13:13 ` Steve Simon [this message]
2011-07-04 13:43 ` erik quanstrom
2011-07-04 13:47 ` Steve Simon
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=eb08eafaf7fc967ecae0a0016c499fad@quintile.net \
--to=steve@quintile.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).