qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>,
	Stefan Hajnoczi <stefanha@redhat.com>
Cc: "Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
	Peter Crosthwaite <peter.crosthwaite@xilinx.com>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL v3 00/15] Tracing patches
Date: Fri, 13 Nov 2015 12:52:37 +0100	[thread overview]
Message-ID: <5645CF05.8010504@redhat.com> (raw)
In-Reply-To: <CAFEAcA8ChriG6wUMC1W5kyTfJQvM1F1FB3PuM-vU7p+GhWBunA@mail.gmail.com>



On 13/11/2015 11:30, Peter Maydell wrote:
> I also now get a handful of extra warnings in the 'make check' output:
> 
>   /aarch64/qom/xilinx-zynq-a9:                                         OK
>   /aarch64/qom/xlnx-ep108:
> WARNING: RAM size 8000000 is small for EP108OK
>   /aarch64/qom/vexpress-a9:                                            OK

This could be an off-by-one.

> (note the missing newline...)
> 
> TEST: tests/qom-test... (pid=19738)
>   /microblaze/qom/none:                                                OK
>   /microblaze/qom/petalogix-s3adsp1800:
> Invalid MicroBlaze version number: (null)
> OK
>   /microblaze/qom/petalogix-ml605:
> Invalid MicroBlaze version number: (null)
> OK

These seem like a genuine problem too.  Peter C. or Edgar, can you look
into them?

Paolo

  parent reply	other threads:[~2015-11-13 11:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-13  7:58 [Qemu-devel] [PULL v3 00/15] Tracing patches Stefan Hajnoczi
2015-11-13 10:30 ` Peter Maydell
2015-11-13 10:44   ` Stefan Hajnoczi
2015-12-21  5:53     ` Denis V. Lunev
2016-01-08  2:49       ` Stefan Hajnoczi
2015-11-13 11:28   ` Peter Maydell
2015-11-13 17:03     ` Edgar E. Iglesias
2015-11-20 12:15       ` Alistair Francis
2015-11-13 11:52   ` Paolo Bonzini [this message]
2016-01-04  8:00 ` Denis V. Lunev

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=5645CF05.8010504@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=edgar.iglesias@gmail.com \
    --cc=peter.crosthwaite@xilinx.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@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 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).