From: "Edgar E. Iglesias" <edgar.iglesias@gmail.com>
To: Muhammad Nouman <nouman307@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Hard Interrupt code in Qemu !
Date: Tue, 12 Mar 2013 15:18:14 +0100 [thread overview]
Message-ID: <20130312141814.GB19147@zapo> (raw)
In-Reply-To: <CAC-BLynMH38Nd7Cop9GBpfcJ1T_j_X3QbpjvX2GxpoocJDjfsg@mail.gmail.com>
On Tue, Mar 12, 2013 at 05:53:51PM +0500, Muhammad Nouman wrote:
> Hi ! i am trying to emulate mips on Qemu but at some point the kernel is
> getting a hard interrupt from Qemu which the kernel is not able to understand
> and makes it a spurious interrupt.Can any one tell me that which part of the
> Qemu code will tell me the source or any information about that hard interrupt
> so i can deal with that?
Hi,
A good starting point is to look at:
target-mips/helper.c: do_interrupt()
These are also useful:
target-mips/cpu.h: cpu_mips_hw_interrupts_pending()
hw/mips_int.c
Cheers,
Edgar
prev parent reply other threads:[~2013-03-12 14:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-12 12:53 [Qemu-devel] Hard Interrupt code in Qemu ! Muhammad Nouman
2013-03-12 14:18 ` Edgar E. Iglesias [this message]
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=20130312141814.GB19147@zapo \
--to=edgar.iglesias@gmail.com \
--cc=nouman307@gmail.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).