From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756219AbXJaBK0 (ORCPT ); Tue, 30 Oct 2007 21:10:26 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752486AbXJaBKP (ORCPT ); Tue, 30 Oct 2007 21:10:15 -0400 Received: from gw.goop.org ([64.81.55.164]:55630 "EHLO mail.goop.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753395AbXJaBKM (ORCPT ); Tue, 30 Oct 2007 21:10:12 -0400 Message-ID: <4727D5F2.6000402@goop.org> Date: Tue, 30 Oct 2007 18:10:10 -0700 From: Jeremy Fitzhardinge User-Agent: Thunderbird 2.0.0.5 (X11/20070727) MIME-Version: 1.0 To: Rusty Russell CC: "Eric W. Biederman" , Ingo Molnar , Thomas Gleixner , "H. Peter Anvin" , 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: <200710311149.23006.rusty@rustcorp.com.au> In-Reply-To: <200710311149.23006.rusty@rustcorp.com.au> X-Enigmail-Version: 0.95.4 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Rusty Russell wrote: > On Saturday 27 October 2007 03:29:04 Eric W. Biederman wrote: > >> The kernel only ever supports 1 version of the boot protocol >> so there is no need to check the boot protocol revision to >> see if a feature is supported. >> > > OK, I'm completely confused, so this is probably a v. dumb question. Doesn't > this boot header come from the boot loader? No, other way around. It the kernel telling the bootloader "I understand boot protocol X", and the bootloader makes sure it doesn't fill out more than X allows. If the bootloader supports