qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: lukas.juenger@rwth-aachen.de
Cc: Eric Auger <eric.auger@redhat.com>,
	qemu-arm <qemu-arm@nongnu.org>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [Qemu-arm] Warning when DTB memory nodes are noped
Date: Thu, 13 Dec 2018 15:11:05 +0000	[thread overview]
Message-ID: <CAFEAcA93tPS-jJBoT3fFekEvXx4pJPR_u3P-x1d3op470uexmQ@mail.gmail.com> (raw)
In-Reply-To: <1544713257.4811.32.camel@rwth-aachen.de>

On Thu, 13 Dec 2018 at 15:00, Jünger, Lukas
<lukas.juenger@rwth-aachen.de> wrote:
>
> On Thu, 2018-12-13 at 14:49 +0000, Peter Maydell wrote:
> > Was the deletion of the memory node actually wrong in your case?
> > If so we should look at fixing the wrong behaviour, rather than
> > just being noisier about what we're doing...

> I see. In my case I wanted to specify the memory using the DTB that I
> passed using the -dtb option. I had two memory ranges in the dtb and
> they didn't show up in the kernel later on because they were noped by
> QEMU. I found it confusing that QEMU makes changes to the DTB that I
> passed via -dtb.

Yeah, we don't edit the DTB much but we do fix it up to
indicate the memory, number of CPUs, kernel command line, etc
passed on the QEMU command line.

thanks
-- PMM

      reply	other threads:[~2018-12-13 15:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1544708743.4811.30.camel@rwth-aachen.de>
2018-12-13 14:49 ` [Qemu-devel] [Qemu-arm] Warning when DTB memory nodes are noped Peter Maydell
2018-12-13 15:00   ` Jünger, Lukas
2018-12-13 15:11     ` Peter Maydell [this message]

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=CAFEAcA93tPS-jJBoT3fFekEvXx4pJPR_u3P-x1d3op470uexmQ@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --cc=eric.auger@redhat.com \
    --cc=lukas.juenger@rwth-aachen.de \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    /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).