mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: Martin Mares <mj@ucw.cz>, kernel list <linux-kernel@vger.kernel.org>
Subject: Re: suspend-to-ram: don't crash when kernel gets big
Date: Mon, 25 Nov 2002 00:39:54 +0100	[thread overview]
Message-ID: <20021124233954.GA6579@atrey.karlin.mff.cuni.cz> (raw)
In-Reply-To: <Pine.LNX.4.33L2.0211241535050.21261-100000@dragon.pdx.osdl.net>


Hi!

> | > > +	pushl	$0			# Kill any dangerous flags
> | > > +	popfl
> | > > +	cli
> | > > +	cld
> | >
> | > Seems like you're trying to be 200% sure ;-)
> |
> | I was not sure if cli really *clears* it as name implies :-).
> 
> Yes, as Martin suggested.  8;)

Actually, as following proves, I wanted to be *300%* sure ;-).

        cli
        cld

# We are now probably running at something like 0x0000 : 0x1000
        call here
here:
        pop      %bx
        subw    $(here-wakeup_start), %bx
        shrw    $4, %bx

        # setup data segment
        movw    %cs, %ax
        addw    %bx, %ax
        movw    %ax, %ds                                        # Make
ds:0 point to wakeup_start
        movw    %ax, %ss
        mov     $(wakeup_stack-wakeup_code), %sp                #
Private stack is needed for ASUS board
        movw    $0x0e00 + 'S', %fs:(0x12)

        pushl   $0                                              # Kill
any dangerous flags
        popfl
        cli
        cld

Fixed now. [Not that it matters.]
							Pavel
-- 
Casualities in World Trade Center: ~3k dead inside the building,
cryptography in U.S.A. and free speech in Czech Republic.

      reply	other threads:[~2002-11-24 23:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-23 19:55 Pavel Machek
2002-11-24 22:49 ` Martin Mares
2002-11-24 22:51   ` Pavel Machek
2002-11-24 23:35     ` Randy.Dunlap
2002-11-24 23:39       ` Pavel Machek [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=20021124233954.GA6579@atrey.karlin.mff.cuni.cz \
    --to=pavel@ucw.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mj@ucw.cz \
    --cc=rddunlap@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 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®