qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Amey Moghe <amey1288@gmail.com>
To: David Turner <digit@google.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] How does QEMU kernel receive any input events from host OS
Date: Fri, 4 Sep 2009 15:28:54 +0530	[thread overview]
Message-ID: <1600c7720909040258i2fa51f31g72dafb308ef90c25@mail.gmail.com> (raw)
In-Reply-To: <60cad3f0909021632n6e7528cam479720b74bb61c67@mail.gmail.com>

Hello,

Thanks for the details.I understood how any input event is processed.
But if I pressed a key in guest OS environment then how does client
i.e. guest OS ( with reference to VNC server )   come to know that it
has to send key_event to VNC server? Does client through qemu,
recognise it either from X server running on host OS (e.g. linux ) or
directly from host OS's kernel ?


Thanks,
Amey.

On 9/3/09, David Turner <digit@google.com> wrote:
> the QEMU frontend (e.g. the VNC server or the SDL window) is in charge of
> translating user events
> into emulated hardware ones. Most generally, this will mean emulating a
> keyboard or mouse IRQ
> and the associated i/o protocol. Exact details depend on which hardware you
> want to emulate.
>
> For example, when emulating a PC with PS/2 keyboard and mouse, the code in
> hw/ps2.c will be used.
>
> Here's a concrete example:
>
>    - The VNC server receives packets from the client (see
>    protocol_client_msg in vnc.c).
>    Some of them correspond to keyboard events (processed in key_event() in
>    the same file),
>    which end up calling kbd_put_keycode() after translating the VNC
>    keycode/state into
>    a different key scancode.
>
>
>    - kbd_put_keycode() is defined in vl.c and calls the hardware-specific
>    keycode translator.
>
>
>    - For PC emulation, this happens to be ps2_put_keycode() defined in
>    hw/ps2.c, and
>    registered at startup by ps2_kbd_init() in the same file. It probably is
>    a different function
>    for different emulated hardware.
>
>
>    - The implementation of ps2_put_keycode() will end up enqueue-ing a
>    keycode into
>    a queue then raising an IRQ.
>
>    - The guest kernel responds to the IRQ by running its keyboard driver
>    code, the latter
>    will try to read data from the PS/2 queue
>
>
> The SDL front-end receives user events differently, but still ends up
> calling kbd_put_keycode().
> Same thing happens for mouse events, and about anything that needs to
> emulate hardware
> (e.g. serial/usb/bluetooth/etc...) but implementations and specifics may
> differ.
>
> Hope this helps
>
> On Wed, Sep 2, 2009 at 5:55 AM, Amey Moghe <amey1288@gmail.com> wrote:
>
>> Hello all,
>>
>> I am new to QEMU.While reading about qemu , I came across one statement:
>> "QEMU does not depend on the presence of graphical output methods on the
>> host system. Instead, it allows one to access the screen of the guest OS
>> via
>> VNC. It can also use an emulated serial line, without any screen, with
>> applicable operating systems." on following link :
>>
>> http://en.wikipedia.org/wiki/QEMU
>>
>> So please can anybodys tell me how does qemu use VNC server for receiving
>> events and if yes then how does it receive events from host OS? Or is
>> there
>> any other way with which QEMU receives input events from host OS?
>

  reply	other threads:[~2009-09-04  9:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-02 12:55 [Qemu-devel] How does QEMU kernel receive any input events from host OS Amey Moghe
2009-09-02 23:32 ` David Turner
2009-09-04  9:58   ` Amey Moghe [this message]
2009-09-04 19:36     ` David Turner
2009-09-05 12:52       ` Amey Moghe

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=1600c7720909040258i2fa51f31g72dafb308ef90c25@mail.gmail.com \
    --to=amey1288@gmail.com \
    --cc=digit@google.com \
    --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).