Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756618Ab1BCRT6 (ORCPT ); Thu, 3 Feb 2011 12:19:58 -0500 Received: from terminus.zytor.com ([198.137.202.10]:34074 "EHLO mail.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756584Ab1BCRT5 (ORCPT ); Thu, 3 Feb 2011 12:19:57 -0500 Message-ID: <4D4AE3AE.7000009@zytor.com> Date: Thu, 03 Feb 2011 09:19:42 -0800 From: "H. Peter Anvin" User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101209 Fedora/3.1.7-0.35.b3pre.fc14 Thunderbird/3.1.7 MIME-Version: 1.0 To: Linux Kernel Mailing List CC: Ingo Molnar , Thomas Gleixner , Jeremy Fitzhardinge , "Pan, Jacob jun" , Rusty Russell , Andres Salomon Subject: RFC: can we kill the KEEP_SEGMENTS bzImage flag? Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 880 Lines: 22 > Bit 6 (write): KEEP_SEGMENTS > Protocol: 2.07+ > - If 0, reload the segment registers in the 32bit entry point. > - If 1, do not reload the segment registers in the 32bit entry point. > Assume that %cs %ds %ss %es are all set to flat segments with > a base of 0 (or the equivalent for their environment). Does anything actually rely on this bit or can we kill it? I think it was added as a crutch for paravirtualization, but I'm being told it is not used... -hpa -- H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak on their behalf. -- 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/