From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756016Ab2GATXP (ORCPT ); Sun, 1 Jul 2012 15:23:15 -0400 Received: from terminus.zytor.com ([198.137.202.10]:46861 "EHLO mail.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751176Ab2GATXP (ORCPT ); Sun, 1 Jul 2012 15:23:15 -0400 Message-ID: <4FF0A399.8070207@zytor.com> Date: Sun, 01 Jul 2012 12:23:05 -0700 From: "H. Peter Anvin" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120605 Thunderbird/13.0 MIME-Version: 1.0 To: "Eric W. Biederman" CC: Tejun Heo , hacklu , linux-kernel@vger.kernel.org Subject: Re: [PATCH 2/2] x86, boot: Optimize the elf header handling. References: <4FB492F7.8050401@gmail.com> <87ipf9gtsb.fsf@xmission.com> <4FCAD590.8000506@zytor.com> <87obp0bxdv.fsf@xmission.com> <4FCB602B.70907@zytor.com> <87fwacb0jq.fsf_-_@xmission.com> <877gvob0g4.fsf_-_@xmission.com> <4FF06701.6010004@zytor.com> <4FF06DF4.4000006@zytor.com> <87wr2nsbvi.fsf@xmission.com> <4FF0769F.8090105@zytor.com> <87sjdbsb0v.fsf@xmission.com> <4FF07E66.2020706@zytor.com> <87d34fs914.fsf@xmission.com> <4FF085B1.6070604@zytor.com> <87a9zj9w43.fsf@xmission.com> <4FF098E2.3040307@zytor.com> <87sjdb8f0m.fsf@xmission.com> In-Reply-To: <87sjdb8f0m.fsf@xmission.com> X-Enigmail-Version: 1.4.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 07/01/2012 12:20 PM, Eric W. Biederman wrote: > > Grumble Grumble. > > If I force a 2M alignment, poffsets and paddrs align and my previous > patches work. Although I don't expect that to be more than a testing > hack. > > Meanwhile if I force a 4K max page size for most purposes things look > better from a file offset perspective. But the data segment is now less > aligned in the file than it is in memory and my patches don't work. > > Sigh. > > I feel like I have stumbled into pandoras box. > Last I looked at this we didn't actually have a general PHDR parser... are you running into its limitations? -hpa