All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH] x86/boot: Move/copy sections more efficiently
Date: Tue, 29 Sep 2015 11:26:48 +0100	[thread overview]
Message-ID: <560A6768.2020501@citrix.com> (raw)
In-Reply-To: <5603E3F502000078000A52F8@prv-mh.provo.novell.com>

On 24/09/15 10:52, Jan Beulich wrote:
>>>> On 24.09.15 at 10:14, <andrew.cooper3@citrix.com> wrote:
>> The ALIGN(STACK_SIZE) actually belongs with .bss.stack_aligned, but
>> __init_end still needs page alignment because of the init sections being
>> freed and returned to the domheap after boot.
> Logically that change makes sense, but ...
>
>> --- a/xen/arch/x86/xen.lds.S
>> +++ b/xen/arch/x86/xen.lds.S
>> @@ -158,11 +158,13 @@ SECTIONS
>>         __xsm_initcall_start = .;
>>         *(.xsm_initcall.init)
>>         __xsm_initcall_end = .;
>> +
>> +       . = ALIGN(PAGE_SIZE);
>>    } :text
>> -  . = ALIGN(STACK_SIZE);
>>    __init_end = .;
>>  
>>    .bss : {                     /* BSS */
>> +       . = ALIGN(STACK_SIZE);
>>         __bss_start = .;
>>         *(.bss.stack_aligned)
>>         . = ALIGN(PAGE_SIZE);
> ... any pages between __init_end and __bss_start will all of the
> sudden no longer get freed. I.e. you'll want to move __init_end
> as well (which belongs inside some section anyway).

Hmm so it does.  I will just defer this change to my superpage mapping
series which will fix this issue in a slightly different way.

~Andrew

      reply	other threads:[~2015-09-29 10:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-24  8:14 [PATCH] x86/boot: Move/copy sections more efficiently Andrew Cooper
2015-09-24  9:52 ` Jan Beulich
2015-09-29 10:26   ` Andrew Cooper [this message]

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=560A6768.2020501@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=JBeulich@suse.com \
    --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 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.