xen-devel.lists.xenproject.org archive mirror
 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 v2 6/8] xen/x86: Reorder .data and .init when linking
Date: Wed, 24 Feb 2016 11:44:11 +0000	[thread overview]
Message-ID: <56CD978B.3030204@citrix.com> (raw)
In-Reply-To: <56CDA50402000078000D595D@prv-mh.provo.novell.com>

On 24/02/16 11:41, Jan Beulich wrote:
>>>> On 23.02.16 at 17:31, <andrew.cooper3@citrix.com> wrote:
>> In preparation for using superpage mappings, .data and .bss will both want to
>> be mapped as read-write.  By making them adjacent, they can share the same
>> superpage and will not require superpage alignment between themselves.
>>
>> While making this change, fix an exposed alignment bug.  __init_end only needs
>> page alignment, while .bss.stack_aligned needs STACK_SIZE alignment.
> Well, this has become a bug only with your changes (perhaps
> that what you mean with "fix an exposed alignment bug", but
> it reads as if there was a latent one, which isn't the case afaict).

It is a latent bug.  The alignment directive for .bss.stack_aligned was
part of .init rather than .bss

>
>>    .bss : {                     /* BSS */
>>         __bss_start = .;
>> +       . = ALIGN(STACK_SIZE);
> These two lines should be swapped - there's no point in starting
> the BSS ahead of the alignment, causing us to needlessly zero
> a few more pages during boot.

Will do.

~Andrew

  reply	other threads:[~2016-02-24 11:44 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-23 16:31 [PATCH v2 0/8] Map Xen code/data/bss with superpages Andrew Cooper
2016-02-23 16:31 ` [PATCH v2 1/8] xen/lockprof: Move .lockprofile.data into .rodata Andrew Cooper
2016-02-24 11:16   ` Jan Beulich
2016-02-23 16:31 ` [PATCH v2 2/8] xen/x86: Improvements to build-time pagetable generation Andrew Cooper
2016-02-24 11:24   ` Jan Beulich
2016-02-24 13:57     ` Andrew Cooper
2016-02-24 14:15       ` Jan Beulich
2016-02-24 14:58         ` Andrew Cooper
2016-02-24 15:18           ` Jan Beulich
2016-02-24 15:22             ` Andrew Cooper
2016-02-24 15:48               ` Jan Beulich
2016-02-24 16:14                 ` Andrew Cooper
2016-02-24 16:59                   ` Jan Beulich
2016-02-24 17:28                     ` Andrew Cooper
2016-02-23 16:31 ` [PATCH v2 3/8] xen/x86: Construct the {l2, l3}_bootmap at compile time Andrew Cooper
2016-02-24 11:34   ` Jan Beulich
2016-02-24 11:40     ` Andrew Cooper
2016-02-24 11:50       ` Jan Beulich
2016-02-24 12:07         ` Andrew Cooper
2016-02-23 16:31 ` [PATCH v2 4/8] xen/memguard: Drop memguard_init() entirely Andrew Cooper
2016-02-24 13:26   ` Jan Beulich
2016-02-24 15:02     ` Stefano Stabellini
2016-02-23 16:31 ` [PATCH v2 5/8] xen/x86: Disable CR0.WP while applying alternatives Andrew Cooper
2016-02-23 16:31 ` [PATCH v2 6/8] xen/x86: Reorder .data and .init when linking Andrew Cooper
2016-02-24 11:41   ` Jan Beulich
2016-02-24 11:44     ` Andrew Cooper [this message]
2016-02-23 16:31 ` [PATCH v2 7/8] xen/x86: Use 2M superpages for text/data/bss mappings Andrew Cooper
2016-02-24 13:17   ` Jan Beulich
2016-02-24 13:21     ` Andrew Cooper
2016-02-24 13:23       ` Andrew Cooper
2016-02-23 16:31 ` [PATCH v2 8/8] xen/x86: Unilaterally remove .init mappings Andrew Cooper

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=56CD978B.3030204@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 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).