From owner-freebsd-current Tue Jan 26 06:13:53 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA08239 for freebsd-current-outgoing; Tue, 26 Jan 1999 06:13:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA08234 for ; Tue, 26 Jan 1999 06:13:51 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191]) by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id GAA27271; Tue, 26 Jan 1999 06:13:06 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id GAA16615; Tue, 26 Jan 1999 06:13:05 -0800 (PST) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id GAA18902; Tue, 26 Jan 1999 06:13:04 -0800 (PST) From: Don Lewis Message-Id: <199901261413.GAA18902@salsa.gv.tsc.tdk.com> Date: Tue, 26 Jan 1999 06:13:04 -0800 In-Reply-To: Dag-Erling Smorgrav "Re: Heads up! New swapper and VM changes have been committed to -4.x" (Jan 26, 12:20pm) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: Dag-Erling Smorgrav , Brian Feldman Subject: Re: Heads up! New swapper and VM changes have been committed to -4.x Cc: Boris Staeblow , dillon@apollo.backplane.com, freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Jan 26, 12:20pm, Dag-Erling Smorgrav wrote: } Subject: Re: Heads up! New swapper and VM changes have been committed to - } Brian Feldman writes: } > On 24 Jan 1999, Dag-Erling Smorgrav wrote: } > > These are dynamically linked, and will automatically pick up the new } > > libkvm. } > But (most) still require the structures to be the exact same way, } > which is the reason for the recompile anyway... don't forget that! } } No, because the libkvm interface has not changed, only its internals. } libkvm must be updated to be able to talk to the kernel, and } applications which use it must be relinked with it. In the case of } dynamically linked applications, this is done automatically at load } time. Or am I reading this wrong? It depends on what has changed. If the application asks libkvm to fetch some structure from the kernel, and the application's idea of what the structure looks like is different that what is compiled into the kernel and libkvm, the application will not work correctly. For instance, if the layout of the proc structure changes, an application that was compiled with the old structure definition that calls kvm_getprocs() will get a pointer to a structure with the new layout. When the application dereferences the pointer that kvm_getprocs() returns at some offset into the structure, it will be looking at some other part of the proc structure than what it wants. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message