On Tue, Feb 7, 2017 at 3:40 PM, Kees Cook wrote:
> Currently CONFIG_TIMER_STATS exposes process information across namespaces:
>
> kernel/time/timer_list.c print_timer():
>
> SEQ_printf(m, ", %s/%d", tmp, timer->start_pid);
>
> /proc/timer_list:
>
> #11: <>, hrtimer_wakeup
On Wed, Feb 8, 2017 at 2:24 AM, Thomas Gleixner wrote:
> On Tue, 7 Feb 2017, John Stultz wrote:
>> On Tue, Feb 7, 2017 at 3:40 PM, Kees Cook wrote:
>> > Currently CONFIG_TIMER_STATS exposes process information across namespaces:
>> >
>> >
On Tue, Aug 1, 2017 at 5:55 AM, Prarit Bhargava wrote:
> printk.time=1/CONFIG_PRINTK_TIME=1 adds a unmodified local hardware clock
> timestamp to printk messages. The local hardware clock loses time each
> day making it difficult to determine exactly when an issue has occurred in
> the kernel log
On Tue, Aug 1, 2017 at 10:35 AM, Prarit Bhargava wrote:
>
>
> On 08/01/2017 01:00 PM, John Stultz wrote:
>> Is there a reason your not also adding PRINTK_TIME_BOOT here (which to
>> me would be more generally useful then REAL or MONO)?
>
> REAL has been useful to me in
va
> Cc: Mark Salyzyn
> Cc: Jonathan Corbet
> Cc: Petr Mladek
> Cc: Sergey Senozhatsky
> Cc: Steven Rostedt
> Cc: John Stultz
> Cc: Thomas Gleixner
> Cc: Stephen Boyd
> Cc: Andrew Morton
> Cc: Greg Kroah-Hartman
> Cc: "Paul E. McKenney"
>
On Mon, Aug 7, 2017 at 11:04 AM, Prarit Bhargava wrote:
> On 08/07/2017 12:52 PM, John Stultz wrote:
>> Still not quite following why you're updating all the defconfigs. I'd
>> make sure the Kconfig default settings are right, and leave updating
>> the defconfig
> diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
> index 98fe715522e8..c303b235a0b1 100644
> --- a/lib/Kconfig.debug
> +++ b/lib/Kconfig.debug
> @@ -1,19 +1,61 @@
> menu "printk and dmesg options"
>
> +choice
> + prompt "printk default clock timestamp"
> +
> +config PRINTK_TIME_DISABLE
>
ping changes into separate patch. Minor include file cleanup.
Signed-off-by: Prarit Bhargava
Cc: Mark Salyzyn
Cc: Jonathan Corbet
Cc: Petr Mladek
Cc: Sergey Senozhatsky
Cc: Steven Rostedt
Cc: John Stultz
Cc: Thomas Gleixner
Cc: Stephen Boyd
Cc: Andrew Morton
Cc: Greg Kroah-Hartman
Cc
On Wed, Aug 16, 2017 at 9:46 PM, John Stultz wrote:
> From: Prarit Bhargava
>
>
> Prarit,
> So I took my own shot at cleaning up the Kconfig settings to make
> it a bit more sane in my opinion. This should allow the legacy
> defconfigs to just work, and avoids all the d
On Wed, Aug 23, 2017 at 11:31 AM, Prarit Bhargava wrote:
> On 08/23/2017 04:45 AM, Petr Mladek wrote:
>> I know that it would make the code more complicated. But
>> I really like the approach used by /sys/power/disk or
>> /sys/power/pm_test. They list all possible values
>> and put the selected on
On Thu, Aug 24, 2017 at 6:42 AM, Prarit Bhargava wrote:
> --- a/include/linux/timekeeping.h
> +++ b/include/linux/timekeeping.h
> @@ -239,6 +239,7 @@ static inline u64 ktime_get_raw_ns(void)
> extern u64 ktime_get_mono_fast_ns(void);
> extern u64 ktime_get_raw_fast_ns(void);
> extern u64 ktime_
On Wed, Aug 3, 2016 at 10:04 PM, Bjorn Andersson
wrote:
> Use the managed resource version of reboot_mode_register().
>
> Cc: John Stultz
> Signed-off-by: Bjorn Andersson
> ---
>
> John, here's a "pointer" to what I meant with my comment on your
> sram
On Wed, Aug 3, 2016 at 10:04 PM, Bjorn Andersson
wrote:
> Provide managed resource version of reboot_mode_register() and
> reboot_mode_unregister() to simplify implementations.
>
> Cc: John Stultz
> Signed-off-by: Bjorn Andersson
> ---
>
> John, here's a &quo
13 matches
Mail list logo