Ar Gwe, 2006-10-13 am 10:49 -0600, ysgrifennodd Matthew Wilcox:
> No it didn't. It's undefined behaviour to perform *any* PCI config
> access to the device while it's doing a D-state transition. It may have
I think you missed the earlier parts of the story - the kernel caches
the base config register state.
> happened to work with the chips you tried it with, but more likely you
> never hit that window because X simply didn't try to do that.
Which is why the kernel caches the register state. This all came up long
ago and the solution we currently have was the one chosen after
considerable debate and analysis about things like locking. We preserved
the historical reliable interface going back to the early Linux PCI
support and used by all the apps.
There are several problems with making it return an error
- What does user space do ?
while(pci_...() == -EAGAIN) yield();
which is useful how - there is no select operation for waiting here, and
while it could be added it just gets uglier
- Who actually wants to get an error in that specific case ?
If you can find someone who desperately wants an error code then code in
O_DIRECT support to do it and preserve the existing sane API.
The job of the kernel is not to expose hardware directly, it is to
provide sane interfaces to it. We don't have separate interfaces to
conf1, conf2, pcibios etc for good reason. Exposing everyone to ugly
minor details of the PCI transition handling isn't progress.
Alan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
