From: Li Shaohua <shaohua.li@intel.com>
To: Hiroshi 2 Itoh <HIROIT@jp.ibm.com>
Cc: ACPI-DEV <acpi-devel@lists.sourceforge.net>,
greg@kroah.com, Len Brown <len.brown@intel.com>,
lkml <linux-kernel@vger.kernel.org>, Pavel Machek <pavel@suse.cz>
Subject: Re: [ACPI] [Proposal]Another way to save/restore PCI config space for suspend/resume
Date: Wed, 27 Oct 2004 09:55:30 +0800 [thread overview]
Message-ID: <1098842129.12477.2.camel@sli10-desk.sh.intel.com> (raw)
In-Reply-To: <OF7E38C2D0.FC23B846-ON49256F3A.000672D1-49256F3A.0007BB88@jp.ibm.com>
On Wed, 2004-10-27 at 09:32, Hiroshi 2 Itoh wrote:
>
>
> Hi,
>
> acpi-devel-admin@lists.sourceforge.net wrote on 2004/10/26 13:50:57:
>
> > Hi,
> > We suffer from PCI config space issue for a long time, which causes many
> > system can't correctly resume. Current Linux mechanism isn't sufficient.
> > Here is a another idea:
> > Record all PCI writes in Linux kernel, and redo all the write after
> > resume in order. The idea assumes Firmware will restore all PCI config
> > space to the boot time state, which is true at least for IA32.
> >
>
> I think a basic problem of current Linux device model is that there is no
> effective message path from sibling devices to their root device.
> Although the message direction from a root device to sibling devices is
> natural from the viewpoint of device enumeration, the direction from
> sibling devices to a root device is required for effective arbitration for
> device configuration and power management.
>
> The Windows driver model uses the direction from sibling drivers to a root
> bus driver mainly, i.e. sibling drivers are layered on a root bus driver.
> While we need a kind of callback mechanism from PCI (sibling) devices to
> PCI bus (root) device instead because their normal call interface is from a
> root device to sibling devices.
Hiro-san,
I don't really understand why this is related with suspend/resume. Could
you please explain it more clearly?
Thanks,
Shaohua
next prev parent reply other threads:[~2004-10-27 2:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-26 4:50 Li Shaohua
2004-10-26 5:11 ` [ACPI] " Andi Kleen
2004-10-26 6:11 ` Len Brown
2004-10-26 8:42 ` Arjan van de Ven
2004-10-26 9:06 ` Karol Kozimor
2004-10-26 9:57 ` Matthew Garrett
2004-10-26 9:09 ` Li Shaohua
2004-10-26 9:21 ` Pavel Machek
2004-10-27 0:50 ` [ACPI] " Li Shaohua
2004-10-27 1:32 ` [ACPI] " Hiroshi 2 Itoh
2004-10-27 1:55 ` Li Shaohua [this message]
2004-10-27 2:26 ` Hiroshi 2 Itoh
2004-10-27 20:14 ` Rajesh Shah
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=1098842129.12477.2.camel@sli10-desk.sh.intel.com \
--to=shaohua.li@intel.com \
--cc=HIROIT@jp.ibm.com \
--cc=acpi-devel@lists.sourceforge.net \
--cc=greg@kroah.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
/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®