From: Paolo Bonzini <pbonzini@redhat.com>
To: Claudio Fontana <cfontana@suse.de>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
qemu-devel@nongnu.org, "Pavel Dovgalyuk" <dovgaluk@ispras.ru>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Richard Henderson" <rth@twiddle.net>
Subject: Re: [PATCH v4 0/3] unbreak non-tcg builds
Date: Mon, 19 Oct 2020 14:59:39 +0200 [thread overview]
Message-ID: <96f02402-fb89-ecc9-aac7-c456c7a2671f@redhat.com> (raw)
In-Reply-To: <6dc61a89-6173-099d-c813-cb8266a7d485@suse.de>
On 19/10/20 12:11, Claudio Fontana wrote:
> Hi all,
>
> anything more for me to do here?
I think nothing, I picked up patch 1 due to conflicts but I was waiting
for comments from Richard. I have now picked them up.
Paolo
> On 10/13/20 9:21 PM, Claudio Fontana wrote:
>> This series now unbreaks current non-tcg builds
>> (!CONFIG_TCG).
>>
>> tests Makefiles need to avoid relying on all non-native
>> archs binaries to be present,
>>
>> bios-tables-test needs to skip tests that are tcg-only,
>>
>> and notably the replay framework needs to consider that
>> it might not be functional (or its code present at all)
>> without TCG.
>>
>> Tested ok target x86_64-softmmu on x86_64 host with:
>>
>> ./configure --enable-tcg --disable-kvm
>> ./configure --enable-kvm --disable-tcg
>> ./configure --enable-tcg --enable-kvm
>>
>> running make check-qtest
>>
>> v3 => v4:
>> * abandon attempts to avoid the code duplication and functional code
>> in stubs, just providing the minimal changes to get things working.
>
> Paolo, is the latest respin ok for you?
>
> Thanks,
>
> Claudio
>
>>
>> v2 => v3:
>>
>> * do not alter the replay api, provide a block wrapper
>> instead to call into replay events handling
>> or the normal call flow depending on whether replay events are enabled.
>>
>> v1: initial RFC
>>
>> Claudio Fontana (2):
>> qtest: unbreak non-TCG builds in bios-tables-test
>> replay: do not build if TCG is not available
>>
>> Paolo Bonzini (1):
>> tests/Makefile.include: unbreak non-tcg builds
>>
>> block/meson.build | 3 +-
>> migration/savevm.c | 11 ++--
>> net/meson.build | 3 +-
>> replay/meson.build | 2 +-
>> replay/replay-input.c | 4 +-
>> stubs/meson.build | 1 -
>> stubs/replay-user.c | 9 ----
>> stubs/replay.c | 98 ++++++++++++++++++++++++++++++++++
>> tests/Makefile.include | 2 +-
>> tests/ptimer-test-stubs.c | 5 --
>> tests/qtest/bios-tables-test.c | 10 ++++
>> tests/qtest/qmp-cmd-test.c | 3 ++
>> ui/input.c | 12 ++++-
>> 13 files changed, 136 insertions(+), 27 deletions(-)
>> delete mode 100644 stubs/replay-user.c
>>
>
prev parent reply other threads:[~2020-10-19 13:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-13 19:21 [PATCH v4 0/3] unbreak non-tcg builds Claudio Fontana
2020-10-13 19:21 ` [PATCH v4 1/3] tests/Makefile.include: " Claudio Fontana
2020-10-13 19:21 ` [PATCH v4 2/3] qtest: unbreak non-TCG builds in bios-tables-test Claudio Fontana
2020-10-13 19:21 ` [PATCH v4 3/3] replay: do not build if TCG is not available Claudio Fontana
2020-10-14 5:42 ` Pavel Dovgalyuk
2020-10-14 6:51 ` Claudio Fontana
2020-10-14 12:07 ` Pavel Dovgalyuk
2020-10-19 10:11 ` [PATCH v4 0/3] unbreak non-tcg builds Claudio Fontana
2020-10-19 12:59 ` Paolo Bonzini [this message]
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=96f02402-fb89-ecc9-aac7-c456c7a2671f@redhat.com \
--to=pbonzini@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=cfontana@suse.de \
--cc=dovgaluk@ispras.ru \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).