From: "Nakajima, Jun" <jun.nakajima@intel.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: linux-kernel@vger.kernel.org
Subject: RE: local APIC may cause XFree86 hang
Date: Wed, 13 Nov 2002 17:16:21 -0800 [thread overview]
Message-ID: <F2DBA543B89AD51184B600508B68D4000F866078@fmsmsx103.fm.intel.com> (raw)
The one instance I saw was that the BIOS was reading 8254 in a tight loop
for a calibration purpose, and it was assuming the time proceeded in a
constant speed, to exit the loop. In other words, it never assumed it could
get interrupts. To vm86, interrupts are invisible, but they have impacts on
the actual speed.
Jun
> -----Original Message-----
> From: Linus Torvalds [mailto:torvalds@transmeta.com]
> Sent: Wednesday, November 13, 2002 4:48 PM
> To: Nakajima, Jun
> Cc: linux-kernel@vger.kernel.org
> Subject: RE: local APIC may cause XFree86 hang
>
>
> On Wed, 13 Nov 2002, Nakajima, Jun wrote:
> >
> > Are we disabling vm86 code to access to PIT or PIC? I saw some video ROM
> > code (either BIOS call or far call) did access PIT, confusing the OS.
>
> Well, the kernel itself doesn't actually disable/enable anything, it
> leaves that decision to the caller.
>
> XFree86 obviously does have IO rights, and I suspect it may allow the
> video BIOS to do just about anything, simply because it doesn't have much
> choise (the video bios clearly needs a lot of IO privileges too). So yes,
> that could easily confuse the OS if it happens, but it should be
> independent of IO-APIC vs not.
>
> Linus
next reply other threads:[~2002-11-14 1:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-14 1:16 Nakajima, Jun [this message]
2002-11-14 1:38 ` Linus Torvalds
2002-11-14 8:08 ` george anzinger
2002-11-14 14:27 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2002-11-14 0:29 Nakajima, Jun
2002-11-14 0:48 ` Linus Torvalds
2002-11-13 22:29 Mikael Pettersson
2002-11-13 23:19 ` Alan Cox
2002-11-13 23:01 ` Mikael Pettersson
2002-11-13 23:52 ` Linus Torvalds
2002-11-14 7:58 ` Gregoire Favre
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=F2DBA543B89AD51184B600508B68D4000F866078@fmsmsx103.fm.intel.com \
--to=jun.nakajima@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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
all inboxes | Powered by JetHome®