From: Nigel Cunningham <ncunningham@users.sourceforge.net>
To: Pavel Machek <pavel@ucw.cz>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Is this too ugly to merge?
Date: Mon, 19 Jan 2004 13:44:54 +1300 [thread overview]
Message-ID: <1074473094.2361.104.camel@laptop-linux> (raw)
In-Reply-To: <20040113114913.GB269@elf.ucw.cz>
[-- Attachment #1: Type: text/plain, Size: 914 bytes --]
Hi.
I'll take the following approach: I'm pretty sure that I've tried
suspending userspace before kernel threads before, and still ran into
possible deadlocks. Nevertheless, I'll set that up and then bang really
hard on it using Michael's test scripts, and let you know the results.
If and when we see that this approach won't cut the mustard, we can come
back to considering this approach. Sound okay?
By the way, the macros are not an alternative to the SIGSTOP-like
method. They're used with it, to ensure it works without deadlocking.
Regards,
Nigel
On Wed, 2004-01-14 at 00:49, Pavel Machek wrote:
> Okay, I can now remember (and agree to) that we need to suspend
> userspace first, and only then suspend kernelspace. Bug I don't see
> why we can't suspend userspace using old, SIGSTOP-like, method.
--
My work on Software Suspend is graciously brought to you by
LinuxFund.org.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-01-19 0:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-09 0:58 Is this too ugly to merge? Nigel Cunningham
2004-01-09 4:44 ` Stephen Hemminger
2004-01-09 4:50 ` Nigel Cunningham
2004-01-09 5:35 ` Nigel Cunningham
2004-01-13 10:45 ` Pavel Machek
2004-01-13 11:49 ` Pavel Machek
2004-01-19 0:44 ` Nigel Cunningham [this message]
2004-01-19 9:51 ` Pavel Machek
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=1074473094.2361.104.camel@laptop-linux \
--to=ncunningham@users.sourceforge.net \
--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