Home
last modified time | relevance | path

Searched refs:MSI (Results 1 – 25 of 2548) sorted by relevance

12345678910>>...102

/dports/benchmarks/py-naarad/naarad-1.0.15/examples/logs/
H A Dproc.interrupts.out16 … 0 0 0 0 0 0 0 IR-PCI-MSI-edge aerdrv
17 … 0 0 0 0 0 0 0 IR-PCI-MSI-edge aerdrv
18 … 0 0 0 0 0 0 0 IR-PCI-MSI-edge aerdrv
19 … 0 0 0 0 0 0 0 IR-PCI-MSI-edge aerdrv
20 … 0 0 0 0 0 0 0 IR-PCI-MSI-edge aerdrv
21 … 0 0 0 0 0 0 0 IR-PCI-MSI-edge megasas
22 … 0 0 0 0 0 0 0 IR-PCI-MSI-edge eth0
23 … 0 0 0 0 0 0 IR-PCI-MSI-edge eth0-TxRx…
31 … 0 0 0 0 0 0 0 IR-PCI-MSI-edge eth1
75 … 0 0 0 0 0 0 0 IR-PCI-MSI-edge eth0
[all …]
/dports/emulators/qemu-powernv/qemu-powernv-3.0.50/roms/skiboot/doc/opal-api/
H A Dopal-get-msi-39-40.rst12 OPAL PHBs encode MVE and XIVE specifiers in MSI DMA and message data values.
15 msi_address parameter returns the MSI DMA address and the msi_data parameter
24 MSI. For ``ibm,opal-ioda2`` PHBs, the MVE number argument is ignored.
28 DMA address and message data value this PE will signal as an MSI ro MSI-X.
32 in put MVE and XIVE, primarily for MSI-conventional Multiple Message
33 Enable > 1 MSI. MSI requires consecutive MSIs per MSI address, and each
34 MSI DMA address must be unique for any given consecutive power of 2 set
39 For MSI conventional, the MSI address and message data returned apply to a
47 data and message address for exactly one MSI specified by the input XIVE
49 for an MSI Capability MME value of 1 MSI. For MSI-X XIVRs, the host should
[all …]
/dports/lang/mono/mono-5.10.1.57/mcs/class/System/Mono.Net.Security/
H A DCallbackHelpers.cs34 using MSI = MonoSecurity::Mono.Security.Interface; typedef
36 using MSI = Mono.Security.Interface; typedef
52 …internal static MSI.MonoRemoteCertificateValidationCallback PublicToMono (RemoteCertificateValidat… in PublicToMono()
60 …internal static MSI.MonoLocalCertificateSelectionCallback PublicToMono (LocalCertificateSelectionC… in PublicToMono()
68 …internal static MSI.MonoRemoteCertificateValidationCallback InternalToMono (RemoteCertValidationCa… in InternalToMono()
84 …internal static MSI.MonoLocalCertificateSelectionCallback InternalToMono (LocalCertSelectionCallba… in InternalToMono()
97 return (t, c, ch, e) => callback (null, c, ch, (MSI.MonoSslPolicyErrors)e); in MonoToPublic()
100 …internal static LocalCertificateSelectionCallback MonoToPublic (MSI.MonoLocalCertificateSelectionC… in MonoToPublic()
108 …internal static RemoteCertValidationCallback MonoToInternal (MSI.MonoRemoteCertificateValidationCa… in MonoToInternal()
113 return (h, c, ch, e) => callback (h, c, ch, (MSI.MonoSslPolicyErrors)e); in MonoToInternal()
[all …]
H A DLegacyTlsProvider.cs32 using MSI = MonoSecurity::Mono.Security.Interface; typedef
34 using MSI = Mono.Security.Interface; typedef
49 class LegacyTlsProvider : MSI.MonoTlsProvider
79 public override MSI.IMonoSslStream CreateSslStream ( in CreateSslStream()
81 MSI.MonoTlsSettings settings = null) in CreateSslStream()
86 internal override MSI.IMonoSslStream CreateSslStreamInternal ( in CreateSslStreamInternal()
88 MSI.MonoTlsSettings settings) in CreateSslStreamInternal()
94 MSI.ICertificateValidator2 validator, string targetHost, bool serverMode, in ValidateCertificate()
96 ref MSI.MonoSslPolicyErrors errors, ref int status11) in ValidateCertificate()
102 errors = (MSI.MonoSslPolicyErrors)xerrors; in ValidateCertificate()
H A DMonoTlsProviderFactory.cs31 using MSI = MonoSecurity::Mono.Security.Interface; typedef
34 using MSI = Mono.Security.Interface; typedef
73 internal static MSI.MonoTlsProvider GetProviderInternal () in GetProviderInternal()
89 MSI.MonoTlsProvider provider; in InitializeInternal()
125 static MSI.MonoTlsProvider defaultProvider;
169 MSI.MonoTlsProvider provider; in LookupProvider()
266 static MSI.MonoTlsProvider CreateDefaultProviderImpl () in CreateDefaultProviderImpl()
268 MSI.MonoTlsProvider provider = null; in CreateDefaultProviderImpl()
286 static MSI.MonoTlsProvider CreateDefaultProviderImpl () in CreateDefaultProviderImpl()
291 static MSI.MonoTlsProvider CreateDefaultProviderImpl () in CreateDefaultProviderImpl()
[all …]
H A DNoReflectionHelper.cs30 using MSI = MonoSecurity::Mono.Security.Interface; typedef
33 using MSI = Mono.Security.Interface; typedef
53 …return ChainValidationHelper.GetInternalValidator ((MSI.MonoTlsProvider)provider, (MSI.MonoTlsSett… in GetInternalValidator()
62 return ChainValidationHelper.GetDefaultValidator ((MSI.MonoTlsSettings)settings); in GetDefaultValidator()
108 …return new HttpWebRequest (requestUri, (MSI.MonoTlsProvider)provider, (MSI.MonoTlsSettings)setting… in CreateHttpsRequest()
117 …return new HttpListener ((X509Certificate)certificate, (MSI.MonoTlsProvider)provider, (MSI.MonoTls… in CreateHttpListener()
/dports/emulators/qemu60/qemu-6.0.0/roms/skiboot/doc/opal-api/
H A Dopal-get-msi-39-40.rst51 OPAL PHBs encode MVE and XIVE specifiers in MSI DMA and message data values.
54 msi_address parameter returns the MSI DMA address and the msi_data parameter
63 MSI. For ``ibm,opal-ioda2`` PHBs, the MVE number argument is ignored.
67 DMA address and message data value this PE will signal as an MSI ro MSI-X.
71 in put MVE and XIVE, primarily for MSI-conventional Multiple Message
72 Enable > 1 MSI. MSI requires consecutive MSIs per MSI address, and each
73 MSI DMA address must be unique for any given consecutive power of 2 set
78 For MSI conventional, the MSI address and message data returned apply to a
86 data and message address for exactly one MSI specified by the input XIVE
88 for an MSI Capability MME value of 1 MSI. For MSI-X XIVRs, the host should
[all …]
/dports/emulators/qemu5/qemu-5.2.0/roms/skiboot/doc/opal-api/
H A Dopal-get-msi-39-40.rst51 OPAL PHBs encode MVE and XIVE specifiers in MSI DMA and message data values.
54 msi_address parameter returns the MSI DMA address and the msi_data parameter
63 MSI. For ``ibm,opal-ioda2`` PHBs, the MVE number argument is ignored.
67 DMA address and message data value this PE will signal as an MSI ro MSI-X.
71 in put MVE and XIVE, primarily for MSI-conventional Multiple Message
72 Enable > 1 MSI. MSI requires consecutive MSIs per MSI address, and each
73 MSI DMA address must be unique for any given consecutive power of 2 set
78 For MSI conventional, the MSI address and message data returned apply to a
86 data and message address for exactly one MSI specified by the input XIVE
88 for an MSI Capability MME value of 1 MSI. For MSI-X XIVRs, the host should
[all …]
/dports/emulators/qemu42/qemu-4.2.1/roms/skiboot/doc/opal-api/
H A Dopal-get-msi-39-40.rst51 OPAL PHBs encode MVE and XIVE specifiers in MSI DMA and message data values.
54 msi_address parameter returns the MSI DMA address and the msi_data parameter
63 MSI. For ``ibm,opal-ioda2`` PHBs, the MVE number argument is ignored.
67 DMA address and message data value this PE will signal as an MSI ro MSI-X.
71 in put MVE and XIVE, primarily for MSI-conventional Multiple Message
72 Enable > 1 MSI. MSI requires consecutive MSIs per MSI address, and each
73 MSI DMA address must be unique for any given consecutive power of 2 set
78 For MSI conventional, the MSI address and message data returned apply to a
86 data and message address for exactly one MSI specified by the input XIVE
88 for an MSI Capability MME value of 1 MSI. For MSI-X XIVRs, the host should
[all …]
/dports/emulators/qemu-utils/qemu-4.2.1/roms/skiboot/doc/opal-api/
H A Dopal-get-msi-39-40.rst51 OPAL PHBs encode MVE and XIVE specifiers in MSI DMA and message data values.
54 msi_address parameter returns the MSI DMA address and the msi_data parameter
63 MSI. For ``ibm,opal-ioda2`` PHBs, the MVE number argument is ignored.
67 DMA address and message data value this PE will signal as an MSI ro MSI-X.
71 in put MVE and XIVE, primarily for MSI-conventional Multiple Message
72 Enable > 1 MSI. MSI requires consecutive MSIs per MSI address, and each
73 MSI DMA address must be unique for any given consecutive power of 2 set
78 For MSI conventional, the MSI address and message data returned apply to a
86 data and message address for exactly one MSI specified by the input XIVE
88 for an MSI Capability MME value of 1 MSI. For MSI-X XIVRs, the host should
[all …]
/dports/emulators/qemu-guest-agent/qemu-5.0.1/roms/skiboot/doc/opal-api/
H A Dopal-get-msi-39-40.rst51 OPAL PHBs encode MVE and XIVE specifiers in MSI DMA and message data values.
54 msi_address parameter returns the MSI DMA address and the msi_data parameter
63 MSI. For ``ibm,opal-ioda2`` PHBs, the MVE number argument is ignored.
67 DMA address and message data value this PE will signal as an MSI ro MSI-X.
71 in put MVE and XIVE, primarily for MSI-conventional Multiple Message
72 Enable > 1 MSI. MSI requires consecutive MSIs per MSI address, and each
73 MSI DMA address must be unique for any given consecutive power of 2 set
78 For MSI conventional, the MSI address and message data returned apply to a
86 data and message address for exactly one MSI specified by the input XIVE
88 for an MSI Capability MME value of 1 MSI. For MSI-X XIVRs, the host should
[all …]
/dports/emulators/qemu/qemu-6.2.0/roms/skiboot/doc/opal-api/
H A Dopal-get-msi-39-40.rst51 OPAL PHBs encode MVE and XIVE specifiers in MSI DMA and message data values.
54 msi_address parameter returns the MSI DMA address and the msi_data parameter
63 MSI. For ``ibm,opal-ioda2`` PHBs, the MVE number argument is ignored.
67 DMA address and message data value this PE will signal as an MSI ro MSI-X.
71 in put MVE and XIVE, primarily for MSI-conventional Multiple Message
72 Enable > 1 MSI. MSI requires consecutive MSIs per MSI address, and each
73 MSI DMA address must be unique for any given consecutive power of 2 set
78 For MSI conventional, the MSI address and message data returned apply to a
86 data and message address for exactly one MSI specified by the input XIVE
88 for an MSI Capability MME value of 1 MSI. For MSI-X XIVRs, the host should
[all …]
/dports/multimedia/libv4l/linux-5.13-rc2/Documentation/PCI/
H A Dmsi-howto.rst5 The MSI Driver Guide HOWTO
17 to change your driver to use MSI or MSI-X and some basic diagnostics to
32 Devices may support both MSI and MSI-X, but only one can be enabled at
73 driver has to set up the device to use MSI or MSI-X. Not all machines
86 Using MSI
93 To automatically use MSI or MSI-X interrupt vectors, use the following
122 MSI-X facilities in preference to the MSI facilities. MSI-X supports any
161 the driver can specify that only MSI or MSI-X is acceptable::
184 pci_nr_irq_vectors() helper that handles MSI and MSI-X transparently.
202 How to tell whether MSI/MSI-X is enabled on a device
[all …]
/dports/multimedia/v4l-utils/linux-5.13-rc2/Documentation/PCI/
H A Dmsi-howto.rst5 The MSI Driver Guide HOWTO
17 to change your driver to use MSI or MSI-X and some basic diagnostics to
32 Devices may support both MSI and MSI-X, but only one can be enabled at
73 driver has to set up the device to use MSI or MSI-X. Not all machines
86 Using MSI
93 To automatically use MSI or MSI-X interrupt vectors, use the following
122 MSI-X facilities in preference to the MSI facilities. MSI-X supports any
161 the driver can specify that only MSI or MSI-X is acceptable::
184 pci_nr_irq_vectors() helper that handles MSI and MSI-X transparently.
202 How to tell whether MSI/MSI-X is enabled on a device
[all …]
/dports/multimedia/v4l_compat/linux-5.13-rc2/Documentation/PCI/
H A Dmsi-howto.rst5 The MSI Driver Guide HOWTO
17 to change your driver to use MSI or MSI-X and some basic diagnostics to
32 Devices may support both MSI and MSI-X, but only one can be enabled at
73 driver has to set up the device to use MSI or MSI-X. Not all machines
86 Using MSI
93 To automatically use MSI or MSI-X interrupt vectors, use the following
122 MSI-X facilities in preference to the MSI facilities. MSI-X supports any
161 the driver can specify that only MSI or MSI-X is acceptable::
184 pci_nr_irq_vectors() helper that handles MSI and MSI-X transparently.
202 How to tell whether MSI/MSI-X is enabled on a device
[all …]
/dports/multimedia/libv4l/linux-5.13-rc2/Documentation/PCI/endpoint/
H A Dpci-test-howto.rst192 MSI-X1: OKAY
193 MSI-X2: OKAY
194 MSI-X3: OKAY
195 MSI-X4: OKAY
196 MSI-X5: OKAY
197 MSI-X6: OKAY
198 MSI-X7: OKAY
199 MSI-X8: OKAY
200 MSI-X9: NOT OKAY
201 MSI-X10: NOT OKAY
[all …]
H A Dpci-ntb-function.rst115 MSI/MSI-X vectors (i.e., initialize the MSI/MSI-X Capability in the
118 to the MSI/MSI-X address programmed by the host. The ARGUMENT
120 lower 16 bits) and if MSI or MSI-X should be configured (BIT 16).
178 in order to raise doorbell. EPF NTB can use either MSI or MSI-X to
179 ring doorbell (MSI-X support will be added later). MSI uses same
180 address for all the interrupts and MSI-X can provide different
181 addresses for different interrupts. The MSI/MSI-X address is provided
182 by the host and the address it gives is based on the MSI/MSI-X
186 for both MSI and MSI-X, EPF NTB allocates a separate region in the
188 be mapped to the MSI/MSI-X address provided by the host. If a host
[all …]
/dports/multimedia/v4l-utils/linux-5.13-rc2/Documentation/PCI/endpoint/
H A Dpci-test-howto.rst192 MSI-X1: OKAY
193 MSI-X2: OKAY
194 MSI-X3: OKAY
195 MSI-X4: OKAY
196 MSI-X5: OKAY
197 MSI-X6: OKAY
198 MSI-X7: OKAY
199 MSI-X8: OKAY
200 MSI-X9: NOT OKAY
201 MSI-X10: NOT OKAY
[all …]
H A Dpci-ntb-function.rst115 MSI/MSI-X vectors (i.e., initialize the MSI/MSI-X Capability in the
118 to the MSI/MSI-X address programmed by the host. The ARGUMENT
120 lower 16 bits) and if MSI or MSI-X should be configured (BIT 16).
178 in order to raise doorbell. EPF NTB can use either MSI or MSI-X to
179 ring doorbell (MSI-X support will be added later). MSI uses same
180 address for all the interrupts and MSI-X can provide different
181 addresses for different interrupts. The MSI/MSI-X address is provided
182 by the host and the address it gives is based on the MSI/MSI-X
186 for both MSI and MSI-X, EPF NTB allocates a separate region in the
188 be mapped to the MSI/MSI-X address provided by the host. If a host
[all …]
/dports/multimedia/v4l_compat/linux-5.13-rc2/Documentation/PCI/endpoint/
H A Dpci-test-howto.rst192 MSI-X1: OKAY
193 MSI-X2: OKAY
194 MSI-X3: OKAY
195 MSI-X4: OKAY
196 MSI-X5: OKAY
197 MSI-X6: OKAY
198 MSI-X7: OKAY
199 MSI-X8: OKAY
200 MSI-X9: NOT OKAY
201 MSI-X10: NOT OKAY
[all …]
/dports/sysutils/ganglia-monitor-core/ganglia-3.7.2/
H A DMakefile.WiX15 MSI=gmond
49 all: $(MSI).msi
51 $(MSI).msi: $(OBJS) $(DEPFILES)
58 $(RM) $(MSI).msi $(OBJS)
60 install: $(MSI).msi
62 msiexec -i $(MSI).msi -l*v install.log
65 msiexec -x $(MSI).msi
/dports/multimedia/libv4l/linux-5.13-rc2/Documentation/devicetree/bindings/pci/
H A Dmediatek-pcie-gen3.yaml16 This PCIe controller supports up to 256 MSI vectors, the MSI hardware
34 |0|1|...|30|31| |0|1|...|30|31| |0|1|...|30|31| (MSI sets)
37 | | | | | | | | | | | | (MSI vectors)
40 (MSI SET0) (MSI SET1) ... (MSI SET7)
42 With 256 MSI vectors supported, the MSI vectors are composed of 8 sets,
43 each set has its own address for MSI message, and supports 32 MSI vectors
/dports/multimedia/v4l-utils/linux-5.13-rc2/Documentation/devicetree/bindings/pci/
H A Dmediatek-pcie-gen3.yaml16 This PCIe controller supports up to 256 MSI vectors, the MSI hardware
34 |0|1|...|30|31| |0|1|...|30|31| |0|1|...|30|31| (MSI sets)
37 | | | | | | | | | | | | (MSI vectors)
40 (MSI SET0) (MSI SET1) ... (MSI SET7)
42 With 256 MSI vectors supported, the MSI vectors are composed of 8 sets,
43 each set has its own address for MSI message, and supports 32 MSI vectors
/dports/multimedia/v4l_compat/linux-5.13-rc2/Documentation/devicetree/bindings/pci/
H A Dmediatek-pcie-gen3.yaml16 This PCIe controller supports up to 256 MSI vectors, the MSI hardware
34 |0|1|...|30|31| |0|1|...|30|31| |0|1|...|30|31| (MSI sets)
37 | | | | | | | | | | | | (MSI vectors)
40 (MSI SET0) (MSI SET1) ... (MSI SET7)
42 With 256 MSI vectors supported, the MSI vectors are composed of 8 sets,
43 each set has its own address for MSI message, and supports 32 MSI vectors
/dports/devel/msitools/msitools-0.101/
H A DREADME.md6 (.MSI) files. It is based on `libmsi`, a portable library to read and
7 write .MSI files. libmsi in turn is a port of (and a subset of)
18 - `msiinfo`, to inspect MSI files
20 - `msibuild`, a low-level tool to create MSI files
22 - `msidiff`, compares contents of two MSI files with diff
24 - `msidump`, dumps raw MSI tables and stream content
26 - `msiextract`, to inspect and extract the files of an MSI file
28 - `wixl`, a WiX-like tool, that builds Windows Installer (MSI)
45 format of .MSI files).

12345678910>>...102