From: "Davda, Bhavesh P \(Bhavesh\)" <bhavesh@avaya.com>
To: "Daniel Jacobowitz" <dan@debian.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: [RFC PATCH] New SA_NOPRNOTIF sigaction flag
Date: Wed, 28 Sep 2005 12:06:21 -0600 [thread overview]
Message-ID: <21FFE0795C0F654FAD783094A9AE1DFC086F02D1@cof110avexu4.global.avaya.com> (raw)
> Yes, I entirely understand what you're saying. I feel like you're not
> reading my responses. GDB _already has a list of signals it does not
> care about_. If ptrace permitted, it could tell the kernel not to
> context switch to deliver those signals. In advance! That's a
> debugger-driven solution to your problem.
>
> I'm not arguing out of theory here. I've implemented this mechanism
> before in other contexts, for instance to prevent the remote protocol
> overhead for ignored signals when using gdb with gdbserver.
>
Okay, I'll come up with an alternative patch that enhances the ptrace
interface so the debugger can guide the kernel to NOT context switch and
bother it about signal x from task y.
Would you be amenable to such a patch?
Thanks
- Bhavesh
next reply other threads:[~2005-09-28 18:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-28 18:06 Davda, Bhavesh P (Bhavesh) [this message]
2005-09-28 18:33 ` [RFC PATCH] New SA_NOPRNOTIF sigaction flag Daniel Jacobowitz
-- strict thread matches above, loose matches on Subject: below --
2005-10-03 15:21 Davda, Bhavesh P (Bhavesh)
2005-10-03 16:12 ` Daniel Jacobowitz
2005-09-28 19:11 Davda, Bhavesh P (Bhavesh)
2005-10-03 0:27 ` Daniel Jacobowitz
2005-09-27 21:55 Davda, Bhavesh P (Bhavesh)
2005-09-28 14:10 ` Daniel Jacobowitz
2005-09-27 16:24 Davda, Bhavesh P (Bhavesh)
2005-09-27 20:39 ` Daniel Jacobowitz
2005-09-27 14:45 Davda, Bhavesh P (Bhavesh)
2005-09-27 15:55 ` Daniel Jacobowitz
2005-09-27 23:26 ` Valdis.Kletnieks
2005-09-26 17:39 Bhavesh P. Davda
2005-09-27 13:06 ` Daniel Jacobowitz
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=21FFE0795C0F654FAD783094A9AE1DFC086F02D1@cof110avexu4.global.avaya.com \
--to=bhavesh@avaya.com \
--cc=dan@debian.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).