This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

RE: Embedded C code - functions that might sleep

From: "Turgis, Frederic" <f-turgis at ti dot com>
To: "Frank Ch. Eigler" <fche at redhat dot com>
Cc: Mark Wielaard <mjw at redhat dot com>, "systemtap at sourceware dot org" <systemtap at sourceware dot org>
Date: Thu, 2 Feb 2012 15:36:42 +0000
Subject: RE: Embedded C code - functions that might sleep
References: <28BE1A38672C8B4481BB423D0FD1F22E18F02E9A@DNCE03.ent.ti.com> <1328103248.2687.55.camel@springer.wildebeest.org> <28BE1A38672C8B4481BB423D0FD1F22E18F02F8D@DNCE03.ent.ti.com> <y0mboph46rr.fsf@fche.csb>

> Not exactly.  Generally, the conditions are imposed upon us through the kernel callback mechanisms used > by the respective probes.  "probe begin" has no material constraints (or should not; PR13641 indicates

I didn't mean to say bad things about systemtap "design choices" ;-) "relevant" was added to say there are good reasons to do that, i.e. respect constraints from the rest of the world. But well, I agree this is not really a choice, so let's talk about design constraints !

Texas Instruments France SA, 821 Avenue Jack Kilby, 06270 Villeneuve Loubet. 036 420 040 R.C.S Antibes. Capital de EUR 753.920

References:
- Embedded C code - functions that might sleep
  - From: Turgis, Frederic
- Re: Embedded C code - functions that might sleep
  - From: Mark Wielaard
- RE: Embedded C code - functions that might sleep
  - From: Turgis, Frederic
- Re: Embedded C code - functions that might sleep
  - From: Frank Ch. Eigler

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]