mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Willy Tarreau <willy@w.ods.org>
To: Daniel Bonekeeper <thehazard@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel loading question
Date: Sat, 3 Dec 2005 10:06:32 +0100	[thread overview]
Message-ID: <20051203090632.GC22139@alpha.home.local> (raw)
In-Reply-To: <e1e1d5f40512022134y73318ed4p54064a07905cef3c@mail.gmail.com>

On Fri, Dec 02, 2005 at 09:34:26PM -0800, Daniel Bonekeeper wrote:
> Well, this probably should not be posted here, but who knows ? =)
> 
> Well, on arch/i386/boot/compressed/head.S line 65 we call
> decompress_kernel that decompresses the kernel starting at $0x100000.
> If we were loaded high, we first move the code back to $0x1000 before
> ljmp'ing it.
> 
> My question is: why, when loaded high, we care to disable interrupts
> (cli  # make sure we don't get interrupted) while otherwise, we don't
> do that ? in both cases, aren't we supposed to disable cli (as they
> can happen in both situations) ?
> 
> Since currently, the kernel boots fine for everybody in the world, I
> know that this is not a bug... but why don't disable interruptions on
> both cases ?

Agreed it's strange. I believe that since very few people load the
kernel in low memory nowadays given its size, it's possible that the
missing CLI never gets noticed, and I suspect that the very first
instructions after the jump are a CLI anyway.

Regards,
Willy


  reply	other threads:[~2005-12-03  9:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-03  5:34 Daniel Bonekeeper
2005-12-03  9:06 ` Willy Tarreau [this message]
2005-12-05 14:18 ` linux-os (Dick Johnson)
2005-12-05 15:54   ` linux-os (Dick 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=20051203090632.GC22139@alpha.home.local \
    --to=willy@w.ods.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thehazard@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®