qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: stefan weids <stefanweids@gmail.com>
To: 陳韋任 <chenwj@iis.sinica.edu.tw>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Moniter The Ram Access On QEMU
Date: Fri, 30 Mar 2012 15:01:48 +0800	[thread overview]
Message-ID: <CABFBR5TX06Zu2ONDS1DX0U3vBsi_vmGOuVXXU2J8tXi6Fu2rQQ@mail.gmail.com> (raw)
In-Reply-To: <20120329110748.GA81907@cs.nctu.edu.tw>

[-- Attachment #1: Type: text/plain, Size: 1818 bytes --]

Hi Wei-Ren,

Thanks for your reply.

According your email, the function "do_interrupt" handle the external
interrupt just like keyboard interrupt, and the function "gen_exception"
handle the exception just like “SWI”.etc. So the function “gen_exception”
seems to be the answer.

Any comments are appreciated.

BR,
Stefan




在 2012年3月29日 下午7:07,陳韋任 <chenwj@iis.sinica.edu.tw>写道:

> > Now I have some probem with the exception handle. I found the funciton
> > "do_interrupt" in "target-arm/helper.c" and "gen_exception" in
> > "target-arm/translate.c" seems to handle the exceptions. But I am
> comfused
> > with those two functions, which function will do the really work about
> > generating an exception. As my understanding, I think “do_interrupt”
> seems
> > to do some preparations before enter exceptions just like operate some
> > registers and accumulate the exception handler address. And
> "gen_exception"
> > seems to do the read job to generate a exception. But I'm not sure.
>
>   Interrupt is a "external" source which breaks the current execution flow
> of
> the CPU. For example, a device might raise an interrupt so that CPU can
> know the
> device has completed its task. On the other hand, exception is an
> "internal"
> source which breaks the current execution flow of the CPU. Take divide by
> zero
> as an example, CPU will detect this error (occurred in the CPU itself). So
> depends on what you mean "exception", do_interrupt or gen_exception might
> does
> the real work.
>
> Regards,
> chenwj
>
> --
> Wei-Ren Chen (陳韋任)
> Computer Systems Lab, Institute of Information Science,
> Academia Sinica, Taiwan (R.O.C.)
> Tel:886-2-2788-3799 #1667
> Homepage: http://people.cs.nctu.edu.tw/~chenwj
>

[-- Attachment #2: Type: text/html, Size: 2351 bytes --]

      reply	other threads:[~2012-03-30  7:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-24 10:30 [Qemu-devel] Moniter The Ram Access On QEMU stefan weids
2012-03-29  3:28 ` 陳韋任
2012-03-29 10:51   ` stefan weids
2012-03-29 11:07     ` 陳韋任
2012-03-30  7:01       ` stefan weids [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=CABFBR5TX06Zu2ONDS1DX0U3vBsi_vmGOuVXXU2J8tXi6Fu2rQQ@mail.gmail.com \
    --to=stefanweids@gmail.com \
    --cc=chenwj@iis.sinica.edu.tw \
    --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).