From: Andrew Cooper <andrew.cooper3@citrix.com>
To: xen-devel@lists.xen.org
Subject: Re: [PATCH 3/5] x86/link: Reduce the number of sections created
Date: Fri, 5 Jun 2015 17:11:24 +0100 [thread overview]
Message-ID: <5571CA2C.7050803@citrix.com> (raw)
In-Reply-To: <5571DE7C02000078000817E4@mail.emea.novell.com>
On 05/06/15 16:38, Jan Beulich wrote:
>>>> On 05.06.15 at 15:31, <andrew.cooper3@citrix.com> wrote:
>> There is no need for top level sections for each of these, so they are
>> subsumed into more-generic sections.
>>
>> .data.read_mostly and .lockprofile.data are moved to .data
>>
>> .init.setup, .initcall.init, .xsm_initcall.init are moved to .init.data
>>
>> This will simplify the later adjustments to use superpages.
> I'm curious, as I wouldn't expect the section count to matter there
> at all. Generally, especially when having to disassemble a xen-syms
> I find it quite useful if e.g. not all data is lumped together into one
> big .data section.
With hindsight since writing, I think I can solve the conceptual problem
I was having with extra commenting in the linker script.
Originally I attempting to coalesce all sections which would have
identical superpage permissions, but this isn't exclusive with having
these sections separately.
Any thoughts about the .reloc section, at least moving it into it to
between __init_begin and __init_end so it gets reclaimed on boot?
~Andrew
next prev parent reply other threads:[~2015-06-05 16:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-05 13:31 [PATCH 0/5] Further x86 cleanup in preparation for superpages Andrew Cooper
2015-06-05 13:31 ` [PATCH 1/5] xen: Use existing __section() macro instead of opencoding it Andrew Cooper
2015-06-08 12:20 ` Jan Beulich
2015-06-08 12:29 ` Ian Campbell
2015-06-08 13:42 ` Jan Beulich
2015-06-08 14:20 ` Ian Campbell
2015-06-05 13:31 ` [PATCH 2/5] xen/x86: Misc boot/link tweaking Andrew Cooper
2015-06-05 13:31 ` [PATCH 3/5] x86/link: Reduce the number of sections created Andrew Cooper
2015-06-05 15:38 ` Jan Beulich
2015-06-05 16:11 ` Andrew Cooper [this message]
2015-06-05 16:22 ` Jan Beulich
2015-06-05 13:31 ` [PATCH 4/5] x86/setup: Move CPU0s stack out of the Xen text/data/bss virtual region Andrew Cooper
2015-06-05 13:31 ` [PATCH 5/5] x86/boot: Move/copy sections more efficiently Andrew Cooper
2015-06-08 12:10 ` Jan Beulich
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=5571CA2C.7050803@citrix.com \
--to=andrew.cooper3@citrix.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.