The default behavior of hardlockup depends on the config of
CONFIG_BOOTPARAM_HARDLOCKUP_PANIC.
Fix the description of nmi_watchdog to make it clear.
Suggested-by: Steven Rostedt (VMware)
Signed-off-by: Zhenzhong Duan
Reviewed-by: Joel Fernandes (Google)
Acked-by: Ingo Molnar
Acked-by: Steven
Hi Frederico,
Em Wed, 22 May 2019 00:54:48 +0200
Federico Vaga escreveu:
> On Monday, May 20, 2019 4:47:29 PM CEST Mauro Carvalho Chehab wrote:
> > There are several broken Documentation/* references within the Kernel
> > tree. There are some reasons for several of them:
> >
> > 1. The acpi and
On Monday, May 20, 2019 4:47:39 PM CEST Mauro Carvalho Chehab wrote:
> Mostly due to x86 and acpi conversion, several documentation
> links are still pointing to the old file. Fix them.
>
> Signed-off-by: Mauro Carvalho Chehab
> ---
> Documentation/acpi/dsd/leds.txt | 2 +-
> D
On Monday, May 20, 2019 4:47:29 PM CEST Mauro Carvalho Chehab wrote:
> There are several broken Documentation/* references within the Kernel
> tree. There are some reasons for several of them:
>
> 1. The acpi and x86 documentation files were renamed, but the
>references weren't updated;
> 2. T
AutoReporter is going away; recent versions of sphinx emit a warning like:
/stuff/k/git/kernel/Documentation/sphinx/kerneldoc.py:125:
RemovedInSphinx20Warning: AutodocReporter is now deprecated.
Use sphinx.util.docutils.switch_source_input() instead.
Make the switch. But switch_sou
Recent versions of sphinx will emit messages like:
/stuff/k/git/kernel/Documentation/sphinx/kerneldoc.py:103:
RemovedInSphinx20Warning: app.warning() is now deprecated.
Use sphinx.util.logging instead.
Switch to sphinx.util.logging to make this unsightly message go away.
Alas, that in
The Sphinx folks are deprecating some interfaces in the upcoming 2.0
release; one immediate result of that is a bunch of warnings that show up
when building with 1.8. These two patches make those warnings go away,
but at a cost:
- It introduces a couple of Sphinx version checks, which are always
From: Masanari Iida
Date: Tue, 21 May 2019 12:41:15 +0900
> This patch fixes some spelling typos found in ip-sysctl.txt
>
> Signed-off-by: Masanari Iida
Documentation typos and fixes are always reasonable for 'net' and
therefore that's where I have applied this.
Thanks.
On Tue, May 21, 2019 at 12:41:50PM +0200, David Hildenbrand wrote:
> > +Future Work
> > +===
> > +
> > + - allowing memory hot-add to ZONE_MOVABLE. maybe we need some switch like
> > +sysctl or new control file.
>
> ... that already works if I am not completely missing the point here
This patch corrects renamed or moved paths in comments.
Signed-off-by: Lukas Prause
Signed-off-by: Lennart Glauer
---
kernel/cgroup/cpuset.c | 2 +-
kernel/locking/mutex-debug.h | 2 +-
kernel/power/power.h | 2 +-
kernel/sched/core.c | 2 +-
kernel/trace/trace.h
On Tue, May 21, 2019 at 12:41:50PM +0200, David Hildenbrand wrote:
> On 14.05.19 10:23, Mike Rapoport wrote:
> > The "Locking Internals" section of the memory-hotplug documentation is
> > duplicated in admin-guide and core-api. Drop the admin-guide copy as
> > locking internals does not belong ther
On Tue, 21 May 2019 09:33:17 -0400
Steven Rostedt wrote:
> On Tue, 21 May 2019 16:56:16 +0900
> Masami Hiramatsu wrote:
>
> > Note that 'trace_event=' option enables trace event at very early
> > timing, but the events added by 'kprobe_event=' are enabled right
> > before enabling device driver
Add driver to support the clocks provided by the Timer/Counter Unit
(TCU) of the JZ47xx SoCs from Ingenic.
Signed-off-by: Paul Cercueil
---
Notes:
v12: New patch
drivers/clk/ingenic/Kconfig | 11 +-
drivers/clk/ingenic/Makefile | 1 +
drivers/clk/ingenic/tcu.c| 458
The old clocksource/timer platform code is now obsoleted by the newly
introduced TCU drivers.
Signed-off-by: Paul Cercueil
---
Notes:
v5: New patch
v6-v11: No change
v12: Only remove clocksource code. The rest will eventually be
removed in a future patchset when th
The default clock (48 MHz) is too fast for the system timer.
Signed-off-by: Paul Cercueil
---
Notes:
v5: New patch
v6: Set also the rate for the clocksource channel's clock
v7: No change
v8: No change
v9: Don't configure clock timer1, as the OS Timer is us
The default clock (12 MHz) is too fast for the system timer, which fails
to report time accurately.
Signed-off-by: Paul Cercueil
---
Notes:
v5: New patch
v6: Remove ingenic,clocksource-channel property
v7-v12: No change
arch/mips/boot/dts/ingenic/qi_lb60.dts | 7 +++
This driver handles the interrupt controller built in the Timer/Counter
Unit (TCU) of the JZ47xx SoCs from Ingenic.
Signed-off-by: Paul Cercueil
---
drivers/irqchip/Kconfig | 11 ++
drivers/irqchip/Makefile | 1 +
drivers/irqchip/irq-ingenic-tcu.c | 182
The default clock (12 MHz) is too fast for the system timer.
Signed-off-by: Paul Cercueil
---
Notes:
v8: New patch
v9: Don't configure clock timer1, as the OS Timer is used as
clocksource on this SoC
v10: Revert back to v8 bahaviour. Let the user choose what
This driver handles the TCU (Timer Counter Unit) present on the Ingenic
JZ47xx SoCs, and provides the kernel with a system timer, a clocksource
and a sched_clock.
Signed-off-by: Paul Cercueil
---
Notes:
v2: Use SPDX identifier for the license
v3: - Move documentation to its own patc
Add DTS nodes for the JZ4780, JZ4770 and JZ4740 devicetree files.
Signed-off-by: Paul Cercueil
---
Notes:
v5: New patch
v6: Fix register lengths in watchdog/pwm nodes
v7: No change
v8: - Fix wrong start address for PWM node
- Add system timer and clocksourc
Add the missing TCU clock to the list of clocks supplied by the CGU for
the JZ4740 SoC.
Signed-off-by: Paul Cercueil
Acked-by: Stephen Boyd
Acked-by: Rob Herring
---
Notes:
v5: New patch
v6-v12: No change
drivers/clk/ingenic/jz4740-cgu.c | 6 ++
include/dt-bindings/clo
Add a documentation file about the Timer/Counter Unit (TCU) present in
the Ingenic JZ47xx SoCs.
The Timer/Counter Unit (TCU) in Ingenic JZ47xx SoCs is a multi-function
hardware block. It features up to to eight channels, that can be used as
counters, timers, or PWM.
- JZ4725B, JZ4750, JZ4755 only
This header provides clock numbers for the ingenic,tcu
DT binding.
Signed-off-by: Paul Cercueil
Reviewed-by: Rob Herring
Acked-by: Stephen Boyd
---
Notes:
v2: Use SPDX identifier for the license
v3/v4: No change
v5: s/JZ47*_/TCU_/ and dropped *_CLK_LAST defines
v
This driver will provide a regmap that can be retrieved very early in
the boot process through the API function ingenic_tcu_get_regmap().
Additionally, it will call devm_of_platform_populate() so that all the
children devices will be probed.
Signed-off-by: Paul Cercueil
---
Notes:
v12: New
Hi,
Here's the V12 of my patchset to add support for the Timer/Counter Unit
(TCU) present on the JZ47xx SoCs from Ingenic.
This patchset is much shorter at only 13 patches vs. 27 patches in V11;
the remaining patches will be sent in parallel (if applicable) or as a
follow-up patchset once this on
Add documentation about how to properly use the Ingenic TCU
(Timer/Counter Unit) drivers from devicetree.
Signed-off-by: Paul Cercueil
---
Notes:
v4: New patch in this series. Corresponds to V2 patches 3-4-5 with
added content.
v5: - Edited PWM/watchdog DT bindings documentatio
On Tue, 21 May 2019 16:56:16 +0900
Masami Hiramatsu wrote:
> Note that 'trace_event=' option enables trace event at very early
> timing, but the events added by 'kprobe_event=' are enabled right
> before enabling device drivers at this point. It is enough for
> tracing device driver initializatio
On Tue, 21 May 2019 17:42:28 +0800
Zhenzhong Duan wrote:
> On 2019/5/15 3:21, Steven Rostedt wrote:
> > On Sun, 12 May 2019 11:35:27 +0800
> > Zhenzhong Duan wrote:
> >
> >> The default behavior of hardlockup depends on the config of
> >> CONFIG_BOOTPARAM_HARDLOCKUP_PANIC.
> >>
> >> Fix the de
On Tue, 21 May 2019 21:30:00 +0900
Masanari Iida wrote:
> This patch fixes some spelling typos in histogram.rst
Acked-by: Steven Rostedt (VMware)
Jon,
Care to take this in your tree?
-- Steve
>
> Signed-off-by: Masanari Iida
> ---
This patch fixes some spelling typos in histogram.rst
Signed-off-by: Masanari Iida
---
Documentation/trace/histogram.rst | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/Documentation/trace/histogram.rst
b/Documentation/trace/histogram.rst
index fb621a1c2638..84086
On Tue, 2019-05-21 at 09:26 +0200, Roberto Sassu wrote:
> On 5/20/2019 11:20 PM, Mimi Zohar wrote:
> > On Thu, 2019-05-16 at 18:12 +0200, Roberto Sassu wrote:
> >> diff --git a/Documentation/admin-guide/kernel-parameters.txt
> >> b/Documentation/admin-guide/kernel-parameters.txt
> >> index 52e6fbb
On 14.05.19 10:23, Mike Rapoport wrote:
> The "Locking Internals" section of the memory-hotplug documentation is
> duplicated in admin-guide and core-api. Drop the admin-guide copy as
> locking internals does not belong there.
>
> While on it, move the "Future Work" section to the core-api part.
Уважаеми Господине/Госпожо,
Съвременната социална придобивка ваучери за храна, които могат да бъдат
използвани в широка търговска мрежа от супермаркети и заведения за хранене в
страната, е инструмент, който ефективно повишава ефикасността на персонала.
Това се потвърждава и от проучването на Св
On 2019/5/15 3:21, Steven Rostedt wrote:
On Sun, 12 May 2019 11:35:27 +0800
Zhenzhong Duan wrote:
The default behavior of hardlockup depends on the config of
CONFIG_BOOTPARAM_HARDLOCKUP_PANIC.
Fix the description of nmi_watchdog to make it clear.
Signed-off-by: Zhenzhong Duan
Reviewed-by:
Add kprobe_event= boot parameter to define kprobe events
at boot time.
The definition syntax is similar to tracefs/kprobe_events
interface, but use ',' and ';' instead of ' ' and '\n'
respectively. e.g.
kprobe_event=p,vfs_read,$arg1,$arg2
This puts a probe on vfs_read with argument1 and 2, and
Initialize kprobes at subsys_initcall stage instead of module_init
since kprobes is not a module. This will allow ftrace kprobe
event to add new events when it is initializing because ftrace
kprobe event is initialized at fs_initcall.
Signed-off-by: Masami Hiramatsu
---
kernel/kprobes.c |2 +
This series adds a kernel parameter, 'kprobe_event=' to add and enable
new kprobe events at boot time.
Currently ftrace can enable some existing trace events at boot time.
This also allows admin/developer to add new kprobe-events at boot
time to debug device drivers etc.
The syntax is similar to
On 5/20/2019 11:20 PM, Mimi Zohar wrote:
On Thu, 2019-05-16 at 18:12 +0200, Roberto Sassu wrote:
This patch ensures that integrity_audit_msg() is called only when the
status is not INTEGRITY_PASS.
Fixes: 8606404fa555c ("ima: digital signature verification support")
Signed-off-by: Roberto Sassu
On 5/20/2019 11:20 PM, Mimi Zohar wrote:
On Thu, 2019-05-16 at 18:12 +0200, Roberto Sassu wrote:
diff --git a/Documentation/admin-guide/kernel-parameters.txt
b/Documentation/admin-guide/kernel-parameters.txt
index 52e6fbb042cc..80e1c233656b 100644
--- a/Documentation/admin-guide/kernel-paramete
39 matches
Mail list logo
