On Mon, Mar 9, 2015 at 12:26 PM, Jeff Haran <Jeff.Haran@xxxxxxxxxx> wrote: > -----Original Message----- > From: kernelnewbies-bounces@xxxxxxxxxxxxxxxxx [mailto:kernelnewbies-bounces@xxxxxxxxxxxxxxxxx] On Behalf Of Matwey V. Kornilov > Sent: Monday, March 09, 2015 8:35 AM > To: kernelnewbies@xxxxxxxxxxxxxxxxx > Subject: Re: Get local CPU id > > > Many thanks for all answers. smp_processor_id() works just fine in interrupt context. > > Unfortunately /proc/interrupts is not what I was looking for. My idea was to print a line to dmesg at every interrupt to have a timestamp like the following: > > [ 926.440799] Enter intr at 0 > [ 926.441059] Exit intr at 0 > > Every interrupt? You might want to spend some time thinking about which interrupts you don't want to do the above printing for. > > Jeff Haran > > > _______________________________________________ > Kernelnewbies mailing list > Kernelnewbies@xxxxxxxxxxxxxxxxx > http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies Jeff, He can just limit the dmesg output by using console_limit I believe. Nick _______________________________________________ Kernelnewbies mailing list Kernelnewbies@xxxxxxxxxxxxxxxxx http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
