From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Andi Kleen <ak@muc.de>
Cc: Ingo Molnar <mingo@elte.hu>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
eich@suse.de
Subject: Re: [patch] context-switching overhead in X, ioport(), 2.6.8.1
Date: Sun, 22 Aug 2004 13:00:54 +0100 [thread overview]
Message-ID: <1093176046.24272.68.camel@localhost.localdomain> (raw)
In-Reply-To: <m3n00nwepr.fsf@averell.firstfloor.org>
On Sul, 2004-08-22 at 13:16, Andi Kleen wrote:
> At least older XFree86 (4.2/3 time frame) used to only use iopl(). I
> know it because at some point ioperm() was completely broken on
> x86-64, but the X server never hit it. I wonder why they changed
> that. Anyways, perhaps it would be better to just change the X server
> back to use iopl(), because it will be always faster than using
Xorg and XFree assume the kernel will have intelligent limits. When the
range went up the EnableIO code in turn switched to ioperm.
The actual code is:
if (ioperm(0, 1024, 1) || iopl(3))
FatalError("xf86EnableIOPorts: Failed to set IOPL for
I/O\n")
(os-support/linux/lnx_video.c:xf86EnableIO)
Flip those around and rebuild.
next prev parent reply other threads:[~2004-08-22 13:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2vEzI-Vw-17@gated-at.bofh.it>
2004-08-22 12:16 ` [patch] context-switching overhead in X, ioport(), 2.6.8.1 Andi Kleen
2004-08-22 12:00 ` Alan Cox [this message]
2004-08-22 14:23 ` Andi Kleen
2004-08-22 14:47 ` Alan Cox
2004-08-22 17:31 ` Ingo Molnar
2004-08-21 13:55 Ingo Molnar
2004-08-22 4:46 ` David S. Miller
2004-08-22 5:42 ` Ryan Cumming
2004-08-22 6:00 ` Lee Revell
2004-08-22 6:06 ` Ryan Cumming
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=1093176046.24272.68.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=ak@muc.de \
--cc=eich@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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