From: "Ahmed S. Darwish" <darwish.07@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: hpa@zytor.com
Subject: i386: Fix null interrupt handler (ignore_int) message ?
Date: Tue, 25 Sep 2007 01:08:17 +0300 [thread overview]
Message-ID: <20070924220817.GA3447@Ahmed> (raw)
Hi all,
I'm getting little confused by some ignore_int (null interrupt handler) code in
head.S. Code notifies the user about the unknown raised interrupt by below
string:
int_msg:
.asciz "Unknown interrupt or fault at EIP %p %p %p\n"
and prints it using below code path:
ignore_int:
pushl %eax; pushl %ecx; pushl %edx; pushl %es; pushl %ds
[...]
pushl 16(%esp); pushl 24(%esp);
pushl 32(%esp); pushl 40(%esp);
pushl $int_msg
[...]
call printk
** But here's the state of stack before calling printk:
??? <-- 40(%esp)
??? <-- 36(%esp)
--> (Automatically pushed by the processor)
%eflags <-- 32(%esp)
%cs <-- 28(%esp)
%eip <-- 24(%esp)
error-code <-- 20(%esp)
--> (Pushed by first lines of ignore_int)
%eax <-- 16(%esp)
%ecx <-- 12(%esp)
%edx <-- 8(%esp)
%es <-- 4(%esp)
%ds <-- %esp
Does 40(%esp) hold a meaningfule value here ?. Also why passing 4 arguments after
the string to prinkt while the string only has 3 conversion specifications (i.e.,
3 * %p) ?.
Best regards,
--
Ahmed S. Darwish
HomePage: http://darwish.07.googlepages.com
Blog: http://darwish-07.blogspot.com
reply other threads:[~2007-09-24 22:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070924220817.GA3447@Ahmed \
--to=darwish.07@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox