qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Graf <agraf@suse.de>
To: Thomas Huth <thuth@linux.vnet.ibm.com>
Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org,
	David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH] pseries: Correct RAM size check for SLOF
Date: Fri, 11 Nov 2011 11:51:12 +0100	[thread overview]
Message-ID: <4EBCFE20.50706@suse.de> (raw)
In-Reply-To: <20111108111221.64984a87@BR8GGW75.de.ibm.com>

On 11/08/2011 11:12 AM, Thomas Huth wrote:
> Am Tue,  8 Nov 2011 16:52:16 +1100
> schrieb David Gibson<david@gibson.dropbear.id.au>:
>
>> The SLOF firmware used on the pseries machine needs a reasonable amount of
>> (guest) RAM in order to run, so we have a check in the machine init
>> function to check that this is available.  However, SLOF runs in real mode
>> (MMU off) which means it can only actually access the RMA (Real Mode Area),
>> not all of RAM.  In many cases the RMA is the same as all RAM, but when
>> running with Book3S HV KVM on PowerPC 970, the RMA must be especially
>> allocated to be (host) physically contiguous.  In this case, the RMA size
>> is determined by what the host admin allocated at boot time, and will
>> usually be less than the whole guest RAM size.
>>
>> This patch corrects the test to see if SLOF has enough memory for this
>> case.
> [...]
>> @@ -562,9 +562,9 @@ static void ppc_spapr_init(ram_addr_t ram_size,
>>
>>           spapr->entry_point = KERNEL_LOAD_ADDR;
>>       } else {
>> -        if (ram_size<  (MIN_RAM_SLOF<<  20)) {
>> +        if (rma_size<  (MIN_RMA_SLOF<<  20)) {
>>               fprintf(stderr, "qemu: pSeries SLOF firmware requires>= "
>> -                    "%ldM guest RAM\n", MIN_RAM_SLOF);
>> +                    "%ldM guest RAM\n", MIN_RMA_SLOF);
> Maybe it's more helpful for the unexperienced users when we change the
> term "guest RAM" to "real mode area (RMA) memory" here? What do you
> think?

Yes, please. That's basically what the patch is changing, so the printf 
should be changed as well :). If you find it too confusing, you can say 
"%ldM guest RAM (RMA)". Whoever uses KVM on a 970 will have to manually 
allocate RMA regions in the first place, so he will know what it means. 
Everyone else will read RAM (which should be correct for p7 KVM and TCG).


Alex

  reply	other threads:[~2011-11-11 10:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-08  5:52 [Qemu-devel] [PATCH] pseries: Correct RAM size check for SLOF David Gibson
2011-11-08 10:12 ` [Qemu-devel] [Qemu-ppc] " Thomas Huth
2011-11-11 10:51   ` Alexander Graf [this message]
2011-11-14  1:44     ` David Gibson

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=4EBCFE20.50706@suse.de \
    --to=agraf@suse.de \
    --cc=david@gibson.dropbear.id.au \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=thuth@linux.vnet.ibm.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).