From: "Alex Bennée" <alex.bennee@linaro.org>
To: Dario Faggioli <dfaggioli@suse.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Claudio Fontana <Claudio.Fontana@suse.com>
Subject: Re: Problem running qos-test when building with gcc12 and LTO
Date: Wed, 25 May 2022 07:41:31 +0100 [thread overview]
Message-ID: <87v8tu5cyy.fsf@linaro.org> (raw)
In-Reply-To: <24c61f36e23339cb1ab80b41e906ea60a0d67d2a.camel@suse.com>
Dario Faggioli <dfaggioli@suse.com> writes:
> [[PGP Signed Part:Undecided]]
> On Mon, 2022-05-23 at 19:19 +0000, Dario Faggioli wrote:
>> As soon as I get rid of _both_ "-flto=auto" _and_ "--enable-lto", the
>> above tests seem to work fine.
>>
>> When they fail, they fail immediately, while creating the graph, like
>> this:
>>
>> MALLOC_PERTURB_=${MALLOC_PERTURB_:-$(( ${RANDOM:-0} % 255 + 1))}
>> QTEST_QEMU_IMG=./qemu-img G_TEST_DBUS_DAEMON=../tests/dbus-vmstate-
>> daemon.sh QTEST_QEMU_STORAGE_DAEMON_BINARY=./storage-daemon/qemu-
>> storage-daemon QTEST_QEMU_BINARY=./qemu-system-x86_64
>> ./tests/qtest/qos-test --tap -k
>> # random seed: R02S90d4b61102dd94459f986c2367d6d375
>> # starting QEMU: exec ./qemu-system-x86_64 -qtest unix:/tmp/qtest-
>> 28822.sock -qtest-log /dev/null -chardev socket,path=/tmp/qtest-
>> 28822.qmp,id=char0 -mon chardev=char0,mode=control -display none -
>> machine none -accel qtest
>> QOSStack: full stack, cannot pushAborted
>>
> Ok, apparently, v6.2.0 works (with GCC 12 and LTO), while as said
> v7.0.0 doesn't.
>
> Therefore, I run a bisect, and it pointed at:
>
> 8dcb404bff6d9147765d7dd3e9c8493372186420
> tests/qtest: enable more vhost-user tests by default
>
> I've also confirmed that on v7.0.0 with 8dcb404bff6d914 reverted, the
> test actually works.
>
> As far as downstream packaging is concerned, I'll revert it locally.
> But I'd be happy to help figuring our what is actually going wrong.
>
> I'll try to dig further. Any idea/suggestion anyone has, feel free.
> :-)
Sounds like there are still memory corruption/not initialised issues
that are affected by moving things around.
Does it still trigger errors with my latest virtio cleanup series (which
adds more tests to qos-test):
Subject: [PATCH v2 00/15] virtio-gpio and various virtio cleanups
Date: Tue, 24 May 2022 16:40:41 +0100
Message-Id: <20220524154056.2896913-1-alex.bennee@linaro.org>
>
> Thanks and Regards
--
Alex Bennée
next prev parent reply other threads:[~2022-05-25 6:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-23 19:19 Problem running qos-test when building with gcc12 and LTO Dario Faggioli
2022-05-24 20:12 ` Dario Faggioli
2022-05-25 6:41 ` Alex Bennée [this message]
2022-05-25 9:40 ` Dario Faggioli
2022-05-25 11:30 ` Dario Faggioli
2022-05-25 13:49 ` 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=87v8tu5cyy.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=Claudio.Fontana@suse.com \
--cc=dfaggioli@suse.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).