Skip to content

Commit

Permalink
Merge tag 'v6.1-rc7' into iommufd.git for-next
Browse files Browse the repository at this point in the history
Resolve conflicts in drivers/vfio/vfio_main.c by using the iommfd version.
The rc fix was done a different way when iommufd patches reworked this
code.

Signed-off-by: Jason Gunthorpe <[email protected]>
  • Loading branch information
jgunthorpe committed Dec 2, 2022
2 parents 169dd5c + b7b275e commit 90337f5
Show file tree
Hide file tree
Showing 1,245 changed files with 49,278 additions and 43,055 deletions.
3 changes: 3 additions & 0 deletions .mailmap
Original file line number Diff line number Diff line change
Expand Up @@ -29,6 +29,7 @@ Alexandre Belloni <[email protected]> <alexandre.belloni@free-electr
Alexei Starovoitov <[email protected]> <[email protected]>
Alexei Starovoitov <[email protected]> <[email protected]>
Alexei Starovoitov <[email protected]> <[email protected]>
Alex Hung <[email protected]> <[email protected]>
Alex Shi <[email protected]> <[email protected]>
Alex Shi <[email protected]> <[email protected]>
Alex Shi <[email protected]> <[email protected]>
Expand Down Expand Up @@ -382,6 +383,7 @@ Santosh Shilimkar <[email protected]>
Santosh Shilimkar <[email protected]>
Sarangdhar Joshi <[email protected]>
Sascha Hauer <[email protected]>
Satya Priya <[email protected]> <[email protected]>
S.Çağlar Onur <[email protected]>
Sean Christopherson <[email protected]> <[email protected]>
Sean Nyekjaer <[email protected]> <[email protected]>
Expand Down Expand Up @@ -416,6 +418,7 @@ TripleX Chung <[email protected]> <[email protected]>
TripleX Chung <[email protected]> <[email protected]>
Tsuneo Yoshioka <[email protected]>
Tycho Andersen <[email protected]> <[email protected]>
Tzung-Bi Shih <[email protected]> <[email protected]>
Uwe Kleine-König <[email protected]>
Uwe Kleine-König <[email protected]>
Uwe Kleine-König <[email protected]>
Expand Down
9 changes: 9 additions & 0 deletions CREDITS
Original file line number Diff line number Diff line change
Expand Up @@ -918,6 +918,11 @@ S: Ottawa, Ontario
S: K1N 6Z9
S: CANADA

N: Vivien Didelot
E: [email protected]
D: DSA framework and MV88E6XXX driver
S: Montreal, Quebec, Canada

N: Jeff Dike
E: [email protected]
W: http://user-mode-linux.sourceforge.net
Expand Down Expand Up @@ -2447,6 +2452,10 @@ S: 482 Shadowgraph Dr.
S: San Jose, CA 95110
S: USA

N: Michal Marek
E: [email protected]
D: Kbuild Maintainer 2009-2017

N: Martin Mares
E: [email protected]
W: http://www.ucw.cz/~mj/
Expand Down
11 changes: 11 additions & 0 deletions Documentation/admin-guide/kernel-parameters.txt
Original file line number Diff line number Diff line change
Expand Up @@ -6959,3 +6959,14 @@
memory, and other data can't be written using
xmon commands.
off xmon is disabled.

amd_pstate= [X86]
disable
Do not enable amd_pstate as the default
scaling driver for the supported processors
passive
Use amd_pstate as a scaling driver, driver requests a
desired performance on this abstract scale and the power
management firmware translates the requests into actual
hardware states (core frequency, data fabric and memory
clocks etc.)
30 changes: 13 additions & 17 deletions Documentation/admin-guide/pm/amd-pstate.rst
Original file line number Diff line number Diff line change
Expand Up @@ -283,23 +283,19 @@ efficiency frequency management method on AMD processors.
Kernel Module Options for ``amd-pstate``
=========================================

.. _shared_mem:

``shared_mem``
Use a module param (shared_mem) to enable related processors manually with
**amd_pstate.shared_mem=1**.
Due to the performance issue on the processors with `Shared Memory Support
<perf_cap_>`_, we disable it presently and will re-enable this by default
once we address performance issue with this solution.

To check whether the current processor is using `Full MSR Support <perf_cap_>`_
or `Shared Memory Support <perf_cap_>`_ : ::

ray@hr-test1:~$ lscpu | grep cppc
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid aperfmperf rapl pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 x2apic movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_llc mwaitx cpb cat_l3 cdp_l3 hw_pstate ssbd mba ibrs ibpb stibp vmmcall fsgsbase bmi1 avx2 smep bmi2 erms invpcid cqm rdt_a rdseed adx smap clflushopt clwb sha_ni xsaveopt xsavec xgetbv1 xsaves cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local clzero irperf xsaveerptr rdpru wbnoinvd cppc arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif v_spec_ctrl umip pku ospke vaes vpclmulqdq rdpid overflow_recov succor smca fsrm

If the CPU flags have ``cppc``, then this processor supports `Full MSR Support
<perf_cap_>`_. Otherwise, it supports `Shared Memory Support <perf_cap_>`_.
Passive Mode
------------

``amd_pstate=passive``

It will be enabled if the ``amd_pstate=passive`` is passed to the kernel in the command line.
In this mode, ``amd_pstate`` driver software specifies a desired QoS target in the CPPC
performance scale as a relative number. This can be expressed as percentage of nominal
performance (infrastructure max). Below the nominal sustained performance level,
desired performance expresses the average performance level of the processor subject
to the Performance Reduction Tolerance register. Above the nominal performance level,
processor must provide at least nominal performance requested and go higher if current
operating conditions allow.


``cpupower`` tool support for ``amd-pstate``
Expand Down
8 changes: 8 additions & 0 deletions Documentation/arm64/booting.rst
Original file line number Diff line number Diff line change
Expand Up @@ -340,6 +340,14 @@ Before jumping into the kernel, the following conditions must be met:
- SMCR_EL2.LEN must be initialised to the same value for all CPUs the
kernel will execute on.

- HWFGRTR_EL2.nTPIDR2_EL0 (bit 55) must be initialised to 0b01.

- HWFGWTR_EL2.nTPIDR2_EL0 (bit 55) must be initialised to 0b01.

- HWFGRTR_EL2.nSMPRI_EL1 (bit 54) must be initialised to 0b01.

- HWFGWTR_EL2.nSMPRI_EL1 (bit 54) must be initialised to 0b01.

For CPUs with the Scalable Matrix Extension FA64 feature (FEAT_SME_FA64)

- If EL3 is present:
Expand Down
38 changes: 37 additions & 1 deletion Documentation/arm64/cpu-feature-registers.rst
Original file line number Diff line number Diff line change
Expand Up @@ -92,7 +92,7 @@ operation if the source belongs to the supported system register space.

The infrastructure emulates only the following system register space::

Op0=3, Op1=0, CRn=0, CRm=0,4,5,6,7
Op0=3, Op1=0, CRn=0, CRm=0,2,3,4,5,6,7

(See Table C5-6 'System instruction encodings for non-Debug System
register accesses' in ARMv8 ARM DDI 0487A.h, for the list of
Expand Down Expand Up @@ -293,6 +293,42 @@ infrastructure:
| WFXT | [3-0] | y |
+------------------------------+---------+---------+

10) MVFR0_EL1 - AArch32 Media and VFP Feature Register 0

+------------------------------+---------+---------+
| Name | bits | visible |
+------------------------------+---------+---------+
| FPDP | [11-8] | y |
+------------------------------+---------+---------+

11) MVFR1_EL1 - AArch32 Media and VFP Feature Register 1

+------------------------------+---------+---------+
| Name | bits | visible |
+------------------------------+---------+---------+
| SIMDFMAC | [31-28] | y |
+------------------------------+---------+---------+
| SIMDSP | [19-16] | y |
+------------------------------+---------+---------+
| SIMDInt | [15-12] | y |
+------------------------------+---------+---------+
| SIMDLS | [11-8] | y |
+------------------------------+---------+---------+

12) ID_ISAR5_EL1 - AArch32 Instruction Set Attribute Register 5

+------------------------------+---------+---------+
| Name | bits | visible |
+------------------------------+---------+---------+
| CRC32 | [19-16] | y |
+------------------------------+---------+---------+
| SHA2 | [15-12] | y |
+------------------------------+---------+---------+
| SHA1 | [11-8] | y |
+------------------------------+---------+---------+
| AES | [7-4] | y |
+------------------------------+---------+---------+


Appendix I: Example
-------------------
Expand Down
1 change: 1 addition & 0 deletions Documentation/dev-tools/kmsan.rst
Original file line number Diff line number Diff line change
Expand Up @@ -67,6 +67,7 @@ uninitialized in the local variable, as well as the stack where the value was
copied to another memory location before use.

A use of uninitialized value ``v`` is reported by KMSAN in the following cases:

- in a condition, e.g. ``if (v) { ... }``;
- in an indexing or pointer dereferencing, e.g. ``array[v]`` or ``*v``;
- when it is copied to userspace or hardware, e.g. ``copy_to_user(..., &v, ...)``;
Expand Down
29 changes: 21 additions & 8 deletions Documentation/devicetree/bindings/hwlock/qcom-hwspinlock.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -15,9 +15,22 @@ description:

properties:
compatible:
enum:
- qcom,sfpb-mutex
- qcom,tcsr-mutex
oneOf:
- enum:
- qcom,sfpb-mutex
- qcom,tcsr-mutex
- items:
- enum:
- qcom,apq8084-tcsr-mutex
- qcom,ipq6018-tcsr-mutex
- qcom,msm8226-tcsr-mutex
- qcom,msm8994-tcsr-mutex
- const: qcom,tcsr-mutex
- items:
- enum:
- qcom,msm8974-tcsr-mutex
- const: qcom,tcsr-mutex
- const: syscon

reg:
maxItems: 1
Expand All @@ -34,9 +47,9 @@ additionalProperties: false

examples:
- |
tcsr_mutex: hwlock@1f40000 {
compatible = "qcom,tcsr-mutex";
reg = <0x01f40000 0x40000>;
#hwlock-cells = <1>;
};
hwlock@1f40000 {
compatible = "qcom,tcsr-mutex";
reg = <0x01f40000 0x40000>;
#hwlock-cells = <1>;
};
...
Original file line number Diff line number Diff line change
Expand Up @@ -62,13 +62,6 @@ properties:
description:
Inform the driver that last channel will be used to sensor battery.

aspeed,trim-data-valid:
type: boolean
description: |
The ADC reference voltage can be calibrated to obtain the trimming
data which will be stored in otp. This property informs the driver that
the data store in the otp is valid.
required:
- compatible
- reg
Expand Down
5 changes: 4 additions & 1 deletion Documentation/devicetree/bindings/input/goodix,gt7375p.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -16,8 +16,11 @@ description:

properties:
compatible:
items:
oneOf:
- const: goodix,gt7375p
- items:
- const: goodix,gt7986u
- const: goodix,gt7375p

reg:
enum:
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ properties:
oneOf:
- items:
- enum:
- qcom,sc7280-bwmon
- qcom,sc7280-cpu-bwmon
- qcom,sdm845-bwmon
- const: qcom,msm8998-bwmon
- const: qcom,msm8998-bwmon # BWMON v4
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -36,13 +36,17 @@ properties:
resets:
maxItems: 1

iommus:
maxItems: 1

required:
- compatible
- reg
- interrupts
- clocks
- clock-names
- resets
- iommus

additionalProperties: false

Expand All @@ -59,6 +63,7 @@ examples:
clocks = <&ccu CLK_BUS_VP9>, <&ccu CLK_VP9>;
clock-names = "bus", "mod";
resets = <&ccu RST_BUS_VP9>;
iommus = <&iommu 5>;
};
...
2 changes: 1 addition & 1 deletion Documentation/devicetree/bindings/net/engleder,tsnep.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -47,7 +47,7 @@ properties:

nvmem-cells: true

nvmem-cells-names: true
nvmem-cell-names: true

phy-connection-type:
enum:
Expand Down
3 changes: 3 additions & 0 deletions Documentation/devicetree/bindings/power/fsl,imx-gpcv2.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -81,6 +81,9 @@ properties:

power-supply: true

power-domains:
maxItems: 1

resets:
description: |
A number of phandles to resets that need to be asserted during
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ title: Audio codec controlled by ChromeOS EC

maintainers:
- Cheng-Yi Chiang <[email protected]>
- Tzung-Bi Shih <tzungbi@google.com>
- Tzung-Bi Shih <tzungbi@kernel.org>

description: |
Google's ChromeOS EC codec is a digital mic codec provided by the
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ $schema: http://devicetree.org/meta-schemas/core.yaml#
title: Realtek rt1015p codec devicetree bindings

maintainers:
- Tzung-Bi Shih <tzungbi@google.com>
- Tzung-Bi Shih <tzungbi@kernel.org>

description: |
Rt1015p is a rt1015 variant which does not support I2C and
Expand Down
1 change: 1 addition & 0 deletions Documentation/driver-api/driver-model/devres.rst
Original file line number Diff line number Diff line change
Expand Up @@ -279,6 +279,7 @@ GPIO
devm_gpio_request_one()

I2C
devm_i2c_add_adapter()
devm_i2c_new_dummy_device()

IIO
Expand Down
5 changes: 2 additions & 3 deletions Documentation/driver-api/miscellaneous.rst
Original file line number Diff line number Diff line change
Expand Up @@ -16,12 +16,11 @@ Parallel Port Devices
16x50 UART Driver
=================

.. kernel-doc:: drivers/tty/serial/serial_core.c
:export:

.. kernel-doc:: drivers/tty/serial/8250/8250_core.c
:export:

See serial/driver.rst for related APIs.

Pulse-Width Modulation (PWM)
============================

Expand Down
10 changes: 10 additions & 0 deletions Documentation/kbuild/reproducible-builds.rst
Original file line number Diff line number Diff line change
Expand Up @@ -119,6 +119,16 @@ To avoid this, you can make the vDSO different for different
kernel versions by including an arbitrary string of "salt" in it.
This is specified by the Kconfig symbol ``CONFIG_BUILD_SALT``.

Git
---

Uncommitted changes or different commit ids in git can also lead
to different compilation results. For example, after executing
``git reset HEAD^``, even if the code is the same, the
``include/config/kernel.release`` generated during compilation
will be different, which will eventually lead to binary differences.
See ``scripts/setlocalversion`` for details.

.. _KBUILD_BUILD_TIMESTAMP: kbuild.html#kbuild-build-timestamp
.. _KBUILD_BUILD_USER and KBUILD_BUILD_HOST: kbuild.html#kbuild-build-user-kbuild-build-host
.. _KCFLAGS: kbuild.html#kcflags
Expand Down
2 changes: 1 addition & 1 deletion Documentation/kernel-hacking/hacking.rst
Original file line number Diff line number Diff line change
Expand Up @@ -120,7 +120,7 @@ You can tell you are in a softirq (or tasklet) using the
.. warning::

Beware that this will return a false positive if a
:ref:`botton half lock <local_bh_disable>` is held.
:ref:`bottom half lock <local_bh_disable>` is held.

Some Basic Rules
================
Expand Down
2 changes: 1 addition & 1 deletion Documentation/networking/generic_netlink.rst
Original file line number Diff line number Diff line change
Expand Up @@ -6,4 +6,4 @@ Generic Netlink

A wiki document on how to use Generic Netlink can be found here:

* http://www.linuxfoundation.org/collaborate/workgroups/networking/generic_netlink_howto
* https://wiki.linuxfoundation.org/networking/generic_netlink_howto
15 changes: 4 additions & 11 deletions Documentation/process/2.Process.rst
Original file line number Diff line number Diff line change
Expand Up @@ -126,17 +126,10 @@ than one development cycle past their initial release. So, for example, the
5.2.21 was the final stable update of the 5.2 release.

Some kernels are designated "long term" kernels; they will receive support
for a longer period. As of this writing, the current long term kernels
and their maintainers are:

====== ================================ =======================
3.16 Ben Hutchings (very long-term kernel)
4.4 Greg Kroah-Hartman & Sasha Levin (very long-term kernel)
4.9 Greg Kroah-Hartman & Sasha Levin
4.14 Greg Kroah-Hartman & Sasha Levin
4.19 Greg Kroah-Hartman & Sasha Levin
5.4 Greg Kroah-Hartman & Sasha Levin
====== ================================ =======================
for a longer period. Please refer to the following link for the list of active
long term kernel versions and their maintainers:

https://www.kernel.org/category/releases.html

The selection of a kernel for long-term support is purely a matter of a
maintainer having the need and the time to maintain that release. There
Expand Down
2 changes: 1 addition & 1 deletion Documentation/process/code-of-conduct-interpretation.rst
Original file line number Diff line number Diff line change
Expand Up @@ -51,7 +51,7 @@ the Technical Advisory Board (TAB) or other maintainers if you're
uncertain how to handle situations that come up. It will not be
considered a violation report unless you want it to be. If you are
uncertain about approaching the TAB or any other maintainers, please
reach out to our conflict mediator, Joanna Lee <[email protected]>.
reach out to our conflict mediator, Joanna Lee <[email protected]>.

In the end, "be kind to each other" is really what the end goal is for
everybody. We know everyone is human and we all fail at times, but the
Expand Down
Loading

0 comments on commit 90337f5

Please sign in to comment.