Skip to content
This repository was archived by the owner on Nov 11, 2024. It is now read-only.

Commit e33a778

Browse files
JeevakaPrabuJeevakaPrabu
committed
Merge branch 'chromium_v5.4.121' into HEAD
Signed-off-by: Jeevaka Prabu Badrappan <jeevaka.badrappan@intel.com>
2 parents 0cd81be + 82a39b5 commit e33a778

1,623 files changed

Lines changed: 66891 additions & 18107 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

‎Documentation/ABI/testing/sysfs-class-intel_pmt‎

Lines changed: 119 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,119 @@
1+
What: /sys/class/intel_pmt/
2+
Date: October 2020
3+
KernelVersion: 5.10
4+
Contact: David Box <david.e.box@linux.intel.com>
5+
Description:
6+
The intel_pmt/ class directory contains information for
7+
devices that expose hardware telemetry using Intel Platform
8+
Monitoring Technology (PMT)
9+
10+
What: /sys/class/intel_pmt/telem<x>
11+
Date: October 2020
12+
KernelVersion: 5.10
13+
Contact: David Box <david.e.box@linux.intel.com>
14+
Description:
15+
The telem<x> directory contains files describing an instance of
16+
a PMT telemetry device that exposes hardware telemetry. Each
17+
telem<x> directory has an associated telem file. This file
18+
may be opened and mapped or read to access the telemetry space
19+
of the device. The register layout of the telemetry space is
20+
determined from an XML file that matches the PCI device id and
21+
GUID for the device.
22+
23+
What: /sys/class/intel_pmt/telem<x>/telem
24+
Date: October 2020
25+
KernelVersion: 5.10
26+
Contact: David Box <david.e.box@linux.intel.com>
27+
Description:
28+
(RO) The telemetry data for this telemetry device. This file
29+
may be mapped or read to obtain the data.
30+
31+
What: /sys/class/intel_pmt/telem<x>/guid
32+
Date: October 2020
33+
KernelVersion: 5.10
34+
Contact: David Box <david.e.box@linux.intel.com>
35+
Description:
36+
(RO) The GUID for this telemetry device. The GUID identifies
37+
the version of the XML file for the parent device that is to
38+
be used to get the register layout.
39+
40+
What: /sys/class/intel_pmt/telem<x>/size
41+
Date: October 2020
42+
KernelVersion: 5.10
43+
Contact: David Box <david.e.box@linux.intel.com>
44+
Description:
45+
(RO) The size of telemetry region in bytes that corresponds to
46+
the mapping size for the telem file.
47+
48+
What: /sys/class/intel_pmt/telem<x>/offset
49+
Date: October 2020
50+
KernelVersion: 5.10
51+
Contact: David Box <david.e.box@linux.intel.com>
52+
Description:
53+
(RO) The offset of telemetry region in bytes that corresponds to
54+
the mapping for the telem file.
55+
56+
What: /sys/class/intel_pmt/crashlog<x>
57+
Date: October 2020
58+
KernelVersion: 5.10
59+
Contact: Alexander Duyck <alexander.h.duyck@linux.intel.com>
60+
Description:
61+
The crashlog<x> directory contains files for configuring an
62+
instance of a PMT crashlog device that can perform crash data
63+
recording. Each crashlog<x> device has an associated crashlog
64+
file. This file can be opened and mapped or read to access the
65+
resulting crashlog buffer. The register layout for the buffer
66+
can be determined from an XML file of specified GUID for the
67+
parent device.
68+
69+
What: /sys/class/intel_pmt/crashlog<x>/crashlog
70+
Date: October 2020
71+
KernelVersion: 5.10
72+
Contact: David Box <david.e.box@linux.intel.com>
73+
Description:
74+
(RO) The crashlog buffer for this crashlog device. This file
75+
may be mapped or read to obtain the data.
76+
77+
What: /sys/class/intel_pmt/crashlog<x>/guid
78+
Date: October 2020
79+
KernelVersion: 5.10
80+
Contact: Alexander Duyck <alexander.h.duyck@linux.intel.com>
81+
Description:
82+
(RO) The GUID for this crashlog device. The GUID identifies the
83+
version of the XML file for the parent device that should be
84+
used to determine the register layout.
85+
86+
What: /sys/class/intel_pmt/crashlog<x>/size
87+
Date: October 2020
88+
KernelVersion: 5.10
89+
Contact: Alexander Duyck <alexander.h.duyck@linux.intel.com>
90+
Description:
91+
(RO) The length of the result buffer in bytes that corresponds
92+
to the size for the crashlog buffer.
93+
94+
What: /sys/class/intel_pmt/crashlog<x>/offset
95+
Date: October 2020
96+
KernelVersion: 5.10
97+
Contact: Alexander Duyck <alexander.h.duyck@linux.intel.com>
98+
Description:
99+
(RO) The offset of the buffer in bytes that corresponds
100+
to the mapping for the crashlog device.
101+
102+
What: /sys/class/intel_pmt/crashlog<x>/enable
103+
Date: October 2020
104+
KernelVersion: 5.10
105+
Contact: Alexander Duyck <alexander.h.duyck@linux.intel.com>
106+
Description:
107+
(RW) Boolean value controlling if the crashlog functionality
108+
is enabled for the crashlog device.
109+
110+
What: /sys/class/intel_pmt/crashlog<x>/trigger
111+
Date: October 2020
112+
KernelVersion: 5.10
113+
Contact: Alexander Duyck <alexander.h.duyck@linux.intel.com>
114+
Description:
115+
(RW) Boolean value controlling the triggering of the crashlog
116+
device node. When read it provides data on if the crashlog has
117+
been triggered. When written to it can be used to either clear
118+
the current trigger by writing false, or to trigger a new
119+
event if the trigger is not currently set.

‎Documentation/ABI/testing/sysfs-class-net‎

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -301,3 +301,18 @@ Contact: netdev@vger.kernel.org
301301
Description:
302302
32-bit unsigned integer counting the number of times the link has
303303
been down
304+
305+
What: /sys/class/net/<iface>/threaded
306+
Date: Jan 2021
307+
KernelVersion: 5.12
308+
Contact: netdev@vger.kernel.org
309+
Description:
310+
Boolean value to control the threaded mode per device. User could
311+
set this value to enable/disable threaded mode for all napi
312+
belonging to this device, without the need to do device up/down.
313+
314+
Possible values:
315+
== ==================================
316+
0 threaded mode disabled for this dev
317+
1 threaded mode enabled for this dev
318+
== ==================================

‎Documentation/admin-guide/kernel-parameters.txt‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3161,9 +3161,9 @@
31613161
[X86,PV_OPS] Disable paravirtualized VMware scheduler
31623162
clock and use the default one.
31633163

3164-
no-steal-acc [X86,KVM] Disable paravirtualized steal time accounting.
3165-
steal time is computed, but won't influence scheduler
3166-
behaviour
3164+
no-steal-acc [X86,KVM,ARM64] Disable paravirtualized steal time
3165+
accounting. steal time is computed, but won't
3166+
influence scheduler behaviour
31673167

31683168
nolapic [X86-32,APIC] Do not enable or use the local APIC.
31693169

‎Documentation/arm/memory.rst‎

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -45,9 +45,14 @@ fffe8000 fffeffff DTCM mapping area for platforms with
4545
fffe0000 fffe7fff ITCM mapping area for platforms with
4646
ITCM mounted inside the CPU.
4747

48-
ffc00000 ffefffff Fixmap mapping region. Addresses provided
48+
ffc80000 ffefffff Fixmap mapping region. Addresses provided
4949
by fix_to_virt() will be located here.
5050

51+
ffc00000 ffc7ffff Guard region
52+
53+
ff800000 ffbfffff Permanent, fixed read-only mapping of the
54+
firmware provided DT blob
55+
5156
fee00000 feffffff Mapping of PCI I/O space. This is a static
5257
mapping within the vmalloc space.
5358

Documentation/DMA-API-HOWTO.txt renamed to Documentation/core-api/dma-api-howto.rst

File renamed without changes.

0 commit comments

Comments
 (0)