From: Ross Lagerwall <ross.lagerwall@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
Julien Grall <julien.grall@arm.com>,
Xen Devel <xen-devel@lists.xen.org>
Subject: Re: xen/x86: efi: warning value truncated
Date: Tue, 14 Jun 2016 11:15:33 +0100 [thread overview]
Message-ID: <575FD945.1030508@citrix.com> (raw)
In-Reply-To: <575FE96102000078000F4AD0@prv-mh.provo.novell.com>
On 06/14/2016 10:24 AM, Jan Beulich wrote:
>>>> On 13.06.16 at 19:13, <julien.grall@arm.com> wrote:
>> I noticed the warnings below when building Xen x86
>> with Livepatch enabled.
>
> I did notice some of these too (not as many though, iirc), but I
> didn't get around yet to check what exactly is causing them. Since
> they're in the symbol table files only, I didn't consider them too
> concerning (at worst some odd symbol won't be found or be
> associated with the wrong address).
>
On my build, they are:
multiboot1_header_start|000000000000051e| ? |
multiboot1_header_start|00000000000008a1| ? |
multiboot1_header_start|00000000000008a3| ? |
multiboot1_header_start|00000000000008a8| ? |
multiboot1_header_start|000000000000102f| ? |
multiboot1_header_start|0000000000001033| ? |
multiboot1_header_start|0000000000001037| ? |
__init_end |ffff82d180650000| D |
None of these look particularly important to me.
--
Ross Lagerwall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-06-14 10:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-13 17:13 xen/x86: efi: warning value truncated Julien Grall
2016-06-14 9:24 ` Jan Beulich
2016-06-14 10:15 ` Ross Lagerwall [this message]
2016-06-14 10:50 ` Jan Beulich
2016-06-14 11:19 ` Ross Lagerwall
2016-06-14 12:36 ` Jan Beulich
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=575FD945.1030508@citrix.com \
--to=ross.lagerwall@citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=julien.grall@arm.com \
--cc=xen-devel@lists.xen.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;
as well as URLs for NNTP newsgroup(s).