From: Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>
To: Li Shaohua <shaohua.li-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: ACPI-DEV
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
lkml <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
greg-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org
Subject: Re: [Proposal]Another way to save/restore PCI config space for suspend/resume
Date: Tue, 26 Oct 2004 11:21:06 +0200 [thread overview]
Message-ID: <20041026092106.GC28897@elf.ucw.cz> (raw)
In-Reply-To: <1098766257.8433.7.camel-U5EdaLXB8smDugQYiPIPGdh3ngVCH38I@public.gmane.org>
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.
Pavel
--
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
next prev parent reply other threads:[~2004-10-26 9:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-26 4:50 [Proposal]Another way to save/restore PCI config space for suspend/resume Li Shaohua
[not found] ` <1098766257.8433.7.camel-U5EdaLXB8smDugQYiPIPGdh3ngVCH38I@public.gmane.org>
2004-10-26 5:11 ` Andi Kleen
2004-10-26 6:11 ` [ACPI] " Len Brown
2004-10-26 8:42 ` Arjan van de Ven
[not found] ` <1098780150.2789.19.camel-PDvaWZGbcxh0dKo7RnIATNi2O/JbrIOy@public.gmane.org>
2004-10-26 9:06 ` Karol Kozimor
2004-10-26 9:57 ` Matthew Garrett
[not found] ` <20041026051100.GA5844-B4tOwbsTzaBolqkO4TVVkw@public.gmane.org>
2004-10-26 9:09 ` Li Shaohua
2004-10-26 9:21 ` Pavel Machek [this message]
[not found] ` <20041026092106.GC28897-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2004-10-27 0:50 ` Li Shaohua
2004-10-27 1:32 ` Hiroshi 2 Itoh
[not found] ` <OF7E38C2D0.FC23B846-ON49256F3A.000672D1-49256F3A.0007BB88-JE5g2YyFxFHQT0dZR+AlfA@public.gmane.org>
2004-10-27 1:55 ` Li Shaohua
2004-10-27 2:26 ` [ACPI] " 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=20041026092106.GC28897@elf.ucw.cz \
--to=pavel-+zi9xunit7i@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=greg-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org \
--cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=shaohua.li-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
/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