From: Gerd Hoffmann <kraxel@redhat.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Alon Levy <alevy@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 3/3] hw/qxl: support client monitor configuration via device
Date: Tue, 11 Sep 2012 14:23:30 +0200 [thread overview]
Message-ID: <504F2D42.7020502@redhat.com> (raw)
In-Reply-To: <504F2BB7.1060509@redhat.com>
Hi,
> This will need spice-server <-> qemu/hw/qxl.c coordination, but I assume we
> will need some changes there anyway to set
> QXL_INTERRUPT_CLIENT_MONITORS_CONFIG,
> the qemu/hw/qxl.c function patching the MonitorsConfig into the romspace,
> and setting the irq in int_pending, could return whether or not the flag
> was
> set in int_mask for example.
Yes, interface_client_monitors_config() can return whenever the guest
has masked the interrupt or not, and based on that spice-server can send
the message to the agent or not.
cheers,
Gerd
next prev parent reply other threads:[~2012-09-11 12:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-11 6:56 [Qemu-devel] [PATCH 1/3] hw/qxl: tracing fixes Alon Levy
2012-09-11 6:56 ` [Qemu-devel] [PATCH 2/3] hw/qxl: add support for QXL_IO_CAPABILITIES_SET Alon Levy
2012-09-11 6:56 ` [Qemu-devel] [PATCH 3/3] hw/qxl: support client monitor configuration via device Alon Levy
2012-09-11 8:45 ` Gerd Hoffmann
2012-09-11 9:35 ` Alon Levy
2012-09-11 11:05 ` Gerd Hoffmann
2012-09-11 11:29 ` Alon Levy
2012-09-11 12:10 ` Gerd Hoffmann
2012-09-11 11:43 ` Hans de Goede
2012-09-11 12:03 ` Alon Levy
2012-09-11 12:10 ` Alon Levy
2012-09-11 12:16 ` Hans de Goede
2012-09-11 12:23 ` Gerd Hoffmann [this message]
2012-09-11 12:37 ` Alon Levy
2012-09-11 13:03 ` Gerd Hoffmann
2012-09-11 13:05 ` Alon Levy
2012-09-11 13:24 ` Hans de Goede
2012-09-11 13:55 ` Alon Levy
-- strict thread matches above, loose matches on Subject: below --
2012-09-12 13:13 [Qemu-devel] [PATCH 0/3] client monitors config support Alon Levy
2012-09-12 13:13 ` [Qemu-devel] [PATCH 3/3] hw/qxl: support client monitor configuration via device Alon Levy
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=504F2D42.7020502@redhat.com \
--to=kraxel@redhat.com \
--cc=alevy@redhat.com \
--cc=hdegoede@redhat.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).