linux-um archives
 help / color / mirror / Atom feed
From: BlaisorBlade <blaisorblade_spam@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Jeff Dike <jdike@addtoit.com>
Subject: Re: [uml-devel] Re: [patch 2/2] add-SIGPROF-get-set_signals
Date: Mon, 13 Sep 2004 20:12:29 +0200	[thread overview]
Message-ID: <200409132012.29994.blaisorblade_spam@yahoo.it> (raw)
In-Reply-To: <20040913033239.GA13207@ccure.user-mode-linux.org>

On Monday 13 September 2004 05:32, Jeff Dike wrote:
> On Sun, Sep 12, 2004 at 08:26:29PM +0200, blaisorblade_spam@yahoo.it wrote:
> >  {
> >  	sigset_t mask;
> > +	sigset_t old_mask;
> >  	int ret;

> Weren't you just complaining about stack consumption?  Do you know how
> big a sigset_t is?

> 	(gdb) p sizeof(sigset_t)
> 	$1 = 128
Yes, I realize (glibc seems seriously original about this - who ever can use 
1024 different signals? The kernel just uses 64 signals - 8 bit).

> I went to a reasonable amount of trouble to get that function to only
> use one sigset_t and now you are proposing to add the old one back.
> Fix the patch and I'll put it in.
I rechecked the patch and understood why I put that in - I understand your 
point, but since that needs at least some, but using such unobvious tricks 
requires at least some comment - I'm adding the comment to the patch (and 
sending it inline separately).

Obviously feel free to delete/change the comment.

> Also, if you're going to fix something, send a patch which does
> nothing but make the fix, and save whatever cleanups you want to make
> for a differet patch.
Ok, I agree at all, and most times I already work like that.
Bye
-- 
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729


-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM. 
Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

  reply	other threads:[~2004-09-13 19:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-12 18:26 [uml-devel] [patch 2/2] add-SIGPROF-get-set_signals blaisorblade_spam
2004-09-13  3:32 ` [uml-devel] " Jeff Dike
2004-09-13 18:12   ` BlaisorBlade [this message]
2004-09-13 22:15     ` Jeff Dike
2004-09-14 19:26     ` Jeff Dike
2004-09-17 18:52       ` BlaisorBlade
2004-09-18  0:45         ` Jeff Dike

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=200409132012.29994.blaisorblade_spam@yahoo.it \
    --to=blaisorblade_spam@yahoo.it \
    --cc=jdike@addtoit.com \
    --cc=user-mode-linux-devel@lists.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