Searched full:physical (Results 1 – 25 of 796) sorted by relevance
12345678910>>...32
| /Documentation/userspace-api/media/cec/ |
| D | cec-ioc-adap-g-phys-addr.rst | 15 CEC_ADAP_G_PHYS_ADDR, CEC_ADAP_S_PHYS_ADDR - Get or set the physical address
40 To query the current physical address applications call
42 driver stores the physical address.
44 To set a new physical address applications store the physical address in
52 To clear an existing physical address use ``CEC_PHYS_ADDR_INVALID``.
60 A :ref:`CEC_EVENT_STATE_CHANGE <CEC-EVENT-STATE-CHANGE>` event is sent when the physical address
63 The physical address is a 16-bit number where each group of 4 bits
64 represent a digit of the physical address a.b.c.d where the most
69 is supported. The physical address a device shall use is stored in the
73 different physical address of the form a.0.0.0 that the sources will
[all …]
|
| /Documentation/admin-guide/mm/ |
| D | concepts.rst | 12 address to a physical address.
19 The physical memory in a computer system is a limited resource and
21 the amount of memory that can be installed. The physical memory is not
27 All this makes dealing directly with physical memory quite complex and
30 The virtual memory abstracts the details of physical memory from the
32 physical memory (demand paging) and provides a mechanism for the
38 address encoded in that instruction to a `physical` address that the
41 The physical system memory is divided into page frames, or pages. The
47 Each physical memory page can be mapped as one or more virtual
49 translation from a virtual address used by programs to the physical
[all …]
|
| /Documentation/mm/ |
| D | memory-model.rst | 4 Physical Memory Model
7 Physical memory in a system may be addressed in different ways. The
8 simplest case is when the physical memory starts at address 0 and
20 All the memory models track the status of physical page frames using
24 mapping between the physical page frame number (PFN) and the
35 non-NUMA systems with contiguous, or mostly contiguous, physical
39 maps the entire physical memory. For most architectures, the holes
49 actual physical pages. In such case, the architecture specific
58 systems with physical memory starting at address different from 0.
65 as hot-plug and hot-remove of the physical memory, alternative memory
[all …]
|
| D | page_tables.rst | 13 Page tables map virtual addresses as seen by the CPU into physical addresses
20 The physical address corresponding to the virtual address is often referenced
21 by the underlying physical page frame. The **page frame number** or **pfn**
22 is the physical address of the page (as seen on the external memory bus)
25 Physical memory address 0 will be *pfn 0* and the highest pfn will be
26 the last page of physical memory the external address bus of the CPU can
41 the fact that Torvald's first computer had 4MB of physical memory. Entries in
56 to a physical memory range, which allows mapping a contiguous range of several
58 shortcuts in mapping virtual memory to physical memory: there is no need to
89 mapping a single page of virtual memory to a single page of physical memory.
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-devices-system-xen_cpu | 5 A collection of global/individual Xen physical cpu attributes
7 Individual physical cpu attributes are contained in
16 Interface to online/offline Xen physical cpus
19 to online/offline physical cpus, except cpu0 due to several
|
| D | sysfs-firmware-efi | 4 Description: It shows the physical address of firmware vendor field in the
11 Description: It shows the physical address of runtime service table entry in
18 Description: It shows the physical address of config table entry in the EFI
25 Description: Displays the physical addresses of all EFI Configuration
|
| D | sysfs-memory-page-offline | 6 Soft-offline the memory page containing the physical address
8 physical address of the page. The kernel will then attempt
28 Hard-offline the memory page containing the physical
30 specifying the physical address of the page. The
|
| D | sysfs-class-net-grcan | 7 Hardware configuration of physical interface 0. This file reads
19 Hardware configuration of physical interface 1. This file reads
31 Configuration of which physical interface to be used. Possible
|
| D | sysfs-devices-sun | 11 the slot number printed on the physical slot whenever possible."
13 So reading the sysfs file, we can identify a physical position
|
| D | sysfs-kernel-vmcoreinfo | 8 Shows physical address and size of vmcoreinfo ELF note.
9 First value contains physical address of note in hex and
|
| /Documentation/admin-guide/RAS/ |
| D | address-translation.rst | 10 physical memory. Devices attached to the Fabric, like memory controllers,
11 I/O, etc., may not have a complete view of the system physical memory map.
12 These devices may provide a "normalized", i.e. device physical, address
14 a system physical address for the kernel to action on the memory.
|
| /Documentation/i2c/ |
| D | i2c-sysfs.rst | 13 is a gap of knowledge to map from the I2C bus physical number and MUX topology
16 the concept of logical I2C buses in the kernel, by knowing the physical I2C
41 start with ``i2c-`` are I2C buses, which may be either physical or logical. The
59 (Physical) I2C Bus Controller
63 physical I2C bus controllers. The controllers are hardware and physical, and the
70 I2C Bus Physical Number
73 For each physical I2C bus controller, the system vendor may assign a physical
82 written upon virtual memory space, instead of physical memory space.
84 Each logical I2C bus may be an abstraction of a physical I2C bus controller, or
90 Physical I2C Bus
[all …]
|
| /Documentation/networking/device_drivers/ethernet/mellanox/mlx5/ |
| D | counters.rst | 78 Physical port counters
82 additional counters like flow control, FEC and more. Physical port counters
86 A set of the physical port counters, per priority per port.
496 software counters. These packets are counted by physical port and vPort
518 physical port and vPort counters. You may open more rx queues and spread
534 counted by physical port and vPort counters.
544 are counted by physical port and vPort counters.
889 Physical Port Counters
891 The physical port counters are the counters on the external port connecting the
896 .. flat-table:: Physical Port Counter Table
[all …]
|
| /Documentation/admin-guide/device-mapper/ |
| D | vdo.rst | 108 If <hash>, <logical>, and <physical> are all set to 0, the work handled by
144 physical:
148 enough to have at least 1 slab per physical thread. The
178 modifiable parameters are <logical device size>, <physical device size>,
181 If the logical device size or physical device size are changed, upon
184 size may not exceed 4 PB. The physical device size must increase by at
187 slab size is chosen: the physical device size may never increase above the
194 physical space, storing to /dev/dm-1 which has more than 1 GB of space.
209 Grow the physical size to 2 GB.
217 Grow the physical size by 1 GB more and increase max discard sectors.
[all …]
|
| D | vdo-design.rst | 248 Each slab is independent of every other. They are assigned to "physical
249 zones" in round-robin fashion. If there are P physical zones, then slab n
257 how full it is. During recovery, each physical zone will attempt to recover
266 The block map contains the logical to physical mapping. It can be thought
268 36 bits of which contain the physical block number which holds the data for
305 new physical mappings. For a block map remapping, the journal records the
306 block map page number and the physical block allocated for it. Block map
311 before each journal block write to ensure that the physical data for the
317 reconstruct the logical to physical mappings after an unexpected
369 missing, it is allocated at this time out of the same physical storage
[all …]
|
| /Documentation/arch/xtensa/ |
| D | booting.rst | 12 address must be the physical address.
19 virtual or physical address. In either case it must be within the default
20 virtual mapping. It is considered physical if it is within the range of
21 physical addresses covered by the default KSEG mapping (XCHAL_KSEG_PADDR..
|
| /Documentation/arch/arm/ |
| D | porting.rst | 12 virtual address to a physical address. Normally, it is simply:
22 virtual or physical addresses here, since the MMU will be off at
43 Physical address to place the initial RAM disk. Only relevant if
54 Physical address of the struct param_struct or tag list, giving the
62 Physical start address of the first bank of RAM.
66 boot phase, virtual address PAGE_OFFSET will be mapped to physical
113 `pram` specifies the physical start address of RAM. Must always
116 `pio` is the physical address of an 8MB region containing IO for
|
| /Documentation/core-api/ |
| D | debugging-via-ohci1394.rst | 2 Using physical DMA provided by OHCI-1394 FireWire controllers for debugging
11 a "Physical Response Unit" which executes specific requests by employing
16 physical system memory and, for read requests, send the result of
17 the physical memory read back to the requester.
26 of physical address space. This can be a problem on machines where memory is
31 physical addresses above 4 GB, but this feature is currently not enabled by
43 The firewire-ohci driver in drivers/firewire uses filtered physical
45 Pass the remote_dma=1 parameter to the driver to get unfiltered physical DMA.
81 disable all physical DMA on each bus reset.
107 controller implements a writable Physical Upper Bound register. This is
[all …]
|
| /Documentation/userspace-api/media/mediactl/ |
| D | media-controller-model.rst | 16 physical hardware devices (CMOS sensor for instance), logical
18 processing pipeline), DMA channels or physical connectors.
27 inputs. Pads should not be confused with physical pins at chip
40 physical module, meaning this lens controller drives the lens for this
|
| /Documentation/virt/geniezone/ |
| D | introduction.rst | 27 VM manager aims to provide vCPUs on the basis of time sharing on physical
33 Direct use of physical memory from VMs is forbidden and designed to be
59 hypervisor with the help of gzvm module, both virtual and physical ones.
60 In case there's no guest VM running, physical interrupts are handled by host
77 The vcpu component is the core of virtualizing an aarch64 physical CPU, and it
|
| /Documentation/arch/powerpc/ |
| D | kasan.txt | 47 - We'd like to place it near the start of physical memory. In theory we can do
48 this at run-time based on how much physical memory we have, but this requires
54 requires knowing how much contiguous physical memory a system has _at compile
56 to handle discontiguous physical memory, total failure to boot on machines
|
| /Documentation/admin-guide/kdump/ |
| D | vmcoreinfo.rst | 59 virtual to physical addresses.
66 direct kernel map to a physical address.
77 Physical addresses are translated to struct pages by treating them as
78 an index into the mem_map array. Right-shifting a physical address
105 Defines the maximum supported physical address space memory.
348 corresponding physical address.
354 to physical addresses. The init_top_pgt is somewhat similar to
393 mask. This is used to remove the SME mask and obtain the true physical
411 Denotes whether physical address extensions are enabled. It has the cost
414 crash kernel when converting virtual addresses to physical addresses.
[all …]
|
| /Documentation/devicetree/bindings/iommu/ |
| D | apple,sart.yaml | 14 physical memory must be added to the SART's allow list before any
20 and allows 36 bit of physical address space and filter entries with sizes
23 SART2, first seen in A14 and M1, allows 36 bit of physical address space
|
| /Documentation/sound/designs/ |
| D | jack-injection.rst | 15 machine and plug/unplug physical devices to the audio jack.
17 In this design, an audio jack doesn't equal to a physical audio jack.
18 Sometimes a physical audio jack contains multi functions, and the
20 ``snd_jack`` represents a physical audio jack and the ``jack_kctl``
21 represents a function, for example a physical jack has two functions:
118 …read-only, get snd_jack's supported events from type (all supported events on the physical audio j…
|
| /Documentation/virt/kvm/loongarch/ |
| D | hypercalls.rst | 77 - a1: Lower part of the bitmap for destination physical CPUIDs
78 - a2: Higher part of the bitmap for destination physical CPUIDs
79 - a3: The lowest physical CPUID in the bitmap
85 Bit 0 of a1 corresponds to the physical CPUID in the third input register (a3)
86 and bit 1 corresponds to the physical CPUID in a3+1, and so on.
|
12345678910>>...32