qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Alexander Graf <agraf@suse.de>
Cc: "qemu-ppc@nongnu.org list:PowerPC" <qemu-ppc@nongnu.org>,
	qemu-devel Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] PPC: E500: Generate device tree on reset
Date: Tue, 23 Jul 2013 16:19:04 -0500	[thread overview]
Message-ID: <1374614344.15592.38@snotra> (raw)
In-Reply-To: <7EA7921E-AF13-4485-94E5-B4068CEDAA9E@suse.de> (from agraf@suse.de on Tue Jul 23 16:15:59 2013)

On 07/23/2013 04:15:59 PM, Alexander Graf wrote:
> 
> On 23.07.2013, at 21:38, Scott Wood wrote:
> 
> > On 07/22/2013 10:28:17 AM, Alexander Graf wrote:
> >> Today we generate the device tree once on machine initialization  
> and then
> >> store the finalized blob in memory to reload it on reset.
> >> This is bad for 2 reasons. First we potentially waste a bunch of  
> RAM for no
> >> good reason, as we have all information required to regenerate the  
> device
> >> tree available anyways.
> >> The second reason is even more important. On machine init when we  
> generate
> >> the device tree for the first time, we don't have all of the  
> devices fully
> >> initialized yet. But the device tree needs to potentially walk  
> devices to
> >> put information about them into the device tree.
> >
> > If you can't produce the entire device tree at init time, how can  
> you calculate its size with a dry run?
> >
> > Device trees are generally pretty small; couldn't we just set a  
> maximum size and allocate that much space?
> 
> It's what we do, unless we load it from the disk. In that case we  
> take the fdt size from disk.

So why do we need the dry run stuff?

-SCott

  reply	other threads:[~2013-07-23 21:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-22 15:28 [Qemu-devel] [PATCH] PPC: E500: Generate device tree on reset Alexander Graf
2013-07-23 19:38 ` Scott Wood
2013-07-23 21:15   ` Alexander Graf
2013-07-23 21:19     ` Scott Wood [this message]
2013-07-23 21:44       ` Alexander Graf
2013-07-23 21:55         ` Scott Wood
2013-07-23 21:56           ` Alexander Graf
2013-07-24  2:58 ` Alexey Kardashevskiy

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=1374614344.15592.38@snotra \
    --to=scottwood@freescale.com \
    --cc=agraf@suse.de \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@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).