qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Donald Liew" <donaldliew@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] why do qem/arm not clear CPU_INTERRUPT_HARD bit of env->interrupt_request automatically?
Date: Sun, 8 Oct 2006 02:15:23 +0800	[thread overview]
Message-ID: <84e41160610071115t75b4ec55vbe656630d5ab9373@mail.gmail.com> (raw)

i'm reading qemu-system-arm code and trying to add some more
evaluation boards support for it. in the 0.8.2 source code i found
something i can't understand, when handling interrupts all other
targets clears this bit after calling do_interrupt, however the arm
target doesn't do this, why? won't this cause problems like redundant
interrupts? any special consideration about this?

donald

             reply	other threads:[~2006-10-07 18:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-07 18:15 Donald Liew [this message]
2006-10-08  2:23 ` [Qemu-devel] why do qem/arm not clear CPU_INTERRUPT_HARD bit of env->interrupt_request automatically? Paul Brook
2006-10-08  7:40   ` Donald Liew

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=84e41160610071115t75b4ec55vbe656630d5ab9373@mail.gmail.com \
    --to=donaldliew@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).