* Qemu interrupt handling
@ 2007-08-17 10:05 saggin-O91pjutqpDaRIi+8W+d3eg
[not found] ` <1695.157.27.242.184.1187345108.squirrel-EqM2KoRJkMdNABFEJvf7Pw@public.gmane.org>
0 siblings, 1 reply; 2+ messages in thread
From: saggin-O91pjutqpDaRIi+8W+d3eg @ 2007-08-17 10:05 UTC (permalink / raw)
To: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f
Hi,
I would like to ask a question about how Qemu handle interrupt in user space.
I would like to understand how Qemu catch hardware interrupt generated by
real (host) peripheral.
I look at the Qemu code, (vl.c : main_loop and main_loop_wait) and I can't
identify where Qemu listens and catches the interrupts, for example, from
host NIC in order to pass to the guest NIC emulated.
Could you help me?
Thanks in advance.
Regards.
Saul Saggin
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Qemu interrupt handling
[not found] ` <1695.157.27.242.184.1187345108.squirrel-EqM2KoRJkMdNABFEJvf7Pw@public.gmane.org>
@ 2007-08-17 12:56 ` Avi Kivity
0 siblings, 0 replies; 2+ messages in thread
From: Avi Kivity @ 2007-08-17 12:56 UTC (permalink / raw)
To: saggin-O91pjutqpDaRIi+8W+d3eg; +Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f
saggin-O91pjutqpDaRIi+8W+d3eg@public.gmane.org wrote:
> Hi,
> I would like to ask a question about how Qemu handle interrupt in user space.
> I would like to understand how Qemu catch hardware interrupt generated by
> real (host) peripheral.
> I look at the Qemu code, (vl.c : main_loop and main_loop_wait) and I can't
> identify where Qemu listens and catches the interrupts, for example, from
> host NIC in order to pass to the guest NIC emulated.
>
> Could you help me?
>
>
This is really more suitable for qemu-devel.
In general, qemu doesn't trap the real hardware interrupt; it waits for
a signal (or select()) indicating that there are packets waiting to be
received. Depending on how the emulated nic is configured, there may or
may not be a virtual interrupt generated.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2007-08-17 12:56 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-08-17 10:05 Qemu interrupt handling saggin-O91pjutqpDaRIi+8W+d3eg
[not found] ` <1695.157.27.242.184.1187345108.squirrel-EqM2KoRJkMdNABFEJvf7Pw@public.gmane.org>
2007-08-17 12:56 ` Avi Kivity
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox