From: Gerd Hoffmann <kraxel@redhat.com>
To: Alon Levy <alevy@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC] hw/qxl: inject interrupts in any state
Date: Thu, 01 Nov 2012 11:33:49 +0100 [thread overview]
Message-ID: <5092500D.6000907@redhat.com> (raw)
In-Reply-To: <833806772.25295125.1351765330902.JavaMail.root@redhat.com>
Hi,
> This prevents a known abort on set_client_capabilities, that should be
> fixed in upstream, but it should also be checked against in qxl. Checks
> every other location that qxl_send_events is eventually possibly called
Why check in all callers instead of qxl_send_events directly?
Just print the warning about the spice server bug & possibly lost events
and go on. With luck the event arrives nevertheless. And if not we at
least sayed before it can happen ;)
> +static void spice_server_bug(PCIQXLDevice *qxl, const char *msg, ...)
> +{
> + va_list ap;
> + va_start(ap, msg);
> + fprintf(stderr, "qxl-%d: spice-server bug: ", qxl->id);
> + vfprintf(stderr, msg, ap);
> + fprintf(stderr, "\n");
> + va_end(ap);
> +}
> +
> +#define SPICE_SERVER_BUG_ONCE(qxl, msg, ...) { \
> + static int called; \
> + if (!called) { \
> + called = 1; \
> + spice_server_bug(qxl, msg, __VA_ARGS__); \
> + } \
> +}
That feels a bit like overkill too.
cheers,
Gerd
next prev parent reply other threads:[~2012-11-01 10:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-31 12:53 [Qemu-devel] [RFC] hw/qxl: inject interrupts in any state Alon Levy
2012-11-01 9:19 ` Gerd Hoffmann
2012-11-01 9:45 ` Alon Levy
2012-11-01 9:55 ` Gerd Hoffmann
2012-11-01 10:22 ` Alon Levy
2012-11-01 10:33 ` Gerd Hoffmann [this message]
2012-11-01 11:48 ` Alon Levy
2012-11-01 12:32 ` Gerd Hoffmann
2012-11-01 12:44 ` Alon Levy
2012-11-01 12:47 ` Gerd Hoffmann
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=5092500D.6000907@redhat.com \
--to=kraxel@redhat.com \
--cc=alevy@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).