From: "H. Peter Anvin" <hpa@zytor.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: mingo@redhat.com, linux-kernel@vger.kernel.org,
tglx@linutronix.de, akinobu.mita@gmail.com,
linux-tip-commits@vger.kernel.org
Subject: Re: [tip:x86/asm] x86: Introduce GDT_ENTRY_INIT()
Date: Sun, 02 Aug 2009 23:27:05 -0700 [thread overview]
Message-ID: <4A768339.9060904@zytor.com> (raw)
In-Reply-To: <20090803062024.GA22365@elte.hu>
Ingo Molnar wrote:
> * tip-bot for Akinobu Mita <akinobu.mita@gmail.com> wrote:
>
>> Commit-ID: d520da1173abd1f918b7e690220e14ba0fc56cfc
>> Gitweb: http://git.kernel.org/tip/d520da1173abd1f918b7e690220e14ba0fc56cfc
>> Author: Akinobu Mita <akinobu.mita@gmail.com>
>> AuthorDate: Sun, 19 Jul 2009 00:12:20 +0900
>> Committer: Ingo Molnar <mingo@elte.hu>
>> CommitDate: Sun, 19 Jul 2009 18:27:53 +0200
>>
>> x86: Introduce GDT_ENTRY_INIT()
>>
>> GDT_ENTRY_INIT is static initializer of desc_struct.
>>
>> We already have similar macro GDT_ENTRY() but it's static
>> initializer for u64 and it cannot be used for desc_struct.
>>
>> Signed-off-by: Akinobu Mita <akinobu.mita@gmail.com>
>> LKML-Reference: <20090718151219.GD11294@localhost.localdomain>
>> Signed-off-by: Ingo Molnar <mingo@elte.hu>
>>
OK, I spotted the following error, which certainly would explain a crash
on an APM machine:
/* data */
- [GDT_ENTRY_APMBIOS_BASE+2] = { { { 0x0000ffff, 0x00409200 } } },
+ [GDT_ENTRY_APMBIOS_BASE+2] = GDT_ENTRY_INIT(0x409a, 0, 0xffff),
Also, we shouldn't be initializing the A bits to clear unless we
actually plan to check the A (and D) bits... that's just a waste of CPU
cycles.
-hpa
-hpa
next prev parent reply other threads:[~2009-08-03 6:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-18 15:08 [PATCH 1/4] x86: use get_desc_base() Akinobu Mita
2009-07-18 15:09 ` [PATCH 2/4] x86: remove unused patch_espfix_desc() Akinobu Mita
2009-07-20 12:01 ` [tip:x86/asm] x86: Remove " tip-bot for Akinobu Mita
2009-07-18 15:11 ` [PATCH 3/4] x86: introduce set_desc_base() and set_desc_limit() Akinobu Mita
2009-07-20 12:01 ` [tip:x86/asm] x86: Introduce " tip-bot for Akinobu Mita
2009-07-18 15:12 ` [PATCH 4/4] x86: introduce GDT_ENTRY_INIT() Akinobu Mita
2009-07-20 12:01 ` [tip:x86/asm] x86: Introduce GDT_ENTRY_INIT() tip-bot for Akinobu Mita
2009-08-03 6:20 ` Ingo Molnar
2009-08-03 6:27 ` H. Peter Anvin [this message]
2009-08-03 15:11 ` Akinobu Mita
2009-08-03 15:17 ` H. Peter Anvin
2009-08-04 12:18 ` Ingo Molnar
2009-08-08 15:48 ` tip-bot for Akinobu Mita
2009-07-20 12:01 ` [tip:x86/asm] x86: Use get_desc_base() tip-bot for Akinobu Mita
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=4A768339.9060904@zytor.com \
--to=hpa@zytor.com \
--cc=akinobu.mita@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
/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