From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Keir Fraser <keir@xen.org>, Xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH 3/4] x86/boot: Move some __high_start code and data into init sections
Date: Mon, 28 Apr 2014 11:16:50 +0100 [thread overview]
Message-ID: <535E2A92.9090305@citrix.com> (raw)
In-Reply-To: <535E45B5020000780000CD1D@nat28.tlf.novell.com>
On 28/04/14 11:12, Jan Beulich wrote:
>>>> On 25.04.14 at 21:50, <andrew.cooper3@citrix.com> wrote:
>> Half of __high_start is strictly for the BSP and will only be run once on
>> boot. To complement 'start_secondary', create 'start_bsp' and move it into
>> the init.code section.
>>
>> The interrupt handler 'ingore_int' is patched into the BSPs IDT, but fully
>> replaced with real handlers early during boot. The BSPs IDT is used by APs
>> until midway through start_secondary, but after the real handlers have been
>> installed. Therefore, 'ignore_int' can move to init.code. Furthermore, its
> s/init[.]code/.init.text/ twice.
I could have sworn I corrected that. I will make certain for v2.
~Andrew
>
>> strings can move to init.data.
> .init.rodata again as well as consistent use of @progbits.
>
> Jan
>
next prev parent reply other threads:[~2014-04-28 10:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-25 19:50 [PATCH 0/4] Improvements to x86 boot code Andrew Cooper
2014-04-25 19:50 ` [PATCH 1/4] x86/boot: Remove high_start and ret_point Andrew Cooper
2014-04-25 19:50 ` [PATCH 2/4] x86/boot: Early data should live in init.data Andrew Cooper
2014-04-28 10:08 ` Jan Beulich
2014-04-28 10:16 ` Andrew Cooper
2014-04-28 10:37 ` Jan Beulich
2014-04-28 10:41 ` Andrew Cooper
2014-04-25 19:50 ` [PATCH 3/4] x86/boot: Move some __high_start code and data into init sections Andrew Cooper
2014-04-28 10:12 ` Jan Beulich
2014-04-28 10:16 ` Andrew Cooper [this message]
2014-04-25 19:50 ` [PATCH 4/4] x86/boot: Use 'hlt' inside terminal loops Andrew Cooper
2014-04-28 10:14 ` 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=535E2A92.9090305@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=keir@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 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.