mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
* kernel loading question
@ 2005-12-03  5:34 Daniel Bonekeeper
  2005-12-03  9:06 ` Willy Tarreau
  2005-12-05 14:18 ` linux-os (Dick Johnson)
  0 siblings, 2 replies; 4+ messages in thread
From: Daniel Bonekeeper @ 2005-12-03  5:34 UTC (permalink / raw)
  To: linux-kernel

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 ?

Thanks !

--
# (perl -e "while (1) { print "\x90"; }") | dd of=/dev/evil

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2005-12-05 15:54 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2005-12-03  5:34 kernel loading question Daniel Bonekeeper
2005-12-03  9:06 ` Willy Tarreau
2005-12-05 14:18 ` linux-os (Dick Johnson)
2005-12-05 15:54   ` linux-os (Dick Johnson)

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®