Date: Wed, 1 Jun 2016 19:21:37 -0700 From: Bryan Drewery <bdrewery@FreeBSD.org> To: Mark Millard <markmi@dsl-only.net>, Nathan Whitehorn <nwhitehorn@freebsd.org> Cc: FreeBSD Current <freebsd-current@freebsd.org>, FreeBSD PowerPC ML <freebsd-ppc@freebsd.org> Subject: Re: [CFT] WITH_META_MODE: Working incremental build [only on i386 and amd64] [filemon fails to load on powerpc64] Message-ID: <5ae8e248-904e-2c33-b76c-566890406b8c@FreeBSD.org> In-Reply-To: <35AFB7AC-7AD4-41D5-AA8D-87C37EB52455@dsl-only.net> References: <FE82CBAD-ED55-41A3-9413-34948A9CBC0F@dsl-only.net> <7748cc71-3788-22ae-fcb2-699eae529310@FreeBSD.org> <9A1A624D-9286-4C0F-A435-D590E07C1149@dsl-only.net> <0165aee5-cf6f-8f01-1690-fc51995e2109@FreeBSD.org> <35AFB7AC-7AD4-41D5-AA8D-87C37EB52455@dsl-only.net>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --Jtq168a0P33B4DFhqBATxSODnEKdFG8Dj Content-Type: multipart/mixed; boundary="qfHe6El5c7HSDG6MF3WHjivET43WvFI4P" From: Bryan Drewery <bdrewery@FreeBSD.org> To: Mark Millard <markmi@dsl-only.net>, Nathan Whitehorn <nwhitehorn@freebsd.org> Cc: FreeBSD Current <freebsd-current@freebsd.org>, FreeBSD PowerPC ML <freebsd-ppc@freebsd.org> Message-ID: <5ae8e248-904e-2c33-b76c-566890406b8c@FreeBSD.org> Subject: Re: [CFT] WITH_META_MODE: Working incremental build [only on i386 and amd64] [filemon fails to load on powerpc64] References: <FE82CBAD-ED55-41A3-9413-34948A9CBC0F@dsl-only.net> <7748cc71-3788-22ae-fcb2-699eae529310@FreeBSD.org> <9A1A624D-9286-4C0F-A435-D590E07C1149@dsl-only.net> <0165aee5-cf6f-8f01-1690-fc51995e2109@FreeBSD.org> <35AFB7AC-7AD4-41D5-AA8D-87C37EB52455@dsl-only.net> In-Reply-To: <35AFB7AC-7AD4-41D5-AA8D-87C37EB52455@dsl-only.net> --qfHe6El5c7HSDG6MF3WHjivET43WvFI4P Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable The fix is easy, I am just wondering why there are 2 ABI formats supported. If only one is normally used and the default then I'll only support that one. Filemon hooks the syscall table. On 6/1/2016 7:16 PM, Mark Millard wrote: > May be Nathan Whitehorn knows what is going on that prevents filemon.ko= > from loading for powerpc64 based on how it is now built (added for more= > than i386 and amd64 as of -r301130)? >=20 > Nathan: See below if it sounds like something you might have a clue > about. As to why this comers up: Loading filemon.ko is required in orde= r > for WITH_META_MODE=3Dyes to work for incremental builds. >=20 > =3D=3D=3D > Mark Millard > markmi at dsl-only.net <http://dsl-only.net>; >=20 > On 2016-Jun-1, at 6:59 PM, Bryan Drewery <bdrewery at FreeBSD.org > <http://freebsd.org>>; wrote: >=20 >> On 6/1/2016 6:39 PM, Mark Millard wrote: >>> while filemon.ko now exists: >>>> # ls -l /boot/*/filemon* >>>> -r-xr-xr-x 1 root wheel 32064 Jun 1 17:59 /boot/kernel/filemon.k= o >>> it does not load: >>>> # kldload -n filemon >>>> kldload: can't load filemon: No such file or directory >>>> # dmesg | grep link_elf >>>> link_elf: symbol elf64_freebsd_sysvec undefined >> >> There's 2 different ABI formats for powerpc64? >> >>> sys/powerpc/powerpc/elf64_machdep.c:INIT_SYSENTVEC(elf64_sysvec_v1, >>> &elf64_freebsd_sysvec_v1); >>> sys/powerpc/powerpc/elf64_machdep.c:INIT_SYSENTVEC(elf64_sysvec_v2, >>> &elf64_freebsd_sysvec_v2); >> >> What's up with that? >> >> --=20 >> Regards, >> Bryan Drewery >=20 >=20 --=20 Regards, Bryan Drewery --qfHe6El5c7HSDG6MF3WHjivET43WvFI4P-- --Jtq168a0P33B4DFhqBATxSODnEKdFG8Dj Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBAgAGBQJXT5gyAAoJEDXXcbtuRpfP0UkIANnjL5JR3byD+RbIiU59V9O3 +Js1peju66sDE26J8Rgc2mc6tlchtxa6sXRE/sboCCom1KLInaGpBVucvNSt89/X 6FWC3uMrYavzCg7eWkCrXjK5G1bsbVQYzhxnl/udR9tBTC51DXjVSqitmUwZABLR 4LK2smVIflBbfzUZvV0sTeqbLChNeMpJ3uuIrG+zSO2CQbVaA9NJ/WFkgw5A8v4D Ypi5XxNX98EkxMnmV0JclVtvSShurRmVkq5f2eZbJ1WfxbpRxhpw3ABpL5uGgE2i dZRscYvI5yNydKi8iaLEOEBvSruFtLTpu1TB0FluaqtbDWxFM3xYhr2ELVWkk8A= =ZZAA -----END PGP SIGNATURE----- --Jtq168a0P33B4DFhqBATxSODnEKdFG8Dj--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5ae8e248-904e-2c33-b76c-566890406b8c>