mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: <linux-kernel@vger.kernel.org>, <linuxppc-dev@lists.linuxppc.org>
Subject: Re: The IO problem on multiple PCI busses
Date: Thu, 1 Mar 2001 12:27:21 -0800 (PST)	[thread overview]
Message-ID: <15006.45225.631466.969004@pizda.ninka.net> (raw)
In-Reply-To: <19350124134100.15285@smtp.wanadoo.fr>
In-Reply-To: <15006.42475.79484.578530@pizda.ninka.net> <19350124134100.15285@smtp.wanadoo.fr>


Benjamin Herrenschmidt writes:
 > Also, an ioctl to retreive the iobase would be useful too

No, the whole point of my suggested mmap() interface is to
_ENTIRELY_ eliminate any reason for the user to even see
what the physical addressing of the machine looks like.

If you start pushing iobases to the user, you break this.

I do not want an interface where the user still has to do
grotty stuff like mmap() on /dev/{mem,kmem}, this was the
core of the problem I had with the syscall idea, don't bring
it back.

Make mmap()'s on a PCI-->ISA bridge do something special, for
example.

The user doesn't need to know anything about physical addressing of
the machine, it all can and should be abstracted away.  This is why I
really detest the XFree86 PCI bus probing layer, it should not need to
poke around at so much of the config space information of devices :-(

It is the reason why, at least still today in Xfree86 CVS, it simply
cannot cope with multiple PCI controllers in a machine because it
assumes a flat MEM/IO space.  They know about the problem and are
working on fixes, but my point is that making this overly knowledgable
PCI prober in the first place is what created these problems.

Later,
David S. Miller
davem@redhat.com

  parent reply	other threads:[~2001-03-01 20:30 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-01 15:33 Benjamin Herrenschmidt
2001-03-01 15:41 ` Benjamin Herrenschmidt
2001-03-01 18:30 ` Alan Cox
2001-03-01 19:09 ` David S. Miller
2001-03-01 19:33   ` Dan Malek
2001-03-01 19:41   ` David S. Miller
2001-03-01 19:59     ` Dan Malek
2001-03-01 20:09     ` Benjamin Herrenschmidt
2001-03-01 20:22     ` David S. Miller
2001-03-01 20:27     ` David S. Miller [this message]
2001-03-02 11:25       ` Benjamin Herrenschmidt
2001-03-03  1:08       ` David S. Miller
2001-03-01 19:49   ` Benjamin Herrenschmidt
2001-03-01 20:21   ` David S. Miller
2001-03-01 22:26     ` Alan Cox
2001-03-02 11:20     ` Benjamin Herrenschmidt
2001-03-03  1:06     ` David S. Miller
2001-03-03  2:25       ` Benjamin Herrenschmidt
2001-03-03 11:01         ` Jeff Garzik
2001-03-03 17:28           ` Benjamin Herrenschmidt
2001-03-05 16:20         ` David Woodhouse
2001-03-06 23:01       ` Oliver Xymoron
2001-03-07  2:07       ` Tony Mantler
2001-03-05 23:21   ` Chris Wedgwood
2001-03-02  1:22 Grant Grundler
2001-03-02  2:19 ` David S. Miller
2001-03-02 17:46   ` Grant Grundler

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=15006.45225.631466.969004@pizda.ninka.net \
    --to=davem@redhat.com \
    --cc=benh@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.linuxppc.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®