From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Adam Belay <abelay@MIT.EDU>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Greg KH <greg@kroah.com>,
linux-pci@atrey.karlin.mff.cuni.cz,
Linux-pm mailing list <linux-pm@lists.osdl.org>,
Kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: [linux-pm] Bug in PCI core
Date: Fri, 13 Oct 2006 16:26:26 +0100 [thread overview]
Message-ID: <1160753187.25218.52.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0610131024340.6460-100000@iolanthe.rowland.org>
Ar Gwe, 2006-10-13 am 10:29 -0400, ysgrifennodd Alan Stern:
> > I'd like to propose that we have the pci config sysfs interface return
> > -EIO when it's blocked (e.g. active BIST or D3cold). This accurately
> > reflects the state of the device to userspace, reduces complexity, and
> > could potentially save some memory per PCI device instance.
>
> Could you resubmit your old patches and include a corresponding fix for
> this access problem?
And then you can fix the applications it breaks, like the X server which
does actually want to know where all the devices are located in PCI
space.
Alan
next prev parent reply other threads:[~2006-10-13 15:26 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-11 20:41 Bug in PCI core Alan Stern
2006-10-13 1:01 ` [linux-pm] " Benjamin Herrenschmidt
2006-10-13 8:50 ` Adam Belay
2006-10-13 9:16 ` Benjamin Herrenschmidt
2006-10-13 9:31 ` Martin Mares
2006-10-13 12:25 ` [linux-pm] " Benjamin Herrenschmidt
2006-10-13 14:29 ` Alan Stern
2006-10-13 15:26 ` Alan Cox [this message]
2006-10-13 15:29 ` [linux-pm] " Arjan van de Ven
2006-10-13 16:06 ` Alan Cox
2006-10-13 16:34 ` Adam Belay
2006-10-13 16:36 ` [linux-pm] " Matthew Wilcox
2006-10-13 17:09 ` Alan Cox
2006-10-13 16:49 ` Matthew Wilcox
2006-10-13 17:34 ` Alan Cox
2006-10-13 17:13 ` Arjan van de Ven
2006-10-13 17:57 ` Alan Stern
2006-10-13 19:18 ` [linux-pm] " Matthew Wilcox
2006-10-13 20:59 ` Alan Stern
2006-10-13 19:30 ` Adam Belay
2006-10-13 23:00 ` Benjamin Herrenschmidt
2006-10-14 2:33 ` Alan Stern
2006-10-14 3:04 ` [linux-pm] " Roland Dreier
2006-10-14 3:07 ` Matthew Wilcox
2006-10-14 3:19 ` Bill Randle
2006-10-14 5:47 ` Greg KH
2006-10-13 17:01 ` Adam Belay
2006-10-13 16:40 ` Adam Belay
2006-10-13 20:48 ` [linux-pm] " Pavel Machek
2006-10-14 5:34 ` Greg KH
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=1160753187.25218.52.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=abelay@MIT.EDU \
--cc=benh@kernel.crashing.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=linux-pm@lists.osdl.org \
--cc=stern@rowland.harvard.edu \
/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