From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1763351AbXJZSAz (ORCPT ); Fri, 26 Oct 2007 14:00:55 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755824AbXJZSAe (ORCPT ); Fri, 26 Oct 2007 14:00:34 -0400 Received: from terminus.zytor.com ([198.137.202.10]:37659 "EHLO terminus.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754970AbXJZSAb (ORCPT ); Fri, 26 Oct 2007 14:00:31 -0400 Message-ID: <47222AFA.9030902@zytor.com> Date: Fri, 26 Oct 2007 10:59:22 -0700 From: "H. Peter Anvin" User-Agent: Thunderbird 2.0.0.5 (X11/20070727) MIME-Version: 1.0 To: "Eric W. Biederman" CC: Ingo Molnar , Thomas Gleixner , Jeremy Fitzhardinge , Rusty Russell , Vivek Goyal , James Bottomley , Zachary Amsden , Andi Kleen , linux-kernel@vger.kernel.org, Andrew Morton Subject: Re: [PATCH] x86: Fix boot protocol KEEP_SEGMENTS check. References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Eric W. Biederman wrote: > > Both x86 and x86_64 support the same boot protocol so we need > to implement the KEEP_SEGMENTS on x86_64 as well. It isn't > just paravirt bootloaders that could use this functionality. > Out of curiousity, what other users do you see? -hpa