Delete drivers/pci/syscall.c?

From: Matthew Wilcox
Date: Tue Oct 19 2004 - 07:50:15 EST



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.

What would break if we just made those syscalls return -ENOSYS?

--
"Next the statesmen will invent cheap lies, putting the blame upon
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince
himself that the war is just, and will thank God for the better sleep
he enjoys after this process of grotesque self-deception." -- Mark Twain
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/