From: Russ Cox <rsc@swtch.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Status of 9vx on Windows?
Date: Fri, 15 Oct 2010 10:48:23 -0400 [thread overview]
Message-ID: <AANLkTinQTAo8vh_dMQC88T-6AqqRu4qnZQiAryG_rwaZ@mail.gmail.com> (raw)
In-Reply-To: <3E7E6601-EF50-4B6A-8E68-7C59D1303B49@gmail.com>
On Thu, Oct 14, 2010 at 3:16 PM, Skip Tavakkolian
<skip.tavakkolian@gmail.com> wrote:
> Has anyone attempted to get it running on Windows?
Andre Gunther had a look during GSoC a few years back.
It is a pain. Windows does not trigger the exception handler
if it thinks the segment registers are wrong, so 9vx cannot
handle its own page faults. I think it might be possible to
structure 9vx as two processes, one operating as a kind of
debugger process attached to the main one, and have the
debugger process grab and redirect the faults, but it seems
like a lot of work.
Russ
prev parent reply other threads:[~2010-10-15 14:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-14 19:16 Skip Tavakkolian
2010-10-15 14:48 ` Russ Cox [this message]
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=AANLkTinQTAo8vh_dMQC88T-6AqqRu4qnZQiAryG_rwaZ@mail.gmail.com \
--to=rsc@swtch.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).