xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@linaro.org>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: stefano.stabellini@eu.citrix.com, tim@xen.org, xen-devel@lists.xen.org
Subject: Re: [PATCH 2/3] xen: arm: use same variables as userspace in dom0 builder place_modules()
Date: Wed, 09 Apr 2014 14:37:03 +0100	[thread overview]
Message-ID: <53454CFF.8030906@linaro.org> (raw)
In-Reply-To: <1397047972.6275.30.camel@kazak.uk.xensource.com>

On 04/09/2014 01:52 PM, Ian Campbell wrote:
> On Wed, 2014-04-09 at 13:45 +0100, Julien Grall wrote:
>> On 04/09/2014 12:51 PM, Ian Campbell wrote:
>>>  static void place_modules(struct kernel_info *info,
>>> -                         paddr_t kernel_start,
>>> -                         paddr_t kernel_end)
>>> +                          paddr_t kernbase, paddr_t kernend)
>>>  {
>>>      /* Align DTB and initrd size to 2Mb. Linux only requires 4 byte alignment */
>>>      const paddr_t initrd_len =
>>>          ROUNDUP(early_info.modules.module[MOD_INITRD].size, MB(2));
>>>      const paddr_t dtb_len = ROUNDUP(fdt_totalsize(info->fdt), MB(2));
>>> -    const paddr_t total = initrd_len + dtb_len;
>>> +    const paddr_t modsize = initrd_len + dtb_len;
>>>  
>>>      /* Convenient */
>>> -    const paddr_t mem_start = info->mem.bank[0].start;
>>> -    const paddr_t mem_size = info->mem.bank[0].size;
>>> -    const paddr_t mem_end = mem_start + mem_size;
>>> -    const paddr_t kernel_size = kernel_end - kernel_start;
>>> +    const paddr_t rambase = info->mem.bank[0].start;
>>> +    const paddr_t ramsize = info->mem.bank[0].size;
>>> +    const paddr_t ramend = rambase + ramsize;
>>> +    const paddr_t kernsize = kernend - kernbase;
>>> +    const paddr_t ram128mb = rambase + MB(128);
>>
>> Shall we use ram0base, ram0size, ram0end to show that we are using that
>> the first bank?
> 
> I was planning to do that in my 1TB RAM series, but this is different
> code isn't it. Oops.
> 
> I'll change if there is some other reason to repost, but I don't think
> it is worth reposting just for that.

Ok. With or without this change:

Acked-by: Julien Grall <julien.grall@linaro.org>

-- 
Julien Grall

  reply	other threads:[~2014-04-09 13:37 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-09 11:50 [PATCH 0/3] xen: arm: fixes for initrd and dtb placement Ian Campbell
2014-04-09 11:51 ` [PATCH 1/3] tools: arm: improve placement of initial modules Ian Campbell
2014-04-09 12:43   ` Julien Grall
2014-04-09 12:46     ` Ian Campbell
2014-04-10 11:38     ` Ian Campbell
2014-04-10 11:39       ` Ian Jackson
2014-05-22 16:07         ` Ian Jackson
2014-04-09 11:51 ` [PATCH 2/3] xen: arm: use same variables as userspace in dom0 builder place_modules() Ian Campbell
2014-04-09 12:45   ` Julien Grall
2014-04-09 12:52     ` Ian Campbell
2014-04-09 13:37       ` Julien Grall [this message]
2014-04-09 11:51 ` [PATCH 3/3] xen: arm: rework dom0 initrd and dtb placement Ian Campbell
2014-04-09 12:54   ` Julien Grall
2014-04-09 12:57     ` Ian Campbell
2014-04-09 13:09       ` Julien Grall
2014-04-09 13:15         ` Ian Campbell
2014-04-09 13:24           ` Julien Grall
2014-04-09 13:28             ` Ian Campbell
2014-04-09 13:35               ` Julien Grall

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=53454CFF.8030906@linaro.org \
    --to=julien.grall@linaro.org \
    --cc=Ian.Campbell@citrix.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=tim@xen.org \
    --cc=xen-devel@lists.xen.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).