The following commit has been merged into the x86/platform branch of tip:
Commit-ID: 3bcf25a40b018e632d70bb866d75746748953fbc
Gitweb:
https://git.kernel.org/tip/3bcf25a40b018e632d70bb866d75746748953fbc
Author:steve.w...@hpe.com
AuthorDate:Mon, 13 Jul 2020 16:30:07 -05:00
On Fri, Jul 17, 2020 at 09:39:25AM -0400, Mathieu Desnoyers wrote:
> - On Jul 16, 2020, at 5:24 PM, Alan Stern st...@rowland.harvard.edu wrote:
>
> > On Thu, Jul 16, 2020 at 02:58:41PM -0400, Mathieu Desnoyers wrote:
> >> - On Jul 16, 2020, at 12:03 PM, Mathieu Desnoyers
> >>
l getting EIO from madvise on some x86 NUMA systems with next-20200717
which includes this patchset.
# git clone https://gitlab.com/cailca/linux-mm
# cd linux-mm; make
# ./random 1
- start: migrate_huge_offline
- use NUMA nodes 0,3.
- mmap and free 8388608 bytes hugepages on node 0
- mmap and
On Fri, Jul 17, 2020 at 12:36 AM Daniel Gutson
wrote:
>
> +static ssize_t internal_callback(struct kobject *kobj,
> +struct kobj_attribute *attr, char *buf)
> +{
> + struct firmware_security_data *fwsd =
> + container_of(attr, struct
Please make sure to cc the linux-arm-msm@vger list for patches of
Qualcomm code.
On Fri, Jul 17, 2020 at 08:02:22PM +0530, Akash Asthana wrote:
> pdev struct doesn't exits for the devices whose status are disabled
s/exits/exist/
> from DT node, in such cases NULL is returned from
On Fri, Jul 17, 2020 at 08:04:18PM +0530, Akhil P Oommen wrote:
> On targets where GMU is available, GMU takes over the ownership of GX GDSC
> during its initialization. So, move the refcount-get on GX PD before we
> initialize the GMU. This ensures that nobody can collapse the GX GDSC
> once GMU
On Fri, 2020-07-17 at 10:36 +0200, Pavel Machek wrote:
> Hi!
>
> > This is a second version of "secret" mappings implementation backed
> > by a file descriptor.
> >
> > The file descriptor is created using memfd_create() syscall with a
> > new MFD_SECRET flag. The file descriptor should be
Hi Cheng-Yi,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on asoc/for-next]
[also build test ERROR on linux/master linus/master v5.8-rc5 next-20200717]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest
On Fri, Jul 17, 2020 at 02:43:52AM +0200, Karol Herbst wrote:
On Fri, Jul 17, 2020 at 1:54 AM Bjorn Helgaas wrote:
[+cc Sasha -- stable kernel regression]
[+cc Patrick, Kai-Heng, LKML]
On Fri, Jul 17, 2020 at 12:10:39AM +0200, Karol Herbst wrote:
> On Tue, Jul 7, 2020 at 9:30 PM Karol Herbst
From: Laurentiu Palcu
Hi,
This patchset adds initial DCSS support for iMX8MQ chip. Initial support
includes only graphics plane support (no video planes), no HDR10 capabilities,
no graphics decompression (only linear, tiled and super-tiled buffers allowed).
Support for the rest of the features
From: Laurentiu Palcu
This adds initial support for iMX8MQ's Display Controller Subsystem (DCSS).
Some of its capabilities include:
* 4K@60fps;
* HDR10;
* one graphics and 2 video pipelines;
* on-the-fly decompression of compressed video and graphics;
The reference manual can be found here:
From: Laurentiu Palcu
Add bindings for iMX8MQ Display Controller Subsystem.
Signed-off-by: Laurentiu Palcu
---
.../bindings/display/imx/nxp,imx8mq-dcss.yaml | 104 ++
1 file changed, 104 insertions(+)
create mode 100644
From: Laurentiu Palcu
The driver is part of DRM subsystem and is located in drivers/gpu/drm/imx/dcss.
Signed-off-by: Laurentiu Palcu
---
MAINTAINERS | 8
1 file changed, 8 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index dad5a62d21a7..200c5985b41f 100644
--- a/MAINTAINERS
From: Laurentiu Palcu
Currently the drm/imx/ directory is compiled only if DRM_IMX is set. Adding a
new IMX related IP in the same directory would need DRM_IMX to be set, which
would
bring in also IPUv3 core driver...
The current patch would allow adding new IPs in the imx/ directory without
On Thu, 2020-07-16 at 12:57 -0700, Florian Fainelli wrote:
>
> On 7/16/2020 7:13 AM, Daniele Alessandrelli wrote:
> > Hi Florian,
> >
> > Thanks for you feedback.
> >
> > On Wed, 2020-07-15 at 15:43 -0700, Florian Fainelli wrote:
> > > On 7/15/2020 9:55 AM, Daniele Alessandrelli wrote:
> > > >
On Mon, Jul 13, 2020 at 02:38:55PM +0530, Amit Tomer wrote:
> Hi,
>
> > Fixed regulators are used to nicely model the regulators which aren't tied
> > to
> > any PMIC. But for some cases we use them to represent supplies when there is
> > no support for the specific PMIC present in the kernel
On Fri, Jul 17, 2020 at 8:28 AM Greg Kroah-Hartman
wrote:
>
> On Thu, Jul 16, 2020 at 07:36:27PM -0300, Daniel Gutson wrote:
> > +What:/sys/kernel/firmware-security/bioswe
>
> Ick, I stopped reading right here.
>
> No, this is not where this belongs.
>
> We already have
Hi Daniel,
在 2020/7/17 下午4:02, Daniel Lezcano 写道:
On 17/07/2020 08:13, Zhou Yanjie wrote:
Hi Daniel,
在 2020/7/17 下午12:20, Daniel Lezcano 写道:
On 10/07/2020 19:02, 周琰杰 (Zhou Yanjie) wrote:
X1000 and SoCs after X1000 (such as X1500 and X1830) had a separate
OST, it no longer belongs to TCU.
Sometimes we want ftrace display more and longer information about
the trace.
$ sudo perf ftrace -G '*'
2) 0.979 us| mutex_unlock();
2) 1.540 us| __fsnotify_parent();
2) 0.433 us| fsnotify();
$ sudo perf ftrace -G '*' --graph-opts verbose
14160.770883 | 0) <...>-47814
This adds an option '--graph-opts thresh' to setup trace duration
threshold for funcgraph tracer.
$ sudo ./perf ftrace -G '*' --graph-opts thresh=100
3) ! 184.060 us |} /* schedule */
3) ! 185.600 us | } /* exit_to_usermode_loop */
2) ! 225.989 us |} /* schedule_idle */
2) #
This is to have a consistent view of all graph tracer options.
The original option '--graph-depth' is marked as deprecated.
Signed-off-by: Changbin Du
---
tools/perf/Documentation/perf-ftrace.txt | 5 +
tools/perf/builtin-ftrace.c | 5 ++---
2 files changed, 3 insertions(+), 7
On Thu, Jul 16, 2020 at 08:28:50PM +0530, Sibi Sankar wrote:
> On 2020-07-16 19:13, Manivannan Sadhasivam wrote:
> > Hi Sibi,
> >
> > On Thu, Jul 16, 2020 at 06:06:29PM +0530, Sibi Sankar wrote:
> > > On SC7180 the MBA firmware stores the bootup text logs in a 4K segment
> > > at the beginning of
Now the __cmd_ftrace() becomes a bit long. This moves the trace
option setting code to a separate function set_tracing_options().
Suggested-by: Namhyung Kim
Signed-off-by: Changbin Du
---
tools/perf/builtin-ftrace.c | 118 +++-
1 file changed, 63 insertions(+),
This adds an option '-D/--delay' to allow us to start tracing some
times later after workload is launched.
Signed-off-by: Changbin Du
---
tools/perf/Documentation/perf-ftrace.txt | 4
tools/perf/builtin-ftrace.c | 19 ---
2 files changed, 20 insertions(+), 3
Add a change log after previous enhancements.
Signed-off-by: Changbin Du
---
tools/perf/builtin-ftrace.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/tools/perf/builtin-ftrace.c b/tools/perf/builtin-ftrace.c
index edf307f7d716..326fd03396d5 100644
--- a/tools/perf/builtin-ftrace.c
+++
This adds an option '--graph-opts noirqs' to filter out functions executed
in irq context.
Signed-off-by: Changbin Du
---
v2: option name '--nofuncgraph-irqs' -> '--graph-noirqs'.
---
tools/perf/Documentation/perf-ftrace.txt | 1 +
tools/perf/builtin-ftrace.c | 21
This adds an option '--graph-opts nosleep-time' which allow us
only to measure on-CPU time. This option is function_graph tracer
only.
Signed-off-by: Changbin Du
---
v3: switch to uniform option --graph-opts.
v2: option name '--nosleep-time' -> '--graph-nosleep-time'.
---
This adds an option '--inherit' to allow us trace children
processes spawned by our target.
Signed-off-by: Changbin Du
---
v2: option name '--trace-children' -> '--inherit'.
---
tools/perf/Documentation/perf-ftrace.txt | 3 ++
tools/perf/builtin-ftrace.c | 38
This adds support to display irq context info for function tracer. To do
this, just specify a '--func-opts irq-info' option.
Signed-off-by: Changbin Du
---
tools/perf/Documentation/perf-ftrace.txt | 1 +
tools/perf/builtin-ftrace.c | 21 -
2 files changed, 21
This makes perf-ftrace display column header before printing trace.
$ sudo perf ftrace
# tracer: function
#
# entries-in-buffer/entries-written: 0/0 #P:8
#
#TASK-PID CPU# TIMESTAMP FUNCTION
# | | | | |
<...>-9246
This factors out a general function perf_parse_sublevel_options() to parse
sublevel options. The 'sublevel' options is something like the '--debug'
options which allow more sublevel options.
Signed-off-by: Changbin Du
---
v2: add util/parse-sublevel-options.c
---
tools/perf/util/Build
This adds support to display call trace for function tracer. To do this,
just specify a '--func-opts call-graph' option.
$ sudo perf ftrace -T vfs_read --func-opts call-graph
iio-sensor-prox-855 [003] 6168.369657: vfs_read <-ksys_read
iio-sensor-prox-855 [003] 6168.369677:
=> vfs_read
We will reuse this function later.
Signed-off-by: Changbin Du
---
tools/perf/builtin-ftrace.c | 17 -
1 file changed, 12 insertions(+), 5 deletions(-)
diff --git a/tools/perf/builtin-ftrace.c b/tools/perf/builtin-ftrace.c
index 3c0e60fdfe0f..9abf97c29cb6 100644
---
This adds an option '-m/--buffer-size' to allow us set the size of per-cpu
tracing buffer.
Signed-off-by: Changbin Du
---
v2: support units as a suffix.
---
tools/perf/Documentation/perf-ftrace.txt | 5 +++
tools/perf/builtin-ftrace.c | 56 +++-
2 files
On targets where GMU is available, GMU takes over the ownership of GX GDSC
during its initialization. So, move the refcount-get on GX PD before we
initialize the GMU. This ensures that nobody can collapse the GX GDSC
once GMU owns the GX GDSC. This patch fixes some GMU OOB errors seen
during GPU
The perf has basic kernel ftrace support but lack support of most tracing
options. This serias is target to enhance the perf ftrace functionality so
that we can make full use of kernel ftrace with perf.
In general, this serias be cataloged into two main changes:
1) Improve usability of existing
This adds an option '-F/--funcs' to list all available functions to trace,
which is read from tracing file 'available_filter_functions'.
$ sudo ./perf ftrace -F | head
trace_initcall_finish_cb
initcall_blacklisted
do_one_initcall
do_one_initcall
trace_initcall_start_cb
run_init_process
On 7/15/2020 12:12 AM, Rob Clark wrote:
On Tue, Jul 14, 2020 at 10:10 AM Matthias Kaehlcke wrote:
On Tue, Jul 14, 2020 at 06:55:30PM +0530, Akhil P Oommen wrote:
On targets where GMU is available, GMU takes over the ownership of GX GDSC
during its initialization. So, take a refcount on the
The '-g/-G' options have already implied function_graph tracer should be
used instead of function tracer. So the extra option '--tracer' can be
killed.
This patch changes the behavior as below:
- By default, function tracer is used.
- If '-g' or '-G' option is on, then function_graph tracer
From: Gregory Herrero
Currently, if a section has a relocation to '_mcount' symbol, a new
__mcount_loc entry will be added whatever the relocation type is.
This is problematic when a relocation to '_mcount' is in the middle of a
section and is not a call for ftrace use.
Such relocation could be
The '-g/-G' options have already implied function_graph tracer should be
used instead of function tracer. So the extra option '--tracer' can be
killed.
This patch changes the behavior as below:
- By default, function tracer is used.
- If '-g' or '-G' option is on, then function_graph tracer
pdev struct doesn't exits for the devices whose status are disabled
from DT node, in such cases NULL is returned from 'of_find_device_by_node'
Later when we try to get drvdata from pdev struct NULL pointer dereference
is triggered.
Add a NULL check for return values to fix the issue.
We were
On Thu, Jul 16, 2020 at 10:47 AM Enric Balletbo i Serra
wrote:
>
> Hi,
>
> On 16/7/20 19:23, Guenter Roeck wrote:
> > On Thu, Jul 16, 2020 at 10:09 AM Yu-Hsuan Hsu wrote:
> >>
> >> It is not guaranteed that I2S RX is disabled when the kernel booting.
> >> For example, if the kernel crashes while
The perf has basic kernel ftrace support but lack support of most tracing
options. This serias is target to enhance the perf ftrace functionality so
that we can make full use of kernel ftrace with perf.
In general, this serias be cataloged into two main changes:
1) Improve usability of existing
On Wed, May 27, 2020 at 10:26:10PM +0800, Dejin Zheng wrote:
Hi Jonathan, Greg, Rafael, Linus, Michal and Wolfram:
Could you help me review this patch if you have free time?
Thank you very very much!
BR,
Dejin
> It will call devm_request_irq() after platform_get_irq() function
> in many drivers,
On Mon, Jul 13, 2020 at 10:59:56AM +0900, Namhyung Kim wrote:
> On Sat, Jul 11, 2020 at 9:42 PM Changbin Du wrote:
> >
> > This adds an option '--inherit' to allow us trace children
> > processes spawned by our target.
> >
> > Signed-off-by: Changbin Du
> >
> > ---
> > v2: option name
On Thu, Jul 16, 2020 at 09:44:27PM -0700, Eric Biggers wrote:
...
> +Note that when the cmpxchg_release() fails due to another task already
> +having done it, a second smp_load_acquire() is required, since we still
> +need to acquire the data that the other task released.
When people talk about
On Fri, Jul 17, 2020 at 09:32:21AM +0800, miaoqinglang wrote:
>
> 在 2020/7/16 21:34, Thierry Reding 写道:
> > On Thu, Jul 16, 2020 at 05:03:23PM +0800, Qinglang Miao wrote:
> > > From: Yongqiang Liu
> > >
> > > Use DEFINE_SHOW_ATTRIBUTE macro to simplify the code.
> > >
> > > Signed-off-by:
On Tue, Jul 14, 2020 at 8:38 AM Ming Lei wrote:
>
> On Wed, Jul 08, 2020 at 09:14:05PM +0800, Ming Lei wrote:
> > IO requests may be held in scheduler queue because of resource contention.
> > However, not like normal completion, when queueing request failed, we don't
> > ask block layer to queue
On Thu, 16 Jul 2020 at 21:55, Patrick Bellasi
wrote:
>
>
> Hi Vincent,
>
> On Mon, Jul 13, 2020 at 14:59:51 +0200, Vincent Guittot
> wrote...
>
> > On Fri, 10 Jul 2020 at 21:59, Patrick Bellasi
> > wrote:
> >> On Fri, Jul 10, 2020 at 15:21:48 +0200, Vincent Guittot
> >> wrote...
> >>
> >>
in
https://git-scm.com/docs/git-format-patch]
url:
https://github.com/0day-ci/linux/commits/Shile-Zhang/virtio_ring-use-alloc_pages_node-for-NUMA-aware-allocation/20200717-173734
base: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
8882572675c1bb1cc544f4e229a11661f1fc52e4
Hello, Jakub,
On 7/16/20 7:56 PM, Jakub Kicinski wrote:
Hi Murali,
thanks for the patches.
It seems like at least the first patch addresses a problem which exist
in Linus's tree, i.e. Linux 5.8-rc.
Could you please separate bug fixes like that out to a new series
addressed to the net tree,
On Thu, Jul 16, 2020 at 8:31 PM Peter Chen wrote:
>
> On 20-07-16 13:24:52, Rob Herring wrote:
> > On Tue, Jul 14, 2020 at 05:18:20PM +0200, Philippe Schenker wrote:
> > > Chipidea depends on some hardware signals to be there in order
> > > for runtime-pm to work well. Add the possibility to
On Mon, Jul 13, 2020 at 11:07:56AM +0900, Namhyung Kim wrote:
> On Sat, Jul 11, 2020 at 9:43 PM Changbin Du wrote:
> >
> > Sometimes we want ftrace display more and longer information about
> > the trace.
> >
> > $ sudo perf ftrace -G
> > 2) 0.979 us| mutex_unlock();
> > 2) 1.540 us
On Fri, Jul 17, 2020 at 03:54:49PM +0200, Arnd Bergmann wrote:
> > And look at the driver core work for many driver subsystems to be fixed
> > up just to get a single kernel image to work on multiple platforms.
> > Just because older ones did it, doesn't mean it actually works today :)
>
> Can
On 16/07/2020 14:42:31+0100, Lee Jones wrote:
> > > diff --git a/drivers/pinctrl/pinctrl-at91.c
> > > b/drivers/pinctrl/pinctrl-at91.c
> > > index 9c52130876597..37997e5ab0538 100644
> > > --- a/drivers/pinctrl/pinctrl-at91.c
> > > +++ b/drivers/pinctrl/pinctrl-at91.c
> > > @@ -22,6 +22,7 @@
> >
From: Kan Liang
Many items are checked in the intel_pmu_disable/enable_event. More items
will be added later, e.g. perf metrics events.
Use switch, which is more efficient, to replace the if-else.
If the idx is invalid, print a warning.
For the case INTEL_PMC_IDX_FIXED_BTS in
From: Kan Liang
The RDPMC index is always re-calculated for the RDPMC userspace support,
which is unnecessary.
The RDPMC index value is stored in the variable event_base_rdpmc for
the kernel usage, which can be used for RDPMC userspace support as well.
Suggested-by: Peter Zijlstra
From: Kan Liang
The RDPMC base offset of fixed counters is hard-code. Use a meaningful
name to replace the magic number to improve the readability of the code.
Signed-off-by: Kan Liang
---
arch/x86/events/core.c| 3 ++-
arch/x86/include/asm/perf_event.h | 3 +++
2 files changed, 5
From: Kan Liang
Bit 15 of the PERF_CAPABILITIES MSR indicates that the perf METRICS
feature is supported. The perf METRICS is not a PEBS feature.
Rename pebs_metrics_available perf_metrics.
The bit is not used in the current code. It will be used in a later
patch.
Signed-off-by: Kan Liang
From: Kan Liang
Magic numbers are used in the current NMI handler for the global status
bit. Use a meaningful name to replace the magic numbers to improve the
readability of the code.
Remove a Tab for all GLOBAL_STATUS_* and INTEL_PMC_IDX_FIXED_BTS macros
to reduce the length of the line.
From: Kan Liang
Intro
=
The TopDown Microarchitecture Analysis (TMA) Method is a structured
analysis methodology to identify critical performance bottlenecks in
out-of-order processors. Current perf has supported the method.
The method works well, but there is one problem. To collect the
EXTI lines are mainly used to wake-up system from CStop low power mode.
Currently, if a device wants to use a EXTI (direct) line as wakeup line,
it has to declare 2 interrupts:
- one for EXTI used to wake-up system (with dedicated_wake_irq api).
- one for GIC used to get the wake up reason
From: Kan Liang
The bit 48 in the PERF_GLOBAL_STATUS is used to indicate the overflow
status of the PERF_METRICS counters.
Move the BTS index to the bit 47.
Signed-off-by: Kan Liang
---
arch/x86/include/asm/perf_event.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
From: Andi Kleen
Add some documentation how to use the topdown metrics in ring 3.
Signed-off-by: Andi Kleen
---
tools/perf/Documentation/topdown.txt | 235 +++
1 file changed, 235 insertions(+)
create mode 100644 tools/perf/Documentation/topdown.txt
diff --git
From: Kan Liang
Starts from Ice Lake, the TopDown metrics are directly available as
fixed counters and do not require generic counters. Also, the TopDown
metrics can be collected per thread. Extend the RDPMC usage to support
per-thread TopDown metrics.
The RDPMC index of the PERF_METRICS will
From: Kan Liang
Users fail to sample-read the slots and metrics events, e.g.,
perf record -e '{slots, topdown-retiring}:S'.
When reading the metrics event, the fixed counter 3 (slots) has to be
reset, which impacts the sampling of the slots event.
Add a specific validate_group() support to
From: Kan Liang
The slots event is required in a Topdown Metric group.
Add a check to examine the Topdown Metric group. Error out if there is
no slots event detected.
Only check the group on the platform which using topdown_metric_attrs,
e.g. Ice Lake.
Signed-off-by: Kan Liang
---
From: Andi Kleen
Icelake has support for reporting per thread TopDown metrics.
These are reported differently than the previous TopDown support,
each metric is standalone, but scaled to pipeline "slots".
We don't need to do anything special for HyperThreading anymore.
Teach perf stat --topdown
From: Kan Liang
Ice Lake supports the hardware TopDown metrics feature, which can free
up the scarce GP counters.
Update the event constraints for the metrics events. The metric counters
do not exist, which are mapped to a dummy offset. The sharing between
multiple users of the same metric
On Fri, Jul 17, 2020 at 4:04 PM Sudeep Holla wrote:
>
> Kbuild test robot reports the following sparse warning:
>
> drivers/firmware/arm_scmi/clock.c:142:21:
> sparse: Using plain integer as NULL pointer
>
> Use NULL pointer instead of integer 0 for rate pointer and fix the
> warning.
>
>
From: Kan Liang
The fourth fixed counter, TOPDOWN.SLOTS, is introduced in Ice Lake to
measure the level 1 TopDown events.
Add MSR address and macros for the new fixed counter, which will be used
in a later patch.
Add comments to explain the event encoding rules for the fixed counters.
From: Kan Liang
Changes since V5:
- Rebase on top of tip perf/core branch
commit c085fb877467 ("perf/x86/intel/lbr: Support XSAVES for arch LBR
read")
- Add more cleanup codes, e.g. ("perf/x86/intel: Use switch in
intel_pmu_disable/enable_event"). Use more macros to replace the magic
If a level has a timer that expires before we reach the next level,
there is no need to iterate further.
The next level is reached when the 3 lower bits of the current level are
cleared. If the next event happens before/during that, the next levels
won't give us an earlier expiration.
Tested-by:
When an expiration delta falls into the last level of the wheel, we want
to compare that delta against the maximum possible delay and reduce our
delta to fit in if necessary.
However instead of comparing the delta against the maximum, we are
comparing the actual expiry against the maximum. Then
Consolidate the code by calling trigger_dyntick_cpu() from
enqueue_timer() instead of calling it from all its callers.
Tested-by: Juri Lelli
Signed-off-by: Frederic Weisbecker
Cc: Peter Zijlstra
Cc: Anna-Maria Behnsen
Cc: Juri Lelli
---
kernel/time/timer.c | 61
On Wed, Jun 17, 2020 at 02:26:22PM +0900, js1...@gmail.com wrote:
> From: Joonsoo Kim
>
> This patch implements workingset detection for anonymous LRU.
> All the infrastructure is implemented by the previous patches so this patch
> just activates the workingset detection by installing/retrieving
There is nothing that prevents us from forwarding the base clock if
it's one jiffy off. This reason for this arbitrary limit is historical
and doesn't seem to stand anymore.
Tested-by: Juri Lelli
Signed-off-by: Frederic Weisbecker
Cc: Peter Zijlstra
Cc: Anna-Maria Behnsen
Cc: Juri Lelli
---
On Tue, 14 Jul 2020 14:08:12 +0200
Joerg Roedel wrote:
> From: Joerg Roedel
>
> Add a function to check whether an instruction has a REP prefix.
This looks good to me.
Reviewed-by: Masami Hiramatsu
Thank you,
>
> Signed-off-by: Joerg Roedel
> ---
> arch/x86/include/asm/insn-eval.h |
Now that the core timer infrastructure doesn't depend anymore on
periodic base->clk increments, even when the CPU is not in NO_HZ mode,
we can delay the timer softirqs until we have actual timers to expire.
Some spurious softirqs can still remain since base->next_expiry doesn't
keep track of
On Thu, 2020-07-16 at 21:27 +0300, Andy Shevchenko wrote:
> When we have no primary fwnode or when it's a software node, we may end up
> in the situation when fwnode is a NULL pointer. There is no point to look for
> secondary fwnode in such case. Add a necessary check to a condition.
>
> Fixes:
Now that we track the next expiry unconditionally when a timer is added,
we can reuse that information on a tick firing after exiting nohz.
Tested-by: Juri Lelli
Signed-off-by: Frederic Weisbecker
Cc: Peter Zijlstra
Cc: Anna-Maria Behnsen
Cc: Juri Lelli
---
kernel/time/timer.c | 6 ++
1
There is no reason to keep this guard around. The code makes sure that
base->clk remains sane and won't be forwarded beyond jiffies nor set
backward.
Tested-by: Juri Lelli
Signed-off-by: Frederic Weisbecker
Cc: Peter Zijlstra
Cc: Anna-Maria Behnsen
Cc: Juri Lelli
---
kernel/time/timer.c |
calc_index() adds 1 unit of the level granularity to the expiry passed
in parameter to ensure that the timer doesn't expire too early. Add a
comment to explain that and the resulting layout in the wheel.
Most-of-the-patch-by: Thomas Gleixner
Tested-by: Juri Lelli
Signed-off-by: Frederic
As for next_expiry, we want to expand base->clk catch up logic beyond
nohz in order to avoid triggering useless softirqs.
If we want to fire softirqs only to expire pending timers, periodic
base->clk increments must be skippable for random amounts of time.
Therefore we must prepare to catch-up
So far next expiry was only tracked while the CPU was in nohz_idle mode
in order to cope with missing ticks that can't increment the base->clk
periodically anymore.
We are going to expand that logic beyond nohz in order to spare timers
softirqs so do it unconditionally.
Tested-by: Juri Lelli
The higher bits of the timer expiration are cropped while calling
calc_index() due to the implicit cast from unsigned long to unsigned int.
This loss shouldn't have consequences on the current code since all the
computation to calculate the index is done on the lower 32 bits.
However we are
This set piggybacks the 3 patches that have been posted seperately
along the reviews.
Changes since v2:
1) Add "timer: Fix wheel index calculation on last level"
This one targets timers/urgent
2) Add "timer: Preserve higher bits of expiration on index calculation"
"timer: Move
From: Anna-Maria Behnsen
The bucket expiry time is the effective expriy time of timers and is
greater than or equal to the requested timer expiry time. This is due
to the guarantee that timers never expire early and the reduced expiry
granularity in the secondary wheel levels.
When a timer is
A couple of reliable unwinder fixes for newly forked tasks, which were
reported by Wang ShaoBo.
Josh Poimboeuf (2):
x86/unwind/orc: Fix ORC for newly forked tasks
x86/stacktrace: Fix reliable check for empty user task stacks
arch/x86/kernel/stacktrace.c | 5 -
The ORC unwinder fails to unwind newly forked tasks which haven't yet
run on the CPU. It correctly reads the 'ret_from_fork' instruction
pointer from the stack, but it incorrectly interprets that value as a
call stack address rather than a "signal" one, so the address gets
incorrectly decremented
If a user task's stack is empty, or if it only has user regs, ORC
reports it as a reliable empty stack. But arch_stack_walk_reliable()
incorrectly treats it as unreliable.
That happens because the only success path for user tasks is inside the
loop, which only iterates on non-empty stacks.
Kbuild test robot reports the following sparse warning:
drivers/firmware/arm_scmi/clock.c:142:21:
sparse: Using plain integer as NULL pointer
Use NULL pointer instead of integer 0 for rate pointer and fix the
warning.
Reported-by: kernel test robot
Signed-off-by: Sudeep Holla
---
On Fri, 17 Jul 2020, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit:aab7ee9f Add linux-next specific files for 20200717
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=123cefcf10
&g
On 17/07/2020 14:54:22+0100, Lee Jones wrote:
> The only way this driver can be probed by MFD via its parent device.
>
> No other reference to 'microchip,at91sam9g45-usart-spi' exists in the kernel.
>
> Fixes the following W=1 kernel build warning(s):
>
> drivers/spi/spi-at91-usart.c:684:34:
Hi Florian
On 7/16/20 20:57, Florian Fainelli wrote:
Given that the kernel must somehow reserve this memory as a shared
memory area for obvious reasons, and the trusted firmware must also
ensure it treats this memory region with specific permissions in its
translation regime, does it really
Hi Hans,
Thanks for taking an interest in this.
On 2020-07-16 11:18:29 +0200, Hans Verkuil wrote:
> What exactly are these warnings? I remember faintly seeing backtraces
> of this before, but it is so long ago. It would be good to see what
> happens with the latest kernel (i.e. media master
On Wed, Jun 17, 2020 at 02:26:19PM +0900, js1...@gmail.com wrote:
> From: Joonsoo Kim
>
> In current implementation, newly created or swap-in anonymous page
> is started on active list. Growing active list results in rebalancing
> active/inactive list so old pages on active list are demoted to
Hello,
syzbot found the following issue on:
HEAD commit:aab7ee9f Add linux-next specific files for 20200717
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=123cefcf10
kernel config: https://syzkaller.appspot.com/x/.config?x=66b5d44ee3d87c99
dashboard
On Tue, 14 Jul 2020 14:08:08 +0200
Joerg Roedel wrote:
> From: Joerg Roedel
>
> The inat-tables.c file has some arrays in it that contain pointers to
> other arrays. These pointers need to be relocated when the kernel
> image is moved to a different location.
>
> The pre-decompression
701 - 800 of 1397 matches
Mail list logo
