From: erik quanstrom <quanstro@coraid.com>
To: 9fans@9fans.net
Subject: Re: [9fans] Keyboard and Mouse
Date: Fri, 10 Jul 2009 09:54:40 -0400 [thread overview]
Message-ID: <233fc0081d92808d03186c4093fadfb6@coraid.com> (raw)
In-Reply-To: <8d11fee952ab7fc2b57d410bd848c1d3@quanstro.net>
> > This problem is well known, and seems to be
> > caused by HyperThreading on some CPU.
> >
> > Try to add the following line to "plan9.ini":
> > *nomp=1
> >
> > It will solve this problem.
>
> hyperthreading? that doesn't sound right.
>
> do you mean a bad mp interrupt table?
you can avoid ht by setting *ncpu=1 in your
plan9.ini without disabling mp interrupts.
so it should be easy to say definitivly which
one causes the problem.
as a further explainer, 8259 interrupts can't
work in an mp environment. you need to
use either mp interrupts or msi interrupts.
since plan 9 doesn't implement msi, *nomp=1
implies that only one cpu may be activated.
so a uniprocessor may still use mp interrupts.
- erik
next prev parent reply other threads:[~2009-07-10 13:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-10 10:42 Eldar Tsraev
2009-07-10 13:38 ` David du Colombier
2009-07-10 13:41 ` erik quanstrom
2009-07-10 13:54 ` erik quanstrom [this message]
2009-07-10 17:30 ` Eldar Tsraev
2009-07-10 13:55 ` David du Colombier
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=233fc0081d92808d03186c4093fadfb6@coraid.com \
--to=quanstro@coraid.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).