From: Andi Kleen <ak@suse.de>
To: Magnus Damm <magnus@valinux.co.jp>
Cc: fastboot@lists.osdl.org, linux-kernel@vger.kernel.org,
ebiederm@xmission.com
Subject: Re: [PATCH][RFC] x86_64: Reload CS when startup_64 is used.
Date: Mon, 21 Aug 2006 12:19:09 +0200 [thread overview]
Message-ID: <200608211219.09042.ak@suse.de> (raw)
In-Reply-To: <20060821095328.3132.40575.sendpatchset@cherry.local>
>
> + /* Reload CS with a value that is within our GDT. We need to do this
> + * if we were loaded by a 64 bit bootloader that happened to use a
> + * CS that is larger than the GDT limit. This is true if we came here
> + * from kexec running under Xen.
> + */
> + movq %rsp, %rdx
> + movq $__KERNEL_DS, %rax
> + pushq %rax /* SS */
> + pushq %rdx /* RSP */
> + movq $__KERNEL_CS, %rax
> + movq $cs_reloaded, %rdx
> + pushq %rax /* CS */
> + pushq %rdx /* RIP */
> + lretq
Can't you just use a normal far jump? That might be simpler.
-Andi
next prev parent reply other threads:[~2006-08-21 10:19 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-21 9:54 [PATCH][RFC] x86_64: Reload CS when startup_64 is used Magnus Damm
2006-08-21 10:19 ` Andi Kleen [this message]
2006-08-21 13:29 ` [Fastboot] " Magnus Damm
2006-08-21 14:16 ` Andi Kleen
2006-08-22 0:47 ` Magnus Damm
2006-08-21 14:17 ` Vivek Goyal
2006-08-21 14:24 ` Andi Kleen
2006-08-21 14:46 ` Vivek Goyal
2006-08-21 15:04 ` Andi Kleen
2006-08-21 20:02 ` Eric W. Biederman
2006-08-21 20:10 ` Andi Kleen
2006-08-21 21:00 ` Eric W. Biederman
2006-08-21 21:02 ` Eric W. Biederman
2006-08-22 0:58 ` Magnus Damm
2006-08-22 3:41 ` Eric W. Biederman
2006-08-22 4:10 ` Magnus Damm
2006-08-22 8:03 ` Andi Kleen
2006-08-22 8:37 ` [PATCH] " Eric W. Biederman
2006-08-22 8:53 ` [Fastboot] " Magnus Damm
2006-08-22 9:25 ` Eric W. Biederman
2006-08-23 3:10 ` Magnus Damm
2006-08-22 9:01 ` Andi Kleen
2006-08-22 9:20 ` 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=200608211219.09042.ak@suse.de \
--to=ak@suse.de \
--cc=ebiederm@xmission.com \
--cc=fastboot@lists.osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=magnus@valinux.co.jp \
/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