| /linux/tools/testing/selftests/verification/test.d/ |
| H A D | rv_monitor_enable_disable.tc | 7 local prefix="$2" # nested monitors 24 local nested 31 nested=$(basename "$nested_dir") 32 grep -q "^$monitor:$nested$" enabled_monitors 34 test -n "$nested" 41 nested=$(basename "$nested_dir") 42 ! grep -q "^$monitor:$nested$" enabled_monitors || false 50 nested=$(basename "$nested_dir") 51 grep -q "^$monitor:$nested$" enabled_monitors 59 nested [all...] |
| H A D | rv_monitor_reactor.tc | 8 local prefix="$2" # nested monitors 23 local nested 33 nested=$(basename "$nested_dir") 34 grep -q "\\[$reactor\\]" "monitors/$monitor/$nested/reactors" 37 test -n "$nested" 44 nested=$(basename "$nested_dir") 45 grep -q "\\[nop\\]" "monitors/$monitor/$nested/reactors" 50 nested=$(basename "$nested_dir") 51 test_monitor_reactor "$nested" "$monitor/"
|
| H A D | rv_monitors_available.tc | 13 nested=$(basename "$nested_dir") 15 grep -q "^$monitor:$nested$" available_monitors
|
| /linux/Documentation/virt/kvm/x86/ |
| H A D | running-nested-guests.rst | 4 Running nested guests with KVM 7 A nested guest is the ability to run a guest inside another guest (it 36 - L2 – level-2 guest; a VM running on L1, this is the "nested guest" 44 resulting in at least four levels in a nested setup — L0 (bare 46 (guest hypervisor), L3 (nested guest). 56 There are several scenarios where nested KVM can be useful, to name a 61 Provider, using nested KVM lets you rent a large enough "guest 63 multiple nested guests (level-2 guests), running different OSes, on 66 - Live migration of "guest hypervisors" and their nested guests, for 76 Enabling "nested" (x86) [all …]
|
| H A D | index.rst | 17 nested-vmx 18 running-nested-guests
|
| H A D | nested-vmx.rst | 16 hypervisors (which use VMX) with their own nested guests. It does so by 20 We describe in much greater detail the theory behind the nested VMX feature, 32 In nested virtualization, we have three levels: The host (KVM), which we call 33 L0, the guest hypervisor, which we call L1, and its nested guest, which we 37 Running nested VMX 40 The nested VMX feature is enabled by default since Linux kernel v4.20. For 41 older Linux kernel, it can be enabled by giving the "nested=1" option to the 65 As a VMX implementation, nested VMX presents a VMCS structure to L1.
|
| /linux/rust/macros/ |
| H A D | zeroable.rs | |
| /linux/rust/pin-init/internal/src/ |
| H A D | zeroable.rs | 34 let mut nested = 0; parse_zeroable_derive_input() localVariable
|
| /linux/Documentation/networking/devlink/ |
| H A D | index.rst | 33 lock of both nested and parent instances at the same time, devlink 34 instance lock of the nested instance should be taken first, only then 37 nested relationship: 39 - ``devl_nested_devlink_set()`` - called to setup devlink -> nested 40 devlink relationship (could be used for multiple nested instances). 42 nested devlink relationship. 44 nested devlink relationship. 46 The nested devlink info is exposed to the userspace over object-specific
|
| /linux/tools/perf/bench/ |
| H A D | epoll-ctl.c | 57 static unsigned int nested = 0; variable 79 …OPT_UINTEGER( 'N', "nested", &nested, "Nesting level epoll hierarchy (default is 0, no nesting)… 105 if (nested > EPOLL_MAXNESTS) in nest_epollfd() 106 nested = EPOLL_MAXNESTS; in nest_epollfd() 107 printinfo("Nesting level(s): %d\n", nested); in nest_epollfd() 109 epollfdp = calloc(nested, sizeof(int)); in nest_epollfd() 113 for (i = 0; i < nested; i++) { in nest_epollfd() 122 for (i = nested - 1; i; i--) { in nest_epollfd() 345 if (nested) in bench_epoll_ctl()
|
| /linux/net/netfilter/ipset/ |
| H A D | ip_set_bitmap_gen.h | 95 struct nlattr *nested; in mtype_head() local 98 nested = nla_nest_start(skb, IPSET_ATTR_DATA); in mtype_head() 99 if (!nested) in mtype_head() 108 nla_nest_end(skb, nested); in mtype_head() 208 struct nlattr *adt, *nested; in mtype_list() local 230 nested = nla_nest_start(skb, IPSET_ATTR_DATA); in mtype_list() 231 if (!nested) { in mtype_list() 244 nla_nest_end(skb, nested); in mtype_list() 254 nla_nest_cancel(skb, nested); in mtype_list()
|
| H A D | ip_set_list_set.c | 459 struct nlattr *nested; in list_set_head() local 462 nested = nla_nest_start(skb, IPSET_ATTR_DATA); in list_set_head() 463 if (!nested) in list_set_head() 472 nla_nest_end(skb, nested); in list_set_head() 484 struct nlattr *atd, *nested; in list_set_list() local 502 nested = nla_nest_start(skb, IPSET_ATTR_DATA); in list_set_list() 503 if (!nested) in list_set_list() 510 nla_nest_end(skb, nested); in list_set_list() 520 nla_nest_cancel(skb, nested); in list_set_list()
|
| /linux/kernel/sched/ext/ |
| H A D | inlines.h | 31 struct task_struct *prev, bool nested) in scx_dispatch_sched() argument 90 if (!nested) in scx_dispatch_sched() 98 if (!nested) in scx_dispatch_sched()
|
| /linux/scripts/coccinelle/locks/ |
| H A D | flags.cocci | 2 /// Find nested lock+irqsave functions that use the same flags variables 73 cocci.print_secs("nested lock+irqsave that reuses flags",p2) 80 msg="ERROR: nested lock+irqsave that reuses flags from line %s." % (p1[0].line)
|
| /linux/Documentation/tools/rv/ |
| H A D | rv-mon-sched.rst | 28 As a monitor container, it will enable all nested monitors and set them 30 Nevertheless nested monitors can also be activated independently both by name 48 The available nested monitors are:
|
| /linux/arch/powerpc/kvm/ |
| H A D | book3s_hv_p9_entry.c | 137 if (!vcpu->arch.nested) { in store_vcpu_state() 201 if (!vcpu->arch.nested) { in restore_p9_host_os_sprs() 303 struct kvm_nested_guest *nested = vcpu->arch.nested; in switch_mmu_to_guest_radix() local 307 lpid = nested ? nested->shadow_lpid : kvm->arch.lpid; in switch_mmu_to_guest_radix() 454 struct kvm_nested_guest *nested) in check_need_tlb_flush() argument 460 if (nested) in check_need_tlb_flush() 461 need_tlb_flush = &nested->need_tlb_flush; in check_need_tlb_flush() 536 struct kvm_nested_guest *nested = vcpu->arch.nested; in kvmhv_vcpu_entry_p9() local 703 check_need_tlb_flush(kvm, vc->pcpu, nested); in kvmhv_vcpu_entry_p9()
|
| H A D | book3s_64_mmu_radix.c | 110 if (vcpu->arch.nested) in kvmhv_copy_tofrom_guest_radix() 111 lpid = vcpu->arch.nested->shadow_lpid; in kvmhv_copy_tofrom_guest_radix() 793 bool kvmppc_hv_handle_set_rc(struct kvm *kvm, bool nested, bool writing, in kvmppc_hv_handle_set_rc() argument 809 if (nested) in kvmppc_hv_handle_set_rc() 1289 struct kvm_nested_guest *nested; in debugfs_radix_read() local 1325 nested = NULL; in debugfs_radix_read() 1331 if (nested) { in debugfs_radix_read() 1332 kvmhv_put_nested(nested); in debugfs_radix_read() 1333 nested = NULL; in debugfs_radix_read() 1344 nested = kvmhv_get_nested(kvm, p->lpid, false); in debugfs_radix_read() [all …]
|
| /linux/Documentation/arch/x86/ |
| H A D | kernel-stacks.rst | 28 hardware interrupt (i.e. not a nested hardware interrupt) then the 54 nested IST interrupts then the handler must adjust the IST values on 59 nested. For example, a debug interrupt can safely be interrupted by an 62 IST events with the same code to be nested. However in most cases, the 95 To handle nested #DB correctly there exist two instances of DB stacks. On 97 so a nested #DB starts from a clean stack. The nested #DB switches
|
| /linux/rust/syn/ |
| H A D | discouraged.rs | 218 let nested = crate::parse::advance_step_cursor(cursor, content); in parse_any_delimiter() localVariable 220 let content = crate::parse::new_parse_buffer(scope, nested, unexpected); in parse_any_delimiter()
|
| /linux/tools/net/ynl/pyynl/ |
| H A D | ynl_gen_c.py | 78 nested = attr['nested-attributes'] 80 nested = attr['sub-message'] 82 nested = None 84 if nested: 85 self.nested_attrs = nested 997 self.nested = type_list is None 1003 if self.nested and space_name in family.consts: 1376 nested = spec['nested-attributes'] 1378 nested = spec.sub_message 1383 if self.pure_nested_structs[nested].recursive: [all …]
|
| /linux/arch/x86/kvm/vmx/ |
| H A D | vmx.c | 135 static bool __read_mostly nested = 1; variable 136 module_param(nested, bool, 0444); 1365 if (vmx->nested.need_vmcs12_to_shadow_sync) in vmx_prepare_switch_to_guest() 1611 WARN_ON_ONCE(vmx->loaded_vmcs != &vmx->nested.vmcs02); in vmx_load_vmcs01() 1620 vmx_switch_loaded_vmcs(vcpu, &to_vmx(vcpu)->nested.vmcs02); in vmx_put_vmcs01() 1899 vmx->nested.mtf_pending = true; in vmx_update_emulated_instruction() 1902 vmx->nested.mtf_pending = false; in vmx_update_emulated_instruction() 2116 if (!nested) in vmx_get_feature_msr() 2118 return vmx_get_vmx_msr(&vmcs_config.nested, msr, data); in vmx_get_feature_msr() 2203 if (vmx_get_vmx_msr(&vmx->nested.msrs, msr_info->index, in vmx_get_msr() [all …]
|
| /linux/tools/testing/selftests/bpf/prog_tests/ |
| H A D | task_local_storage.c | 289 value.nested.udata = &udata; in test_uptr_basic() 334 value.nested.udata = &udata2; in test_uptr_basic() 349 value.nested.udata = &udata2; in test_uptr_basic() 363 ASSERT_EQ(value.nested.udata, NULL, "value.nested.udata"); in test_uptr_basic() 372 value.nested.udata = &udata2; in test_uptr_basic()
|
| /linux/scripts/coccinelle/misc/ |
| H A D | irqf_oneshot.cocci | 106 …ING: Threaded IRQ with no primary handler requested without IRQF_ONESHOT (unless it is nested IRQ)" 112 …ING: Threaded IRQ with no primary handler requested without IRQF_ONESHOT (unless it is nested IRQ)"
|
| /linux/Documentation/driver-api/ |
| H A D | dpll.rst | 102 state (``DPLL_A_PIN_OPERSTATE``) attribute nested under the parent 132 Pins registered with a MUX-type pin provide user with additional nested 137 ``DPLL_CMD_PIN_GET`` would contain multiple pin-parent nested 154 on desired parent, with the use of ``DPLL_A_PIN_PARENT`` nested 159 ``DPLL_A_PIN_PARENT_PIN`` nested attribute for requesting configuration 181 ``DPLL_A_PIN_PARENT_DEVICE`` nested attribute for requesting configuration 232 ``DPLL_A_PIN_PARENT_DEVICE`` nested attribute for requesting 346 ``DPLL_A_PIN_REFERENCE_SYNC`` nested attribute for providing info or 439 ``DPLL_A_PIN_FREQUENCY_SUPPORTED`` nested attr provides supported 451 ``DPLL_A_PIN_PARENT_DEVICE`` nested attr for each parent device [all …]
|
| /linux/tools/verification/rv/include/ |
| H A D | rv.h | 10 int nested; member
|