| /openbmc/qemu/target/xtensa/core-dsp3400/ |
| H A D | core-matmap.h | 2 * xtensa/config/core-matmap.h -- Memory access and translation mapping
10 * information contained in the core-isa.h header file.
19 * XCHAL_ICACHE_SIZE (presence of I-cache)
20 * XCHAL_DCACHE_SIZE (presence of D-cache)
25 /* Copyright (c) 1999-2010 Tensilica Inc.
49 /*----------------------------------------------------------------------
51 ----------------------------------------------------------------------*/
54 /* Cache Attribute encodings -- lists of access modes for each cache attribute: */
108 * one is returned instead (eg. writethru instead of writeback,
112 #define XCHAL_CA_WRITETHRU 1 /* cache enabled (write-through) mode */
[all …]
|
| /openbmc/linux/arch/mips/include/asm/octeon/ |
| H A D | cvmx-l2c.h | 7 * Copyright (c) 2003-2017 Cavium, Inc.
14 * AS-IS and WITHOUT ANY WARRANTY; without even the implied warranty
21 * Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
44 #define CVMX_L2C_IDX_MASK (cvmx_l2c_get_num_sets() - 1)
52 /* Number of L2C Tag-and-data sections (TADs) that are connected to LMC. */
159 * Configure one of the four L2 Cache performance counters to capture event
183 * Return the L2 Cache way partitioning for a given core.
189 * -1 on error
199 * a way, while a 1 bit blocks the core from evicting any
200 * lines from that way. There must be at least one allowed
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/mux/ |
| H A D | mux-controller.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/mux/mux-controller.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Peter Rosin <peda@axentia.se>
13 A multiplexer (or mux) controller will have one, or several, consumer devices
15 several parallel multiplexers. Presumably there will be at least one
20 space is a simple zero-based enumeration. I.e. 0-1 for a 2-way multiplexer,
21 0-7 for an 8-way multiplexer, etc.
25 --------------------
[all …]
|
| /openbmc/linux/scripts/tracing/ |
| H A D | ftrace-bisect.sh | 2 # SPDX-License-Identifier: GPL-2.0
25 # The old (slow) way, for kernels before v5.1.
27 # [old-way] # cat available_filter_functions > ~/full-file
29 # [old-way] *** Note *** this process will take several minutes to update the
30 # [old-way] filters. Setting multiple functions is an O(n^2) operation, and we
31 # [old-way] are dealing with thousands of functions. So go have coffee, talk
32 # [old-way] with your coworkers, read facebook. And eventually, this operation
33 # [old-way] will end.
35 # The new way (using numbers) is an O(n) operation, and usually takes less than a second.
37 # seq `wc -l available_filter_functions | cut -d' ' -f1` > ~/full-file
[all …]
|
| /openbmc/linux/Documentation/filesystems/ |
| H A D | inotify.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 Inotify - A Powerful yet Simple File Change Notification System
13 - Deleted obsoleted interface, just refer to manpages for user interface.
29 What is the design decision behind using an-fd-per-instance as opposed to
30 an fd-per-watch?
33 An fd-per-watch quickly consumes more file descriptors than are allowed,
35 select()-able. Yes, root can bump the per-process fd limit and yes, users
38 spaces is thus sensible. The current design is what user-space developers
39 want: Users initialize inotify, once, and add n watches, requiring but one
41 thousand times is silly. If we can implement user-space's preferences
[all …]
|
| /openbmc/linux/Documentation/arch/ia64/ |
| H A D | efirtc.rst | 13 the IA-64 platform.
18 EFI provides 4 calls one can make once the OS is booted: GetTime(),
28 portable way, the CMOS clock. A program like /sbin/hwclock uses such a clock
31 Because we wanted to minimize the impact on existing user-level apps using
32 the CMOS clock, we decided to expose an API that was very similar to the one
38 EFI uses a slightly different way of representing the time, noticeably
39 the reference date is different. Year is the using the full 4-digit format.
41 expose this new way of representing time. Instead we use something very
43 One of the reasons for doing it this way is to allow for EFI to still evolve
47 The driver exposes two interfaces, one via the device file and a set of
[all …]
|
| /openbmc/linux/arch/nios2/mm/ |
| H A D | tlb.c | 22 ((((1UL << (cpuinfo.tlb_ptr_sz - cpuinfo.tlb_num_ways_log2))) - 1) \
42 * This one is only used for pages with the global bit set so we don't care
47 unsigned int way; in replace_tlb_one_pid() local
50 /* remember pid/way until we return. */ in replace_tlb_one_pid()
55 for (way = 0; way < cpuinfo.tlb_num_ways; way++) { in replace_tlb_one_pid()
60 tlbmisc = TLBMISC_RD | (way << TLBMISC_WAY_SHIFT); in replace_tlb_one_pid()
73 (way << TLBMISC_WAY_SHIFT); in replace_tlb_one_pid()
90 pr_debug("Flush tlb-entry for vaddr=%#lx\n", addr); in flush_tlb_one_pid()
97 pr_debug("Reload tlb-entry for vaddr=%#lx\n", addr); in reload_tlb_one_pid()
105 unsigned long mmu_pid = get_pid_from_context(&vma->vm_mm->context); in flush_tlb_range()
[all …]
|
| /openbmc/linux/Documentation/process/ |
| H A D | 2.Process.rst | 9 course of one year, the kernel has since had to evolve a number of
14 ---------------
16 The kernel developers use a loosely time-based release process, with a new
53 be called 5.6-rc1. The -rc1 release is the signal that the time to
63 exception is made for drivers for previously-unsupported hardware; if they
64 touch no in-tree code, they cannot cause regressions and should be safe to
67 As fixes make their way into the mainline, the patch rate will slow over
68 time. Linus releases new -rc kernels about once a week; a normal series
69 will get up to somewhere between -rc6 and -rc9 before the kernel is
78 September 30 5.4-rc1, merge window closes
[all …]
|
| H A D | stable-api-nonsense.rst | 8 Greg Kroah-Hartman <greg@kroah.com>
18 The kernel to userspace interface is the one that application programs use,
22 That interface is the one that users and application programmers can count
27 -----------------
38 -----
41 to worry about the in-kernel interfaces changing. For the majority of
55 discuss the binary stuff first to get it out of the way.
59 -----------------------
64 - Depending on the version of the C compiler you use, different kernel
71 - Depending on what kernel build options you select, a wide range of
[all …]
|
| H A D | 4.Coding.rst | 6 While there is much to be said for a solid and community-oriented design
19 ---------
25 :ref:`Documentation/process/coding-style.rst <codingstyle>`. For much of
38 strangely-formatted code.
43 giving up a degree of control in a number of ways - including control over
48 reformatting patches as a way of gaining familiarity with the process, or
49 as a way of getting their name into the kernel changelogs - or both. But
59 80-column limit, for example), just do it.
61 Note that you can also use the ``clang-format`` tool to help you with
62 these rules, to quickly re-format parts of your code automatically,
[all …]
|
| /openbmc/docs/designs/ |
| H A D | vpd-collection.md | 5 Created: 2019-06-11
9 On OpenBMC, Vital Product Data (VPD) collection is limited to only one or two
10 Field Replaceable Units (FRUs) today - one example is the BMC FRU. On OpenPower
11 systems, the BMC also supports just one VPD format, the [OpenPower VPD] [1]
18 - Some of the VPD information such as FRU part number, serial number need to be
21 - Several use cases on the BMC require that the applications decide on a certain
26 - There are use cases for the BMC to send VPD data to the host
31 of certain parameters of the FRU (atypical - for FRUs that do not have an
39 Essentially, the IPZ VPD structure consists of key-value pairs called keywords.
47 laid out one after another.
[all …]
|
| /openbmc/linux/Documentation/driver-api/pci/ |
| H A D | p2pdma.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 PCI Peer-to-Peer DMA Support
9 called Peer-to-Peer (or P2P). However, there are a number of issues that
10 make P2P transactions tricky to do in a perfectly safe way.
12 One of the biggest issues is that PCI doesn't require forwarding
15 simple way to determine if a given Root Complex supports this or not.
36 * Provider - A driver which provides or publishes P2P resources like
38 * Client - A driver which makes use of a resource by setting up a
40 * Orchestrator - A driver which orchestrates the flow of data between
59 one could imagine slight tweaks to this that would allow for the same
[all …]
|
| /openbmc/linux/Documentation/arch/x86/ |
| H A D | microcode.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 :Authors: - Fenghua Yu <fenghua.yu@intel.com>
8 - Borislav Petkov <bp@suse.de>
9 - Ashok Raj <ashok.raj@intel.com>
13 updating the microcode on platforms beyond the OEM End-Of-Life support,
14 and updating the microcode on long-running systems without rebooting.
39 During BSP (BootStrapping Processor) boot (pre-SMP), the kernel
56 if [ -z "$1" ]; then
66 rm -rf $TMPDIR
70 mkdir -p $DSTDIR
[all …]
|
| /openbmc/qemu/docs/devel/migration/ |
| H A D | main.rst | 14 two times. I.e. it can only restore the state in one guest that has
15 the same devices that the one it was saved (this last requirement can
20 requested: migration. This means that QEMU is able to start in one
26 can take a while to move all state from one machine to another. Live
41 - tcp migration: do the migration using tcp sockets
42 - unix migration: do the migration using unix sockets
43 - exec migration: do the migration using the stdin/stdout through a process.
44 - fd migration: do the migration using a file descriptor that is
46 - file migration: do the migration using a file that is passed to QEMU
54 (see add-fd QMP command documentation). This method allows a
[all …]
|
| H A D | compatibility.rst | 5 ---------------------------------
10 The difficult one is when they are different versions.
15 - QEMU version
16 - machine type version
20 - qemu-system-x86_64 (v5.2), from now on qemu-5.2.
21 - qemu-system-x86_64 (v5.1), from now on qemu-5.1.
26 - pc-q35-5.2 (newer one in qemu-5.2) from now on pc-5.2
27 - pc-q35-5.1 (newer one in qemu-5.1) from now on pc-5.1
40 1 - qemu-5.2 -M pc-5.2 -> migrates to -> qemu-5.2 -M pc-5.2
45 2 - qemu-5.1 -M pc-5.1 -> migrates to -> qemu-5.1 -M pc-5.1
[all …]
|
| /openbmc/linux/Documentation/input/devices/ |
| H A D | rotary-encoder.rst | 2 rotary-encoder - a generic driver for GPIO connected devices
8 --------
11 peripherals with two wires. The outputs are phase-shifted by 90 degrees
16 a stable state with both outputs high (half-period mode) and some have
17 a stable state in all steps (quarter-period mode).
33 |<-------->|
34 one step
36 |<-->|
37 one step (half-period mode)
40 one step (quarter-period mode)
[all …]
|
| /openbmc/linux/Documentation/power/ |
| H A D | pci.rst | 13 power management refer to Documentation/driver-api/pm/devices.rst and
27 1.1. Native and Platform-Based Power Management
28 -----------------------------------------------
30 In general, power management is a feature allowing one to save energy by putting
31 devices into states in which they draw less power (low-power states) at the
34 Usually, a device is put into a low-power state when it is underutilized or
36 again, it has to be put back into the "fully functional" state (full-power
41 PCI devices may be put into low-power states in two ways, by using the device
46 specific value into one of its standard configuration registers. The second
53 to put the device that sent it into the full-power state. However, the PCI Bus
[all …]
|
| /openbmc/linux/Documentation/timers/ |
| H A D | no_hz.rst | 2 NO_HZ: Reducing Scheduling-Clock Ticks
7 reduce the number of scheduling-clock interrupts, thereby improving energy
9 some types of computationally intensive high-performance computing (HPC)
10 applications and for real-time applications.
12 There are three main ways of managing scheduling-clock interrupts
13 (also known as "scheduling-clock ticks" or simply "ticks"):
15 1. Never omit scheduling-clock ticks (CONFIG_HZ_PERIODIC=y or
16 CONFIG_NO_HZ=n for older kernels). You normally will -not-
19 2. Omit scheduling-clock ticks on idle CPUs (CONFIG_NO_HZ_IDLE=y or
23 3. Omit scheduling-clock ticks on CPUs that are either idle or that
[all …]
|
| /openbmc/linux/Documentation/admin-guide/acpi/ |
| H A D | ssdt-overlays.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 In order to support ACPI open-ended hardware configurations (e.g. development
8 boards) we need a way to augment the ACPI configuration provided by the firmware
18 way to augment firmware ACPI configuration is by dynamically loading
59 ASL Optimizing Compiler version 20140214-64 [Mar 29 2014]
60 Copyright (c) 2000 - 2014 Intel Corporation
62 ASL Input: minnomax.asl - 30 lines, 614 bytes, 7 keywords
63 AML Output: minnowmax.aml - 165 bytes, 6 named objects, 1 executable opcodes
67 The resulting AML code can then be loaded by the kernel using one of the methods
76 It works in a similar way with initrd based ACPI tables override/upgrade: SSDT
[all …]
|
| /openbmc/qemu/target/xtensa/core-de233_fpu/ |
| H A D | core-matmap.h | 2 * xtensa/config/core-matmap.h -- Memory access and translation mapping
10 * information contained in the core-isa.h header file.
19 * XCHAL_ICACHE_SIZE (presence of I-cache)
20 * XCHAL_DCACHE_SIZE (presence of D-cache)
25 /* Copyright (c) 1999-2020 Tensilica Inc.
49 /*----------------------------------------------------------------------
51 ----------------------------------------------------------------------*/
55 /* Cache Attribute encodings -- lists of access modes for each cache attribute: */
113 * one is returned instead (eg. writethru instead of writeback,
117 #define XCHAL_CA_WRITETHRU 11 /* cache enabled (write-through) mode */
[all …]
|
| /openbmc/linux/Documentation/arch/arm/ |
| H A D | interrupts.rst | 5 2.5.2-rmk5:
7 major architecture-specific subsystems.
9 Firstly, it contains some pretty major changes to the way we handle the
10 MMU TLB. Each MMU TLB variant is now handled completely separately -
18 The 2.5 kernels will be having major changes to the way IRQs are handled.
26 SA1100 ------------> Neponset -----------> SA1111
28 -----------> USAR
30 -----------> SMC9196
32 The way stuff currently works, all SA1111 interrupts are mutually
33 exclusive of each other - if you're processing one interrupt from the
[all …]
|
| /openbmc/linux/Documentation/driver-api/media/ |
| H A D | v4l2-event.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 -----------
6 The V4L2 events provide a generic way to pass events to user space.
9 Events are subscribed per-filehandle. An event specification consists of a
18 struct is added to :c:type:`v4l2_fh`\ ``.subscribed``, one for every
28 generating lots of events of one type in a short time, then that will
31 But if you get more events of one type than the size of the
33 and the new one added.
47 - struct v4l2_fh has two lists: one of the ``subscribed`` events,
48 and one of the ``available`` events.
[all …]
|
| /openbmc/qemu/docs/specs/ |
| H A D | ivshmem-spec.rst | 2 Device Specification for Inter-VM shared memory device
5 The Inter-VM shared memory device (ivshmem) is designed to share a
12 can obtain one from an ivshmem server.
27 --------
31 - BAR0 holds device registers (256 Byte MMIO)
32 - BAR1 holds MSI-X table and PBA (only ivshmem-doorbell)
33 - BAR2 maps the shared memory object
37 - If you only need the shared memory part, BAR2 suffices. This way,
41 - If you additionally need the capability for peers to interrupt each
50 IVPosition register (described below) to become non-negative before
[all …]
|
| /openbmc/linux/sound/soc/google/ |
| H A D | chv3-i2s.c | 1 // SPDX-License-Identifier: GPL-2.0-only
9 * The I2S interface consists of two ring buffers - one for RX and one for
11 * on which way the data is flowing, either the software or the hardware
16 * (see chv3_dma_ack). This seems to be the only way to reliably obtain
21 * will wait for the consumer index to move out of the way. With playback,
24 * would have to wait for the consumer index to move out of the way by
25 * busy-waiting, which would keep stalling the kernel for quite a long time.
28 * is one frame behind what it actually is (see chv3_dma_pointer). This
29 * way, ALSA will not try to fill up the entire buffer, and all callbacks
30 * are wait-free.
[all …]
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/User/Ldap/ |
| H A D | Config.interface.yaml | 3 User.Ldap.Config interface on one or more objects must implement
7 - name: LDAPServerURI
12 - xyz.openbmc_project.Common.Error.InternalFailure
13 - xyz.openbmc_project.Common.Error.InvalidArgument
14 - xyz.openbmc_project.Common.Error.NoCACertificate
15 - name: LDAPBindDN
21 - xyz.openbmc_project.Common.Error.InternalFailure
22 - xyz.openbmc_project.Common.Error.InvalidArgument
23 - name: LDAPBindDNPassword
29 on the D-bus object itself. Implementation can use the given value and
[all …]
|