From: "H. Peter Anvin" <hpa@zytor.com>
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>
Subject: Re: x86_64 allyesconfig has screwed up voffset and blows up KVM
Date: Mon, 05 May 2014 13:31:11 -0700 [thread overview]
Message-ID: <5367F50F.8080909@zytor.com> (raw)
In-Reply-To: <CALCETrX+J643i-YPjATo-u6O+_MgZm_v9x-VBp5WmFm-1g0Twg@mail.gmail.com>
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
prev parent reply other threads:[~2014-05-05 20:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-05 18:41 x86_64 allyesconfig has screwed up voffset and blows up KVM Andy Lutomirski
2014-05-05 20:31 ` H. Peter Anvin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5367F50F.8080909@zytor.com \
--to=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox