* [Qemu-devel] Can anybody simply explains how the device model gets run?
@ 2010-01-04 6:53 刘鹏程
2010-01-06 1:40 ` [Qemu-devel] " 刘鹏程
0 siblings, 1 reply; 2+ messages in thread
From: 刘鹏程 @ 2010-01-04 6:53 UTC (permalink / raw)
To: Qemu-devel, pcliu.fd
[-- Attachment #1: Type: text/plain, Size: 199 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 262 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
* [Qemu-devel] Re: Can anybody simply explains how the device model gets run?
2010-01-04 6:53 [Qemu-devel] Can anybody simply explains how the device model gets run? 刘鹏程
@ 2010-01-06 1:40 ` 刘鹏程
0 siblings, 0 replies; 2+ messages in thread
From: 刘鹏程 @ 2010-01-06 1:40 UTC (permalink / raw)
To: Qemu-devel, pcliu.fd
[-- Attachment #1: Type: text/plain, Size: 581 bytes --]
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 刘鹏程 <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
>
[-- Attachment #2: Type: text/html, Size: 958 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2010-01-06 1:40 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-01-04 6:53 [Qemu-devel] Can anybody simply explains how the device model gets run? 刘鹏程
2010-01-06 1:40 ` [Qemu-devel] " 刘鹏程
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).