qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Michael Rolnik <mrolnik@gmail.com>
To: Thomas Huth <thuth@redhat.com>
Cc: "Richard Henderson" <richard.henderson@linaro.org>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>,
	"QEMU Developers" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v27 8/8] target/avr: Add tests
Date: Mon, 22 Jul 2019 15:33:03 +0300	[thread overview]
Message-ID: <CAK4993i6uGJahzxRFGHyBqSzNrfb3Q=kUbQkjcLmTQSVem63dA@mail.gmail.com> (raw)
In-Reply-To: <0a74e963-8465-e45e-b5af-6c543c2c7454@redhat.com>

I changed it to info_report.
raw binaries are totally fine, however if a user supplies a damaged elf he
will never know if no warning/info is reported.

On Mon, Jul 22, 2019 at 12:41 PM Thomas Huth <thuth@redhat.com> wrote:

>  Hi Michael,
>
> On 22/07/2019 11.16, Michael Rolnik wrote:
> > Hi Thomas.
> > where should I specify this command?
>
> In patch 6/8, you introduced the error message:
>
>         if (bytes_loaded < 0) {
>             error_report(
>                 "Unable to load %s as ELF, trying again as raw binary",
>                 firmware);
>             bytes_loaded = load_image_targphys(
>                 filename, OFFSET_CODE, SIZE_FLASH);
>         }
>
> You should fence it there like this:
>
>         if (bytes_loaded < 0) {
>             if (!qtest_enabled()) {
>                 error_report(
>                     "Unable to load %s as ELF, trying again as raw binary",
>                     firmware);
>             }
>             bytes_loaded = load_image_targphys(
>                 filename, OFFSET_CODE, SIZE_FLASH);
>         }
>
> Also, is this really an error, or should this rather be a warn_report()
> instead? Or maybe you don't even need this message at all, in case raw
> binaries are a valid alternative?
>
>   Thomas
>
>
> > On Sun, Jul 21, 2019 at 10:13 AM Thomas Huth <thuth@redhat.com
> > <mailto:thuth@redhat.com>> wrote:
> >
> >     On 19/07/2019 15.26, Philippe Mathieu-Daudé wrote:
> >     > On 7/19/19 10:26 AM, Michael Rolnik wrote:
> [...]
> >     > Testing shows:
> >     >
> >     >   TEST    check-qtest-avr: tests/boot-serial-test
> >     > qemu-system-avr: Unable to load /tmp/qtest-boot-serial-cOndewD as
> ELF,
> >     > trying again as raw binary
> >     >
> >     > I wonder if this might fail Peter's testing, so Cc'ing Thomas.
> >
> >     Such messages are quite a bit anoying during "make check", indeed.
> Could
> >     you please fence the message with qtest_enabled() ?
> >
> >      Thanks,
> >        Thomas
> >
> >
> >
> > --
> > Best Regards,
> > Michael Rolnik
>
>

-- 
Best Regards,
Michael Rolnik

  reply	other threads:[~2019-07-22 12:33 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-19  8:26 [Qemu-devel] [PATCH v27 0/8] QEMU AVR 8 bit cores Michael Rolnik
2019-07-19  8:26 ` [Qemu-devel] [PATCH v27 1/8] target/avr: Add outward facing interfaces and core CPU logic Michael Rolnik
2019-07-19  8:26 ` [Qemu-devel] [PATCH v27 2/8] target/avr: Add instruction helpers Michael Rolnik
2019-07-19  8:26 ` [Qemu-devel] [PATCH v27 3/8] target/avr: Add instruction decoding Michael Rolnik
2019-07-19  8:26 ` [Qemu-devel] [PATCH v27 4/8] target/avr: Add instruction translation Michael Rolnik
2019-07-19  8:26 ` [Qemu-devel] [PATCH v27 5/8] target/avr: Add limited support for USART and 16 bit timer peripherals Michael Rolnik
2019-07-25 10:00   ` Pavel Dovgalyuk
2019-07-25 17:52     ` Michael Rolnik
2019-07-26 14:53       ` Sarah Harris
2019-12-05 10:27     ` Aleksandar Markovic
2019-12-05 10:33       ` Aleksandar Markovic
2019-12-05 11:13         ` Aleksandar Markovic
2019-12-06 11:32       ` Pavel Dovgalyuk
2019-07-19  8:26 ` [Qemu-devel] [PATCH v27 6/8] target/avr: Add example board configuration Michael Rolnik
2019-07-19 14:02   ` Philippe Mathieu-Daudé
2019-07-19 15:04     ` Michael Rolnik
2019-07-19 15:14       ` Michael Rolnik
2019-07-19 15:29         ` Philippe Mathieu-Daudé
2019-07-19  8:26 ` [Qemu-devel] [PATCH v27 7/8] target/avr: Register AVR support with the rest of QEMU, the build system, and the MAINTAINERS file Michael Rolnik
2019-07-19 15:43   ` Eric Blake
2019-07-19 16:04     ` Michael Rolnik
2019-07-19  8:26 ` [Qemu-devel] [PATCH v27 8/8] target/avr: Add tests Michael Rolnik
2019-07-19 13:26   ` Philippe Mathieu-Daudé
2019-07-19 15:05     ` Michael Rolnik
2019-07-21  7:13     ` Thomas Huth
2019-07-22  9:16       ` Michael Rolnik
2019-07-22  9:41         ` Thomas Huth
2019-07-22 12:33           ` Michael Rolnik [this message]
2019-07-22 12:40             ` Peter Maydell
2019-07-22 13:45               ` Michael Rolnik

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='CAK4993i6uGJahzxRFGHyBqSzNrfb3Q=kUbQkjcLmTQSVem63dA@mail.gmail.com' \
    --to=mrolnik@gmail.com \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.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).