From: ebiederm@xmission.com (Eric W. Biederman)
To: "Yinghai Lu" <yhlu.kernel@gmail.com>
Cc: "Andi Kleen" <ak@suse.de>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Vivek Goyal" <vgoyal@in.ibm.com>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH]x86_64: build and use GDT on copied compressed kernel
Date: Sun, 13 May 2007 00:48:53 -0600 [thread overview]
Message-ID: <m1abw9qkve.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <86802c440705122329y27c6ef92v8cff43d52b99ae69@mail.gmail.com> (Yinghai Lu's message of "Sat, 12 May 2007 23:29:23 -0700")
"Yinghai Lu" <yhlu.kernel@gmail.com> writes:
> On 5/12/07, Eric W. Biederman <ebiederm@xmission.com> wrote:
>> Overwriting the GDT should be fine because we don't reload the segments,
>> after we overwrite it. GDT entries are only read when we load segments.
>> Interrupts are disabled so that should not cause a problem.
>>
>> Why do you think the current behaviour is a problem?
>
> just think if GDT should not be overwriten when we are still under
> that GDT setting.
> didn't have chance to test that in HDT or other debug device, when
> setting breaking point after that GDT is overwriten.
It would be interesting to see if you could produce a failure using
that gdt, I don't think you will be able to, even with a debugger.
For data segments we never use that GDT, it is only for the code
segment we use the GDT and that only to get us into 64bit mode.
Eric
next prev parent reply other threads:[~2007-05-13 6:49 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-13 5:33 Yinghai Lu
2007-05-13 5:52 ` Andi Kleen
2007-05-13 6:41 ` Yinghai Lu
2007-05-13 6:09 ` Eric W. Biederman
2007-05-13 6:29 ` Yinghai Lu
2007-05-13 6:48 ` Eric W. Biederman [this message]
2007-05-13 6:55 ` Yinghai Lu
2007-05-13 7:06 ` Eric W. Biederman
2007-05-13 7:27 ` Yinghai Lu
2007-05-13 18:01 ` Yinghai Lu
2007-05-13 19:49 ` Eric W. Biederman
2007-05-13 21:06 ` Yinghai Lu
2007-05-13 21:23 ` Eric W. Biederman
2007-05-14 17:26 ` [PATCH] serial: set RTS and DTR if flow is 'r' Yinghai Lu
2007-05-14 17:54 ` Randy Dunlap
2007-05-14 17:57 ` [PATCH] serial: set RTS and DTR if flow is 'r' --- resend Yinghai Lu
2007-05-14 18:10 ` Russell King
2007-05-14 19:04 ` Yinghai Lu
2007-05-14 19:19 ` Russell King
2007-05-14 19:46 ` Yinghai Lu
2007-05-14 19:50 ` Russell King
2007-05-14 20:04 ` Yinghai Lu
2007-05-15 20:48 ` [PATCH] serial: set DTR in uart for kernel serial console Yinghai Lu
2007-05-22 19:31 ` PATCH] serial: convert early_uart to earlycon for 8250 Yinghai Lu
2007-05-28 10:51 ` Russell King
2007-05-28 17:50 ` Yinghai Lu
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=m1abw9qkve.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vgoyal@in.ibm.com \
--cc=yhlu.kernel@gmail.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
all inboxes | Powered by JetHome®