From: "David S. Miller" <davem@redhat.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PCI domain stuff
Date: 30 Jun 2003 23:02:56 -0700 [thread overview]
Message-ID: <1057039376.32118.3.camel@rth.ninka.net> (raw)
In-Reply-To: <bdr7a6$4eu$1@cesium.transmeta.com>
[ 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. :-)
next prev parent reply other threads:[~2003-07-01 5:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1057010214.1277.11.camel@albertc>
[not found] ` <20030630220758.GA27368@kroah.com>
[not found] ` <1057014182.4048.3887.camel@cube>
[not found] ` <20030630231515.GA27813@kroah.com>
2003-07-01 4:05 ` Matthew Wilcox
2003-07-01 4:25 ` H. Peter Anvin
2003-07-01 4:34 ` David S. Miller
2003-07-01 5:47 ` H. Peter Anvin
2003-07-01 6:02 ` David S. Miller [this message]
2003-07-01 6:06 ` H. Peter Anvin
2003-07-01 6:03 ` David S. Miller
2003-07-01 6:13 ` H. Peter Anvin
2003-07-01 16:30 ` Andy Isaacson
2003-07-01 16:34 ` H. Peter Anvin
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=1057039376.32118.3.camel@rth.ninka.net \
--to=davem@redhat.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
/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®