Al Viro writes:
> OTTH, it's not really needed there - see vfs.git #work.audit
> for (untested) turning that sucker non-blocking. I hadn't tried
> a followup that would get rid of the entire AVC_NONBLOCKING thing yet,
> but I suspect that it should simplify the things in there nicely...
I went
On 1/13/21 6:37 PM, Sean Christopherson wrote:
Replace calls to svm_sev_enabled() with direct checks on sev_enabled, or
in the case of svm_mem_enc_op, simply drop the call to svm_sev_enabled().
This effectively replaces checks against a valid max_sev_asid with checks
against sev_enabled.
On Thu, Jan 14, 2021 at 2:47 PM Paul Moore wrote:
>
> On Tue, Jan 12, 2021 at 12:15 PM Paul Moore wrote:
> >
> > On Fri, Jan 8, 2021 at 5:22 PM Lokesh Gidra wrote:
> > >
> > > Userfaultfd in unprivileged contexts could be potentially very
> > > useful. We'd like to harden userfaultfd to make
Il 14/01/21 23:44, Jeffrey Hugo ha scritto:
On Thu, Jan 14, 2021 at 3:40 PM AngeloGioacchino Del Regno
wrote:
Il 14/01/21 23:33, Jeffrey Hugo ha scritto:
On Thu, Jan 14, 2021 at 3:13 PM AngeloGioacchino Del Regno
wrote:
Il 14/01/21 23:12, Jeffrey Hugo ha scritto:
On Sat, Jan 9, 2021 at
This is similar to commit b21ebf2fb4cd ("x86: Treat R_X86_64_PLT32 as
R_X86_64_PC32"), but for i386. As far as Linux kernel is concerned,
R_386_PLT32 can be treated the same as R_386_PC32.
R_386_PC32/R_X86_64_PC32 are PC-relative relocation types with the
requirement that the symbol address is
On Tue, Jan 12, 2021 at 12:15 PM Paul Moore wrote:
>
> On Fri, Jan 8, 2021 at 5:22 PM Lokesh Gidra wrote:
> >
> > Userfaultfd in unprivileged contexts could be potentially very
> > useful. We'd like to harden userfaultfd to make such unprivileged use
> > less risky. This patch series allows
Tyrel,
I think this patch series is looking pretty good. I don't think we need
to wait for resolution of the can_queue issue being discussed, since
that is an issue that exists prior to this patch series and this patch
series doesn't make the issue any worse. Let's work that separately.
Thanks,
This is basically a revert of commit 644592d32837 ("objtool: Fail the
kernel build on fatal errors").
That change turned out to be more trouble than it's worth. Failing the
build is an extreme measure which sometimes gets too much attention and
blocks CI build testing.
These fatal-type warnings
Hi Stephen,
On Fri, Jan 15, 2021 at 09:23:01AM +1100, Stephen Rothwell wrote:
> Hi all,
>
> In commit
>
> c339b3aec780 ("power: supply: cpcap-battery: Fix missing
> power_supply_put()")
>
> Fixes tag
>
> Fixes: b0134cc14b9 ("power: supply: cpcap-battery: Fix handling of lowered
>
Reviewed-by: Brian King
--
Brian King
Power Linux I/O
IBM Linux Technology Center
Hi Stephen,
On Fri, Jan 15, 2021 at 06:39:35AM +1100, Stephen Rothwell wrote:
> In commit
>
> e1cc2d7d3868 ("power: supply: bq256xx: Fix BQ256XX_NUM_WD_VAL and
> bq256xx_watchdog_time[] overrun")
>
> Fixes tag
>
> Fixes: 32e4978bb92 ("power: supply: bq256xx: Introduce the BQ256XX charger
On Thu, Jan 14, 2021 at 3:40 PM AngeloGioacchino Del Regno
wrote:
>
> Il 14/01/21 23:33, Jeffrey Hugo ha scritto:
> > On Thu, Jan 14, 2021 at 3:13 PM AngeloGioacchino Del Regno
> > wrote:
> >>
> >> Il 14/01/21 23:12, Jeffrey Hugo ha scritto:
> >>> On Sat, Jan 9, 2021 at 6:47 AM AngeloGioacchino
On Thu, 14 Jan 2021 at 18:56, Christian König wrote:
> Unfortunately not of hand.
>
> I also don't see any bug reports from other people and can't reproduce
> the last backtrace you send out TTM here.
Because only the most desperate will install kernels with enabled
debug flags and then load the
On Wed, Jan 13, 2021 at 6:30 AM AngeloGioacchino Del Regno
wrote:
>
> Il 13/01/21 03:41, Rob Herring ha scritto:
> > On Mon, Jan 11, 2021 at 07:29:28PM +0100, AngeloGioacchino Del Regno wrote:
> >> Add bindings for the Awinic AW9523/AW9523B I2C GPIO Expander driver.
> >>
> >> Signed-off-by:
Reviewed-by: Brian King
--
Brian King
Power Linux I/O
IBM Linux Technology Center
On Thu, Jan 14, 2021 at 7:54 PM Mickaël Salaün wrote:
> On 14/01/2021 04:22, Jann Horn wrote:
> > On Wed, Dec 9, 2020 at 8:28 PM Mickaël Salaün wrote:
> >> Thanks to the Landlock objects and ruleset, it is possible to identify
> >> inodes according to a process's domain. To enable an
Hello:
This pull request was applied to netdev/net.git (refs/heads/master):
On Thu, 14 Jan 2021 12:05:51 -0800 you wrote:
> Hi!
>
> We have a few fixes for long standing issues, in particular
> Eric's fix to not underestimate the skb sizes, and my fix for
> brokenness of register_netdevice()
Il 14/01/21 23:33, Jeffrey Hugo ha scritto:
On Thu, Jan 14, 2021 at 3:13 PM AngeloGioacchino Del Regno
wrote:
Il 14/01/21 23:12, Jeffrey Hugo ha scritto:
On Sat, Jan 9, 2021 at 6:47 AM AngeloGioacchino Del Regno
wrote:
This clock enables the GPLL0 output to the multimedia subsystem
clock
On 1/14/21 3:19 PM, Arnd Bergmann wrote:
On Thu, Jan 14, 2021 at 7:07 PM Pierre-Louis Bossart
wrote:
On 1/14/21 9:09 AM, Arnd Bergmann wrote:
On Tue, Jan 12, 2021 at 9:32 PM Arnd Bergmann wrote:
---
v2: fix various build issues in the first version, now passes
all randconfig builds
On Thu, Jan 14, 2021 at 3:13 PM AngeloGioacchino Del Regno
wrote:
>
> The GPU IOMMU depends on this clock and the hypervisor will crash
> the SoC if this clock gets disabled because the secure contexts
> that have been set on this IOMMU by the bootloader will become
> unaccessible (or they get
On Thu, 14 Jan 2021 13:37:17 -0800 Linus Torvalds wrote:
> On Thu, Jan 14, 2021 at 12:05 PM Jakub Kicinski wrote:
> >
> > Current release - regressions:
> > ...
> > Current release - always broken:
>
> So I understand what you mean, but it does sound odd with that
> "Current release - always
On Thu, Jan 14, 2021 at 3:13 PM AngeloGioacchino Del Regno
wrote:
>
> Il 14/01/21 23:12, Jeffrey Hugo ha scritto:
> > On Sat, Jan 9, 2021 at 6:47 AM AngeloGioacchino Del Regno
> > wrote:
> >>
> >> This clock enables the GPLL0 output to the multimedia subsystem
> >> clock controller.
> >>
> >>
On Wed, Jan 13, 2021 at 11:46:45PM +0100, Andreas Kemnade wrote:
> On Tue, 12 Jan 2021 20:39:02 +0100
> Andreas Kemnade wrote:
>
> [...]
> > > +static int ntxec_pwm_probe(struct platform_device *pdev)
[...]
> > Hmm, I needed
> > chip->dev = >dev.parent to use the backlight example
> > in patch
On Thu, Jan 14, 2021 at 04:24:15PM -0600, Josh Poimboeuf wrote:
> Thanks to a recent binutils change which doesn't generate unused
> symbols, it's now possible for thunk_64.o be completely empty with
> CONFIG_PREEMPTION: no text, no data, no symbols.
>
> We could edit the Makefile to only build
On Tue, Dec 15, 2020 at 4:23 PM Daniel Latypov wrote:
>
> Commit fadb08e7c750 ("kunit: Support for Parameterized Testing")
> introduced support but lacks documentation for how to use it.
>
> This patch builds on commit 1f0e943df68a ("Documentation: kunit: provide
> guidance for testing many
Rob Herring 於 2021年1月15日 週五 上午3:11寫道：
>
> On Mon, 11 Jan 2021 15:43:37 +0800, Yongqiang Niu wrote:
> > add description for postmask
> > postmask is used control round corner for display frame
> >
> > Signed-off-by: Yongqiang Niu
> > ---
> >
Thanks to a recent binutils change which doesn't generate unused
symbols, it's now possible for thunk_64.o be completely empty with
CONFIG_PREEMPTION: no text, no data, no symbols.
We could edit the Makefile to only build that file when
CONFIG_PREEMPTION is enabled, but that will likely create
On Wed, Jan 13, 2021 at 07:33:37PM +0100, AngeloGioacchino Del Regno wrote:
> From: Konrad Dybcio
>
> The upstream API for some reason uses logbase2 instead of
> just passing the argument as-is, whereas downstream CAF
> kernel does the latter.
>
> Hence, a mistake has been made when porting:
>
On Wed, Jan 13, 2021 at 07:33:38PM +0100, AngeloGioacchino Del Regno wrote:
> From: Konrad Dybcio
>
> Port over the command from downstream to prevent undefined
> behaviour.
Reviewed-by: Jordan Crouse
> Signed-off-by: Konrad Dybcio
> Signed-off-by: AngeloGioacchino Del Regno
>
> ---
>
On Wed, Jan 13, 2021 at 07:33:39PM +0100, AngeloGioacchino Del Regno wrote:
> From: Konrad Dybcio
>
> Port over the command from downstream to prevent undefined
> behaviour.
Reviewed-by: Jordan Crouse
> Signed-off-by: Konrad Dybcio
> Signed-off-by: AngeloGioacchino Del Regno
>
> ---
>
On Wed, Dec 2, 2020 at 11:09 AM Daniel Latypov wrote:
>
> * Stop leaking file objects.
> * Use self.addCleanup() to ensure we call cleanup functions even if
> setUp() fails.
> * use mock.patch.stopall instead of more error-prone manual approach
>
> Signed-off-by: Daniel Latypov
Tested-by:
Hi all,
In commit
c339b3aec780 ("power: supply: cpcap-battery: Fix missing power_supply_put()")
Fixes tag
Fixes: b0134cc14b9 ("power: supply: cpcap-battery: Fix handling of lowered
charger voltage")
has these problem(s):
- Target SHA1 does not exist
Maybe you meant
Fixes:
On Wed, Dec 2, 2020 at 11:09 AM Daniel Latypov wrote:
>
> Use self.assertEqual/assertNotEqual() instead.
> Besides being more appropriate in a unit test, it'll also give a better
> error message by show the unexpected values.
>
> Also
> * Delete redundant check of exception types.
5fdc7db644 ("module: setup load info before module_sig_check()")
moved the ELF setup, so that it was done before the signature
check. This made the module name available to signature error
messages.
However, the checks for ELF correctness in setup_load_info
are not sufficient to prevent bad
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 65f0d2414b7079556fbbcc070b3d1c9f9587606d
commit: 0cd1ad2d7fd41e0de4969fd1dd0aa846c99830d1 iwlwifi: move all
bus-independent TX functions to common code
date: 4 months ago
config:
So-recently a bunch of laptops on the market have started using DPCD
backlight controls instead of the traditional DDI backlight controls.
Originally we thought we had this handled by adding VESA backlight
control support to i915, but the story ended up being a lot more
complicated then that.
On Wed, Dec 2, 2020 at 11:09 AM Daniel Latypov wrote:
>
> The use of manual open() and .close() calls seems to be an attempt to
> keep the contents in scope.
> But Python doesn't restrict variables like that, so we can introduce new
> variables inside of a `with` and use them outside.
>
> Do so
Since we now support controlling panel backlights through DPCD using
both the standard VESA interface, and Intel's proprietary HDR backlight
interface, we should allow the user to be able to explicitly choose
between one or the other in the event that we're wrong about panels
reliably reporting
This reverts commit 0883ce8146ed6074c76399f4e70dbed788582e12. Originally
these quirks were added because of the issues with using the eDP
backlight interfaces on certain laptop panels, which made it impossible
to properly probe for DPCD backlight support without having a whitelist
for panels that
Currently, every different type of backlight hook that i915 supports is
pretty straight forward - you have a backlight, probably through PWM
(but maybe DPCD), with a single set of platform-specific hooks that are
used for controlling it.
HDR backlights, in particular VESA and Intel's HDR
In the next commit where we split PWM related backlight functions from
higher-level backlight functions, we'll want to be able to retrieve the
backlight level for the current display panel from the
intel_panel_bl_funcs->setup() function using pwm_funcs->get(). Since
intel_panel_bl_funcs->setup()
On Wed, Dec 2, 2020 at 11:09 AM Daniel Latypov wrote:
>
> Also take this time to rename get_absolute_path() to test_data_path().
>
> 1. the name is currently a lie. It gives relative paths, e.g. if I run
> from the same dir as the test file, it gives './test_data/'
>
> See
On Mon, 11 Jan 2021 11:06:41 -0800
Stephen Boyd wrote:
> Quoting Stephen Boyd (2020-12-02 12:02:52)
> > This DT property can be 0, 16, and then 64, but not 32. The math here
> > doesn't recognize this slight bump in the power of 2 numbers and
> > translates a DT property of 64 into the register
On Wed, Jan 13, 2021 at 03:48:42PM +0100, Jessica Yu wrote:
>
>
[...]
> > + err = validate_section_offset(info, shdr);
> > + if (err < 0) {
> > + pr_err("Invalid ELF section in module
> > (section %u type %u)\n",
> > +
Il 14/01/21 23:12, Jeffrey Hugo ha scritto:
On Sat, Jan 9, 2021 at 6:47 AM AngeloGioacchino Del Regno
wrote:
This clock enables the GPLL0 output to the multimedia subsystem
clock controller.
Signed-off-by: AngeloGioacchino Del Regno
Any reason why you are not also adding the div_clk?
On 1/13/21 6:37 PM, Sean Christopherson wrote:
Move the allocation of the SEV VMCB array to sev.c to help pave the way
toward encapsulating SEV enabling wholly within sev.c.
No functional change intended.
Signed-off-by: Sean Christopherson
Reviewed-by: Tom Lendacky
---
Il 14/01/21 23:10, AngeloGioacchino Del Regno ha scritto:
This patch series fixes some issues with the MSM8998 clocks and, in
particular, brings a very important fix to the GCC PLLs.
These fixes are enhancing this SoC's stability and also makes it
possible to eventually enable the Adreno GPU
On Sat, Jan 9, 2021 at 6:47 AM AngeloGioacchino Del Regno
wrote:
>
> This clock enables the GPLL0 output to the multimedia subsystem
> clock controller.
>
> Signed-off-by: AngeloGioacchino Del Regno
>
Any reason why you are not also adding the div_clk?
Hardware clock gating is supported on some of the clocks declared in
there: ignoring that it does exist may lead to unstabilities on some
firmwares.
Add the HWCG registers where applicable to stop potential crashes.
This was verified on a smartphone shipped with a recent MSM8998
firmware, which
This GDSC enables (or cuts!) power to the Multimedia Subsystem IOMMU
(mmss smmu), which has bootloader pre-set secure contexts.
In the event of a complete power loss, the secure contexts will be
reset and the hypervisor will crash the SoC.
To prevent this, and get a working multimedia subsystem,
All of the GPLLs in the MSM8998 Global Clock Controller are Fabia PLLs
and not generic alphas: this was producing bad effects over the entire
clock tree of MSM8998, where any GPLL child clock was declaring a false
clock rate, due to their parent also showing the same.
The issue resides in the
Add new clock definition to gcc-msm8998 dt-bindings
Signed-off-by: AngeloGioacchino Del Regno
---
include/dt-bindings/clock/qcom,gcc-msm8998.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/dt-bindings/clock/qcom,gcc-msm8998.h
b/include/dt-bindings/clock/qcom,gcc-msm8998.h
index
This clock enables the GPLL0 output to the multimedia subsystem
clock controller.
Signed-off-by: AngeloGioacchino Del Regno
---
drivers/clk/qcom/gcc-msm8998.c | 17 +
1 file changed, 17 insertions(+)
diff --git a/drivers/clk/qcom/gcc-msm8998.c b/drivers/clk/qcom/gcc-msm8998.c
The GPU GX GDSC has GPU_GX_BCR reset and gfx3d_clk CXC, as stated
on downstream kernels (and as verified upstream, because otherwise
random lockups happen).
Also, add PWRSTS_RET and NO_RET_PERIPH: also as found downstream,
and also as verified here, to avoid GPU related lockups it is
necessary to
The pixel and byte clocks rate should not be cached, as a VCO shutdown
may clear the frequency setup and this may not be set again due to the
cached rate being present.
This will also be useful when shadow clocks will be implemented in
the DSI PLL for seamless timing/resolution switch.
The GPU IOMMU depends on this clock and the hypervisor will crash
the SoC if this clock gets disabled because the secure contexts
that have been set on this IOMMU by the bootloader will become
unaccessible (or they get reset).
Mark this clock as critical to avoid this issue when the Adreno
GPU is
Add new clock definition to gcc-msm8998 dt-bindings.
Signed-off-by: AngeloGioacchino Del Regno
---
include/dt-bindings/clock/qcom,gcc-msm8998.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/dt-bindings/clock/qcom,gcc-msm8998.h
b/include/dt-bindings/clock/qcom,gcc-msm8998.h
index
This patch series fixes some issues with the MSM8998 clocks and, in
particular, brings a very important fix to the GCC PLLs.
These fixes are enhancing this SoC's stability and also makes it
possible to eventually enable the Adreno GPU (with proper clock
scaling) and other components.
This patch
The GPU PLL0 is not a fixed PLL and the rate can be set on it:
this is necessary especially on boards which bootloader is setting
a very low rate on this PLL before booting Linux, which would be
unsuitable for postdividing to reach the maximum allowed Adreno GPU
frequency of 710MHz (or, actually,
To achieve CPR-Hardened functionality this clock must be on: add it
in order to be able to get it managed by the CPR3 driver.
Signed-off-by: AngeloGioacchino Del Regno
---
drivers/clk/qcom/gcc-msm8998.c | 20
1 file changed, 20 insertions(+)
diff --git
This patch deprecates f2fs_trace_io, since f2fs uses page->private more broadly,
resulting in more buggy cases.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/Kconfig | 10 ---
fs/f2fs/Makefile | 1 -
fs/f2fs/checkpoint.c | 3 -
fs/f2fs/data.c | 4 --
fs/f2fs/file.c | 2 -
On Thu, Jan 14, 2021 at 01:05:33PM -0800, Yonghong Song wrote:
>
>
> On 1/14/21 12:01 PM, Jiri Olsa wrote:
> > On Thu, Jan 14, 2021 at 10:56:33AM -0800, Yonghong Song wrote:
> > >
> > >
> > > On 1/14/21 5:40 AM, Jiri Olsa wrote:
> > > > It's possible to have other build id types (other than
On Thu, 14 Jan 2021 21:35:53 +
Chris Wilson wrote:
> Quoting Steven Rostedt (2021-01-14 21:32:06)
> > On reboot, one of my test boxes now triggers the following warning:
>
> 057fe3535eb3 ("drm/i915: Disable RPM wakeref assertions during driver
> shutdown")
> is included with the
On Thu, Jan 14, 2021 at 1:54 PM 'Fangrui Song' via Clang Built Linux
wrote:
>
> clang-12 -fno-pic (since
> https://github.com/llvm/llvm-project/commit/a084c0388e2a59b9556f2de008232da3f1d6)
> can emit `call __stack_chk_fail@PLT` instead of `call __stack_chk_fail`
> on x86. The two forms
The pull request you sent on Thu, 14 Jan 2021 13:52:41 -0700:
> git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest
> tags/linux-kselftest-fixes-5.11-rc4
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/146620506274bd24d52fb1c589110a30eed8240b
Thank
The pull request you sent on Thu, 14 Jan 2021 13:33:57 +0100 (CET):
> git://git.kernel.org/pub/scm/linux/kernel/git/hid/hid.git for-linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/2bbe17ae87938ca44756741ec77e3be76a4a0ea0
Thank you!
--
Deet-doot-dot, I am a
The pull request you sent on Thu, 14 Jan 2021 12:05:51 -0800:
> git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git tags/net-5.11-rc4
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/e8c13a6bc8ebbef7bd099ec1061633d1c9c94d5b
Thank you!
--
Deet-doot-dot, I am
Jarod Wilson wrote:
>On Wed, Jan 13, 2021 at 05:58:18PM -0800, Jakub Kicinski wrote:
>> On Wed, 13 Jan 2021 17:35:48 -0500 Jarod Wilson wrote:
>> > This comes from an end-user request, where they're running multiple VMs on
>> > hosts with bonded interfaces connected to some interest switch
On 12/30, Chao Yu wrote:
> ThreadA ThreadB
> - f2fs_ioc_start_atomic_write
> - write
> - f2fs_ioc_commit_atomic_write
> - f2fs_commit_inmem_pages
> - f2fs_drop_inmem_pages
> - f2fs_drop_inmem_pages
> - __revoke_inmem_pages
>
clang-12 -fno-pic (since
https://github.com/llvm/llvm-project/commit/a084c0388e2a59b9556f2de008232da3f1d6)
can emit `call __stack_chk_fail@PLT` instead of `call __stack_chk_fail`
on x86. The two forms should have identical behaviors on x86-64 but the
former causes GNU as<2.37 to produce an
On 1/14/21 3:37 PM, Brijesh Singh wrote:
On 1/13/21 6:37 PM, Sean Christopherson wrote:
Move the allocation of the SEV VMCB array to sev.c to help pave the way
toward encapsulating SEV enabling wholly within sev.c.
No functional change intended.
Signed-off-by: Sean Christopherson
---
On Thu, Jan 14, 2021 at 10:55 AM Jon Hunter wrote:
>
>
> On 14/01/2021 16:52, Saravana Kannan wrote:
>
> ...
>
> > Thanks! I think you forgot to enable those logs though. Also, while
> > you are at it, maybe enable the logs in device_link_add() too please?
>
>
> Sorry try this one.
>
> Cheers
>
On 14.01.21 17:04:24, Viresh Kumar wrote:
> Hello,
>
> The "oprofile" user-space tools don't use the kernel OPROFILE support
> any more, and haven't in a long time. User-space has been converted to
> the perf interfaces.
>
> Remove oprofile and dcookies (whose only user is oprofile) support from
From: Mahesh Kumar Kalikot Veetil
Modules with a large number of compilation units may be
exceeding AR and LD command argument list. Handle this gracefully by
writing the long argument list in a file. The command line options
read from file are inserted in place of the original @file option.
On 1/13/21 6:37 PM, Sean Christopherson wrote:
Query max_sev_asid directly after setting it instead of bouncing through
its wrapper, svm_sev_enabled(). Using the wrapper is unnecessary
obfuscation.
No functional change intended.
Signed-off-by: Sean Christopherson
Reviewed-by: Tom Lendacky
On 1/13/21 6:37 PM, Sean Christopherson wrote:
> Replace calls to svm_sev_enabled() with direct checks on sev_enabled, or
> in the case of svm_mem_enc_op, simply drop the call to svm_sev_enabled().
> This effectively replaces checks against a valid max_sev_asid with checks
> against sev_enabled.
On 1/13/21 6:37 PM, Sean Christopherson wrote:
> Remove the forward declaration of sev_flush_asids(), which is only a few
> lines above the function itself.
>
> No functional change intended.
>
> Signed-off-by: Sean Christopherson
> ---
> arch/x86/kvm/svm/sev.c | 1 -
> 1 file changed, 1
On Tue, 12 Jan 2021 05:59:44 +,
Samuel Holland wrote:
>
> Maintain bitmaps of wake-enabled IRQs and mux inputs, and program them
> to the hardware during the syscore phase of suspend and shutdown. Then
> restore the original set of enabled IRQs (only the NMI) during resume.
>
> This serves
Il 14/01/21 20:07, Rob Herring ha scritto:
On Sat, Jan 09, 2021 at 02:46:09PM +0100, AngeloGioacchino Del Regno wrote:
This clock enables the GPLL0 output to the multimedia subsystem
clock controller.
Signed-off-by: AngeloGioacchino Del Regno
---
drivers/clk/qcom/gcc-msm8998.c
On Thu, 14 Jan 2021 13:28:27 -0800
t...@redhat.com wrote:
> diff --git a/arch/x86/mm/mmio-mod.c b/arch/x86/mm/mmio-mod.c
> index bd7aff5c51f7..cd768dafca9e 100644
> --- a/arch/x86/mm/mmio-mod.c
> +++ b/arch/x86/mm/mmio-mod.c
> @@ -10,8 +10,6 @@
>
> #define pr_fmt(fmt) "mmiotrace: " fmt
>
>
On Thu, Jan 14, 2021 at 01:23:14PM -0800, Jakub Kicinski wrote:
> On Thu, 14 Jan 2021 16:11:41 -0500 Jarod Wilson wrote:
> > In truth, this code started out as a copy of bond_eth_hash(), which also
> > only uses the last byte, though of both source and destination macs. In
> > the typical use case
On Tue, Jan 12, 2021 at 05:39:16PM +0800, peng@nxp.com wrote:
> From: Peng Fan
>
> The hook is used to parse memory-regions and load resource table
> from the address the remote processor published.
>
> Signed-off-by: Peng Fan
> Reviewed-by: Richard Zhu
> Reviewed-by: Mathieu Poirier
>
On Thu, Jan 14, 2021 at 12:05 PM Jakub Kicinski wrote:
>
> Current release - regressions:
> ...
> Current release - always broken:
So I understand what you mean, but it does sound odd with that
"Current release - always broken" thing not being a regression. The
"always broken" makes it sound
Quoting Steven Rostedt (2021-01-14 21:32:06)
> On reboot, one of my test boxes now triggers the following warning:
057fe3535eb3 ("drm/i915: Disable RPM wakeref assertions during driver shutdown")
is included with the drm-intel-fixes PR.
-Chris
On 1/13/21 6:37 PM, Sean Christopherson wrote:
> Move the allocation of the SEV VMCB array to sev.c to help pave the way
> toward encapsulating SEV enabling wholly within sev.c.
>
> No functional change intended.
>
> Signed-off-by: Sean Christopherson
> ---
> arch/x86/kvm/svm/sev.c | 13
On Tue, Jan 12, 2021 at 05:39:19PM +0800, peng@nxp.com wrote:
> From: Peng Fan
>
> Use virtio/mailbox to build connection between Remote Proccessors
> and Linux. Add work queue to handle incoming messages.
>
> Reviewed-by: Richard Zhu
> Signed-off-by: Peng Fan
> ---
>
On 1/11/21 5:50 PM, Halil Pasic wrote:
On Tue, 22 Dec 2020 20:15:58 -0500
Tony Krowiak wrote:
The APCB is a field within the CRYCB that provides the AP configuration
to a KVM guest. Let's introduce a shadow copy of the KVM guest's APCB and
maintain it for the lifespan of the guest.
On 1/13/21 6:37 PM, Sean Christopherson wrote:
> Query max_sev_asid directly after setting it instead of bouncing through
> its wrapper, svm_sev_enabled(). Using the wrapper is unnecessary
> obfuscation.
>
> No functional change intended.
>
> Signed-off-by: Sean Christopherson
> ---
>
[ Forgot to add those on the commit itself ]
-- Steve
On Thu, 14 Jan 2021 16:32:06 -0500
Steven Rostedt wrote:
> On reboot, one of my test boxes now triggers the following warning:
>
> [ cut here ]
> RPM raw-wakeref not held
> WARNING: CPU: 4 PID: 1 at
On 2021-01-14 13:07, Nick Desaulniers wrote:
From: Mahesh Kumar Kalikot Veetil
Modules with a large number of compilation units may be
exceeding AR and LD command argument list. Handle this gracefully by
writing the long argument list in a file. The command line options
read from file are
On 1/13/21 6:37 PM, Sean Christopherson wrote:
> Remove the redundant svm_sev_enabled() check when calling
> sev_hardware_teardown(), the teardown helper itself does the check.
> Removing the check from svm.c will eventually allow dropping
> svm_sev_enabled() entirely.
>
> No functional change
On reboot, one of my test boxes now triggers the following warning:
[ cut here ]
RPM raw-wakeref not held
WARNING: CPU: 4 PID: 1 at drivers/gpu/drm/i915/intel_runtime_pm.h:106
gen6_write32+0x1bc/0x2a0 [i915]
Modules linked in: ebtable_filter ebtables bridge stp llc
> On Dec 23, 2020, at 07:56, Bae, Chang Seok wrote:
>
> Changes from v2 [5]:
> * Removed the patch for the tile data inheritance. Also, updated the
> selftest patch. (Andy Lutomirski)
> * Changed the kernel tainted when any unknown state is enabled. (Andy
> Lutomirski)
> * Changed to use the
> On Dec 23, 2020, at 10:37, Randy Dunlap wrote:
>
> On 12/23/20 7:57 AM, Chang S. Bae wrote:
>> diff --git a/Documentation/admin-guide/kernel-parameters.txt
>> b/Documentation/admin-guide/kernel-parameters.txt
>> index 44fde25bb221..a67ae04d43c5 100644
>> ---
From: Tom Rix
Defining DEBUG should only be done in development.
So remove DEBUG.
Signed-off-by: Tom Rix
---
net/core/neighbour.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/net/core/neighbour.c b/net/core/neighbour.c
index 277ed854aef1..ff073581b5b1 100644
--- a/net/core/neighbour.c
Hi Leo,
On Thu, 14 Jan 2021 at 13:46, Leo Yan wrote:
>
> Hi Mike,
>
> On Wed, Jan 13, 2021 at 01:35:04PM +, Mike Leach wrote:
> > The current fixed metadata version format (version 0), means that adding
> > metadata parameter items renders files from a previous version of perf
> >
From: Arnd Bergmann
An earlier commit moved out some functions to not be inlined by gcc, but
after some other rework to remove one of those, clang started inlining
the other one and ran into the same problem as gcc did before:
fs/ubifs/replay.c:1174:5: error: stack frame size of 1152 bytes in
On Thu, Jan 14, 2021 at 9:55 PM Josh Poimboeuf wrote:
>
> This logic will also be needed for the CONFIG_CFI_CLANG support.
>
Good you fixed that in v2.
I re-pulled from [1].
- Sedat -
[1]
https://git.kernel.org/pub/scm/linux/kernel/git/jpoimboe/linux.git/log/?h=objtool-vmlinux
>
From: Tom Rix
Defining DEBUG should only be done in development.
So remove DEBUG.
Signed-off-by: Tom Rix
---
v1: merge all 4 in arch/x86/
---
arch/x86/kernel/cpu/mtrr/generic.c | 1 -
arch/x86/kernel/cpu/mtrr/mtrr.c| 2 --
arch/x86/kernel/pci-iommu_table.c | 3 ---
arch/x86/mm/mmio-mod.c
On 1/13/21 6:37 PM, Sean Christopherson wrote:
> Define sev_enabled and sev_es_enabled as 'false' and explicitly #ifdef
> out all of sev_hardware_setup() if CONFIG_KVM_AMD_SEV=n. This kills
> three birds at once:
>
> - Makes sev_enabled and sev_es_enabled off by default if
>
301 - 400 of 1491 matches
Mail list logo
