From: Li Shaohua <shaohua.li@intel.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: ACPI-DEV <acpi-devel@lists.sourceforge.net>,
lkml <linux-kernel@vger.kernel.org>,
Len Brown <len.brown@intel.com>,
greg@kroah.com
Subject: Re: [ACPI] Re: [Proposal]Another way to save/restore PCI config space for suspend/resume
Date: Wed, 27 Oct 2004 08:50:46 +0800 [thread overview]
Message-ID: <1098838245.12245.4.camel@sli10-desk.sh.intel.com> (raw)
In-Reply-To: <20041026092106.GC28897@elf.ucw.cz>
On Tue, 2004-10-26 at 17:21, Pavel Machek wrote:
> 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.
>
> That looks extremely ugly to me. If you want to do something special
> in resume function, just do it there. It will probably share a lot of
> code with your init function, anyway.
How can you handle devices without driver? And how to save/restore
config space for special devices, such as LPC bridge and host bridge?
-Shaohua
next prev parent reply other threads:[~2004-10-27 0:58 UTC|newest]
Thread overview: 15+ 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 ` Li Shaohua [this message]
2004-10-27 1:32 ` [ACPI] " Hiroshi 2 Itoh
2004-10-27 1:55 ` Li Shaohua
2004-10-27 2:26 ` Hiroshi 2 Itoh
2004-10-27 20:14 ` Rajesh Shah
[not found] <fa.fvou17m.1f5oa9u@ifi.uio.no>
[not found] ` <fa.ivj042g.g5qnoo@ifi.uio.no>
2004-10-27 6:30 ` [ACPI] " Len Brown
2004-10-27 9:57 ` Benjamin Herrenschmidt
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=1098838245.12245.4.camel@sli10-desk.sh.intel.com \
--to=shaohua.li@intel.com \
--cc=acpi-devel@lists.sourceforge.net \
--cc=greg@kroah.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.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®