Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261785AbTELAz0 (ORCPT ); Sun, 11 May 2003 20:55:26 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261788AbTELAz0 (ORCPT ); Sun, 11 May 2003 20:55:26 -0400 Received: from neon-gw-l3.transmeta.com ([63.209.4.196]:16914 "EHLO neon-gw.transmeta.com") by vger.kernel.org with ESMTP id S261785AbTELAzV (ORCPT ); Sun, 11 May 2003 20:55:21 -0400 To: linux-kernel@vger.kernel.org From: "H. Peter Anvin" Subject: Re: [PATCH] Use correct x86 reboot vector Date: 11 May 2003 18:07:54 -0700 Organization: Transmeta Corporation, Santa Clara CA Message-ID: References: <20030511190023.GC9173@waste.org> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT Disclaimer: Not speaking for Transmeta in any way, shape, or form. Copyright: Copyright 2003 H. Peter Anvin - All Rights Reserved Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 998 Lines: 24 Followup to: <20030511190023.GC9173@waste.org> By author: Matt Mackall In newsgroup: linux.dev.kernel > > There's a missing piece of behavior here that's probably fatal. > Namely, the next time the CS descriptor is loaded, even with the same > value, the high bits are lost. So, for example, if you're running BIOS > out of ROM, decompressing it into the top of 20-bit address space, > then long jumping to your uncompressed code, you don't want to find > yourself back in ROM. > Nope, that's *exactly* the desired behaviour. -hpa -- at work, in private! "Unix gives you enough rope to shoot yourself in the foot." Architectures needed: ia64 m68k mips64 ppc ppc64 s390 s390x sh v850 x86-64 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/