On 02/12/2018 10:44 AM, Peter Zijlstra wrote:
> On Mon, Feb 12, 2018 at 10:18:06AM -0500, Prarit Bhargava wrote:
>>> But when I specify "earlyprintk=serial,ttyS0,115200" this SPCR crud will
>>> not interfere?
>>>
>>
>> I tested "ea
On 02/12/2018 09:56 AM, Peter Zijlstra wrote:
> On Mon, Feb 12, 2018 at 08:47:57AM -0500, Prarit Bhargava wrote:
>>
>>
>> On 02/12/2018 08:34 AM, Peter Zijlstra wrote:
>>> On Thu, Jan 18, 2018 at 10:09:51AM -0500, Prarit Bhargava wrote:
>>>> config ACPI
On 02/12/2018 09:43 AM, Timur Tabi wrote:
> On 2/12/18 7:47 AM, Prarit Bhargava wrote:
>> ACPI SPCR is used by a vendor to define the serial console for a system. If
>> SPCR exists a user can add kernel parameter "earlycon" (no extra kernel
>> parameters
On 02/12/2018 08:34 AM, Peter Zijlstra wrote:
> On Thu, Jan 18, 2018 at 10:09:51AM -0500, Prarit Bhargava wrote:
>> config ACPI_SPCR_TABLE
>> +bool "ACPI Serial Port Console Redirection Support"
>> +default y if X86
>> +help
>> +
On 01/22/2018 04:49 PM, Timur Tabi wrote:
> On 01/18/2018 09:09 AM, Prarit Bhargava wrote:
>> if (acpi_disabled) {
>> -if (earlycon_init_is_deferred)
>> +if (earlycon_acpi_spcr_enable)
>
> This patch works for me, so I can ACK it, but fir
default. Modify acpi_parse_spcr() to allow options for initializing
the early console and console separately.
Signed-off-by: Prarit Bhargava <pra...@redhat.com>
Cc: linux-a...@vger.kernel.org
Cc: linux-doc@vger.kernel.org
Cc: linux-arm-ker...@lists.infradead.org
Cc: linux...@vger.kernel.org
[Sorry everyone for the late response, I went away on vacation and pushed this
off until I returned.]
On 12/13/2017 07:45 AM, Lorenzo Pieralisi wrote:
> [+Mark, Graeme]
>
> In $SUBJECT, s/avialable/available
>
> On Mon, Dec 11, 2017 at 10:50:58AM -0500, Prarit Bhargava
ven if SMT is disabled.
topology_max_smt_threads() already returns the active number of threads.
Introduce topology_hw_smt_threads() which returns the maximum number of
threads. These are used to fix and replace references to smp_num_siblings.
Signed-off-by: Prarit Bhargava <pra...@redhat.co
The ACPI SPCR code has been used to define an earlycon console for ARM64
and can be used for x86.
Modify the ACPI SPCR parsing code to account for console behaviour
differences between ARM64 and x86. Initialize the SPCR code from
x86 ACPI initialization code.
Signed-off-by: Prarit Bhargava <
systems to test Qualcomm quirks, HPE Mantis system to test xgene
quirks. Tested several x86 systems with and without a SPCR to confirm
no changes in default behaviour.
[v2]: See 1/2 for code changes.
Signed-off-by: Prarit Bhargava <pra...@redhat.com>
Cc: linux-doc@vger.kernel.org
Cc: lin
the Documention on the use of
the SPCR.
[v2]: Don't return an error in the baud_rate check of acpi_parse_spcr().
Keep ACPI_SPCR_TABLE selected for ARM64. Fix 8-bit port access width
mmio value. Move baud rate check earlier.
Signed-off-by: Prarit Bhargava <pra...@redhat.com>
Cc: linux-doc@vger.kern
On 12/07/2017 01:43 PM, Timur Tabi wrote:
> On Thu, Dec 7, 2017 at 11:29 AM, Prarit Bhargava <pra...@redhat.com> wrote:
>> Other architectures can use SPCR to setup an early console or console but
>> the current code is ARM64 specific.
>>
>> Change the name o
On 12/08/2017 10:31 AM, Jeffrey Hugo wrote:
> On 12/8/2017 7:29 AM, Prarit Bhargava wrote:
>>
>>
>> On 12/08/2017 01:29 AM, Ingo Molnar wrote:
>>>
>>> * Prarit Bhargava <pra...@redhat.com> wrote:
>>>
>>>> The SPCR (Seri
On 12/08/2017 01:29 AM, Ingo Molnar wrote:
>
> * Prarit Bhargava <pra...@redhat.com> wrote:
>
>> The SPCR (Serial Port Console Redirection) Table provides information
>> about the configuration of serial port. This information can be used
>> to configur
On 12/07/2017 01:46 PM, Timur Tabi wrote:
> On Thu, Dec 7, 2017 at 11:29 AM, Prarit Bhargava <pra...@redhat.com> wrote:
>> -int __init acpi_parse_spcr(bool earlycon)
>> +int __init acpi_parse_spcr(bool earlycon, bool enable_console)
>> {
>> sta
or
earlycon parameter is defined and the SPCR exists , the serial port is not
configured. If the earlycon parameter is used both the early console
and the console are configured using the data from the SPCR.
Signed-off-by: Prarit Bhargava <pra...@redhat.com>
Cc: linux-doc@vger.kernel.org
Cc:
On 09/26/2017 07:48 AM, Petr Mladek wrote:
> On Mon 2017-09-18 13:51:00, 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
On 09/17/2017 06:46 AM, Sergey Senozhatsky wrote:
> I'm a bit uncomfortable with the "breaks user space" part. since this
> is a strictly debugging option, would it be sufficient to store those
> extended timestamps as prefixes of every message?
> see (sorry for "self-quoting"):
>
-by: Prarit Bhargava <pra...@redhat.com>
Cc: Mark Salyzyn <saly...@android.com>
Cc: Jonathan Corbet <cor...@lwn.net>
Cc: Petr Mladek <pmla...@suse.com>
Cc: Sergey Senozhatsky <sergey.senozhat...@gmail.com>
Cc: Steven Rostedt <rost...@goodmis.org>
Cc: John Stultz <john
On 09/15/2017 09:28 AM, Petr Mladek wrote:
>
> I am still slightly nervous that external tools would need updating.
> Also they might have troubles to interpret the time stamps especially
> when the source is changed at runtime via
> /sys/module/printk/parameters/time.
In earlier versions I
issues relate to each other in real time.
Add monotonic, boottime, and real clock timestamps in addition to the existing
local hardware clock timestamp.
Signed-off-by: Prarit Bhargava <pra...@redhat.com>
Cc: Mark Salyzyn <saly...@android.com>
Cc: Jonathan Corbet <cor...@lwn.net&g
name param
functions. Adjust configs, enum, and timestamp_sources_str to be 0-4.
Add mention realtime clock is UTC in Documentation.
v9: Fix typo. Add __ktime_get_real_fast_ns_unsafe().
v10: Remove time parameter restrictions.
Signed-off-by: Prarit Bhargava <pra...@redhat.com>
Cc: Ma
Adjust configs, enum, and timestamp_sources_str to be 0-4.
Add mention realtime clock is UTC in Documentation.
v9: Fix typo. Add __ktime_get_real_fast_ns_unsafe().
v10: Remove time parameter restrictions.
Signed-off-by: Prarit Bhargava <pra...@redhat.com>
Cc: Mark Salyzyn <saly...@android.
issues relate to each other in real time.
Add monotonic, boottime, and real clock timestamps in addition to the existing
local hardware clock timestamp.
Signed-off-by: Prarit Bhargava <pra...@redhat.com>
Cc: Mark Salyzyn <saly...@android.com>
Cc: Jonathan Corbet <cor...@lwn.net&g
Adjust configs, enum, and timestamp_sources_str to be 0-4.
Add mention realtime clock is UTC in Documentation.
v9: Fix typo. Add __ktime_get_real_fast_ns_unsafe().
Signed-off-by: Prarit Bhargava <pra...@redhat.com>
Cc: Mark Salyzyn <saly...@android.com>
Cc: Jonathan Corbet <cor...@l
issues relate to each other in real time.
Add monotonic, boottime, and real clock timestamps in addition to the existing
local hardware clock timestamp.
Signed-off-by: Prarit Bhargava <pra...@redhat.com>
Cc: Mark Salyzyn <saly...@android.com>
Cc: Jonathan Corbet <cor...@lwn.net&g
On 08/24/2017 02:50 PM, John Stultz wrote:
> On Thu, Aug 24, 2017 at 6:42 AM, Prarit Bhargava <pra...@redhat.com> wrote:
>> --- a/include/linux/timekeeping.h
>> +++ b/include/linux/timekeeping.h
>> @@ -239,6 +239,7 @@ static inline u64 ktime_get_raw_ns(void)
>>
issues relate to each other in real time.
Add monotonic, boottime, and real clock timestamps in addition to the existing
local hardware clock timestamp.
Signed-off-by: Prarit Bhargava <pra...@redhat.com>
Cc: Mark Salyzyn <saly...@android.com>
Cc: Jonathan Corbet <cor...@lwn.net&g
On 08/23/2017 04:45 AM, Petr Mladek wrote:
> On Thu 2017-08-17 09:15:39, 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
On 08/22/2017 10:23 AM, Petr Mladek wrote:
> On Tue 2017-08-22 10:09:40, Prarit Bhargava wrote:
>>
>>
>> On 08/17/2017 11:30 AM, Mark Salyzyn wrote:
>>> On 08/17/2017 06:15 AM, Prarit Bhargava wrote:
>>>> printk.time=1/CONFIG_PRINTK_TIME=1 adds a unmo
On 08/17/2017 11:30 AM, Mark Salyzyn wrote:
> On 08/17/2017 06:15 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
Signed-off-by: Prarit Bhargava <pra...@redhat.com>
Cc: Mark Salyzyn <saly...@android.com>
Cc: Jonathan Corbet <cor...@lwn.net>
Cc: Petr Mladek <pmla...@suse.com>
Cc: Sergey Senozhatsky <sergey.senozhat...@gmail.com>
Cc: Steven Rostedt <rost...@goodmis.org>
issues relate to each other in real time.
Add monotonic, boottime, and real clock timestamps in addition to the existing
local hardware clock timestamp.
Signed-off-by: Prarit Bhargava <pra...@redhat.com>
Cc: Mark Salyzyn <saly...@android.com>
Cc: Jonathan Corbet <cor...@lwn.net&g
On 08/17/2017 12:46 AM, John Stultz wrote:
> From: Prarit Bhargava <pra...@redhat.com>
>
>
> 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, a
NDEFINED for !CONFIG_PRINTK builds. Separate
timekeeping changes into separate patch. Minor include file cleanup.
Signed-off-by: Prarit Bhargava <pra...@redhat.com>
Cc: Mark Salyzyn <saly...@android.com>
Cc: Jonathan Corbet <cor...@lwn.net>
Cc: Petr Mladek <pmla...@suse.com>
Cc: Ser
issues relate to each other in real time.
Add monotonic, boottime, and real clock timestamps in addition to the existing
local hardware clock timestamp.
Signed-off-by: Prarit Bhargava <pra...@redhat.com>
Cc: Mark Salyzyn <saly...@android.com>
Cc: Jonathan Corbet <cor...@lwn.net&g
: Christoffer Dall <cd...@linaro.org>
Cc: Deepa Dinamani <deepa.ker...@gmail.com>
Cc: Ingo Molnar <mi...@kernel.org>
Cc: Joel Fernandes <joe...@google.com>
Cc: Prarit Bhargava <pra...@redhat.com>
Cc: Kees Cook <keesc...@chromium.org>
Cc: Peter Zijlstra <pet..
On 08/09/2017 02:24 PM, Luis R. Rodriguez wrote:
> On Mon, Aug 07, 2017 at 02:17:33PM -0400, Prarit Bhargava wrote:
>>
>>
>> On 08/07/2017 01:14 PM, Luis R. Rodriguez wrote:
>>
>>>
>>> Note printk_late_init() is a late_initcall(). This mean
On 08/08/2017 04:28 AM, Peter Zijlstra wrote:
> On Mon, Aug 07, 2017 at 01:36:39PM -0700, Paul E. McKenney wrote:
>> On Mon, Aug 07, 2017 at 04:06:09PM -0400, Prarit Bhargava wrote:
>
>>> peterz? Want to offer a suggestion? The issue is that I'm changing a bool
>&g
On 08/07/2017 08:19 PM, Sergey Senozhatsky wrote:
> On (08/07/17 11:52), Prarit Bhargava wrote:
> [..]
>> +if (strlen(param) == 1) {
>> +/* Preserve legacy boolean settings */
>> +if (!strcmp("0", param) || !strcmp("n&quo
On 08/07/2017 08:19 PM, Sergey Senozhatsky wrote:
> On (08/07/17 11:52), Prarit Bhargava wrote:
> [..]
>> +/**
>> + * enum printk_time_type - Timestamp types for printk() messages.
>> + * @PRINTK_TIME_DISABLE: No time stamp.
>> + * @PRINTK_TIME_LOCAL:
On 08/07/2017 02:47 PM, John Stultz wrote:
> On Mon, Aug 7, 2017 at 11:04 AM, Prarit Bhargava <pra...@redhat.com> 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 K
On 08/07/2017 01:14 PM, Luis R. Rodriguez wrote:
>
> Note printk_late_init() is a late_initcall(). This means if the
> printk_time_setting was disabled it will take a while to enable it. Enabling
> it
> is done at the device_initcall(), so if printk setting is disabled but a user
> enables it
On 08/07/2017 12:58 PM, Mark Salyzyn wrote:
> On 08/07/2017 08:52 AM, Prarit Bhargava wrote:
>> diff --git a/arch/arm/configs/aspeed_g4_defconfig
>> b/arch/arm/configs/aspeed_g4_defconfig
>> index cfc2465e8b77..5f3c50914e92 100644
>> --- a/arch/arm/configs/aspeed_g4_
On 08/07/2017 12:52 PM, John Stultz wrote:
> On Mon, Aug 7, 2017 at 8:52 AM, Prarit Bhargava <pra...@redhat.com> wrote:
>> printk.time=1/CONFIG_PRINTK_TIME=1 adds a unmodified local hardware clock
>> timestamp to printk messages. The local hardware clock loses ti
On 08/04/2017 11:36 AM, Mark Salyzyn wrote:
> On 08/03/2017 06:18 PM, Prarit Bhargava wrote:
>
>> diff --git a/arch/arm/configs/aspeed_g4_defconfig
>> b/arch/arm/configs/aspeed_g4_defconfig
>> index cfc2465e8b77..6c73c305ad17 100644
>> --- a/arch/arm/configs/asp
ionality.
Signed-off-by: Prarit Bhargava <pra...@redhat.com>
Cc: Mark Salyzyn <saly...@android.com>
Cc: Jonathan Corbet <cor...@lwn.net>
Cc: Petr Mladek <pmla...@suse.com>
Cc: Sergey Senozhatsky <sergey.senozhat...@gmail.com>
Cc: Steven Rostedt <rost...@goodmis.org>
On 08/01/2017 01:00 PM, John Stultz wrote:
> On Tue, Aug 1, 2017 at 5:55 AM, Prarit Bhargava <pra...@redhat.com> wrote:
>> printk.time=1/CONFIG_PRINTK_TIME=1 adds a unmodified local hardware clock
>> timestamp to printk messages. The local hardware clock loses ti
lock in the call to
ktime_get_log_ts() in printk_get_ts().
v2: Use peterz's suggested Kconfig options. Merge patchset together. Fix
i386 !CONFIG_PRINTK builds.
Signed-off-by: Prarit Bhargava <pra...@redhat.com>
Cc: Mark Salyzyn <saly...@android.com>
Cc: Jonathan Corbet <cor...@lwn.n
On 07/25/2017 08:55 AM, Luis R. Rodriguez wrote:
> On Tue, Jul 25, 2017 at 08:17:26AM -0400, Prarit Bhargava wrote:
>> diff --git a/kernel/printk/printk.c b/kernel/printk/printk.c
>> index fc47863f629c..26cf6cadd267 100644
>> --- a/kernel/printk/printk.c
>> +
On 07/25/2017 09:00 AM, Peter Zijlstra wrote:
> On Tue, Jul 25, 2017 at 08:17:27AM -0400, Prarit Bhargava wrote:
>> diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
>> index 5b1662ec546f..6cd38a25f8ea 100644
>> --- a/lib/Kconfig.debug
>> +++ b/lib/Kconfig.debug
hout the protection of a sequence lock in the
call to ktime_get_log_ts() in printk_get_ts().
Signed-off-by: Prarit Bhargava <pra...@redhat.com>
Cc: Mark Salyzyn <saly...@android.com>
Cc: Jonathan Corbet <cor...@lwn.net>
Cc: Petr Mladek <pmla...@suse.com>
Cc: Sergey Senozhatsky <s
ion of a sequence lock in the call to
ktime_get_log_ts() in printk_get_ts().
Signed-off-by: Prarit Bhargava <pra...@redhat.com>
Cc: Mark Salyzyn <saly...@android.com>
Cc: Jonathan Corbet <cor...@lwn.net>
Cc: Petr Mladek <pmla...@suse.com>
Cc: Sergey Senozhatsky <sergey.sen
CONFIG_PRINTK_TIME is a bool and in order to add timestamp options for
the monotonic and real time clock it must be expanded to an int.
Signed-off-by: Prarit Bhargava <pra...@redhat.com>
Cc: Mark Salyzyn <saly...@android.com>
Cc: Jonathan Corbet <cor...@lwn.net>
Cc: Petr Mladek
ity of permanently blacklisting a module
by its name via the kernel parameter module_blacklist=module_name.
[v2]: Rusty, use core_param() instead of __setup() which simplifies
things.
[v3]: Rusty, undo wreckage from strsep()
[v4]: Rusty, simpler version of blacklisted()
Signed-off-by: Prarit Bhargava &
ist=module_name.
[v2]: Rusty, use core_param() instead of __setup() which simplifies
things.
[v3]: Rusty, undo wreckage from strsep()
Signed-off-by: Prarit Bhargava <pra...@redhat.com>
Cc: Jonathan Corbet <cor...@lwn.net>
Cc: Rusty Russell <ru...@rustcorp.com.au>
Cc: linu
things.
[v3]: Rusty, undo wreckage from strsep()
Signed-off-by: Prarit Bhargava <pra...@redhat.com>
Cc: Jonathan Corbet <cor...@lwn.net>
Cc: Rusty Russell <ru...@rustcorp.com.au>
Cc: linux-doc@vger.kernel.org
---
Documentation/kernel-parameters.txt |3 ++
On 06/14/2016 05:20 PM, Rusty Russell wrote:
> Prarit Bhargava <pra...@redhat.com> writes:
>> Blacklisting a module in linux has long been a problem. The current
>> procedure is to use rd.blacklist=module_name, however, that doesn't
>> cover the case after the initram
On 06/14/2016 01:17 PM, Christoph Hellwig wrote:
> On Mon, Jun 13, 2016 at 08:32:41AM -0400, Prarit Bhargava wrote:
>> Blacklisting a module in linux has long been a problem. The process of
>> blacklisting a module has changed over time, and it seems that every OS
>
simplifies things.
Signed-off-by: Prarit Bhargava <pra...@redhat.com>
Cc: Jonathan Corbet <cor...@lwn.net>
Cc: Rusty Russell <ru...@rustcorp.com.au>
Cc: linux-doc@vger.kernel.org
---
Documentation/kernel-parameters.txt |3 +++
kernel/module.c
60 matches
Mail list logo
