All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Jeremy Fitzhardinge <jeremy@xensource.com>,
	Rusty Russell <rusty@rustcorp.com.au>,
	Vivek Goyal <vgoyal@in.ibm.com>,
	James Bottomley <James.Bottomley@HansenPartnership.com>,
	Zachary Amsden <zach@vmware.com>, Andi Kleen <ak@suse.de>,
	linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] x86: Fix boot protocol KEEP_SEGMENTS check.
Date: Fri, 26 Oct 2007 11:52:05 -0700	[thread overview]
Message-ID: <47223755.4030707@goop.org> (raw)
In-Reply-To: <m1r6jh3hun.fsf@ebiederm.dsl.xmission.com>

Eric W. Biederman wrote:
> The kernel only ever supports 1 version of the boot protocol
> so there is no need to check the boot protocol revision to
> see if a feature is supported.
>
> Both x86 and x86_64 support the same boot protocol so we need
> to implement the KEEP_SEGMENTS on x86_64 as well.  It isn't
> just paravirt bootloaders that could use this functionality.
>   

Ack.  I was planning on sending this patch out today...

    J
> Signed-off-by: Eric W. Biederman <ebiederm@xmission.com>
> Cc: Jeremy Fitzhardinge <jeremy@xensource.com>
> Cc: Rusty Russell <rusty@rustcorp.com.au>
> Cc: H. Peter Anvin <hpa@zytor.com>
> Cc: Vivek Goyal <vgoyal@in.ibm.com>
> Cc: James Bottomley <James.Bottomley@HansenPartnership.com>
> Cc: Zachary Amsden <zach@vmware.com>
> Cc: Andi Kleen <ak@suse.de>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: Ingo Molnar <mingo@elte.hu>
> ---
>  arch/x86/boot/compressed/head_32.S |   12 ++++--------
>  arch/x86/boot/compressed/head_64.S |    7 +++++++
>  arch/x86/kernel/asm-offsets_64.c   |   10 ++++++++++
>  3 files changed, 21 insertions(+), 8 deletions(-)
>
> diff --git a/arch/x86/boot/compressed/head_32.S b/arch/x86/boot/compressed/head_32.S
> index a0ae2e7..036e635 100644
> --- a/arch/x86/boot/compressed/head_32.S
> +++ b/arch/x86/boot/compressed/head_32.S
> @@ -33,24 +33,20 @@
>  	.globl startup_32
>  
>  startup_32:
> -	/* check to see if KEEP_SEGMENTS flag is meaningful */
> -	cmpw $0x207, BP_version(%esi)
> -	jb 1f
> -
> +	cld
>  	/* test KEEP_SEGMENTS flag to see if the bootloader is asking
>  	 * us to not reload segments */
>  	testb $(1<<6), BP_loadflags(%esi)
> -	jnz 2f
> +	jnz 1f
>  
> -1:	cli
> +	cli
>  	movl $(__BOOT_DS),%eax
>  	movl %eax,%ds
>  	movl %eax,%es
>  	movl %eax,%fs
>  	movl %eax,%gs
>  	movl %eax,%ss
> -
> -2:	cld
> +1:
>  
>  /* Calculate the delta between where we were compiled to run
>   * at and where we were actually loaded at.  This can only be done
> diff --git a/arch/x86/boot/compressed/head_64.S b/arch/x86/boot/compressed/head_64.S
> index 4946764..1ccb38a 100644
> --- a/arch/x86/boot/compressed/head_64.S
> +++ b/arch/x86/boot/compressed/head_64.S
> @@ -29,6 +29,7 @@
>  #include <asm/pgtable.h>
>  #include <asm/page.h>
>  #include <asm/msr.h>
> +#include <asm/asm-offsets.h>
>  
>  .section ".text.head"
>  	.code32
> @@ -36,11 +37,17 @@
>  
>  startup_32:
>  	cld
> +	/* test KEEP_SEGMENTS flag to see if the bootloader is asking
> +	 * us to not reload segments */
> +	testb $(1<<6), BP_loadflags(%esi)
> +	jnz 1f
> +
>  	cli
>  	movl	$(__KERNEL_DS), %eax
>  	movl	%eax, %ds
>  	movl	%eax, %es
>  	movl	%eax, %ss
> +1:
>  
>  /* Calculate the delta between where we were compiled to run
>   * at and where we were actually loaded at.  This can only be done
> diff --git a/arch/x86/kernel/asm-offsets_64.c b/arch/x86/kernel/asm-offsets_64.c
> index 7e50bda..d1b6ed9 100644
> --- a/arch/x86/kernel/asm-offsets_64.c
> +++ b/arch/x86/kernel/asm-offsets_64.c
> @@ -15,12 +15,16 @@
>  #include <asm/segment.h>
>  #include <asm/thread_info.h>
>  #include <asm/ia32.h>
> +#include <asm/bootparam.h>
>  
>  #define DEFINE(sym, val) \
>          asm volatile("\n->" #sym " %0 " #val : : "i" (val))
>  
>  #define BLANK() asm volatile("\n->" : : )
>  
> +#define OFFSET(sym, str, mem) \
> +	DEFINE(sym, offsetof(struct str, mem))
> +
>  #define __NO_STUBS 1
>  #undef __SYSCALL
>  #undef _ASM_X86_64_UNISTD_H_
> @@ -109,5 +113,11 @@ int main(void)
>  	DEFINE(crypto_tfm_ctx_offset, offsetof(struct crypto_tfm, __crt_ctx));
>  	BLANK();
>  	DEFINE(__NR_syscall_max, sizeof(syscalls) - 1);
> +
> +	BLANK();
> +	OFFSET(BP_scratch, boot_params, scratch);
> +	OFFSET(BP_loadflags, boot_params, hdr.loadflags);
> +	OFFSET(BP_hardware_subarch, boot_params, hdr.hardware_subarch);
> +	OFFSET(BP_version, boot_params, hdr.version);
>  	return 0;
>  }
>   


  parent reply	other threads:[~2007-10-26 18:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-26 17:29 [PATCH] x86: Fix boot protocol KEEP_SEGMENTS check Eric W. Biederman
2007-10-26 17:59 ` H. Peter Anvin
2007-10-26 18:22   ` Eric W. Biederman
2007-10-26 18:52 ` Jeremy Fitzhardinge [this message]
2007-10-26 19:40 ` H. Peter Anvin
2007-10-31  0:49 ` Rusty Russell
2007-10-31  1:10   ` Jeremy Fitzhardinge

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=47223755.4030707@goop.org \
    --to=jeremy@goop.org \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=ebiederm@xmission.com \
    --cc=hpa@zytor.com \
    --cc=jeremy@xensource.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rusty@rustcorp.com.au \
    --cc=tglx@linutronix.de \
    --cc=vgoyal@in.ibm.com \
    --cc=zach@vmware.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 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.