From mboxrd@z Thu Jan  1 00:00:00 1970
From: "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: x86_64 allyesconfig has screwed up voffset and blows up KVM
Date: Mon, 05 May 2014 13:31:11 -0700
Message-ID: <5367F50F.8080909@zytor.com>
References: <CALCETrX+J643i-YPjATo-u6O+_MgZm_v9x-VBp5WmFm-1g0Twg@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
To: Andy Lutomirski <luto@amacapital.net>, X86 ML <x86@kernel.org>,
	kvm list <kvm@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Return-path: <linux-kernel-owner@vger.kernel.org>
In-Reply-To: <CALCETrX+J643i-YPjATo-u6O+_MgZm_v9x-VBp5WmFm-1g0Twg@mail.gmail.com>
Sender: linux-kernel-owner@vger.kernel.org
List-Id: kvm.vger.kernel.org

On 05/05/2014 11:41 AM, Andy Lutomirski wrote:
> I'm testing 39bfe90706ab0f588db7cb4d1c0e6d1181e1d2f9.  I'm not sure
> what's going on here.
> 
> voffset.h contains:
> 
> #define VO__end 0xffffffff8111c7a0
> #define VO__end 0xffffffff8db9a000
> #define VO__text 0xffffffff81000000
> 
> because
> 
> $ nm vmlinux|grep ' _end'
> ffffffff8111c7a0 t _end
> ffffffff8db9a000 B _end
> 

The "t _end" implies there is a local symbol _end which I guess the
scripts are incorrectly picking up.  Taking a look now.

	-hpa