This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos 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: Thread identification

From: Andrew Lunn <andrew dot lunn at ascom dot ch>
To: Nick Garnett <nickg at ecoscentric dot com>
Cc: ecos-discuss at sources dot redhat dot com
Date: Tue, 27 May 2003 14:04:49 +0200
Subject: Re: [ECOS] Thread identification
References: <00a301c32432$e0038e40$9881ab93@imag.fr> <m3llwsk8tn.fsf@miso.calivar.com>

On Tue, May 27, 2003 at 11:00:52AM +0100, Nick Garnett wrote:
> "Michele Portolan" <michele.Portolan@imag.fr> writes:
> 
> > Is it possible from an ISR to understand which thread was running when the
> > interruption occurred?
> > 
> 
> You can probably call cyg_thread_self(). But why would you want to do
> this? 

Profiling. Find out which threads are running the most.

       Andrew

-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

References:
- Thread identification
  - From: Michele Portolan
- Re: Thread identification
  - From: Nick Garnett

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