All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: Markus Armbruster <armbru@redhat.com>,
	 Stefan Hajnoczi <stefanha@redhat.com>
Cc: qemu-trivial@nongnu.org, qemu-devel@nongnu.org, mst@redhat.com
Subject: Re: [Qemu-trivial] [Qemu-devel] [PATCH 1/1] qtest:Fix the bug about disabling vnc causes "make check" hang
Date: Tue, 07 Jan 2014 12:36:11 +0100	[thread overview]
Message-ID: <52CBE6AB.1060400@suse.de> (raw)
In-Reply-To: <8761pw2i6o.fsf@blackfin.pond.sub.org>

Am 07.01.2014 11:35, schrieb Markus Armbruster:
> Stefan Hajnoczi <stefanha@redhat.com> writes:
>> On Tue, Dec 31, 2013 at 01:19:02AM +0100, Andreas Färber wrote:
>>> Am 30.12.2013 09:46, schrieb Kewei Yu:
>>>> diff --git a/tests/fdc-test.c b/tests/fdc-test.c
>>>> index 38b5b17..80dbdfb 100644
>>>> --- a/tests/fdc-test.c
>>>> +++ b/tests/fdc-test.c
>>>> @@ -538,7 +538,11 @@ int main(int argc, char **argv)
>>>>      /* Run the tests */
>>>>      g_test_init(&argc, &argv, NULL);
>>>>  
>>>> +#ifdef CONFIG_VNC
>>>>      cmdline = g_strdup_printf("-vnc none ");
>>>> +#else
>>>> +    cmdline = NULL;
>>>> +#endif
>>>>  
>>>>      qtest_start(cmdline);
>>>>      qtest_irq_intercept_in(global_qtest, "ioapic");
>>>
>>> I have already made -display none a default used by all qtests.
>>> http://git.qemu.org/?p=qemu.git;a=commit;h=2ad645d2854746b55ddfd1d8e951f689cca5d78f
>>>
>>> Is there a reason not to do the same for -vnc none?
>>> That would consolidate the #ifdef'ery to one central point.
>>
>> Agreed, let's set -vnc none by default in one place (if enabled by
>> ./configure).
>>
>> I wonder if we should use -nodefaults too?  That may require adding some
>> new options to explicitly set up devices used by existing tests.
> 
> Try and see what explodes?

I fear that will render my qom-test useless, which is supposed to test
our defaults. If -nodefaults drops serial ports, floppy drives, etc.
that will reduce its usefulness. Unless of course we find a way to
override -nodefaults with some generic -defaults options. :)
I haven't noticed anyone actually adding qtests along with new machines,
adding them to qom-test already required some poking of mine.

End of last year I was preparing some qtests for optional PCI devices,
but even such stubs are hard to share across multiple shoulders due to
resulting Makefile conflicts...

Andreas

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg


WARNING: multiple messages have this Message-ID (diff)
From: "Andreas Färber" <afaerber@suse.de>
To: Markus Armbruster <armbru@redhat.com>,
	Stefan Hajnoczi <stefanha@redhat.com>
Cc: qemu-trivial@nongnu.org, Kewei Yu <keweihk@gmail.com>,
	qemu-devel@nongnu.org, mst@redhat.com
Subject: Re: [Qemu-devel] [PATCH 1/1] qtest:Fix the bug about disabling vnc causes "make check" hang
Date: Tue, 07 Jan 2014 12:36:11 +0100	[thread overview]
Message-ID: <52CBE6AB.1060400@suse.de> (raw)
In-Reply-To: <8761pw2i6o.fsf@blackfin.pond.sub.org>

Am 07.01.2014 11:35, schrieb Markus Armbruster:
> Stefan Hajnoczi <stefanha@redhat.com> writes:
>> On Tue, Dec 31, 2013 at 01:19:02AM +0100, Andreas Färber wrote:
>>> Am 30.12.2013 09:46, schrieb Kewei Yu:
>>>> diff --git a/tests/fdc-test.c b/tests/fdc-test.c
>>>> index 38b5b17..80dbdfb 100644
>>>> --- a/tests/fdc-test.c
>>>> +++ b/tests/fdc-test.c
>>>> @@ -538,7 +538,11 @@ int main(int argc, char **argv)
>>>>      /* Run the tests */
>>>>      g_test_init(&argc, &argv, NULL);
>>>>  
>>>> +#ifdef CONFIG_VNC
>>>>      cmdline = g_strdup_printf("-vnc none ");
>>>> +#else
>>>> +    cmdline = NULL;
>>>> +#endif
>>>>  
>>>>      qtest_start(cmdline);
>>>>      qtest_irq_intercept_in(global_qtest, "ioapic");
>>>
>>> I have already made -display none a default used by all qtests.
>>> http://git.qemu.org/?p=qemu.git;a=commit;h=2ad645d2854746b55ddfd1d8e951f689cca5d78f
>>>
>>> Is there a reason not to do the same for -vnc none?
>>> That would consolidate the #ifdef'ery to one central point.
>>
>> Agreed, let's set -vnc none by default in one place (if enabled by
>> ./configure).
>>
>> I wonder if we should use -nodefaults too?  That may require adding some
>> new options to explicitly set up devices used by existing tests.
> 
> Try and see what explodes?

I fear that will render my qom-test useless, which is supposed to test
our defaults. If -nodefaults drops serial ports, floppy drives, etc.
that will reduce its usefulness. Unless of course we find a way to
override -nodefaults with some generic -defaults options. :)
I haven't noticed anyone actually adding qtests along with new machines,
adding them to qom-test already required some poking of mine.

End of last year I was preparing some qtests for optional PCI devices,
but even such stubs are hard to share across multiple shoulders due to
resulting Makefile conflicts...

Andreas

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

  reply	other threads:[~2014-01-07 11:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-30  8:46 [Qemu-trivial] [PATCH 1/1] qtest:Fix the bug about disabling vnc causes "make check" hang Kewei Yu
2013-12-30  8:46 ` [Qemu-devel] " Kewei Yu
2013-12-31  0:19 ` [Qemu-trivial] " Andreas Färber
2013-12-31  0:19   ` Andreas Färber
2014-01-02  4:08   ` [Qemu-trivial] " Stefan Hajnoczi
2014-01-02  4:08     ` Stefan Hajnoczi
2014-01-07 10:35     ` [Qemu-trivial] " Markus Armbruster
2014-01-07 10:35       ` Markus Armbruster
2014-01-07 11:36       ` Andreas Färber [this message]
2014-01-07 11:36         ` Andreas Färber
2014-01-09 13:33         ` [Qemu-trivial] " Markus Armbruster
2014-01-09 13:33           ` Markus Armbruster

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=52CBE6AB.1060400@suse.de \
    --to=afaerber@suse.de \
    --cc=armbru@redhat.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.org \
    --cc=stefanha@redhat.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 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.