qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Taimoor Mirza <taimoor.mrza@gmail.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Problems with QEMU sdcard while using glib 2.33.8
Date: Thu, 19 Sep 2013 10:11:06 +0200	[thread overview]
Message-ID: <CAJSP0QWLt4a-Etvp1Lae3QEX1YpWs+t6V3TCtnDjMCjX87RisA@mail.gmail.com> (raw)
In-Reply-To: <CAO6-N=YYXGWE==E_jFB+onOCZQs=LQ5WxwUgiPSBH0vscgkPFw@mail.gmail.com>

On Thu, Sep 19, 2013 at 8:36 AM, Taimoor Mirza <taimoor.mrza@gmail.com> wrote:

Please use Reply-All to keep the CC list on your reply email.  This
way others on the mailing list can follow the discussion and
participate.

> O1 disassembly is at http://pastebin.com/yxWAmmmf
>
> O2 disassembly is at http://pastebin.com/v0uqHuYY

I diffed them.  The differences look reasonable, nothing obviously broken:
 * The broken -O2 version inlines qemu_coroutine_switch() into
coroutine_trampoline().
 * The broken -O2 version changes the ordering of basic blocks and
switches a few instructions for shorter/cheaper equivalents.

Taimoor: Can you try "make check" with the -O2 version?  In
particular, the test-coroutine tests may fail and that could help us
figure out which operation is broken.

Paolo: CCed you in case you want to diff the working -O1 against the
broken -O2 disassembly.  Perhaps Taimoor's gcc 4.6.2 -O2 subtly breaks
around the Windows Fiber API calls.

> On Wed, Sep 18, 2013 at 7:10 PM, Stefan Hajnoczi <stefanha@gmail.com> wrote:
>> On Thu, Sep 05, 2013 at 04:02:43PM +0500, Taimoor Mirza wrote:
>>> I am using released 1.5.0 version from http://wiki.qemu.org/Download.
>>> I think it should be same as commit ID
>>> "295d81c62414a63c625fa2e78175573d4b3f5ba4"
>>>
>>> I have observed some interesting behavior. This problem does not come
>>> if I use MinGW with GCC version 4.7.2. I was originally using 4.6.2. I
>>> spent some time looking at what can cause this problem and found out
>>> an interesting thing. If I change optimization flag from O2 to O1
>>> while building coroutine-win32 then it works fine even with 4.6.2.
>>> For this I first built QEMU binary with default O2 flag, remove
>>> coroutine-win32.o, changed CFLAG in makefile to O1 and rerun make.
>>> Generated binary works fine without any problem.
>>
>> Can you pastebin the output of "objdump -dr coroutine-win32.o" for both
>> -O2 and -O1?
>>
>> Let's diff them and figure out why it breaks with -O2.
>>
>> Stefan

  parent reply	other threads:[~2013-09-19  8:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-28  5:14 [Qemu-devel] Problems with QEMU sdcard while using glib 2.33.8 Taimoor Mirza
2013-08-28  8:11 ` Stefan Hajnoczi
2013-08-28 11:17   ` Taimoor Mirza
2013-08-28 13:38     ` Stefan Hajnoczi
2013-08-28 19:10       ` Taimoor Mirza
2013-08-29  6:31         ` Taimoor Mirza
2013-08-29  6:59           ` Taimoor Mirza
2013-08-29  8:28         ` Stefan Hajnoczi
2013-09-05 11:02           ` Taimoor Mirza
2013-09-18 14:10             ` Stefan Hajnoczi
     [not found]               ` <CAO6-N=YYXGWE==E_jFB+onOCZQs=LQ5WxwUgiPSBH0vscgkPFw@mail.gmail.com>
2013-09-19  8:11                 ` Stefan Hajnoczi [this message]
2013-09-19 13:38                   ` Paolo Bonzini

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=CAJSP0QWLt4a-Etvp1Lae3QEX1YpWs+t6V3TCtnDjMCjX87RisA@mail.gmail.com \
    --to=stefanha@gmail.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=taimoor.mrza@gmail.com \
    /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).