From: Jeff Dike <jdike@addtoit.com>
To: BlaisorBlade <blaisorblade_spam@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Re: [patch 2/2] add-SIGPROF-get-set_signals
Date: Tue, 14 Sep 2004 15:26:48 -0400 [thread overview]
Message-ID: <200409141926.i8EJQm4W003530@ccure.user-mode-linux.org> (raw)
In-Reply-To: Your message of "Mon, 13 Sep 2004 20:12:29 +0200." <200409132012.29994.blaisorblade_spam@yahoo.it>
Actually, I had second thoughts about this patch. I left SIGPROF out of
[un]block_signals on purpose. The reason is that you want to be able to
profile all of UML, not just the pieces where signals are enabled. This is
safe because the profiling code doesn't share any data with the kernel.
A comment to this effect may be warranted, but the signal itself should be
left alone.
Jeff
-------------------------------------------------------
This SF.Net email is sponsored by: thawte's Crypto Challenge Vl
Crack the code and win a Sony DCRHC40 MiniDV Digital Handycam
Camcorder. More prizes in the weekly Lunch Hour Challenge.
Sign up NOW http://ad.doubleclick.net/clk;10740251;10262165;m
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2004-09-14 18:22 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
2004-09-13 22:15 ` Jeff Dike
2004-09-14 19:26 ` Jeff Dike [this message]
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=200409141926.i8EJQm4W003530@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=blaisorblade_spam@yahoo.it \
--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