public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Nigel Cunningham <ncunningham@users.sourceforge.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Is this too ugly to merge?
Date: Tue, 13 Jan 2004 11:45:52 +0100	[thread overview]
Message-ID: <20040113104552.GA269@elf.ucw.cz> (raw)
In-Reply-To: <1073609923.2003.10.camel@laptop-linux>

Hi!

> My question, then (at last!) is, are these 'too ugly', so that they'd
> never get merged? If you do consider them ugly, is it because you'd like
> to see better names (lower case? replace SWSUSP?) and/or because you
> think the whole idea is ugly and have a better solution?

Well, problem is not as much with uglyness of those macros, but with
need to patch many files to include those macros. If you can get
number of uses of those macros down to, say, 10, it will get
better. Can't you just do something at each syscall/pagefault
entry/exit?

Ordinarily, process get stopped by sending them SIGSTOP. That suggests
to me that we might be able to reuse existing mechanism... SIGSTOP-ed
task should not hold any locks since it can be SIGSTOPed for very long
time. And if SIGSTOP does not work properly ... well that would be
simple bugfix.

								Pavel

-- 
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]

  parent reply	other threads:[~2004-01-13 10:44 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 [this message]
2004-01-13 11:49 ` Pavel Machek
2004-01-19  0:44   ` Nigel Cunningham
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=20040113104552.GA269@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ncunningham@users.sourceforge.net \
    /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