* ELF .note BSD_SYMTAB
@ 2014-08-06 19:24 Ryan O'Neill
2014-08-06 19:31 ` Andrew Cooper
0 siblings, 1 reply; 3+ messages in thread
From: Ryan O'Neill @ 2014-08-06 19:24 UTC (permalink / raw)
To: xen-devel
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello. After reading through some of the libelf-loader.c and
libelf-dominfo.c code, it appears that Xen expects BSD guest kernels
to have an ELF .note auxillary entry of type XEN_ELFNOTE_BSD_SYMTAB
that gets parsed in so that Xen knows to allocate room for the kernels
symbol table. I do not see this Note (Or any note segment/section) in
my freebsd guest kernel image (readelf -n). Can someone explain to me
if this Note is still used? If so, then in what case?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBAgAGBQJT4oDeAAoJEBKyrGQNkDKcPpUIAL2KI7Y5LcJTnNk+q+C9jVjG
2wddVrMKAe7JHy/xMu01diC8gfAD3iprPYAN+AtUdBlHlKFPodM5JN6R1RONZNM7
dFegRuIYoFTelJNj58gdTTyQlZz616vomPq5ctayYl1JIilMibrNq/hlnZwFSSFx
PwBZYjxKRbCahfgfXLSEb6/N7cIOn9W1XK58WNpE4q7bczIkzCelgAfSRdTqOmla
jIXiIypiVkqj5fcC/GX1Ar26qfLEfQvLMXl/bFJrKyRTei71nYJrRe9U2v+8VG+y
iVu9qKWqW95qtbGcpL1wdaFmw36jY+uuuW/grQ8dpYtKNKKcVsOwVFOrDG+yEsk=
=FXiC
-----END PGP SIGNATURE-----
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: ELF .note BSD_SYMTAB
2014-08-06 19:24 ELF .note BSD_SYMTAB Ryan O'Neill
@ 2014-08-06 19:31 ` Andrew Cooper
2014-08-07 8:55 ` Egger, Christoph
0 siblings, 1 reply; 3+ messages in thread
From: Andrew Cooper @ 2014-08-06 19:31 UTC (permalink / raw)
To: xen-devel
[-- Attachment #1.1: Type: text/plain, Size: 765 bytes --]
On 06/08/2014 20:24, Ryan O'Neill wrote:
> Hello. After reading through some of the libelf-loader.c and
> libelf-dominfo.c code, it appears that Xen expects BSD guest kernels
> to have an ELF .note auxillary entry of type XEN_ELFNOTE_BSD_SYMTAB
> that gets parsed in so that Xen knows to allocate room for the kernels
> symbol table. I do not see this Note (Or any note segment/section) in
> my freebsd guest kernel image (readelf -n). Can someone explain to me
> if this Note is still used? If so, then in what case?
>
There is no expectation persay. Merely alternative actions taken if found.
I seem to recall (or I might be completely confused), it is a somewhat
legacy NetBSDism, so I would not be at all surprised if modern FreeBSD
doesn't use it.
~Andrew
[-- Attachment #1.2: Type: text/html, Size: 1148 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: ELF .note BSD_SYMTAB
2014-08-06 19:31 ` Andrew Cooper
@ 2014-08-07 8:55 ` Egger, Christoph
0 siblings, 0 replies; 3+ messages in thread
From: Egger, Christoph @ 2014-08-07 8:55 UTC (permalink / raw)
To: xen-devel
On 06.08.14 21:31, Andrew Cooper wrote:
> On 06/08/2014 20:24, Ryan O'Neill wrote:
>> Hello. After reading through some of the libelf-loader.c and
>> libelf-dominfo.c code, it appears that Xen expects BSD guest kernels
>> to have an ELF .note auxillary entry of type XEN_ELFNOTE_BSD_SYMTAB
>> that gets parsed in so that Xen knows to allocate room for the kernels
>> symbol table. I do not see this Note (Or any note segment/section) in
>> my freebsd guest kernel image (readelf -n). Can someone explain to me
>> if this Note is still used? If so, then in what case?
>>
>
> There is no expectation persay. Merely alternative actions taken if found.
>
> I seem to recall (or I might be completely confused), it is a somewhat
> legacy NetBSDism, so I would not be at all surprised if modern FreeBSD
> doesn't use it.
I recommend to add port-xen@netbsd.org to this thread to get NetBSD
people in.
Christoph
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2014-08-07 8:55 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-08-06 19:24 ELF .note BSD_SYMTAB Ryan O'Neill
2014-08-06 19:31 ` Andrew Cooper
2014-08-07 8:55 ` Egger, Christoph
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).