From: Linus Torvalds <torvalds@osdl.org>
To: Matthew Wilcox <matthew@wil.cx>
Cc: Greg KH <greg@kroah.com>,
linux-kernel@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz
Subject: Re: Delete drivers/pci/syscall.c?
Date: Tue, 19 Oct 2004 08:04:07 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.58.0410190801250.2317@ppc970.osdl.org> (raw)
In-Reply-To: <20041019124850.GM16153@parcelfarce.linux.theplanet.co.uk>
On Tue, 19 Oct 2004, Matthew Wilcox wrote:
>
> Linus, I noticed you touching drivers/pci/syscall.c which made me look
> a bit more carefully at that file. It is broken for machines with
> overlapping PCI bus numbers in separate domains. There's basically no
> way to fix this unless we encode the domain into the upper bits of the
> bus number.
>
> The information is already available through /proc and /sys. It's hooked
> into the syscall tables of alpha, arm, ia64, ppc, ppc64, sparc and
> sparc64. Whatever's using those syscalls must have some kind of backup
> strategy for grovelling around in files.
While the system calls may be broken in theory (multiple domains) they are
not broken in practice (single-domain workstations), and they _were_ used
by X, at least on alpha last time I looked.
And no, expectign X to have a fallback and to understand multiple domains
is likely not a valid expectation.
So right now X may work only on single-domain setups, or on setups where
the video card has a unique address when ignoring the domnain number.
That's pretty much all of the affected machines, so no, I don't think we
can/should remove it.
Will X eventually learn about multiple domains? Maybe.
Linus
next prev parent reply other threads:[~2004-10-19 15:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-19 12:48 Matthew Wilcox
2004-10-19 15:04 ` Linus Torvalds [this message]
2004-10-19 15:21 ` Arjan van de Ven
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=Pine.LNX.4.58.0410190801250.2317@ppc970.osdl.org \
--to=torvalds@osdl.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=matthew@wil.cx \
/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®