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 11:09:00 -0800 (PST)	[thread overview]
Message-ID: <15006.40524.929644.25622@pizda.ninka.net> (raw)
In-Reply-To: <19350124090521.18330@mailhost.mipsys.com>
In-Reply-To: <19350124090521.18330@mailhost.mipsys.com>


Benjamin Herrenschmidt writes:
 > I'm, of course open to any comments about this (in fact, I'd really like
 > some feedback). One thing is that we also need to find a way to pass
 > those infos to userland. Currently, we implement an arch-specific syscall
 > that allow to retreive the IO physical base of a given PCI bus. That may
 > be enough, but we may also want something that match more closely what we
 > do in the kernel.

Same problem on sparc64.  Using a special PCI syscall is fine, _if_ we
all end up using the same one.  However, I would prefer another
mechanism...

I think a cleaner scheme is to allow mmap() on
/proc/bus/pci/${BUS}/${DEVICE} nodes, that is much cleaner and solves
transparently any "different word size between userland and kernel"
issues (specifically 32-bit userlands executing on 64-bit kernels).

I played around with something akin to this, and some of the necessary
Xfree86-4.0.x hackery needed, some time ago.  But I never finished
this.

Later,
David S. Miller
davem@redhat.com


  parent reply	other threads:[~2001-03-01 19:14 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 [this message]
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
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.40524.929644.25622@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®