Lines Matching +full:application +full:- +full:dependent

8 kvm_open, kvm_close \- specify a kernel to examine
12 \fBcc\fR [ \fIflag\fR\&.\|.\|. ] \fIfile\fR\&.\|.\|. \fB-lkvm\fR [ \fIlibrary\fR\&.\|.\|.]
78 pointer, no error messages will be printed. If it is non-null, it is assumed to
85 Applications using  \fBlibkvm\fR are dependent on the underlying data model of
91 For example, a 32\(mibit application that uses the 32\(mibit version of the
93 a 64\(mibit application that uses the 64\(mibit version of the \fBlibkvm\fR
105 The \fBkvm_open()\fR function returns a non-null value suitable for use with
154 MT-Level	Unsafe
179 created. While a 32-bit application running on a 64-bit kernel can examine a
180 32-bit core dump, a 64-bit application running on a 64-bit kernel cannot
181 examine a kernel core dump from the 32-bit system.
184 On 32-bit systems, applications that use \fBlibkvm\fR to access the running
185 kernel must be 32-bit applications. On systems that support both 32-bit and
186 64-bit applications, applications that use the \fBlibkvm\fR interfaces to
187 access the running kernel must themselves be 64-bit applications.
195 Applications using  \fBlibkvm\fR are likely to be platform- and
196 release-dependent.