From: Thomas Huth <thuth@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
qemu-devel@nongnu.org, Laurent Vivier <lvivier@redhat.com>,
Ben Warren <ben@skyportsystems.com>,
Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [Qemu-devel] [PATCH] tests: switch pxe and vm gen id tests to use kvm
Date: Mon, 17 Jul 2017 09:33:25 +0200 [thread overview]
Message-ID: <35fc2797-a83e-c9bd-639a-02dbcc5b1663@redhat.com> (raw)
In-Reply-To: <20170714173714-mutt-send-email-mst@kernel.org>
On 14.07.2017 16:45, Michael S. Tsirkin wrote:
> On Fri, Jul 14, 2017 at 07:59:54AM +0200, Thomas Huth wrote:
>> On 13.07.2017 19:00, Paolo Bonzini wrote:
>>> On 13/07/2017 18:47, Michael S. Tsirkin wrote:
>>>> Speed up tests on host systems with kvm support.
[...]
>>>> diff --git a/tests/vmgenid-test.c b/tests/vmgenid-test.c
>>>> index 0556ba2..6477dcc 100644
>>>> --- a/tests/vmgenid-test.c
>>>> +++ b/tests/vmgenid-test.c
>>>> @@ -132,7 +132,7 @@ static char disk[] = "tests/vmgenid-test-disk-XXXXXX";
>>>>
>>>> static char *guid_cmd_strdup(const char *guid)
>>>> {
>>>> - return g_strdup_printf("-machine accel=tcg "
>>>> + return g_strdup_printf("-machine accel=kvm:tcg "
>>>> "-device vmgenid,id=testvgid,guid=%s "
>>>> "-drive id=hd0,if=none,file=%s,format=raw "
>>>> "-device ide-hd,drive=hd0 ",
>>>
>>> Acked-by: Paolo Bonzini <pbonzini@redhat.com>
>>
>> NACK.
>
> As a rule, don't send nacks please. Skip directly to the technical
> argument. Nacks add very little to the discussion and tend to scare away
> contributors.
I hope I won't scare *you* away that easily ;-)
But ok, I got the message, and will try to remember it.
>> It's not that simple. If you do it like this, you then suddenly get
>> these ugly '"kvm" accelerator not found' messages during "make check"
>> which we really should avoid.
>>
>> Laurent suggested some better ideas a couple of months ago, but I think
>> the common sense was rather "unit tests should always use TCG" at that
>> point in time:
>>
>> https://lists.gnu.org/archive/html/qemu-devel/2016-10/msg00400.html
>
> Looks good. This was never posted as a patch. Would you or him care
> to test it and re-post? I'll include it with my patch.
That URL points to Paolo's "we should always only use TCG mail" ... I
guess you are rather referring to the other URL below?
Thomas
>> Well, now that we've got the "--disable-tcg" configure option, we should
>> maybe start to reconsider that ;-)
>>
>> So I'm fine with the patch if you also include Laurent's patch to shut
>> up the error message:
>>
>> https://lists.gnu.org/archive/html/qemu-devel/2016-10/msg00395.html
>>
>> Thomas
next prev parent reply other threads:[~2017-07-17 7:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-13 16:47 [Qemu-devel] [PATCH] tests: switch pxe and vm gen id tests to use kvm Michael S. Tsirkin
2017-07-13 17:00 ` Paolo Bonzini
2017-07-14 5:59 ` Thomas Huth
2017-07-14 6:20 ` Paolo Bonzini
2017-07-14 14:37 ` Michael S. Tsirkin
2017-07-17 7:28 ` Laurent Vivier
2017-07-17 13:21 ` Michael S. Tsirkin
2017-07-14 14:45 ` Michael S. Tsirkin
2017-07-17 7:33 ` Thomas Huth [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-07-13 16:43 Michael S. Tsirkin
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=35fc2797-a83e-c9bd-639a-02dbcc5b1663@redhat.com \
--to=thuth@redhat.com \
--cc=ben@skyportsystems.com \
--cc=lvivier@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--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).