From: Juergen Gross <jgross@suse.com>
To: xen-devel <xen-devel@lists.xenproject.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Peter Lieven <pl@kamp.de>
Cc: Gerd Hoffmann <kraxel@redhat.com>, Paolo Bonzini <pbonzini@redhat.com>
Subject: [Qemu-devel] Regression with commit 095497ffc66b7f031
Date: Fri, 15 Jul 2016 08:32:37 +0200 [thread overview]
Message-ID: <57888385.1080403@suse.com> (raw)
Commit 095497ffc66b7f031ff2a17f1e50f5cb105ce588 ("vnc-enc-tight: use
thread local storage for palette") introduced a regression with Xen:
Since this commit qemu used as a device model is no longer capable
to register Xenstore watches (that's the effect visible to a user).
Reverting this commit makes qemu behave well again. I have no idea
why that commit would have this effect with Xen, may be some memory
is clobbered?
Juergen
next reply other threads:[~2016-07-15 6:32 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-15 6:32 Juergen Gross [this message]
2016-07-15 7:39 ` [Qemu-devel] Regression with commit 095497ffc66b7f031 Peter Lieven
2016-07-15 8:47 ` Juergen Gross
2016-07-15 8:47 ` [Qemu-devel] " Juergen Gross
2016-07-15 9:03 ` Peter Lieven
2016-07-15 9:23 ` Juergen Gross
2016-07-15 9:23 ` [Qemu-devel] " Juergen Gross
2016-07-15 9:03 ` Peter Lieven
2016-07-15 10:02 ` Paolo Bonzini
2016-07-15 10:02 ` [Qemu-devel] " Paolo Bonzini
2016-07-15 10:07 ` Peter Lieven
2016-07-15 10:07 ` [Qemu-devel] " Peter Lieven
2016-07-15 10:12 ` Paolo Bonzini
2016-07-15 10:12 ` Paolo Bonzini
2016-07-15 10:13 ` [Qemu-devel] " Peter Lieven
2016-07-15 10:13 ` Peter Lieven
2016-07-15 10:12 ` [Qemu-devel] " Gerd Hoffmann
2016-07-15 10:12 ` Gerd Hoffmann
2016-07-15 10:35 ` Paolo Bonzini
2016-07-15 10:35 ` [Qemu-devel] " Paolo Bonzini
2016-07-15 10:41 ` Juergen Gross
2016-07-15 12:42 ` Paolo Bonzini
2016-07-15 13:21 ` [Qemu-devel] [Xen-devel] " Juergen Gross
2016-07-15 13:21 ` Juergen Gross
2016-07-15 12:42 ` Paolo Bonzini
2016-07-15 10:41 ` Juergen Gross
2016-07-15 7:39 ` Peter Lieven
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=57888385.1080403@suse.com \
--to=jgross@suse.com \
--cc=kraxel@redhat.com \
--cc=pbonzini@redhat.com \
--cc=pl@kamp.de \
--cc=qemu-devel@nongnu.org \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.