From: geoff@plan9.bell-labs.com
To: me@acm.jhu.edu, 9fans@9fans.net
Subject: Re: [9fans] vga vesa works on mp pc
Date: Tue, 8 Dec 2009 21:27:43 -0500 [thread overview]
Message-ID: <425c285155e5e2e5adcd28085c93ec13@plan9.bell-labs.com> (raw)
In-Reply-To: <f75780240912081721o1b706b89wfe71973a125af34e@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 187 bytes --]
As far as I can tell, yes, that's all it took.
The old code had been turning off the old 8259 interrupt controllers
used by uniprocessors but didn't disable the lapic on mp systems.
[-- Attachment #2: Type: message/rfc822, Size: 3462 bytes --]
From: Venkatesh Srinivas <me@acm.jhu.edu>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] vga vesa works on mp pc
Date: Tue, 8 Dec 2009 20:21:18 -0500
Message-ID: <f75780240912081721o1b706b89wfe71973a125af34e@mail.gmail.com>
On Tue, Dec 8, 2009 at 7:05 PM, <geoff@plan9.bell-labs.com> wrote:
> I've just pushed out a small change to /sys/src/9/pc/realmode.c that
> allows monitor=vesa to work on multiprocessor pcs without *nomp being
> defined in plan9.ini (i.e., you can use all available processors [or
> cores] and still use vesa mode). I've also pushed out new kernels, so
> the distribution built tonight should include this fix.
Cool, thanks!
If I read this right, you turn off interrupts on just the CPU
executing in realmode. Is the really all that had to be done for vesa
to support MP systems?
-- vs
next prev parent reply other threads:[~2009-12-09 2:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-09 0:05 geoff
2009-12-09 1:21 ` Venkatesh Srinivas
2009-12-09 2:27 ` geoff [this message]
[not found] <<5635c0230e722ea92c95aec5a5887400@plan9.bell-labs.com>
2009-12-09 0:37 ` erik quanstrom
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=425c285155e5e2e5adcd28085c93ec13@plan9.bell-labs.com \
--to=geoff@plan9.bell-labs.com \
--cc=9fans@9fans.net \
--cc=me@acm.jhu.edu \
/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).