Home
last modified time | relevance | path

Searched refs:isolate (Results 1 – 25 of 50) sorted by relevance

12

/linux-6.6.21/include/linux/
Dlist_lru.h167 list_lru_walk_cb isolate, void *cb_arg,
184 list_lru_walk_cb isolate, void *cb_arg,
187 list_lru_walk_cb isolate, void *cb_arg,
192 list_lru_walk_cb isolate, void *cb_arg) in list_lru_shrink_walk() argument
194 return list_lru_walk_one(lru, sc->nid, sc->memcg, isolate, cb_arg, in list_lru_shrink_walk()
200 list_lru_walk_cb isolate, void *cb_arg) in list_lru_shrink_walk_irq() argument
202 return list_lru_walk_one_irq(lru, sc->nid, sc->memcg, isolate, cb_arg, in list_lru_shrink_walk_irq()
207 list_lru_walk(struct list_lru *lru, list_lru_walk_cb isolate, in list_lru_walk() argument
214 isolated += list_lru_walk_node(lru, nid, isolate, in list_lru_walk()
/linux-6.6.21/mm/
Dlist_lru.c207 list_lru_walk_cb isolate, void *cb_arg, in __list_lru_walk_one() argument
231 ret = isolate(item, l, &nlru->lock, cb_arg); in __list_lru_walk_one()
269 list_lru_walk_cb isolate, void *cb_arg, in list_lru_walk_one() argument
276 ret = __list_lru_walk_one(lru, nid, memcg_kmem_id(memcg), isolate, in list_lru_walk_one()
285 list_lru_walk_cb isolate, void *cb_arg, in list_lru_walk_one_irq() argument
292 ret = __list_lru_walk_one(lru, nid, memcg_kmem_id(memcg), isolate, in list_lru_walk_one_irq()
299 list_lru_walk_cb isolate, void *cb_arg, in list_lru_walk_node() argument
304 isolated += list_lru_walk_one(lru, nid, NULL, isolate, cb_arg, in list_lru_walk_node()
317 isolate, cb_arg, in list_lru_walk_node()
/linux-6.6.21/Documentation/ABI/testing/
Dsysfs-driver-uacce29 0 means never isolate the device. The maximum value is 65535. You can write
32 What: /sys/class/uacce/<dev_name>/isolate
/linux-6.6.21/drivers/firmware/arm_ffa/
DKconfig12 virtualization extension to isolate software images provided
/linux-6.6.21/arch/m68k/fpsp040/
Dx_store.S42 bfextu %d0{#6:#3},%d0 |isolate dest. reg from cmdreg3b
237 andw #0x7,%d0 |isolate register number
Dbugfix.S280 | It is necessary to isolate the result of the instruction in the
406 | It is necessary to isolate the result of the instruction in the
Dres_func.S117 andib #0x3b,%d0 |isolate bits to select inst
725 andib #0x60,%d0 |isolate tag bits
1418 andiw #0x0c00,%d0 |isolate last 2 bits of size field
1956 bfextu %d0{#16:#3},%d0 |isolate source bits
1984 bfextu %d0{#25:#3},%d0 |isolate register for dynamic k-factor
Dx_operr.S258 andil #7,%d0 |isolate register number
/linux-6.6.21/drivers/iommu/amd/
DKconfig18 can isolate the DMA memory of different devices and protect the
/linux-6.6.21/Documentation/dev-tools/kunit/api/
Dfunctionredirection.rst10 When writing unit tests, it's important to be able to isolate the code being
24 manage, isolate, and restore state, or they can avoid it altogether by
/linux-6.6.21/arch/mips/dec/
Dint-handler.S138 and t0,t1 # isolate allowed ones
/linux-6.6.21/Documentation/devicetree/bindings/net/
Dmicrel.txt54 isolate and power-down mode. On some boards this input is connected
/linux-6.6.21/arch/alpha/lib/
Dstrrchr.S56 negq t1, t4 # e0 : isolate first null byte match
Dev67-strrchr.S84 negq t1, t4 # E : isolate first null byte match
Dstxcpy.S216 negq t8, t6 # e0 : isolate low bit set
Dev6-stxcpy.S243 negq t8, t6 # E : isolate low bit set
/linux-6.6.21/Documentation/gpu/
Dvkms.rst65 sudo systemctl isolate multi-user.target
69 sudo systemctl isolate graphical.target
/linux-6.6.21/drivers/vfio/
DKconfig67 VFIO is built on the ability to isolate devices using the IOMMU.
/linux-6.6.21/arch/arm/mach-omap2/
Dsram242x.S143 mov r5, r5, lsr #8 @ isolate rfr field and drop burst
280 and r8, r8, #3 @ isolate field
Dsram243x.S143 mov r5, r5, lsr #8 @ isolate rfr field and drop burst
280 and r8, r8, #3 @ isolate field
/linux-6.6.21/drivers/fpga/
DKconfig113 isolate one region of the FPGA from the busses while that
123 The PR Decoupler exists in the FPGA fabric to isolate one
/linux-6.6.21/Documentation/arch/arm/nwfpe/
Dnwfpe.rst44 attempting to isolate the problem. Please report them, but don't
/linux-6.6.21/drivers/crypto/hisilicon/
Dqm.c2515 struct qm_err_isolate *isolate; in qm_hw_err_isolate() local
2518 isolate = &qm->isolate_data; in qm_hw_err_isolate()
2523 if (qm->uacce->is_vf || isolate->is_isolate || !isolate->err_threshold) in qm_hw_err_isolate()
2536 mutex_lock(&isolate->isolate_lock); in qm_hw_err_isolate()
2538 list_for_each_entry_safe(err, tmp, &isolate->qm_hw_errs, list) { in qm_hw_err_isolate()
2547 list_add(&hw_err->list, &isolate->qm_hw_errs); in qm_hw_err_isolate()
2548 mutex_unlock(&isolate->isolate_lock); in qm_hw_err_isolate()
2550 if (count >= isolate->err_threshold) in qm_hw_err_isolate()
2551 isolate->is_isolate = true; in qm_hw_err_isolate()
/linux-6.6.21/Documentation/mm/
Dvmalloced-kernel-stacks.rst23 it difficult to isolate and root-cause.
/linux-6.6.21/arch/arm/kernel/
Dphys2virt.S104 lsrs r3, r6, #29 @ isolate top 3 bits of displacement

12