From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1NSKsw-0002Me-SS
	for qemu-devel@nongnu.org; Tue, 05 Jan 2010 20:40:30 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1NSKss-0002LT-Dr
	for Qemu-devel@nongnu.org; Tue, 05 Jan 2010 20:40:30 -0500
Received: from [199.232.76.173] (port=49112 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1NSKss-0002LP-8Q
	for Qemu-devel@nongnu.org; Tue, 05 Jan 2010 20:40:26 -0500
Received: from mail-yw0-f176.google.com ([209.85.211.176]:47508)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <pcliu.fd@gmail.com>) id 1NSKsr-00023d-QR
	for Qemu-devel@nongnu.org; Tue, 05 Jan 2010 20:40:25 -0500
Received: by ywh6 with SMTP id 6so17024116ywh.4
	for <Qemu-devel@nongnu.org>; Tue, 05 Jan 2010 17:40:24 -0800 (PST)
MIME-Version: 1.0
In-Reply-To: <3f48acb81001032253w7ec96753t3c708a292cf8e58@mail.gmail.com>
References: <3f48acb81001032253w7ec96753t3c708a292cf8e58@mail.gmail.com>
Date: Wed, 6 Jan 2010 09:40:23 +0800
Message-ID: <3f48acb81001051740s4140e9c5m605828f7217cac8b@mail.gmail.com>
From: =?GB2312?B?wfXF9LPM?= <pcliu.fd@gmail.com>
Content-Type: multipart/alternative; boundary=0016e640d408c87a24047c7509d8
Subject: [Qemu-devel] Re: Can anybody simply explains how the device model
	gets run?
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Qemu-devel@nongnu.org, pcliu.fd@gmail.com

--0016e640d408c87a24047c7509d8
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: quoted-printable

let me be more specific, for pci nic rtl8139, some callback functions are
registered
during initialization, such as rtl8139_receive, rtl8139_can_receive. When
and how
do these functions get called? My qemu vertion is qemu-0.10.6.
Can anyone generally explain the process? It will be very appreciated.

Thanks

2010/1/4 =C1=F5=C5=F4=B3=CC <pcliu.fd@gmail.com>

> As a learner of qemu, I am a little bit confused about the qemu device
> model.
> How the device model gets run and when the device interrupt is raised to
> CPU?
> In the cpu_exec loop or before it?
>
> Thanks
>

--0016e640d408c87a24047c7509d8
Content-Type: text/html; charset=GB2312
Content-Transfer-Encoding: quoted-printable

<div>let me be more specific, for pci nic rtl8139, some callback functions =
are registered</div>
<div>during initialization, such as rtl8139_receive, rtl8139_can_receive. W=
hen and how</div>
<div>do these functions get called? My qemu vertion is qemu-0.10.6.&nbsp;</=
div>
<div>Can anyone generally explain the process? It will be very appreciated.=
</div>
<div>&nbsp;</div>
<div>Thanks<br><br></div>
<div class=3D"gmail_quote">2010/1/4 =C1=F5=C5=F4=B3=CC <span dir=3D"ltr">&l=
t;<a href=3D"mailto:pcliu.fd@gmail.com">pcliu.fd@gmail.com</a>&gt;</span><b=
r>
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div>As a learner of qemu, I am a little bit confused about the qemu device=
 model.</div>
<div>How the device model gets run and when the&nbsp;device interrupt is ra=
ised to CPU?</div>
<div>In the cpu_exec loop or before it?&nbsp;</div>
<div>&nbsp;</div>
<div>Thanks&nbsp;</div></blockquote></div><br>

--0016e640d408c87a24047c7509d8--