qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: "Greg Kurz" <groug@kaod.org>, "Cédric Le Goater" <clg@kaod.org>,
	"Thomas Huth" <thuth@redhat.com>
Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org,
	David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [PATCH] ppc/pnv: Silence missing BMC warning with qtest
Date: Mon, 22 Jun 2020 10:24:17 +0200	[thread overview]
Message-ID: <e2b5e91c-fb8a-e007-ef1f-fbea886d6ae5@redhat.com> (raw)
In-Reply-To: <20200622095312.0919cfc4@bahia.lan>

On 6/22/20 9:53 AM, Greg Kurz wrote:
> On Mon, 22 Jun 2020 09:13:46 +0200
> Cédric Le Goater <clg@kaod.org> wrote:
> 
>> On 6/22/20 8:57 AM, Greg Kurz wrote:
>>> The device introspect test in qtest emits some warnings with the
>>> the pnv machine types during the "nodefaults" phase:
>>>
>>> TEST check-qtest-ppc64: tests/qtest/device-introspect-test
>>> qemu-system-ppc64: warning: machine has no BMC device. Use '-device
>>> ipmi-bmc-sim,id=bmc0 -device isa-ipmi-bt,bmc=bmc0,irq=10' to define
>>> one
>>> qemu-system-ppc64: warning: machine has no BMC device. Use '-device
>>> ipmi-bmc-sim,id=bmc0 -device isa-ipmi-bt,bmc=bmc0,irq=10' to define
>>> one
>>> qemu-system-ppc64: warning: machine has no BMC device. Use '-device
>>> ipmi-bmc-sim,id=bmc0 -device isa-ipmi-bt,bmc=bmc0,irq=10' to define
>>> one
>>>
>>> This is expected since the pnv machine doesn't create the internal
>>> BMC simulator fallback when "-nodefaults" is passed on the command
>>> line, but these warnings appear in ci logs and confuse people.
>>>
>>> Not having a BMC isn't recommended but it is still a supported
>>> configuration, so a straightforward fix is to just silent this
>>> warning when qtest is enabled.
>>>
>>> Fixes: 25f3170b0654 ("ppc/pnv: Create BMC devices only when defaults are enabled")
>>> Reported-by: Philippe Mathieu-Daudé <philmd@redhat.com>
>>> Signed-off-by: Greg Kurz <groug@kaod.org>
>>
>> Reviewed-by: Cédric Le Goater <clg@kaod.org>
>>
>> It looks good but could you reproduce ? 
>>
> 
> Yup, this test is only run in "slow" mode, eg:
> 
>     make check-qtest-ppc64 SPEED=slow

Indeed:
https://gitlab.com/qemu-project/qemu/-/jobs/603546723#L3337

See in .gitlab-ci.yml:

  build-disabled:
   ...
   - make -j"$JOBS"
   - make -j"$JOBS" check-qtest SPEED=slow

Thomas, FYI this job is now timeouting most of the time.

> 
> 
>> C.
>>
>>> ---
>>>  hw/ppc/pnv.c |    9 ++++++---
>>>  1 file changed, 6 insertions(+), 3 deletions(-)
>>>
>>> diff --git a/hw/ppc/pnv.c b/hw/ppc/pnv.c
>>> index 806a5d9a8d34..1622d29b4ba7 100644
>>> --- a/hw/ppc/pnv.c
>>> +++ b/hw/ppc/pnv.c
>>> @@ -21,6 +21,7 @@
>>>  #include "qemu-common.h"
>>>  #include "qemu/units.h"
>>>  #include "qapi/error.h"
>>> +#include "sysemu/qtest.h"
>>>  #include "sysemu/sysemu.h"
>>>  #include "sysemu/numa.h"
>>>  #include "sysemu/reset.h"
>>> @@ -587,9 +588,11 @@ static void pnv_reset(MachineState *machine)
>>>      bmc = pnv_bmc_find(&error_fatal);
>>>      if (!pnv->bmc) {
>>>          if (!bmc) {
>>> -            warn_report("machine has no BMC device. Use '-device "
>>> -                        "ipmi-bmc-sim,id=bmc0 -device isa-ipmi-bt,bmc=bmc0,irq=10' "
>>> -                        "to define one");
>>> +            if (!qtest_enabled()) {
>>> +                warn_report("machine has no BMC device. Use '-device "
>>> +                            "ipmi-bmc-sim,id=bmc0 -device isa-ipmi-bt,bmc=bmc0,irq=10' "
>>> +                            "to define one");
>>> +            }
>>>          } else {
>>>              pnv_bmc_set_pnor(bmc, pnv->pnor);
>>>              pnv->bmc = bmc;
>>>
>>>
>>
> 



  reply	other threads:[~2020-06-22  8:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-22  6:57 [PATCH] ppc/pnv: Silence missing BMC warning with qtest Greg Kurz
2020-06-22  7:13 ` Cédric Le Goater
2020-06-22  7:53   ` Greg Kurz
2020-06-22  8:24     ` Philippe Mathieu-Daudé [this message]
2020-06-22  8:46       ` Thomas Huth
2020-06-22  7:50 ` David Gibson

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=e2b5e91c-fb8a-e007-ef1f-fbea886d6ae5@redhat.com \
    --to=philmd@redhat.com \
    --cc=clg@kaod.org \
    --cc=david@gibson.dropbear.id.au \
    --cc=groug@kaod.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@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).