* [Qemu-devel] Keyboard interrupt routing from QEMU to guest OS
@ 2013-12-09 7:25 Maryyam Muhammad Din
2013-12-09 7:34 ` Samuel Thibault
0 siblings, 1 reply; 4+ messages in thread
From: Maryyam Muhammad Din @ 2013-12-09 7:25 UTC (permalink / raw)
To: qemu-discuss, qemu-devel
[-- Attachment #1: Type: text/plain, Size: 309 bytes --]
Hi everyone,
I am unable to figure-out when someone presses control-c on the keyboard,
how host OS routes it to QEMU and how QEMU then
routes it to the guest?
Please suggest me how can I extract complete control flow.
Thank You
--
Maryyam Muhammad Din
Al-Khawarizmi Institute of Computer Science
UET Lahore
[-- Attachment #2: Type: text/html, Size: 939 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [Qemu-devel] Keyboard interrupt routing from QEMU to guest OS
2013-12-09 7:25 [Qemu-devel] Keyboard interrupt routing from QEMU to guest OS Maryyam Muhammad Din
@ 2013-12-09 7:34 ` Samuel Thibault
2013-12-09 7:44 ` Maryyam Muhammad Din
0 siblings, 1 reply; 4+ messages in thread
From: Samuel Thibault @ 2013-12-09 7:34 UTC (permalink / raw)
To: Maryyam Muhammad Din; +Cc: qemu-devel, qemu-discuss
Maryyam Muhammad Din, le Mon 09 Dec 2013 12:25:23 +0500, a écrit :
> I am unable to figure-out when someone presses control-c on the keyboard,
> how host OS routes it to QEMU and how QEMU then
> routes it to the guest?
It depends which QEMU UI you are using.
> Please suggest me how can I extract complete control flow.
Well, you can read the source for instance :)
Samuel
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [Qemu-devel] Keyboard interrupt routing from QEMU to guest OS
2013-12-09 7:34 ` Samuel Thibault
@ 2013-12-09 7:44 ` Maryyam Muhammad Din
2013-12-09 11:57 ` Samuel Thibault
0 siblings, 1 reply; 4+ messages in thread
From: Maryyam Muhammad Din @ 2013-12-09 7:44 UTC (permalink / raw)
To: Samuel Thibault; +Cc: qemu-devel, qemu-discuss
[-- Attachment #1: Type: text/plain, Size: 907 bytes --]
I have gone through the source code of QEMU but could not figure out how
external interrupts are handled by QEMU for guest. I have tried gdb and
print statements for debugging but there are no conclusive results. If
anyone have experience in debugging QEMU with gdb or any other tool please
guide me.
Thank You
On Mon, Dec 9, 2013 at 12:34 PM, Samuel Thibault <samuel.thibault@gnu.org>wrote:
> Maryyam Muhammad Din, le Mon 09 Dec 2013 12:25:23 +0500, a écrit :
> > I am unable to figure-out when someone presses control-c on the keyboard,
> > how host OS routes it to QEMU and how QEMU then
> > routes it to the guest?
>
> It depends which QEMU UI you are using.
>
> > Please suggest me how can I extract complete control flow.
>
> Well, you can read the source for instance :)
>
> Samuel
>
--
Maryyam Muhammad Din
Al-Khawarizmi Institute of Computer Science
UET Lahore
[-- Attachment #2: Type: text/html, Size: 1495 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [Qemu-devel] Keyboard interrupt routing from QEMU to guest OS
2013-12-09 7:44 ` Maryyam Muhammad Din
@ 2013-12-09 11:57 ` Samuel Thibault
0 siblings, 0 replies; 4+ messages in thread
From: Samuel Thibault @ 2013-12-09 11:57 UTC (permalink / raw)
To: Maryyam Muhammad Din; +Cc: qemu-devel, qemu-discuss
Maryyam Muhammad Din, le Mon 09 Dec 2013 12:44:20 +0500, a écrit :
> I have gone through the source code of QEMU but could not figure out how
> external interrupts are handled by QEMU for guest.
They aren't. It's the UI that manages keyboard etc. So it depends on the
UI you are using. Unless you tell us which one you want to study, we
won't be able to help you.
Samuel
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2013-12-09 11:57 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-12-09 7:25 [Qemu-devel] Keyboard interrupt routing from QEMU to guest OS Maryyam Muhammad Din
2013-12-09 7:34 ` Samuel Thibault
2013-12-09 7:44 ` Maryyam Muhammad Din
2013-12-09 11:57 ` Samuel Thibault
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).