From: Aurelien Jarno <aurelien@aurel32.net>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: Amit Shah <amit.shah@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Bug 1127369] Re: i386 emulation unreliable since commit b76f0d8c2e3eac94bc7fd90a510cb7426b2a2699
Date: Mon, 1 Apr 2013 00:10:54 +0200 [thread overview]
Message-ID: <20130331221054.GA12198@hall.aurel32.net> (raw)
In-Reply-To: <20130331192420.8829.56464.malone@gac.canonical.com>
Anthony,
On Sun, Mar 31, 2013 at 07:24:20PM -0000, Andreas Gustafsson wrote:
> Thank you. Now if someone could also fix bug 1154328 , my automated
> tests might run again...
This bug is indeed quite problematic and is caused by one of your
patches:
commit a29753f8aa79a34a324afebe340182a51a5aef11
Author: Anthony Liguori <aliguori@us.ibm.com>
Date: Tue Mar 5 23:21:19 2013 +0530
qemu-char: convert fd_chr to use a GIOChannel
This uses the newly introduced IOWatchPoll source.
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
Signed-off-by: Amit Shah <amit.shah@redhat.com>
Message-id: 0cb5d14510ee835a0ebc23676d10a2cce9280da5.1362505276.git.amit.shah@redhat.com
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
Are you aware of the issue? Are you working on a fix?
Regards,
Aurelien
--
Aurelien Jarno GPG: 1024D/F1BCDB73
aurelien@aurel32.net http://www.aurel32.net
next prev parent reply other threads:[~2013-03-31 22:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130216171535.8893.2.malonedeb@gac.canonical.com>
2013-03-31 16:39 ` [Qemu-devel] [Bug 1127369] Re: i386 emulation unreliable since commit b76f0d8c2e3eac94bc7fd90a510cb7426b2a2699 Aurelien Jarno
2013-03-31 17:47 ` Richard Jones
2013-03-31 18:46 ` Aurelien Jarno
2013-03-31 19:24 ` Andreas Gustafsson
2013-03-31 22:10 ` Aurelien Jarno [this message]
2013-03-31 20:08 ` Richard Jones
2013-04-11 6:43 ` Andreas Gustafsson
2013-05-17 17:57 ` Andreas Gustafsson
2013-05-20 17:32 ` Aurelien Jarno
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=20130331221054.GA12198@hall.aurel32.net \
--to=aurelien@aurel32.net \
--cc=aliguori@us.ibm.com \
--cc=amit.shah@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).