Subject: Re: PCI domain stuff
From: "David S. Miller" <davem@redhat.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org
In-Reply-To: <bdr7a6$4eu$1@cesium.transmeta.com>
References: <1057010214.1277.11.camel@albertc>
	 <20030630231515.GA27813@kroah.com>
	 <20030701040531.GB23597@parcelfarce.linux.theplanet.co.uk>
	 <1057034041.31826.1.camel@rth.ninka.net>
	 <bdr7a6$4eu$1@cesium.transmeta.com>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Message-Id: <1057039376.32118.3.camel@rth.ninka.net>
Mime-Version: 1.0
Date: 30 Jun 2003 23:02:56 -0700
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1106
Lines: 27

[ Pater, please retain the CC: list in your replies.  I scan
linux-kernel casually at best, and I probably would have missed
this reply of yours under normal circumstances, if you had retained
the CC: list I would have read it via my non-lkml account and therefore
not have missed it. ]

On Mon, 2003-06-30 at 22:47, H. Peter Anvin wrote:
> Presumably only on architectures which use memory-mapped IO address
> space.

On ones that don't we use the x86's existing facilities for doing
this, ioperm() and direct I/O instructions.

These issues are platform dependant for other reasons anyways
(endianness, barrier instructions needed, etc.)

But everything the most demanding testcase in userspace needs (this
being xfree86) needs can be done with the existing facilities.

Unlike other people, I do not see the value in having 50 ways to
do the same thing. :-)

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/