Home
last modified time | relevance | path

Searched refs:topology (Results 1 – 25 of 49) sorted by relevance

12

/f-stack/freebsd/x86/x86/
H A Dmp_x86.c685 struct topo_analysis topology; in cpu_mp_announce() local
688 if (topo_analyze(&topo_root, 1, &topology)) { in cpu_mp_announce()
690 if (topology.entities[TOPO_LEVEL_GROUP] > 1) in cpu_mp_announce()
692 topology.entities[TOPO_LEVEL_GROUP]); in cpu_mp_announce()
696 if (topology.entities[TOPO_LEVEL_CORE] > 0) in cpu_mp_announce()
698 topology.entities[TOPO_LEVEL_CORE]); in cpu_mp_announce()
701 topology.entities[TOPO_LEVEL_THREAD]); in cpu_mp_announce()
711 topology.entities[TOPO_LEVEL_PKG]); in cpu_mp_announce()
714 topology.entities[TOPO_LEVEL_GROUP]); in cpu_mp_announce()
718 if (topology.entities[TOPO_LEVEL_CORE] > 0) in cpu_mp_announce()
[all …]
/f-stack/freebsd/contrib/device-tree/Bindings/cpu/
H A Dcpu-topology.txt2 CPU topology binding description
25 CPU topology bindings allow one to associate cpu nodes with hierarchical groups
29 Currently, only ARM/RISC-V intend to use this cpu topology binding but it may be
35 A topology description containing phandles to cpu nodes that are not compliant
42 The ARM/RISC-V CPU topology is defined within the cpu-map node, which is a direct
43 child of the cpus node and provides a container where the actual topology
48 Usage: Optional - On SMP systems provide CPUs topology to the OS.
49 Uniprocessor systems do not require a topology
54 subnodes describe the CPU topology.
76 The nodes describing the CPU topology (socket/cluster/core/thread) can
[all …]
/f-stack/freebsd/contrib/openzfs/etc/zfs/
H A Dvdev_id.conf.sas_switch.example1 topology sas_switch
H A Dvdev_id.conf.scsi.example2 topology scsi
H A Dvdev_id.conf.sas_direct.example2 topology sas_direct
/f-stack/freebsd/amd64/vmm/
H A Dvmm_dev.c384 struct vm_cpu_topology *topology; in vmmdev_ioctl() local
844 topology = (struct vm_cpu_topology *)data; in vmmdev_ioctl()
845 error = vm_set_topology(sc->vm, topology->sockets, in vmmdev_ioctl()
846 topology->cores, topology->threads, topology->maxcpus); in vmmdev_ioctl()
849 topology = (struct vm_cpu_topology *)data; in vmmdev_ioctl()
850 vm_get_topology(sc->vm, &topology->sockets, &topology->cores, in vmmdev_ioctl()
851 &topology->threads, &topology->maxcpus); in vmmdev_ioctl()
/f-stack/freebsd/contrib/device-tree/Bindings/fsi/
H A Dfsi.txt15 Under the masters' nodes, we can describe the bus topology using nodes to
19 /* top-level of FSI bus topology, bound to an FSI master driver and
39 Note that since the bus is probe-able, some (or all) of the topology may
52 Since the master nodes describe the top-level of the FSI topology, they also
/f-stack/freebsd/contrib/device-tree/Bindings/memory-controllers/
H A Dcalxeda-ddr-ctrlr.yaml12 purposes and to learn about the DRAM topology.
/f-stack/freebsd/contrib/device-tree/Bindings/mips/img/
H A Dpistachio.txt13 A CPU sub-node is also required for at least CPU 0. Since the topology may
/f-stack/freebsd/contrib/device-tree/Bindings/arm/
H A Dpsci.yaml114 power topology of the system. Individual nodes in a topology have their
118 CPU topology, must conform to the binding in [3]. The idle states
H A Dcoresight-cti.yaml13 a star topology via the Cross Trigger Matrix (CTM), which is not programmable.
25 CTIs are interconnected in a star topology via the CTM, using a number of
27 described in the DEVID register. The star topology is not required to be
H A Dvexpress-sysreg.txt65 topology properties - see main vexpress node documentation for more
/f-stack/freebsd/contrib/device-tree/Bindings/openrisc/opencores/
H A Dor1ksim.txt18 A CPU sub-node is also required for at least CPU 0. Since the topology may
/f-stack/freebsd/contrib/device-tree/Bindings/hwmon/
H A Dcirrus,lochnagar.yaml17 Audio system topology, clocking and power can all be controlled through
/f-stack/freebsd/contrib/device-tree/Bindings/sound/
H A Dcirrus,lochnagar.yaml17 Audio system topology, clocking and power can all be controlled through
/f-stack/freebsd/contrib/device-tree/Bindings/
H A Dnuma.txt15 topology information to OS.
63 4 nodes connected in mesh/ring topology as below,
/f-stack/dpdk/doc/guides/howto/
H A Dpvp_reference_benchmark.rst57 cat /sys/devices/system/cpu/cpu*[0-9]/topology/thread_siblings_list \
246 <topology sockets='1' cores='3' threads='1'/>
337 --portmask=3 --forward-mode=macswap --port-topology=chained \
/f-stack/freebsd/contrib/device-tree/Bindings/dma/
H A Drenesas,shdma.txt5 the same configuration. To describe this topology we require all compatible
/f-stack/dpdk/doc/guides/nics/
H A Dpcap_ring.rst144 -- --port-topology=chained
152 -- --port-topology=chained
160 -- --port-topology=chained
208 -- --port-topology=chained --no-flush-rx
/f-stack/freebsd/contrib/device-tree/Bindings/phy/
H A Dphy-miphy365x.txt17 nodes to describe the controller's topology. These nodes
H A Dphy-mtk-xsphy.txt29 the controller's topology.
H A Dphy-miphy28lp.txt15 nodes to describe the controller's topology. These nodes
/f-stack/freebsd/contrib/device-tree/Bindings/clock/
H A Dcirrus,lochnagar.yaml17 Audio system topology, clocking and power can all be controlled through
/f-stack/freebsd/contrib/device-tree/Bindings/i2c/
H A Di2c-mux-gpmux.txt45 in more detail in Documentation/i2c/i2c-topology.rst.
/f-stack/freebsd/contrib/openzfs/cmd/vdev_id/
H A Dvdev_id108 -g Storage network topology [default="$TOPOLOGY"]

12