Kay
On Thu, Aug 2, 2012 at 7:19 PM, Pandita, Vikram wrote:
> Kay
>
> On Thu, Aug 2, 2012 at 5:06 PM, Kay Sievers wrote:
>> On Fri, Aug 3, 2012 at 1:50 AM, Pandita, Vikram
>> wrote:
>>> On Thu, Aug 2, 2012 at 1:08 PM, Kay Sievers wrote:
>>
How is that supposed to be useful?
The
Kay
On Thu, Aug 2, 2012 at 7:19 PM, Pandita, Vikram vikram.pand...@ti.com wrote:
Kay
On Thu, Aug 2, 2012 at 5:06 PM, Kay Sievers k...@vrfy.org wrote:
On Fri, Aug 3, 2012 at 1:50 AM, Pandita, Vikram vikram.pand...@ti.com
wrote:
On Thu, Aug 2, 2012 at 1:08 PM, Kay Sievers k...@vrfy.org
Kay
On Thu, Aug 2, 2012 at 5:06 PM, Kay Sievers wrote:
> On Fri, Aug 3, 2012 at 1:50 AM, Pandita, Vikram wrote:
>> On Thu, Aug 2, 2012 at 1:08 PM, Kay Sievers wrote:
>
>>> How is that supposed to be useful?
>>>
>>> The prefix is added while exporting data from the kmsg buffer, which
>>> is
On Fri, Aug 3, 2012 at 1:50 AM, Pandita, Vikram wrote:
> On Thu, Aug 2, 2012 at 1:08 PM, Kay Sievers wrote:
>> How is that supposed to be useful?
>>
>> The prefix is added while exporting data from the kmsg buffer, which
>> is just the CPU that *reads* the data from the buffer, not the one
>>
Kay
On Thu, Aug 2, 2012 at 1:08 PM, Kay Sievers wrote:
>
> On Thu, Aug 2, 2012 at 9:46 PM, Vikram Pandita
> wrote:
> > From: Vikram Pandita
> >
> > Introduce config option to enable CPU id reporting for printk() calls.
> >
> > Its sometimes very useful to have printk also print the CPU
On Thu, Aug 2, 2012 at 9:46 PM, Vikram Pandita wrote:
> From: Vikram Pandita
>
> Introduce config option to enable CPU id reporting for printk() calls.
>
> Its sometimes very useful to have printk also print the CPU Identifier
> that executed the call. This has helped to debug various SMP issues
From: Vikram Pandita
Introduce config option to enable CPU id reporting for printk() calls.
Its sometimes very useful to have printk also print the CPU Identifier
that executed the call. This has helped to debug various SMP issues on shipping
products.
Known limitation is, if the system gets
From: Vikram Pandita vikram.pand...@ti.com
Introduce config option to enable CPU id reporting for printk() calls.
Its sometimes very useful to have printk also print the CPU Identifier
that executed the call. This has helped to debug various SMP issues on shipping
products.
Known limitation is,
On Thu, Aug 2, 2012 at 9:46 PM, Vikram Pandita vikram.pand...@ti.com wrote:
From: Vikram Pandita vikram.pand...@ti.com
Introduce config option to enable CPU id reporting for printk() calls.
Its sometimes very useful to have printk also print the CPU Identifier
that executed the call. This
Kay
On Thu, Aug 2, 2012 at 1:08 PM, Kay Sievers k...@vrfy.org wrote:
On Thu, Aug 2, 2012 at 9:46 PM, Vikram Pandita vikram.pand...@ti.com
wrote:
From: Vikram Pandita vikram.pand...@ti.com
Introduce config option to enable CPU id reporting for printk() calls.
Its sometimes very useful
On Fri, Aug 3, 2012 at 1:50 AM, Pandita, Vikram vikram.pand...@ti.com wrote:
On Thu, Aug 2, 2012 at 1:08 PM, Kay Sievers k...@vrfy.org wrote:
How is that supposed to be useful?
The prefix is added while exporting data from the kmsg buffer, which
is just the CPU that *reads* the data from the
Kay
On Thu, Aug 2, 2012 at 5:06 PM, Kay Sievers k...@vrfy.org wrote:
On Fri, Aug 3, 2012 at 1:50 AM, Pandita, Vikram vikram.pand...@ti.com wrote:
On Thu, Aug 2, 2012 at 1:08 PM, Kay Sievers k...@vrfy.org wrote:
How is that supposed to be useful?
The prefix is added while exporting data from
12 matches
Mail list logo
