Date: Tue, 21 Jul 2015 09:24:42 -0700 From: Adrian Chadd <adrian.chadd@gmail.com> To: Venkat Duvvuru <venkatkumar.duvvuru@avagotech.com> Cc: Allan Jude <allanjude@freebsd.org>, freebsd-current <freebsd-current@freebsd.org> Subject: Re: Kernel Application Binary Interface (kABI) support in FreeBSD Message-ID: <CAJ-VmonKY1sduoSNSZeNpTwE_D4YfSaqJz0P5meRAUPZNLHB%2BA@mail.gmail.com> In-Reply-To: <CADFzAK_wzBbhGsF3G1C32TY5afY5Yu0P6TCJmcFuJvkmRn3ZOg@mail.gmail.com> References: <e99bd6bc6ecf65c35f442e4065533c71@mail.gmail.com> <55A9157A.8050208@freebsd.org> <55A91837.50805@freebsd.org> <CADFzAK_wzBbhGsF3G1C32TY5afY5Yu0P6TCJmcFuJvkmRn3ZOg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Yes, I think the FreeBSD developers have been doing this since before Redhat was a thing. -a On 20 July 2015 at 23:02, Venkat Duvvuru <venkatkumar.duvvuru@avagotech.com> wrote: > Yes, my question was about kernel module compatibililty with FreeBSD's > major releases of a particular version. > For example, will FreeBSD makes sure that the driver built on 10.0 version > of Freebsd seamlessly load on all other 10.x versions of FreeBSD? > Does it make sure that the symbols and their parameters are not blindly > changed without considering the binary compatibility with other FreeBSD > version binaries? > > RHEL kABI whitelist makes sure that once the symbol is added into the > whitelist, it will never be changed during the major releases of that > kernel. > > > Thanks, > Venkat. > > On Fri, Jul 17, 2015 at 8:29 PM, Allan Jude <allanjude@freebsd.org> wrote: > >> On 2015-07-17 10:47, Julian Elischer wrote: >> > On 7/17/15 9:02 PM, Venkat Duvvuru wrote: >> >> Hi, >> >> >> >> Is there kABI (Kabi-whitelist) equivalent feature in FreeBSD? >> > well, yes and no. >> > >> > Firstly, FreeBSD maintains a backwards compatible kABI (with the >> > exception of programs that hunt around in kernel memory). >> > We also use symbol versioning on the libc. so depending on what you want >> > to do. the answer may be useful to you or not. >> > Basically any binary should continue to run on a newer kernel, even if >> > the syscalls change, because we should still support the old abi. >> > >> > tell us more about what you need and we can be more specific. >> > >> > I have run Freebsd 1.1 binaries on a Freebsd 8 system, in fact I have >> > done a system build in a freebsd 1.1 chroot on an 8 system. >> > I haven't tried it on 9 or 10 but I'd expect it to work.. >> > >> > >> >> >> >> >> >> >> >> Thanks, >> >> >> >> Venkat. >> >> _______________________________________________ >> >> freebsd-current@freebsd.org mailing list >> >> http://lists.freebsd.org/mailman/listinfo/freebsd-current >> >> To unsubscribe, send any mail to >> >> "freebsd-current-unsubscribe@freebsd.org" >> >> >> >> >> > >> > _______________________________________________ >> > freebsd-current@freebsd.org mailing list >> > http://lists.freebsd.org/mailman/listinfo/freebsd-current >> > To unsubscribe, send any mail to " >> freebsd-current-unsubscribe@freebsd.org" >> >> I think the question related to drivers (kernel modules). >> >> In which case, they should be compatible across major versions (module >> from 10.0 works in 10.2, but not 9.3 or 11.0) >> >> -- >> Allan Jude >> >> > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmonKY1sduoSNSZeNpTwE_D4YfSaqJz0P5meRAUPZNLHB%2BA>