From: Pavel Machek <pavel-AlSwsSmVLrQ@public.gmane.org>
To: Li Shaohua <shaohua.li-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: ACPI-DEV
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
Nigel Cunningham
<ncunningham-jjFNsPSvq+iXDw4h08c5KA@public.gmane.org>
Subject: Re: RFC 0/4: make ACPI interpret safe for suspend/resume
Date: Thu, 20 Jan 2005 10:40:42 +0100 [thread overview]
Message-ID: <20050120094042.GC1452@elf.ucw.cz> (raw)
In-Reply-To: <1106213207.16186.10.camel-U5EdaLXB8smDugQYiPIPGdh3ngVCH38I@public.gmane.org>
Hi!
> > > > Freezing all processes should not be required.
> > > How about just make suspend/resume task as a highest priority task with
> > > FIFO scheduler policy?
> >
> > That might do the trick for S3,
> What I like it is a) it speeds up freeze process in a system with many
> tasks, b) easy to move to SMP case on the future.
>
> > but not for swsusp. Imagine normal
> > process holding some lock you want (for writing image to disk). You
> > can run on FIFO scheduler, but then you block on this lock, and
> > userspace process gets to run, and gets confused.
> Ok, that makes sense. Could we split S3 from swsusp? That is S3 doesn't
> use freeze_process.
Yes, that's certainly an option. I liked the idea of code being
shared, and had refrigerator code handy...
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: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
prev parent reply other threads:[~2005-01-20 9:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-19 3:17 RFC 0/4: make ACPI interpret safe for suspend/resume Li Shaohua
[not found] ` <1106104620.12957.270.camel-U5EdaLXB8smDugQYiPIPGdh3ngVCH38I@public.gmane.org>
2005-01-19 7:21 ` Nigel Cunningham
2005-01-19 7:55 ` Li Shaohua
2005-01-19 10:18 ` Pavel Machek
[not found] ` <20050119101858.GE25623-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2005-01-20 1:28 ` Li Shaohua
[not found] ` <1106184495.13181.68.camel-U5EdaLXB8smDugQYiPIPGdh3ngVCH38I@public.gmane.org>
2005-01-20 9:12 ` Pavel Machek
[not found] ` <20050120091242.GB1452-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2005-01-20 9:26 ` Li Shaohua
[not found] ` <1106213207.16186.10.camel-U5EdaLXB8smDugQYiPIPGdh3ngVCH38I@public.gmane.org>
2005-01-20 9:40 ` Pavel Machek [this message]
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=20050120094042.GC1452@elf.ucw.cz \
--to=pavel-alswssmvlrq@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=ncunningham-jjFNsPSvq+iXDw4h08c5KA@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