All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hollis Blanchard <hollisb@us.ibm.com>
To: Jerone Young <jyoung5@us.ibm.com>
Cc: kvm-devel@lists.sourceforge.net, kvm-ppc-devel@lists.sourceforge.net
Subject: Re: [kvm-ppc-devel] [PATCH 7 of 7] Add ability to specify ram
Date: Fri, 14 Mar 2008 19:16:39 +0000	[thread overview]
Message-ID: <1205522199.16133.32.camel@basalt> (raw)
In-Reply-To: <3060b75a9597d4ab67c2.1205514554@thinkpad.austin.ibm.com>

On Fri, 2008-03-14 at 12:09 -0500, Jerone Young wrote:
> # HG changeset patch
> # User Jerone Young <jyoung5@us.ibm.com>
> # Date 1205514174 18000
> # Branch merge
> # Node ID 3060b75a9597d4ab67c23871df41fc5e5476df2b
> # Parent  63237bde74818a5dc3cdb1baee781dab101290ce
> Add ability to specify ram on command line for bamboo board model
> 
> This patch adds the ability to now specify ram sizes on the command line.
> Due to the nature of the code there are restictions on exactly how
> much ram and the multiple that the size must match.
> 
> Signed-off-by: Jerone Young <jyoung5@us.ibm.com>
> 
> diff --git a/qemu/hw/ppc440_bamboo.c b/qemu/hw/ppc440_bamboo.c
> --- a/qemu/hw/ppc440_bamboo.c
> +++ b/qemu/hw/ppc440_bamboo.c
> @@ -40,32 +40,50 @@ void bamboo_init(ram_addr_t ram_size, in
>  	target_ulong dt_base=0;
>  	void *fdt;
>  	int ret;
> + 	unsigned long ram_sticks[] = {0, 0}; /* Value will be in bytes */
> +	ram_addr_t tmp_ram_size;
> +	int ram_stick_sizes[] = {256, 128, 64, 32, 16, 8 }; /* in Mega bytes */
> +	int i=0, k=0;
> 
>  	uint32_t cpu_freq;
>  	uint32_t timebase_freq;
> 
>  	printf("%s: START\n", __func__);
> 
> -	/* Setup Memory */
> -	if (ram_size) {
> -		printf("Ram size specified on command line is %i bytes\n",
> -								(int)ram_size);
> -		printf("WARNING: RAM is hard coded to 144MB\n");
> -	}
> -	else {
> -		printf("Using defualt ram size of %iMB\n",
> -						((int)ram_size/1024)/1024);
> + 	/* Setup Memory */
> + 	printf("Ram size passed is: %i MB\n",
> + 				((int)ram_size/1024)/1024); 		
> + 
> +	tmp_ram_size = ram_size;
> +
> +	for (i=0; i < (sizeof(ram_sticks)/sizeof(unsigned long)); i++)
> +	{
> +		for (k=0; k < (sizeof(ram_stick_sizes)/sizeof(int)); k++)
> +		{
> +			if ((((tmp_ram_size/1024)/1024)/ram_stick_sizes[k]) > 0)
> +			{
> +				ram_sticks[i] = ram_stick_sizes[k]*1024*1024;
> +				tmp_ram_size -= ram_stick_sizes[k]*1024*1024; 
> +				break;
> +			}
> +		}
> +	
>  	}

Please match the curly brace syntax used everywhere else.

Also, I don't think it makes any sense to multiply and divide by
1024*1024 everywhere; just use the proper units to begin with. Try N<<20
to represent N MB.

"tmp_ram_size" is also unnecessary; just subtract from "ram_size" and
see if it's non-zero at the end.

> -	/* Each bank can only have memory in configurations of
> -	 *   16MB, 32MB, 64MB, 128MB, or 256MB
> -	 */
> -	ram_bases[0] = 0x0;
> -	ram_sizes[0] = 0x08000000;
> -	ram_bases[1] = 0x0;
> -	ram_sizes[1] = 0x01000000;
> +	if (tmp_ram_size)
> +		printf("WARNING: %i left over memory is ram\n", 
> +			(tmp_ram_size/1024)/1024);
> 
> -	printf("Ram size of domain is %d bytes\n", (int)ram_size);
> + 	/* Each bank can only have memory in configurations of
> + 	 *   4MB, 8MB, 16MB, 32MB, 64MB, 128MB, or 256MB
> + 	 *   why? see sdram_bcr()
> + 	 *   
> + 	 *   Max of 512MB
> + 	 */
> + 	ram_bases[0] = 0x0;
> + 	ram_sizes[0] = ram_sticks[0];
> + 	ram_bases[1] = 0x0;
> + 	ram_sizes[1] = ram_sticks[1];

Why keep a separate ram_sticks[] array? Just operate directly on
ram_sizes[], and while you're at it stop hardcoding 2 entries: the SDRAM
controller can emulate all 4.

Also, ram_bases[1] here is very wrong; that definitely needs to be
fixed.

-- 
Hollis Blanchard
IBM Linux Technology Center


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
kvm-ppc-devel mailing list
kvm-ppc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-ppc-devel

WARNING: multiple messages have this Message-ID (diff)
From: Hollis Blanchard <hollisb@us.ibm.com>
To: Jerone Young <jyoung5@us.ibm.com>
Cc: kvm-devel@lists.sourceforge.net, kvm-ppc-devel@lists.sourceforge.net
Subject: Re: [kvm-ppc-devel] [PATCH 7 of 7] Add ability to specify ram on	command line for bamboo	board model
Date: Fri, 14 Mar 2008 14:16:39 -0500	[thread overview]
Message-ID: <1205522199.16133.32.camel@basalt> (raw)
In-Reply-To: <3060b75a9597d4ab67c2.1205514554@thinkpad.austin.ibm.com>

On Fri, 2008-03-14 at 12:09 -0500, Jerone Young wrote:
> # HG changeset patch
> # User Jerone Young <jyoung5@us.ibm.com>
> # Date 1205514174 18000
> # Branch merge
> # Node ID 3060b75a9597d4ab67c23871df41fc5e5476df2b
> # Parent  63237bde74818a5dc3cdb1baee781dab101290ce
> Add ability to specify ram on command line for bamboo board model
> 
> This patch adds the ability to now specify ram sizes on the command line.
> Due to the nature of the code there are restictions on exactly how
> much ram and the multiple that the size must match.
> 
> Signed-off-by: Jerone Young <jyoung5@us.ibm.com>
> 
> diff --git a/qemu/hw/ppc440_bamboo.c b/qemu/hw/ppc440_bamboo.c
> --- a/qemu/hw/ppc440_bamboo.c
> +++ b/qemu/hw/ppc440_bamboo.c
> @@ -40,32 +40,50 @@ void bamboo_init(ram_addr_t ram_size, in
>  	target_ulong dt_base=0;
>  	void *fdt;
>  	int ret;
> + 	unsigned long ram_sticks[] = {0, 0}; /* Value will be in bytes */
> +	ram_addr_t tmp_ram_size;
> +	int ram_stick_sizes[] = {256, 128, 64, 32, 16, 8 }; /* in Mega bytes */
> +	int i=0, k=0;
> 
>  	uint32_t cpu_freq;
>  	uint32_t timebase_freq;
> 
>  	printf("%s: START\n", __func__);
> 
> -	/* Setup Memory */
> -	if (ram_size) {
> -		printf("Ram size specified on command line is %i bytes\n",
> -								(int)ram_size);
> -		printf("WARNING: RAM is hard coded to 144MB\n");
> -	}
> -	else {
> -		printf("Using defualt ram size of %iMB\n",
> -						((int)ram_size/1024)/1024);
> + 	/* Setup Memory */
> + 	printf("Ram size passed is: %i MB\n",
> + 				((int)ram_size/1024)/1024); 		
> + 
> +	tmp_ram_size = ram_size;
> +
> +	for (i=0; i < (sizeof(ram_sticks)/sizeof(unsigned long)); i++)
> +	{
> +		for (k=0; k < (sizeof(ram_stick_sizes)/sizeof(int)); k++)
> +		{
> +			if ((((tmp_ram_size/1024)/1024)/ram_stick_sizes[k]) > 0)
> +			{
> +				ram_sticks[i] = ram_stick_sizes[k]*1024*1024;
> +				tmp_ram_size -= ram_stick_sizes[k]*1024*1024; 
> +				break;
> +			}
> +		}
> +	
>  	}

Please match the curly brace syntax used everywhere else.

Also, I don't think it makes any sense to multiply and divide by
1024*1024 everywhere; just use the proper units to begin with. Try N<<20
to represent N MB.

"tmp_ram_size" is also unnecessary; just subtract from "ram_size" and
see if it's non-zero at the end.

> -	/* Each bank can only have memory in configurations of
> -	 *   16MB, 32MB, 64MB, 128MB, or 256MB
> -	 */
> -	ram_bases[0] = 0x0;
> -	ram_sizes[0] = 0x08000000;
> -	ram_bases[1] = 0x0;
> -	ram_sizes[1] = 0x01000000;
> +	if (tmp_ram_size)
> +		printf("WARNING: %i left over memory is ram\n", 
> +			(tmp_ram_size/1024)/1024);
> 
> -	printf("Ram size of domain is %d bytes\n", (int)ram_size);
> + 	/* Each bank can only have memory in configurations of
> + 	 *   4MB, 8MB, 16MB, 32MB, 64MB, 128MB, or 256MB
> + 	 *   why? see sdram_bcr()
> + 	 *   
> + 	 *   Max of 512MB
> + 	 */
> + 	ram_bases[0] = 0x0;
> + 	ram_sizes[0] = ram_sticks[0];
> + 	ram_bases[1] = 0x0;
> + 	ram_sizes[1] = ram_sticks[1];

Why keep a separate ram_sticks[] array? Just operate directly on
ram_sizes[], and while you're at it stop hardcoding 2 entries: the SDRAM
controller can emulate all 4.

Also, ram_bases[1] here is very wrong; that definitely needs to be
fixed.

-- 
Hollis Blanchard
IBM Linux Technology Center


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

  reply	other threads:[~2008-03-14 19:16 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-14 17:09 [kvm-ppc-devel] [PATCH 0 of 7] [v2] PowerPC kvm-userspace patches Jerone Young
2008-03-14 17:09 ` Jerone Young
2008-03-14 17:09 ` [kvm-ppc-devel] [PATCH 1 of 7] Add libfdt to KVM userspace Jerone Young
2008-03-14 17:09   ` Jerone Young
2008-03-14 17:09 ` [kvm-ppc-devel] [PATCH 2 of 7] Add libfdt support to qemu Jerone Young
2008-03-14 17:09   ` Jerone Young
2008-03-16  5:37   ` [kvm-ppc-devel] [kvm-devel] [PATCH 2 of 7] Add libfdt support Anthony Liguori
2008-03-16  5:37     ` [PATCH 2 of 7] Add libfdt support to qemu Anthony Liguori
2008-03-14 17:09 ` [kvm-ppc-devel] [PATCH 3 of 7] Create new load_uboot() & gunzip Jerone Young
2008-03-14 17:09   ` [PATCH 3 of 7] Create new load_uboot() & gunzip support to uboot loader in Qemu Jerone Young
2008-03-14 17:09 ` [kvm-ppc-devel] [PATCH 4 of 7] Add PPC 440EP bamboo board device Jerone Young
2008-03-14 17:09   ` [PATCH 4 of 7] Add PPC 440EP bamboo board device tree source & binary into qemu Jerone Young
2008-03-14 19:06   ` [kvm-ppc-devel] [PATCH 4 of 7] Add PPC 440EP bamboo Hollis Blanchard
2008-03-14 19:06     ` [kvm-ppc-devel] [PATCH 4 of 7] Add PPC 440EP bamboo board device tree source & binary into qemu Hollis Blanchard
2008-03-14 20:00     ` [kvm-ppc-devel] [PATCH 4 of 7] Add PPC 440EP bamboo Jerone Young
2008-03-14 20:00       ` [kvm-ppc-devel] [PATCH 4 of 7] Add PPC 440EP bamboo board device tree source & binary into qemu Jerone Young
2008-03-14 17:09 ` [kvm-ppc-devel] [PATCH 5 of 7] Add dynamic device tree manipulation Jerone Young
2008-03-14 17:09   ` [PATCH 5 of 7] Add dynamic device tree manipulation & change uboot loader for PPC bamboo board model Jerone Young
2008-03-14 17:09 ` [kvm-ppc-devel] [PATCH 6 of 7] Modify PPC bamboo & ppc440 board Jerone Young
2008-03-14 17:09   ` [PATCH 6 of 7] Modify PPC bamboo & ppc440 board models Jerone Young
2008-03-14 17:09 ` [kvm-ppc-devel] [PATCH 7 of 7] Add ability to specify ram on Jerone Young
2008-03-14 17:09   ` [PATCH 7 of 7] Add ability to specify ram on command line for bamboo board model Jerone Young
2008-03-14 19:16   ` Hollis Blanchard [this message]
2008-03-14 19:16     ` [kvm-ppc-devel] " Hollis Blanchard
2008-03-14 20:07     ` [kvm-ppc-devel] [PATCH 7 of 7] Add ability to specify ram Jerone Young
2008-03-14 20:07       ` [kvm-ppc-devel] [PATCH 7 of 7] Add ability to specify ram on command line for bamboo board model Jerone Young
2008-03-16  5:34   ` [kvm-ppc-devel] [kvm-devel] [PATCH 7 of 7] Add ability to Anthony Liguori
2008-03-16  5:34     ` [PATCH 7 of 7] Add ability to specify ram on command line for bamboo board model Anthony Liguori
2008-03-14 21:20 ` [kvm-ppc-devel] [PATCH 0 of 7] [v2] PowerPC Hollis Blanchard
2008-03-14 21:20   ` [kvm-ppc-devel] [PATCH 0 of 7] [v2] PowerPC kvm-userspace patches Hollis Blanchard
  -- strict thread matches above, loose matches on Subject: below --
2008-03-19 14:45 [kvm-ppc-devel] [PATCH 7 of 7] Add ability to specify ram on Jerone Young
2008-03-19 17:55 ` [kvm-ppc-devel] [PATCH 7 of 7] Add ability to specify ram Hollis Blanchard
2008-03-18 20:06 [kvm-ppc-devel] [PATCH 7 of 7] Add ability to specify ram on Jerone Young
2008-03-18 21:03 ` [kvm-ppc-devel] [PATCH 7 of 7] Add ability to specify ram Hollis Blanchard
2008-03-18 21:17   ` Jerone Young
2008-03-12  4:50 [kvm-ppc-devel] [PATCH 7 of 7] Add ability to specify ram on Jerone Young
2008-03-13  2:23 ` [kvm-ppc-devel] [PATCH 7 of 7] Add ability to specify ram Hollis Blanchard

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=1205522199.16133.32.camel@basalt \
    --to=hollisb@us.ibm.com \
    --cc=jyoung5@us.ibm.com \
    --cc=kvm-devel@lists.sourceforge.net \
    --cc=kvm-ppc-devel@lists.sourceforge.net \
    /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.