| /linux/drivers/s390/net/ |
| A D | qeth_core_sys.c | 411 switch (card->options.isolation) { in qeth_dev_isolation_show()
427 enum qeth_ipa_isolation_modes isolation; in qeth_dev_isolation_store() local
440 isolation = ISOLATION_MODE_NONE; in qeth_dev_isolation_store()
442 isolation = ISOLATION_MODE_FWD; in qeth_dev_isolation_store()
444 isolation = ISOLATION_MODE_DROP; in qeth_dev_isolation_store()
451 rc = qeth_setadpparms_set_access_ctrl(card, isolation); in qeth_dev_isolation_store()
454 WRITE_ONCE(card->options.isolation, isolation); in qeth_dev_isolation_store()
462 static DEVICE_ATTR(isolation, 0644, qeth_dev_isolation_show,
|
| /linux/drivers/gpu/drm/i915/gt/ |
| A D | intel_engine_user.c | 241 unsigned int isolation; in intel_engines_driver_register() local
273 isolation = intel_engines_has_context_isolation(i915); in intel_engines_driver_register()
278 if ((isolation & bit) != expected) { in intel_engines_driver_register()
|
| /linux/arch/arm/boot/dts/ |
| A D | armada-385-clearfog-gtr.dtsi | 50 47 - Control isolation of boot sensitive SAR signals
172 cf_gtr_isolation_pins: cf-gtr-isolation-pins {
437 sar-isolation {
441 line-name = "sar-isolation";
|
| /linux/kernel/sched/ |
| A D | built-in.a | 25 isolation.o/
|
| A D | Makefile | 41 obj-$(CONFIG_CPU_ISOLATION) += isolation.o
|
| A D | .built-in.a.cmd | 1 …sched/cpufreq.o kernel/sched/cpufreq_schedutil.o kernel/sched/membarrier.o kernel/sched/isolation.o
|
| A D | .isolation.o.cmd | 1 …isolation.o := /usr/bin/ccache /home/test/workspace/code/optee_3.16/build/../toolchains/aarch64/bi…
3 source_kernel/sched/isolation.o := kernel/sched/isolation.c
5 deps_kernel/sched/isolation.o := \
773 include/linux/sched/isolation.h \
1529 kernel/sched/isolation.o: $(deps_kernel/sched/isolation.o)
1531 $(deps_kernel/sched/isolation.o):
|
| /linux/drivers/clk/xilinx/ |
| A D | Kconfig | 8 Provides the driver to enable and disable the isolation between the
|
| /linux/Documentation/devicetree/bindings/soc/xilinx/ |
| A D | xlnx,vcu.txt | 7 LogicoreIP design to provide the isolation between processing system
|
| /linux/drivers/net/can/peak_canfd/ |
| A D | Kconfig | 11 up to 12 Mbit/s. A galvanic isolation of the CAN ports protects the
|
| /linux/Documentation/vm/ |
| A D | page_migration.rst | 178 as PG_isolated so concurrent isolation in several CPUs skip the page
179 for isolation. If a driver cannot isolate the page, it should return *false*.
187 After isolation, VM calls migratepage() of driver with the isolated page.
233 If the driver releases the page after isolation by VM, page->mapping
251 To prevent concurrent isolation among several CPUs, VM marks isolated page
|
| /linux/Documentation/devicetree/bindings/soc/dove/ |
| A D | pmu.txt | 28 - marvell,pmu_iso_mask: specifies the mask value for PMU isolation register
|
| /linux/Documentation/devicetree/bindings/misc/ |
| A D | fsl,qoriq-mc.txt | 16 same hardware "isolation context" and a 10-bit value called an ICID
17 (isolation context id) is expressed by the hardware to identify
|
| /linux/Documentation/dev-tools/kunit/ |
| A D | faq.rst | 13 test a single unit of code in isolation, hence the name. A unit test should be
47 - A unit test is supposed to test a single unit of code in isolation, hence the
|
| A D | index.rst | 45 A unit test is supposed to test a single unit of code in isolation, hence the
|
| /linux/Documentation/devicetree/bindings/phy/ |
| A D | samsung-phy.txt | 38 control pmu registers for power isolation.
166 control pmu registers for power isolation.
|
| /linux/Documentation/admin-guide/LSM/ |
| A D | SafeSetID.rst | 73 Unfortunately, it is not generally feasible to use user namespaces in isolation,
85 configurations. Using user namespaces in isolation causes problems regarding
|
| /linux/Documentation/driver-api/ |
| A D | vfio.rst | 46 isolation properties into what was, in many cases, an interface only
52 This isolation is not always at the granularity of a single device
54 interconnects, and IOMMU topologies can each reduce this isolation.
312 out of the window leads to the whole PE isolation.
513 still provide isolation. For PCI, SR-IOV Virtual Functions are the
|
| /linux/kernel/ |
| A D | built-in.a | 58 sched/isolation.o/
|
| /linux/Documentation/s390/ |
| A D | pci.rst | 103 The segments determine the isolation of a function.
|
| /linux/Documentation/devicetree/bindings/interrupt-controller/ |
| A D | msi.txt | 28 MSI controller and device rather than a property of either in isolation).
|
| /linux/Documentation/driver-api/mei/ |
| A D | iamt.rst | 21 - Selective network isolation of Ethernet and IP protocol flows based
|
| /linux/Documentation/networking/device_drivers/ethernet/freescale/dpaa2/ |
| A D | overview.rst | 124 All objects in a container share the same hardware "isolation context".
125 This means that with respect to an IOMMU the isolation granularity
|
| /linux/drivers/net/wireless/broadcom/b43/ |
| A D | phy_lp.c | 161 u16 isolation; in lpphy_adjust_gain_table() local
166 isolation = lpphy->tx_isolation_med_band; in lpphy_adjust_gain_table()
168 isolation = lpphy->tx_isolation_low_band; in lpphy_adjust_gain_table()
170 isolation = lpphy->tx_isolation_med_band; in lpphy_adjust_gain_table()
172 isolation = lpphy->tx_isolation_hi_band; in lpphy_adjust_gain_table()
174 temp[0] = ((isolation - 26) / 12) << 12; in lpphy_adjust_gain_table()
|
| /linux/Documentation/dev-tools/ |
| A D | testing-overview.rst | 33 of the kernel, which can be tested in isolation. This aligns well with the
|