/openbmc/linux/tools/testing/selftests/tc-testing/creating-testcases/ |
H A D | AddingTestCases.txt | 12 Include the 'id' field, but do not assign a value. Running tdc with the -i
|
/openbmc/linux/arch/arc/boot/dts/ |
H A D | hsdk.dts | 103 /* 64-bit Global Free Running Counter */
|
/openbmc/openbmc-test-automation/openpower/ext_interfaces/ |
H A D | test_client_identifier.robot | 188 ${ip_address}= Get Running System IP
|
/openbmc/phosphor-host-ipmid/docs/ |
H A D | testing.md | 1 # Running Tests 119 ## Building and Running 444 ## Quickly Running At Home
|
/openbmc/linux/Documentation/bpf/ |
H A D | s390.rst | 127 4. Running the test suite
|
/openbmc/u-boot/doc/ |
H A D | README.memory-test | 29 - It is terribly slow. Running "mtest" on the whole system RAM
|
/openbmc/qemu/docs/system/riscv/ |
H A D | microchip-icicle-kit.rst | 63 Running HSS
|
/openbmc/openbmc/poky/meta/classes/ |
H A D | useradd_base.bbclass | 59 bbnote "${PN}: Running groupmems command with group $groupname and user $username"
|
/openbmc/openbmc/meta-arm/meta-arm-bsp/documentation/corstone1000/ |
H A D | user-guide.rst | 284 Running the software on FPGA 326 Running the software on FVP 374 **NOTE**: Running the SystemReady-IR tests described below requires the user to 829 Running the FVP with the IR prebuilt image 840 Running the FPGA with the IR prebuilt image 1291 instructions in `Running the software on FVP`_ section to boot Linux in FVP 1329 Running the software on FVP on Windows or AArch64 Linux
|
/openbmc/openbmc/poky/documentation/dev-manual/ |
H A D | qemu.rst | 40 Running QEMU 177 Running Under a Network File System (NFS) Server 245 into QEMU in the ``runqemu`` script. Running ``qemu -cpu help`` returns a
|
/openbmc/linux/Documentation/dev-tools/kunit/ |
H A D | faq.rst | 80 3. Running the UML kernel directly can often reveal issues or error messages,
|
/openbmc/linux/Documentation/scheduler/ |
H A D | schedutil.rst | 35 Using this we track 2 key metrics: 'running' and 'runnable'. 'Running'
|
/openbmc/phosphor-logging/ |
H A D | log_manager.cpp | 367 if (hostState != Host::HostState::Running) in checkAndQuiesceHost()
|
/openbmc/openbmc-test-automation/openpower/ras/ |
H A D | ras_utils.robot | 68 Is Host Running
|
/openbmc/openbmc/poky/documentation/sdk-manual/ |
H A D | working-projects.rst | 146 project. Running the command prints the architecture on which the 217 Running the
|
H A D | using.rst | 124 Running the SDK Environment Setup Script
|
/openbmc/openbmc-test-automation/lib/ |
H A D | dump_utils.robot | 287 # "TaskState": "Running", 311 # "TaskState": "Running",
|
/openbmc/linux/Documentation/admin-guide/pm/ |
H A D | intel-speed-select.rst | 592 # Running 'sched/pipe' benchmark: 692 # Running 'sched/pipe' benchmark: 812 # Running 'sched/pipe' benchmark: 925 # Running 'sched/pipe' benchmark:
|
/openbmc/linux/Documentation/power/powercap/ |
H A D | powercap.rst | 15 example, the intel-rapl control type represents the Intel "Running Average
|
/openbmc/linux/Documentation/fb/ |
H A D | vesafb.rst | 88 XF68_FBDev should work just fine, but it is non-accelerated. Running
|
/openbmc/docs/development/ |
H A D | devtool-hello-world.md | 82 ## Loading an Application Directly Into a Running QEMU
|
/openbmc/linux/Documentation/virt/kvm/x86/ |
H A D | nested-vmx.rst | 37 Running nested VMX
|
/openbmc/openbmc-test-automation/redfish/task_service/ |
H A D | test_tasks_service.robot | 114 # "TaskState": "Running",
|
/openbmc/linux/Documentation/devicetree/bindings/ |
H A D | writing-schema.rst | 139 Running checks
|
/openbmc/openbmc/poky/meta/classes-recipe/ |
H A D | autotools.bbclass | 100 bbnote "Running $cfgscript ${CONFIGUREOPTS} ${EXTRA_OECONF} $@"
|