public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [RFC] [PATCH] 2.5.44 bootloader fix
Date: 26 Oct 2002 13:46:42 -0700	[thread overview]
Message-ID: <apeuvi$t5k$1@cesium.transmeta.com> (raw)
In-Reply-To: m1pttxlebr.fsf@frodo.biederman.org

Followup to:  <m1pttxlebr.fsf@frodo.biederman.org>
By author:    ebiederm@xmission.com (Eric W. Biederman)
In newsgroup: linux.dev.kernel
> 
> What I am proposing is an interface change.  The only known bootloader
> this does not fix is gujin and the fix of loading segments earlier is
> trivial, and fully backwards compatible.  The advantage of this patch
> is that no future changes to the kernel's gdt will affect bootloaders.
> 

Please detail how the interface changes.  It is not at all clear from
the code.

> @@ -101,7 +96,8 @@
>  	popl %eax	# hcount
>  	movl $0x100000,%edi
>  	cli		# make sure we don't get interrupted
> -	ljmp $(__KERNEL_CS), $0x1000 # and jump to the move routine
> +	movl $0x1000, %ebp
> +	jmpl *%ebp	# and jump to the move routine
>  
>  /*
>   * Routine (template) for moving the decompressed kernel in place,

Why are you avoiding to set __SETUP_CS here?

	-hpa
-- 
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt	<amsp@zytor.com>

  reply	other threads:[~2002-10-26 20:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-26  9:49 [RFC] [PATCH] 2.5.44 bootloader fix Eric W. Biederman
2002-10-26 20:46 ` H. Peter Anvin [this message]
2002-10-28 16:55   ` Eric W. Biederman

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='apeuvi$t5k$1@cesium.transmeta.com' \
    --to=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.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