tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
x86/timers
branch HEAD: bd35c77e32e4359580207891c0f7a438ad4b42df x86/tsc: Add
tsc_early_khz command line parameter
elapsed time: 3628m
configs tested: 122
configs skipped: 1
The following configs have been built
The following commit has been merged into the x86/timers branch of tip:
Commit-ID: bd35c77e32e4359580207891c0f7a438ad4b42df
Gitweb:
https://git.kernel.org/tip/bd35c77e32e4359580207891c0f7a438ad4b42df
Author:Krzysztof Piecuch
AuthorDate:Thu, 23 Jan 2020 16:09:26
Committer
Commit 100214889973 ("clocksource: dw_apb_timer_of: use
clocksource_of_init") replaced a publicly available driver
initialization method with one called by the timer_probe() method
available after CLKSRC_OF. In current implementation it traverses
all the timers available in the system
Commit 100214889973 ("clocksource: dw_apb_timer_of: use
clocksource_of_init") replaced a publicly available driver
initialization method with one called by the timer_probe() method
available after CLKSRC_OF. In current implementation it traverses
all the timers available in the system
On Tue, 07 Jan 2020, Peter Ujfalusi wrote:
> dma_request_slave_channel() is a wrapper on top of dma_request_chan()
> eating up the error code.
>
> By using dma_request_chan() directly the driver can support deferred
> probing against DMA.
>
> Signed-off-by: Peter Ujfalusi
> ---
> Hi,
>
>
Xianting Tian writes:
> Use set_current_state macro instead of current->state = TASK_RUNNING
>
> Signed-off-by: Xianting Tian
> ---
> kernel/time/timer.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/kernel/time/timer.c b/kernel/time/timer.c
> index 4820823..b9ecf87
On 20/04/2020 14:16, Benjamin Gaignard wrote:
> From: Benjamin Gaignard
>
> Implement clock event driver using low power STM32 timers.
> Low power timer counters running even when CPUs are stopped.
> It could be used as clock event broadcaster to wake up CPUs but not like
> a c
On 18/05/2020 19:00, Tony Lindgren wrote:
> * Daniel Lezcano [200518 16:59]:
>>
>> Hi Tony,
>>
>> On 07/05/2020 19:23, Tony Lindgren wrote:
>>> Hi all,
>>>
>>> Here's v3 series to udpate omaps to use drivers/clocksource timers for
>>
* Daniel Lezcano [200518 16:59]:
>
> Hi Tony,
>
> On 07/05/2020 19:23, Tony Lindgren wrote:
> > Hi all,
> >
> > Here's v3 series to udpate omaps to use drivers/clocksource timers for
> > the 32k counter and dmtimer, and to remove the old legacy platf
Hi Tony,
On 07/05/2020 19:23, Tony Lindgren wrote:
> Hi all,
>
> Here's v3 series to udpate omaps to use drivers/clocksource timers for
> the 32k counter and dmtimer, and to remove the old legacy platform code.
> Please review and test.
>
> I've updated the timer-ti-dm-s
On 5/15/20 5:25 PM, Daniel Lezcano wrote:
> Hi Benjamin,
>
> On 05/05/2020 09:26, Benjamin GAIGNARD wrote:
>>
>> On 4/20/20 2:16 PM, Benjamin Gaignard wrote:
>>> From: Benjamin Gaignard
>>>
>>> Implement clock event driver using low power STM32 t
Hi Benjamin,
On 05/05/2020 09:26, Benjamin GAIGNARD wrote:
>
>
> On 4/20/20 2:16 PM, Benjamin Gaignard wrote:
>> From: Benjamin Gaignard
>>
>> Implement clock event driver using low power STM32 timers.
>> Low power timer counters running even when CPUs are stop
Please review this one, thanks.
https://lkml.org/lkml/2020/5/14/796
-邮件原件-
发件人: tianxianting (RD)
发送时间: 2020年5月14日 9:46
收件人: 'Thomas Gleixner' ; john.stu...@linaro.org;
sb...@kernel.org
抄送: linux-kernel@vger.kernel.org
主题: 答复: [PATCH] timers: use set_current_state macro
Hi Thomas
Thanks
z.h:18:35: warning: its scope is only this
definition or declaration, which is probably not what you want [enabled by
default]
Fixes: ebc0f83c78a2 ("timers/nohz: Update NOHZ load in remote tick")
Cc: Peter Zijlstra
Cc: Frederic Weisbecker
Cc: Thomas Gleixner
Cc: Ingo Molnar
Signed-off
Use set_current_state macro instead of current->state = TASK_RUNNING
Signed-off-by: Xianting Tian
---
kernel/time/timer.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/time/timer.c b/kernel/time/timer.c
index 4820823..b9ecf87 100644
--- a/kernel/time/timer.c
+++
before, and patches were accepted.
-邮件原件-
发件人: Thomas Gleixner [mailto:t...@linutronix.de]
发送时间: 2020年5月14日 5:22
收件人: tianxianting (RD) ; john.stu...@linaro.org;
sb...@kernel.org
抄送: linux-kernel@vger.kernel.org; tianxianting (RD)
主题: Re: [PATCH] timers: use set_current_state macro
Xianting
Prasad,
psoda...@codeaurora.org writes:
> On 2020-05-13 13:28, Thomas Gleixner wrote:
>> psoda...@codeaurora.org writes:
>>> It is not clear to me how to avoid #ifdef's in this case. Could you
>>> please share an example here?
>>
>> The answer is further down already:
>
> I think, you are
Xianting,
Xianting Tian writes:
thanks for your patch.
Can you please fix your mail client to have proper mail headers? It
provides:
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable
but it fails to provide the charset information. That causes the footer
to become
On 2020-05-13 13:28, Thomas Gleixner wrote:
psoda...@codeaurora.org writes:
On 2020-05-06 06:28, Thomas Gleixner wrote:
#ifdef CONFIG_SMP
+struct timer_base timer_base_deferrable;
unsigned int sysctl_timer_migration = 1;
DEFINE_STATIC_KEY_FALSE(timers_migration_enabled);
@@ -841,8 +842,14
psoda...@codeaurora.org writes:
> On 2020-05-06 06:28, Thomas Gleixner wrote:
>>> #ifdef CONFIG_SMP
>>> +struct timer_base timer_base_deferrable;
>>> unsigned int sysctl_timer_migration = 1;
>>>
>>> DEFINE_STATIC_KEY_FALSE(timers_migration_enabled);
>>> @@ -841,8 +842,14 @@ static inline
John Stultz writes:
> On Wed, May 13, 2020 at 2:13 AM Sergey Organov wrote:
>>
>> John Stultz writes:
>>
>> > On Tue, May 12, 2020 at 3:31 PM Eugene Syromiatnikov
>> > wrote:
>> >> On Tue, May 12, 2020 at 10:58:16PM +0300, Sergey Organov wrote:
>> >> > Eugene Syromiatnikov writes:
>> >> >
>>
Hi Tglx,
On 2020-05-06 06:28, Thomas Gleixner wrote:
Prasad Sodagudi writes:
To make all cpu unbound deferrable timers are scalable, introduce a
common
timer base which is only for cpu unbound deferrable timers to make
those
are indeed cpu unbound so that can be scheduled by any of non idle
On Wed, May 13, 2020 at 2:13 AM Sergey Organov wrote:
>
> John Stultz writes:
>
> > On Tue, May 12, 2020 at 3:31 PM Eugene Syromiatnikov
> > wrote:
> >> On Tue, May 12, 2020 at 10:58:16PM +0300, Sergey Organov wrote:
> >> > Eugene Syromiatnikov writes:
> >> >
> >> > > As of now, there is no
John Stultz writes:
> On Tue, May 12, 2020 at 3:31 PM Eugene Syromiatnikov wrote:
>> On Tue, May 12, 2020 at 10:58:16PM +0300, Sergey Organov wrote:
>> > Eugene Syromiatnikov writes:
>> >
>> > > As of now, there is no interface exposed for converting pid/fd into
>> > > clockid and vice versa;
On Tue, May 12, 2020 at 3:31 PM Eugene Syromiatnikov wrote:
> On Tue, May 12, 2020 at 10:58:16PM +0300, Sergey Organov wrote:
> > Eugene Syromiatnikov writes:
> >
> > > As of now, there is no interface exposed for converting pid/fd into
> > > clockid and vice versa; linuxptp, for example, has
On Tue, May 12, 2020 at 10:58:16PM +0300, Sergey Organov wrote:
> Eugene Syromiatnikov writes:
>
> > As of now, there is no interface exposed for converting pid/fd into
> > clockid and vice versa; linuxptp, for example, has been carrying these
> > definitions in missing.h header for quite some
Eugene Syromiatnikov writes:
> As of now, there is no interface exposed for converting pid/fd into
> clockid and vice versa; linuxptp, for example, has been carrying these
> definitions in missing.h header for quite some time[1].
>
> [1]
* Rob Herring [200512 14:53]:
> On Wed, 29 Apr 2020 14:53:49 -0700, Tony Lindgren wrote:
> > The TI dual-mode timer can be used for both clocksource and clockevent
> > system timers. We need a way to specify which dual-mode timers are
> > reserved for system timers as there a
On Wed, 29 Apr 2020 14:53:49 -0700, Tony Lindgren wrote:
> The TI dual-mode timer can be used for both clocksource and clockevent
> system timers. We need a way to specify which dual-mode timers are
> reserved for system timers as there are multiple instances available
> that may req
On 16/04/2020 11.46, Lee Jones wrote:
> On Tue, 07 Jan 2020, Peter Ujfalusi wrote:
>
>> dma_request_slave_channel() is a wrapper on top of dma_request_chan()
>> eating up the error code.
>>
>> By using dma_request_chan() directly the driver can support deferred
>> probing against DMA.
>>
>>
Use set_current_state macro instead of current->state = TASK_RUNNING.
Signed-off-by: Xianting Tian
---
kernel/time/timer.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/time/timer.c b/kernel/time/timer.c
index a5221abb4..7c6d42755 100644
--- a/kernel/time/timer.c
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
x86/timers
branch HEAD: cec5f268cd02d25d2d74807843d8ae0292fe0fb7 x86/delay: Introduce
TPAUSE delay
i386-tinyconfig vmlinux size
We can now init system timers using the dmtimer and 32k counter
based on only devicetree data and drivers/clocksource timers.
Let's configure the clocksource and clockevent, and drop the old
unused platform data.
As we're just dropping platform data, and the early platform data
init is based
We can now init system timers using the dmtimer and 32k counter
based on only devicetree data and drivers/clocksource timers.
Let's configure the clocksource and clockevent, and drop the old
unused platform data.
As we're just dropping platform data, and the early platform data
init is based
We can now init system timers using the dmtimer and 32k counter
based on only devicetree data and drivers/clocksource timers.
Let's configure the clocksource and clockevent, and drop the old
unused platform data.
As we're just dropping platform data, and the early platform data
init is based
As timers no longer need legacy quirk handling, let's move them to
the CONFIG_DEBUG section to make it easier to see which drivers still
need more work.
Let's also add detection for few more older timer revisions while at
it as that makes CONFIG_DEBUG output easier to read with proper names.
Cc
We can now init system timers using the dmtimer and 32k counter
based on only devicetree data and drivers/clocksource timers.
Let's configure the clocksource and clockevent, and drop the old
unused platform data.
As we're just dropping platform data, and the early platform data
init is based
We can now init system timers using the dmtimer and 32k counter
based on only devicetree data and drivers/clocksource timers.
Let's configure the clocksource and clockevent, and drop the old
unused platform data.
As we're just dropping platform data, and the early platform data
init is based
Hi all,
Here's v3 series to udpate omaps to use drivers/clocksource timers for
the 32k counter and dmtimer, and to remove the old legacy platform code.
Please review and test.
I've updated the timer-ti-dm-systimer.c patch based on the comments from
Daniel and Rob, and added support for selecting
We can now init system timers using the dmtimer and 32k counter
based on only devicetree data and drivers/clocksource timers.
Let's configure the clocksource and clockevent, and drop the old
unused platform data.
As we're just dropping platform data, and the early platform data
init is based
We can now init system timers using the dmtimer and 32k counter
based on only devicetree data and drivers/clocksource timers.
Let's configure the clocksource and clockevent, and drop the old
unused platform data.
As we're just dropping platform data, and the early platform data
init is based
The following commit has been merged into the x86/timers branch of tip:
Commit-ID: 46f90c7aad62be1af76588108c730d826308a801
Gitweb:
https://git.kernel.org/tip/46f90c7aad62be1af76588108c730d826308a801
Author:Kyung Min Park
AuthorDate:Fri, 24 Apr 2020 12:37:55 -07:00
The following commit has been merged into the x86/timers branch of tip:
Commit-ID: e8824890249355656968d8846908a313fe231f11
Gitweb:
https://git.kernel.org/tip/e8824890249355656968d8846908a313fe231f11
Author:Thomas Gleixner
AuthorDate:Fri, 24 Apr 2020 12:37:54 -07:00
The following commit has been merged into the x86/timers branch of tip:
Commit-ID: cec5f268cd02d25d2d74807843d8ae0292fe0fb7
Gitweb:
https://git.kernel.org/tip/cec5f268cd02d25d2d74807843d8ae0292fe0fb7
Author:Kyung Min Park
AuthorDate:Fri, 24 Apr 2020 12:37:56 -07:00
Commit 100214889973 ("clocksource: dw_apb_timer_of: use
clocksource_of_init") replaced a publicly available driver
initialization method with one called by the timer_probe() method
available after CLKSRC_OF. In current implementation it traverses
all the timers available in the system
Prasad Sodagudi writes:
> Subject: sched: Add...
How is this related to the scheduler?
> Add a check to find expired unbound deferrable timers
> and trigger softirq for handling timers. This way a CPU
> can process all the expired deferrable timers whenever
> it is out off
Prasad Sodagudi writes:
> To make all cpu unbound deferrable timers are scalable, introduce a common
> timer base which is only for cpu unbound deferrable timers to make those
> are indeed cpu unbound so that can be scheduled by any of non idle cpus.
> This common timer fixes scala
On 4/20/20 2:16 PM, Benjamin Gaignard wrote:
> From: Benjamin Gaignard
>
> Implement clock event driver using low power STM32 timers.
> Low power timer counters running even when CPUs are stopped.
> It could be used as clock event broadcaster to wake up CPUs but not like
> a c
Hi Prasad,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on tip/timers/core]
[also build test ERROR on tip/auto-latest tip/timers/nohz v5.7-rc4
next-20200504]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we
Hi Prasad,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on tip/timers/core]
[also build test ERROR on tip/auto-latest tip/timers/nohz v5.7-rc4
next-20200501]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we
Hi Prasad,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on tip/timers/core]
[also build test ERROR on tip/auto-latest tip/timers/nohz v5.7-rc4
next-20200501]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we
Add a check to find expired unbound deferrable timers
and trigger softirq for handling timers. This way a CPU
can process all the expired deferrable timers whenever
it is out off idle state due to an interrupt.
Signed-off-by: Prasad Sodagudi
---
include/linux/timer.h| 3 +++
kernel/time
These patches are introducing support for global deferrable timers
and this feature is very useful for the mobile chipsets. All comments
in initial discussion [1] are addressed. Here is the latest discussion - [2]
as these patches are in downstream kernel for quite a long time.
[1]- https
is
queued on which is same with queue_delayed_work_on(smp_processor_id())
effectively.
As a result WORK_CPU_UNBOUND work items aren't really cpu unbound now.
In fact this is perfectly fine with UP kernel and also won't affect much a
system without dyntick with SMP kernel too as every cpus run timers
On Wed, Apr 29, 2020 at 4:54 PM Tony Lindgren wrote:
>
> We can now init system timers using the dmtimer and 32k counter
> based on only devicetree data and drivers/clocksource timers.
> Let's configure the clocksource and clockevent, and drop the old
> unused platform data.
&g
@nanos.tec.linutronix.de/
Ref: 33ab0fec3352 ("posix-timers: Consolidate posix_cpu_clock_get()")
Ref: 55e8c8eb2c7b ("posix-cpu-timers: Store a reference to a pid not a task")
Signed-off-by: "Eric W. Biederman"
---
kernel/time/posix-cpu-timers.c | 75 ++--
Taking a clock and returning a pid_type is a more general and
a superset of taking a timer and returning a pid_type.
Perform this generalization so that future changes may use
this code on clocks as well as timers.
Signed-off-by: "Eric W. Biederman"
---
kernel/time/posix-cpu-ti
Now that the code stores of pid references it is no longer necessary
or desirable to take a reference on task_struct in __get_task_for_clock.
Instead extend the scope of rcu_read_lock and remove the reference
counting on struct task_struct entirely.
Signed-off-by: "Eric W. Biederman"
---
The current posix-cpu-timer code uses pids when holding persistent
references in timers. However the lookups from clockid_t still return
tasks that need to be converted into pids for use.
This results in usage being pid->task->pid and that can race with
release_task and de_thread. Th
We can now init system timers using the dmtimer and 32k counter
based on only devicetree data and drivers/clocksource timers.
Let's configure the clocksource and clockevent, and drop the old
unused platform data.
As we're just dropping platform data, and the early platform data
init is based
We can now init system timers using the dmtimer and 32k counter
based on only devicetree data and drivers/clocksource timers.
Let's configure the clocksource and clockevent, and drop the old
unused platform data.
As we're just dropping platform data, and the early platform data
init is based
As timers no longer need legacy quirk handling, let's move them to
the CONFIG_DEBUG section to make it easier to see which drivers still
need more work.
Let's also add detection for few more older timer revisions while at
it as that makes CONFIG_DEBUG output easier to read with proper names.
Cc
The TI dual-mode timer can be used for both clocksource and clockevent
system timers. We need a way to specify which dual-mode timers are
reserved for system timers as there are multiple instances available
that may require a board specific configuration.
Let's add a generic compatible &qu
We can now init system timers using the dmtimer and 32k counter
based on only devicetree data and drivers/clocksource timers.
Let's configure the clocksource and clockevent, and drop the old
unused platform data.
As we're just dropping platform data, and the early platform data
init is based
We can now init system timers using the dmtimer and 32k counter
based on only devicetree data and drivers/clocksource timers.
Let's configure the clocksource and clockevent, and drop the old
unused platform data.
As we're just dropping platform data, and the early platform data
init is based
We can now init system timers using the dmtimer and 32k counter
based on only devicetree data and drivers/clocksource timers.
Let's configure the clocksource and clockevent, and drop the old
unused platform data.
As we're just dropping platform data, and the early platform data
init is based
We can now init system timers using the dmtimer and 32k counter
based on only devicetree data and drivers/clocksource timers.
Let's configure the clocksource and clockevent, and drop the old
unused platform data.
As we're just dropping platform data, and the early platform data
init is based
We can now init system timers using the dmtimer and 32k counter
based on only devicetree data and drivers/clocksource timers.
Let's configure the clocksource and clockevent, and drop the old
unused platform data.
As we're just dropping platform data, and the early platform data
init is based
Hi all,
Here's v2 series to udpate omaps to use drivers/clocksource timers for
the 32k counter and dmtimer, and to remove the old legacy platform code.
Please review and test.
I've updated the timer-ti-dm-systimer.c patch based on the comments from
Daniel, and also updated the dts files
.
Signed-off-by: Masahiro Yamada
Acked-by: Sam Ravnborg
---
Changes in v2: None
samples/Kconfig | 4
samples/Makefile| 1 +
samples/timers/Makefile | 17 +++--
3 files changed, 8 insertions(+), 14 deletions(-)
diff --git a/samples/Kconfig b/samples/Kconfig
index
Hi Prasad,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on tip/timers/core]
[also build test ERROR on tip/auto-latest tip/timers/nohz v5.7-rc3
next-20200428]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we
Hi Prasad,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on tip/timers/core]
[also build test ERROR on tip/auto-latest tip/timers/nohz v5.7-rc3
next-20200428]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we
Hi Prasad,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on tip/timers/core]
[also build test WARNING on tip/auto-latest tip/timers/nohz v5.7-rc3
next-20200428]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system
These patches introduce support for global deferrable timers and this feature
is very useful
for the mobile chipsets and initial discussion link -[1]. Lastest discussion
was with - [2]
as these patches are in downstream kernel for quite a long time.
[1]- https://lore.kernel.org/patchwork/patch
is
queued on which is same with queue_delayed_work_on(smp_processor_id())
effectively.
As a result WORK_CPU_UNBOUND work items aren't really cpu unbound now.
In fact this is perfectly fine with UP kernel and also won't affect much a
system without dyntick with SMP kernel too as every cpus run timers
Add a check for cpu unbound deferrable timer expiry and raise
softirq for handling the expired timers so that the CPU can
process the cpu unbound deferrable times as early as possible
when a cpu tries to enter/exit idle loop.
Signed-off-by: Prasad Sodagudi
---
include/linux/timer.h| 3
On 04/27, Eric W. Biederman wrote:
>
> Oleg Nesterov writes:
>
> > Eric,
> >
> > I am sick today and can't read the code, but I feel this patch is not
> > right ... please correct me.
>
>
> > So, iiuc when posix_cpu_timer_create() is called and CPUCLOCK_PERTHREAD
> > is false we roughly have
> >
The following commit has been merged into the timers/urgent branch of tip:
Commit-ID: 086ee46b08634a999bcd1707eabe3b0dc1806674
Gitweb:
https://git.kernel.org/tip/086ee46b08634a999bcd1707eabe3b0dc1806674
Author:Ben Dooks (Codethink)
AuthorDate:Tue, 22 Oct 2019 14:12:26 +01
The following commit has been merged into the timers/urgent branch of tip:
Commit-ID: 7f2cbcbcafbca5360efbd175b3320852b8f7c637
Gitweb:
https://git.kernel.org/tip/7f2cbcbcafbca5360efbd175b3320852b8f7c637
Author:Yi Wang
AuthorDate:Mon, 21 Oct 2019 15:44:12 +08:00
Committer
The following commit has been merged into the timers/urgent branch of tip:
Commit-ID: 1638b8f096ca165965189b9626564c933c79fe63
Gitweb:
https://git.kernel.org/tip/1638b8f096ca165965189b9626564c933c79fe63
Author:Thomas Gleixner
AuthorDate:Mon, 21 Oct 2019 12:07:15 +02:00
Include the timekeeping.h header to get the declaration of the
sched_clock_{suspend,resume} functions. Fixes the following
sparse warnings:
kernel/time/sched_clock.c:275:5: warning: symbol 'sched_clock_suspend' was not
declared. Should it be static?
kernel/time/sched_clock.c:286:6: warning:
Commit b7be4ef1365d ("posix-cpu-timers: Switch thread group sampling to
array") and commit 001f7971433a ("posix-cpu-timers: Make expiry checks
array based") made some modification on parameters of function
thread_group_sample_cputime() and task_cputimers_expired(), but forgot
t
The pull request you sent on Sun, 20 Oct 2019 10:13:56 -:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> timers-urgent-for-linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/188768f3c0727d4cb95eaad6c67799449aebcc03
Thank you!
--
Deet-do
Linus,
please pull the latest timers-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
timers-urgent-for-linus
up to: ff229eee3d89: hrtimer: Annotate lockless access to timer->base
A single commit annotating the lockcless access to timer-&g
On Sun, Oct 13, 2019 at 9:28 PM kbuild test robot wrote:
>
> Hi Dmitry,
>
> Thank you for the patch! Yet something to improve:
>
> [auto build test ERROR on linus/master]
> [cannot apply to v5.4-rc2 next-20191011]
> [if your patch is applied to the wrong git tree, please drop us a note to help
>
The following commit has been merged into the timers/urgent branch of tip:
Commit-ID: ff229eee3d897f52bd001c841f2d3cce8853ecdc
Gitweb:
https://git.kernel.org/tip/ff229eee3d897f52bd001c841f2d3cce8853ecdc
Author:Eric Dumazet
AuthorDate:Tue, 08 Oct 2019 10:32:04 -07:00
Hi Dmitry,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linus/master]
[cannot apply to v5.4-rc2 next-20191011]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify
Hi Dmitry,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linus/master]
[cannot apply to v5.4-rc2 next-20191011]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify
From: Andrei Vagin
Wire timer_settime() syscall into time namespace virtualization.
sys_timer_settime() calls the ktime->timer_set() callback. Right now,
common_timer_set() is the only implementation for the callback.
There user-supplied timer's value is converted from timespec64 to ktime
and
From: Andrei Vagin
clock_nanosleep() accepts absolute values of expiration time, if the
TIMER_ABSTIME flag is set. This value is in the task time namespace,
which has to be converted to the host time namespace.
Signed-off-by: Andrei Vagin
Co-developed-by: Dmitry Safonov
Signed-off-by: Dmitry
From: Andrei Vagin
Now, when the clock_get_ktime() callback exists, the suboptimal
timespec64-based conversion can be removed from common_timer_get().
Suggested-by: Thomas Gleixner
Signed-off-by: Andrei Vagin
Co-developed-by: Dmitry Safonov
Signed-off-by: Dmitry Safonov
---
it by don't advertise direct mode
synthetic timers and discarding the inject when lapic is not in kernel.
syzkaller source: https://syzkaller.appspot.com/x/repro.c?x=1752fe0a60
Reported-by: syzbot+dff25ee91f0c7d5c1...@syzkaller.appspotmail.com
Cc: Paolo Bonzini
Cc: Radim Krčmář
Signed-off
it by don't advertise direct mode
synthetic timers and discarding the inject when lapic is not in kernel.
syzkaller source: https://syzkaller.appspot.com/x/repro.c?x=1752fe0a60
Reported-by: syzbot+dff25ee91f0c7d5c1...@syzkaller.appspotmail.com
Cc: Paolo Bonzini
Cc: Radim Krčmář
Signed-off
From: Thomas Gleixner
[ Upstream commit 692117c1f7a6770ed41dd8f277cd9fed1dfb16f1 ]
Warning when p == NULL and then proceeding and dereferencing p does not
make any sense as the kernel will crash with a NULL pointer dereference
right away.
Bailing out when p == NULL and returning an error code
From: Thomas Gleixner
[ Upstream commit 692117c1f7a6770ed41dd8f277cd9fed1dfb16f1 ]
Warning when p == NULL and then proceeding and dereferencing p does not
make any sense as the kernel will crash with a NULL pointer dereference
right away.
Bailing out when p == NULL and returning an error code
From: Thomas Gleixner
[ Upstream commit 692117c1f7a6770ed41dd8f277cd9fed1dfb16f1 ]
Warning when p == NULL and then proceeding and dereferencing p does not
make any sense as the kernel will crash with a NULL pointer dereference
right away.
Bailing out when p == NULL and returning an error code
it by don't advertise direct mode
synthetic timers and discarding the inject when lapic is not in kernel.
syzkaller source: https://syzkaller.appspot.com/x/repro.c?x=1752fe0a60
Reported-by: syzbot+dff25ee91f0c7d5c1...@syzkaller.appspotmail.com
Cc: Paolo Bonzini
Cc: Radim Krčmář
Signed-off
it by don't advertise direct mode
synthetic timers and discarding the inject when lapic is not in kernel.
syzkaller source: https://syzkaller.appspot.com/x/repro.c?x=1752fe0a60
Reported-by: syzbot+dff25ee91f0c7d5c1...@syzkaller.appspotmail.com
Cc: Paolo Bonzini
Cc: Radim Krčmář
Signed-off
The following commit has been merged into the timers/core branch of tip:
Commit-ID: b9023b91dd020ad7e093baa5122b6968c48cc9e0
Gitweb:
https://git.kernel.org/tip/b9023b91dd020ad7e093baa5122b6968c48cc9e0
Author:Balasubramani Vivekanandan
AuthorDate:Thu, 26 Sep 2019 15:51:01
On Mon, 23 Sep 2019, Sebastian Andrzej Siewior wrote:
> Patch ("posix-timers: Add expiry lock") acquired a lock in
> run_posix_cpu_timers() but didn't drop the lock in the early return.
>
> Unlock the lock in the early return path.
>
> Reported-by: kbuild te
401 - 500 of 9144 matches
Mail list logo
