From: mike <qiudayu@linux.vnet.ibm.com>
To: Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: David Gibson <david@gibson.dropbear.id.au>,
qemu-ppc@nongnu.org, qemu-devel@nongnu.org,
Alexander Graf <agraf@suse.de>
Subject: Re: [Qemu-devel] [PATCH] spapr: increase temporary fdt buffer size
Date: Tue, 24 Sep 2013 18:05:47 +0800 [thread overview]
Message-ID: <524163FB.5080101@linux.vnet.ibm.com> (raw)
In-Reply-To: <1380002395-14600-1-git-send-email-aik@ozlabs.ru>
On 09/24/2013 01:59 PM, Alexey Kardashevskiy wrote:
> At the moment the size of the buffer is set to 64K which is
> enough for approximately 150 VCPUs which is not the limit.
>
> This increases the buffer up to 256K which allows having
> a tree for approximately 600 VCPUs which is way beyond the real
> number we need.
>
> As only the real size of the tree is copied to the guest, there
> will be no impact on existing configurations.
>
> Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>
> ---
> hw/ppc/spapr.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/hw/ppc/spapr.c b/hw/ppc/spapr.c
> index 1bb76f1..063fe63 100644
> --- a/hw/ppc/spapr.c
> +++ b/hw/ppc/spapr.c
> @@ -62,7 +62,7 @@
> *
> * We load our kernel at 4M, leaving space for SLOF initial image
> */
> -#define FDT_MAX_SIZE 0x10000
> +#define FDT_MAX_SIZE 0x40000
> #define RTAS_MAX_SIZE 0x10000
> #define FW_MAX_SIZE 0x400000
> #define FW_FILE_NAME "slof.bin"
Signed-off-by: Mike Qiu <qiudayu@linux.vnet.ibm.com>
next prev parent reply other threads:[~2013-09-24 10:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-24 5:59 [Qemu-devel] [PATCH] spapr: increase temporary fdt buffer size Alexey Kardashevskiy
2013-09-24 10:05 ` mike [this message]
2013-09-25 14:55 ` Alexander Graf
2013-09-25 15:00 ` Alexander Graf
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=524163FB.5080101@linux.vnet.ibm.com \
--to=qiudayu@linux.vnet.ibm.com \
--cc=agraf@suse.de \
--cc=aik@ozlabs.ru \
--cc=david@gibson.dropbear.id.au \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.