qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Vivier <lvivier@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>, Thomas Huth <thuth@redhat.com>
Cc: pbonzini@redhat.com, qemu-devel@nongnu.org,
	"Peter Maydell" <peter.maydell@linaro.org>,
	"Marcel Apfelbaum" <marcel.a@redhat.com>,
	"David Gibson" <dgibson@redhat.com>,
	"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [Qemu-devel] kvm test warnings
Date: Thu, 29 Sep 2016 17:16:56 +0200	[thread overview]
Message-ID: <da06ced9-57a0-6c22-6414-2bd7f91f552d@redhat.com> (raw)
In-Reply-To: <20160910003052-mutt-send-email-mst@kernel.org>



On 09/09/2016 23:31, Michael S. Tsirkin wrote:
> On Fri, Sep 09, 2016 at 09:24:45PM +0200, Thomas Huth wrote:
>> On 09.09.2016 21:03, Michael S. Tsirkin wrote:
>>> I am running make test on a box without kvm, and I am seeing these warnings:
>>>
>>> GTESTER check-qtest-ppc64
>>> "kvm" accelerator not found.
>>> "kvm" accelerator not found.
>>> GTESTER check-qtest-x86_64
>>> Could not access KVM kernel module: No such file or directory
>>> failed to initialize KVM: No such file or directory
>>> Back to tcg accelerator.
>>> Could not access KVM kernel module: No such file or directory
>>> failed to initialize KVM: No such file or directory
>>> Back to tcg accelerator.
>>>
>>> This is with
>>> commit c2a57aae9a1c3dd7de77daf5478df10379aeeebf
>>> Merge: 5f31bbf f8042de
>>> Author: Peter Maydell <peter.maydell@linaro.org>
>>> Date:   Fri Sep 9 12:49:41 2016 +0100
>>>
>>> I originally thought this is due to Marcel's test change,
>>> but it triggers without ask well.
>>>
>>> Help will be appreciated.
>>
>> See this thread here:
>>
>> https://lists.gnu.org/archive/html/qemu-devel/2016-07/msg05809.html
>>
>> It's not so easy to avoid this warning ... suggestions are welcome...
>>
>>  Thomas
> 
> 
> Really, we just need to add a command line argument
> "--suppress-test-warnings" and pass it in from test framework.
> 

What do you think of only displaying the error on the last accelerator
of the list?

--- a/accel.c
+++ b/accel.c
@@ -99,7 +99,12 @@ void configure_accelerator(MachineState *ms)
         p = get_opt_name(buf, sizeof(buf), p, ':');
         acc = accel_find(buf);
         if (!acc) {
-            fprintf(stderr, "\"%s\" accelerator not found.\n", buf);
+            if (*p != ':') {
+                /* to avoid to pollute logs, display error only
+                 * on the last accelerator of the list
+                 */
+                fprintf(stderr, "\"%s\" accelerator not found.\n", buf);
+            }
             continue;
         }
         if (acc->available && !acc->available()) {

The accelerator list can be seen as a failover list, so I don't think we
have to display an error in this case as it is the expected behavior.

Laurent

  reply	other threads:[~2016-09-29 15:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-09 19:03 [Qemu-devel] kvm test warnings Michael S. Tsirkin
2016-09-09 19:24 ` Thomas Huth
2016-09-09 21:31   ` Michael S. Tsirkin
2016-09-29 15:16     ` Laurent Vivier [this message]
2016-09-29 15:28       ` Thomas Huth

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=da06ced9-57a0-6c22-6414-2bd7f91f552d@redhat.com \
    --to=lvivier@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=dgibson@redhat.com \
    --cc=marcel.a@redhat.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@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 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).