From: Coywolf Qi Hunt <coywolf@greatcn.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Coywolf Qi Hunt <coywolf@greatcn.org>,
Linux-Kernel@vger.kernel.org, tao@acc.umu.se,
Riley@Williams.Name, davej@codemonkey.org.uk,
alan@lxorguk.ukuu.org.uk, root@chaos.analogic.com,
torvalds@osdl.org
Subject: Re: [2.0.40 2.2.25 2.4.25] Fix boot GDT limit 0x800 to 0x7ff in setup.S or not
Date: Mon, 23 Feb 2004 13:30:58 +0800 [thread overview]
Message-ID: <40399012.1050205@greatcn.org> (raw)
In-Reply-To: <4036DA90.2030709@zytor.com>
[-- Attachment #1: Type: text/plain, Size: 318 bytes --]
H. Peter Anvin wrote:
> Coywolf Qi Hunt wrote:
>
>>
>> Please fix 0x8000 to 0x800 in 2.4, and 0x800 to 0x7ff in 2.0~2.4, ok?
>> This is my last appeal.
>>
>
> Submit a patch.
>
> -hpa
(A patch enclosed for fix 0x800 to 0x7ff for 2.4.25)
--
Coywolf Qi Hunt
Admin of http://GreatCN.org and http://LoveCN.org
[-- Attachment #2: patch-cy0402231 --]
[-- Type: text/plain, Size: 367 bytes --]
--- arch/i386/boot/setup.S.orig 2003-11-29 02:26:20.000000000 +0800
+++ arch/i386/boot/setup.S 2004-02-23 01:15:42.000000000 +0800
@@ -1093,7 +1093,7 @@
.word 0 # idt limit = 0
.word 0, 0 # idt base = 0L
gdt_48:
- .word 0x8000 # gdt limit=2048,
+ .word 0x7ff # gdt limit=2047,
# 256 GDT entries
.word 0, 0 # gdt base (filled in later)
next prev parent reply other threads:[~2004-02-23 5:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-16 19:07 [PATCH 2.4.24] Fix GDT limit in setup.S Coywolf Qi Hunt
2004-02-16 20:44 ` Richard B. Johnson
2004-02-19 0:54 ` Coywolf Qi Hunt
2004-02-19 1:18 ` Coywolf Qi Hunt
2004-02-19 8:33 ` { Linux not only practical, but an ideal. } " Coywolf Qi Hunt
2004-02-17 3:51 ` [2.0.40 2.2.25 2.4.25] Fix boot GDT limit 0x800 to 0x7ff in setup.S or not Coywolf Qi Hunt
2004-02-21 3:39 ` Coywolf Qi Hunt
2004-02-21 4:12 ` H. Peter Anvin
2004-02-23 5:30 ` Coywolf Qi Hunt [this message]
2004-02-23 14:02 ` [PATCH] Fix GDT limit in setup.S for 2.0 and 2.2 Coywolf Qi Hunt
2004-02-23 14:21 ` David Weinehall
2004-02-25 0:10 ` Pavel Machek
2004-02-23 14:43 ` Richard B. Johnson
2004-02-23 15:28 ` Richard B. Johnson
2004-02-23 16:21 ` Richard B. Johnson
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=40399012.1050205@greatcn.org \
--to=coywolf@greatcn.org \
--cc=Linux-Kernel@vger.kernel.org \
--cc=Riley@Williams.Name \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davej@codemonkey.org.uk \
--cc=hpa@zytor.com \
--cc=root@chaos.analogic.com \
--cc=tao@acc.umu.se \
--cc=torvalds@osdl.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 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.