mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: vgoyal@in.ibm.com
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@osdl.org>, Andi Kleen <ak@muc.de>,
	Morton Andrew Morton <akpm@osdl.org>,
	Fastboot mailing list <fastboot@lists.osdl.org>,
	Adrian Bunk <bunk@stusta.de>, Jean Delvare <khali@linux-fr.org>,
	Segher Boessenkool <segher@kernel.crashing.org>
Subject: Re: [PATCH] i386 kernel instant reboot with older binutils fix
Date: Tue, 02 Jan 2007 23:44:34 -0700	[thread overview]
Message-ID: <m1tzz8k3sd.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <20070103041645.GA17546@in.ibm.com> (Vivek Goyal's message of "Wed, 3 Jan 2007 09:46:45 +0530")

Vivek Goyal <vgoyal@in.ibm.com> writes:

> o i386 kernel reboots instantly if compiled with binutils older than
>   2.6.15.
>
> o Older binutils required explicit flags to mark a section allocatable
>   and executable(AX). Newer binutils automatically mark a section AX if
>   the name starts with .text.
>
> o While defining a new section using assembler "section" directive,
>   explicitly mention section flags. 

As such this patch looks fine, and is certainly harmless.  But don't we
also need to address the issue that .text.head is not listed in the
linker script?

i.e.  Don't we also need?

  .text : AT(ADDR(.text) - LOAD_OFFSET) {
  	_text = .;			/* Text and read-only data */
+	*(.text.head)
	*(.text)
	SCHED_TEXT
	LOCK_TEXT
	KPROBES_TEXT
	*(.fixup)
	*(.gnu.warning)
  	_etext = .;			/* End of text section */
  } :text = 0x9090


I'm not even certain how the i386 kernel links properly without the above.

Eric

  reply	other threads:[~2007-01-03  6:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-03  4:16 Vivek Goyal
2007-01-03  6:44 ` Eric W. Biederman [this message]
2007-01-03  6:55   ` Vivek Goyal
2007-01-03  7:50     ` Eric W. Biederman
2007-01-03 13:53 ` Adrian Bunk
2007-01-03 14:18   ` Vivek Goyal
2007-01-03 15:02     ` Segher Boessenkool
2007-01-03 14:18   ` Jean Delvare

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=m1tzz8k3sd.fsf@ebiederm.dsl.xmission.com \
    --to=ebiederm@xmission.com \
    --cc=ak@muc.de \
    --cc=akpm@osdl.org \
    --cc=bunk@stusta.de \
    --cc=fastboot@lists.osdl.org \
    --cc=khali@linux-fr.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=segher@kernel.crashing.org \
    --cc=torvalds@osdl.org \
    --cc=vgoyal@in.ibm.com \
    /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

Powered by JetHome