mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Mika Penttilä" <mika.penttila@kolumbus.fi>
To: Patrick Mochel <mochel@osdl.org>
Cc: Pavel Machek <pavel@ucw.cz>, kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [pm] Strange cleanups in -test8 kernel/acpi/wakeup.S
Date: Mon, 20 Oct 2003 23:34:27 +0300	[thread overview]
Message-ID: <3F9446D3.6060209@kolumbus.fi> (raw)
In-Reply-To: <Pine.LNX.4.44.0310201115270.13116-100000@cherise>



Patrick Mochel wrote:

>>Some more changes landed in -test8. I have not seen them
>>before. Patrick, please, if you change something, can you post patch
>>somewhere for review before merging with Linus?
>>    
>>
>
>Pavel, I wrote the code in the first place, before you littered your
>'debug hacks' throughout it. I have merely been trying to simplify it for 
>debugging on other processors that are known not to work. While I 
>understand your generic plea for review, I fail to see how it would help 
>with this assembly.. 
>
>  
>
>>bkcvs info is:
>>BitKeeper to RCS/CVS export
>>----------------------------
>>revision 1.5
>>date: 2003/10/08 22:55:45;  author: mochel;  state: Exp;  lines: +37
>>-89
>>[power] Clean up ACPI STR assembly.
>>    
>>
>
>It might help if you read the full changeset comments. 
>
>  
>
>>diff -Nru a/arch/i386/kernel/acpi/wakeup.S
>>b/arch/i386/kernel/acpi/wakeup.S
>>--- a/arch/i386/kernel/acpi/wakeup.S    Fri Oct 17 14:43:50 2003
>>+++ b/arch/i386/kernel/acpi/wakeup.S    Fri Oct 17 14:43:50 2003
>>@@ -172,14 +172,13 @@
>> .org   0x1000
>>
>> wakeup_pmode_return:
>>-       movl    $__KERNEL_DS, %eax
>>-       movl    %eax, %ds
>>-       movw    $0x0e00 + 'u', %ds:(0xb8016)
>>-
>>-       # restore other segment registers
>>-       xorl    %eax, %eax
>>+       movw    $__KERNEL_DS, %ax
>>+       movw    %ax, %ss
>>+       movw    %ax, %ds
>>+       movw    %ax, %es
>>        movw    %ax, %fs
>>        movw    %ax, %gs
>>+       movw    $0x0e00 + 'u', 0xb8016
>>
>>        # reload the gdt, as we need the full 32 bit address
>>        lgdt    saved_gdt
>>	~~~~~~~~~~~~~~~~~
>>
>>Notice lgdt here. You have moved setup of segment registers before
>>loading gdt. This is actually okay, if you can be sure that all such
>>registers are in gdt (and not in ldt, for example).
>>    
>>
>
>All segments are in the GDT, as we use the same GDT in real mode as we do 
>in protected mode. However, you must reload the GDT in protected mode 
>because the GDTR is only 24 bits in real mode, but 32 in protected mode. 
>
>  
>
To be exact, GDTR is always 48 bits in x86. Reloading it twice seems 
pretty pointless.

--Mika





      parent reply	other threads:[~2003-10-20 20:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-18 20:12 Pavel Machek
2003-10-20 18:26 ` Patrick Mochel
2003-10-20 19:31   ` Pavel Machek
2003-10-20 19:41     ` Patrick Mochel
2003-10-20 20:34   ` Mika Penttilä [this message]

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=3F9446D3.6060209@kolumbus.fi \
    --to=mika.penttila@kolumbus.fi \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mochel@osdl.org \
    --cc=pavel@ucw.cz \
    /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

Powered by JetHome