content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 8BIT
Subject: RE: [RFC PATCH] New SA_NOPRNOTIF sigaction flag
Date: Wed, 28 Sep 2005 12:06:21 -0600
Message-ID: <21FFE0795C0F654FAD783094A9AE1DFC086F02D1@cof110avexu4.global.avaya.com>
Thread-Topic: [RFC PATCH] New SA_NOPRNOTIF sigaction flag
Thread-Index: AcXENmLaJQWJgFi9RZGK1SCQam7eWwAIIxbQ
From: "Davda, Bhavesh P \(Bhavesh\)" <bhavesh@avaya.com>
To: "Daniel Jacobowitz" <dan@debian.org>
Cc: <linux-kernel@vger.kernel.org>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1021
Lines: 26

> 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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/