From: "Alex Bennée" <alex.bennee@linaro.org>
To: Richard Henderson <richard.henderson@linaro.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH] tests/plugin: Remove duplicate insn log from libinsn.so
Date: Mon, 19 Jun 2023 18:34:03 +0100 [thread overview]
Message-ID: <87mt0vjqxi.fsf@linaro.org> (raw)
In-Reply-To: <1199d248-8aee-4e93-95cd-ad8847ed2255@linaro.org>
Richard Henderson <richard.henderson@linaro.org> writes:
> On 6/12/23 04:50, Richard Henderson wrote:
>> On 6/11/23 02:14, Alex Bennée wrote:
>>>
>>> Richard Henderson <richard.henderson@linaro.org> writes:
>>>
>>>> This is a perfectly natural occurrence for x86 "rep movb",
>>>> where the "rep" prefix forms a counted loop of the one insn.
>>>>
>>>> During the tests/tcg/multiarch/memory test, this logging is
>>>> triggered over 350000 times. Within the context of cross-i386-tci
>>>> build, which is already slow by nature, the logging is sufficient
>>>> to push the test into timeout.
>>>
>>> How does this get triggered because I added these:
>>>
>>> # non-inline runs will trigger the duplicate instruction heuristics in libinsn.so
>>> run-plugin-%-with-libinsn.so:
>>> $(call run-test, $@, \
>>> $(QEMU) -monitor none -display none \
>>> -chardev file$(COMMA)path=$@.out$(COMMA)id=output \
>>> -plugin ../../plugin/libinsn.so$(COMMA)inline=on \
>>> -d plugin -D $*-with-libinsn.so.pout \
>>> $(QEMU_OPTS) $*)
>>>
>>> to prevent the callback versions from being called for x86. The original
>>> intent of the check was to detect failures due to cpu_io_recompile, see
>>> e025d799af (tests/plugin: expand insn test to detect duplicate instructions)
>> I have no idea how, but it's happening.
>>
>>>> Signed-off-by: Richard Henderson <richard.henderson@linaro.org>
>>>> ---
>>>> Irritatingly, it doesn't timeout locally, so I used staging to double-check:
>>>>
>>>> Fail: https://gitlab.com/qemu-project/qemu/-/jobs/4450754282#L5062
>>>> Pass: https://gitlab.com/qemu-project/qemu/-/jobs/4450927108
>> Note that in the pass case, we don't even log that the test ran.
>
> Any further thoughts on this? Otherwise I'll merge it to get rid of
> the cross-i386-tci failure...
>
>
> r~
I'm happy to drop the feature from the plugin but the clean-up also
needs to be applied to the run-plugin-%-with-libinsn.so: rules for i386
and x86_64.
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
next prev parent reply other threads:[~2023-06-19 17:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-10 17:19 [PATCH] tests/plugin: Remove duplicate insn log from libinsn.so Richard Henderson
2023-06-11 9:14 ` Alex Bennée
2023-06-12 2:50 ` Richard Henderson
2023-06-19 15:28 ` Richard Henderson
2023-06-19 17:34 ` Alex Bennée [this message]
2023-06-20 7:34 ` Richard Henderson
2023-06-20 12:05 ` Alex Bennée
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=87mt0vjqxi.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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.