linux-kernel - Re: when interrupt came, the kernel save pt

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.DEB.2.00.0812130854380.28394@montezuma.windriver.com>
Date:	Sat, 13 Dec 2008 08:55:55 -0800 (PST)
From:	Zwane Mwaikambo <zwane@...radead.org>
To:	pl ice <telent997@...il.com>
cc:	linux-kernel@...r.kernel.org
Subject: Re: when interrupt came, the kernel save pt_regs->eip always the
 same?

On Sat, 13 Dec 2008, pl ice wrote:

> HI,
>     These day i wanted get cpu context ,when interrupt came.BUT i
> found when interrupt came kernel saved cpu context in struct pt_regs
> and delivered to do_IRQ ,and i print the pt_regs->eip,they alway same
> on the same interrupt?
>      The interrupt can come anytime,i think the eip will be very
> different every time.BUT i debug kernel ,print eip in the function
> do_IRQ,found it didn't run as i thought.Can anybody tell me why?

If the cpu is idle, you have a higher probability that the idle function 
is in regs->eip

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