Searched full:interpretation (Results 1 – 25 of 183) sorted by relevance
12345678
81 /* Setup Adapter Event Notification Interpretation */ in zpci_setup_aipb()237 * enabled for interpretation in kvm_s390_pci_aif_enable()430 * Register device with the specified KVM. If interpretation facilities are459 * If interpretation facilities aren't available, add the device to in kvm_s390_pci_register_kvm()460 * the kzdev list but don't enable for interpretation. in kvm_s390_pci_register_kvm()480 * access this device via interpretation to be used by host CLP in kvm_s390_pci_register_kvm()536 * A 0 gisa means interpretation was never enabled, just remove the in kvm_s390_pci_unregister_kvm()542 /* Forwarding must be turned off before interpretation */ in kvm_s390_pci_unregister_kvm()
485 * Without SIGP interpretation, only SRS interpretation (if available) in kvm_s390_use_sca_entries()511 * interpretation as well as adapter interruption forwarding.
10 interpretation of this settings is required by the end application according to24 and may vary greatly on a part-by-part basis. For exact interpretation of
27 bool "Support for SMP interpretation for SAS hosts"
12 * specific interpretation.
3 Linux Kernel Contributor Covenant Code of Conduct Interpretation10 community will interpret it. We also do not expect this interpretation
82 Interpretation chapter
63 code-of-conduct-interpretation
8 the pixel format, compression and colour space. The interpretation of the
18 timing information, required for precise interpretation of timestamps, contained
31 code-of-conduct-interpretation
5 :Original: :ref:`Documentation/process/code-of-conduct-interpretation.rst <code_of_conduct_interpre…
3 :Original: :ref:`Documentation/process/code-of-conduct-interpretation.rst <code_of_conduct_interpre…
30 code-of-conduct-interpretation
44 /* Interpretation of modem status lines */
49 * Interpretation of the PERF_RECORD_AUX_OUTPUT_HW_ID payload.
29 doubts about its interpretation. Additionally, some people prefer to read
48 driver for interpretation. This driver makes use of the kernel's in-core
47 Domain Of Interpretation (DOI) definition and are configured through the
77 systems within a single Domain of Interpretation (DOI). A DOI is a96 LENGTH INTERPRETATION114 3.3 Domain of Interpretation Identifier159 only be meaningful in certain Domains of Interpretation. For these tag
62 See datasheet Table 11 for n-Factor range list and value interpretation.
22 All interpretation of userspace memory addresses by the kernel assumes
92 * @type: type of owner - allows interpretation of owner_handle.
21 The interpretation of these parameters is implementation-defined, so