On 8/26/20 1:26 AM, Pavel Machek wrote:
Hi!
Hi Pavel,
We have a user space tool (rtas_errd) on LPAR to monitor for
EPOW_SHUTDOWN_ON_UPS. Once it gets an event it initiates shutdown
after predefined time. It also starts monitoring for any new EPOW
Yeah, so there's userspace tool, and
On 11/25/2015 08:47 PM, Jacek Anaszewski wrote:
> On 11/25/2015 03:44 PM, Vasant Hegde wrote:
>> On 11/23/2015 02:58 PM, Saurabh Sengar wrote:
>>> no need to explicitly check for pointer to be null,
>>> of_prop_next_string anyways return NULL, if passed pointer
On 11/23/2015 02:58 PM, Saurabh Sengar wrote:
> no need to explicitly check for pointer to be null,
> of_prop_next_string anyways return NULL, if passed pointer is NULL
> and hence loop will continue
Thanks! Patch looks good.
-Vasant
--
To unsubscribe from this list: send the line "unsubscribe
On 11/25/2015 08:47 PM, Jacek Anaszewski wrote:
> On 11/25/2015 03:44 PM, Vasant Hegde wrote:
>> On 11/23/2015 02:58 PM, Saurabh Sengar wrote:
>>> no need to explicitly check for pointer to be null,
>>> of_prop_next_string anyways return NULL, if passed pointer
On 11/23/2015 02:58 PM, Saurabh Sengar wrote:
> no need to explicitly check for pointer to be null,
> of_prop_next_string anyways return NULL, if passed pointer is NULL
> and hence loop will continue
Thanks! Patch looks good.
-Vasant
--
To unsubscribe from this list: send the line "unsubscribe
On 08/22/2015 05:10 AM, Michael Ellerman wrote:
> On Fri, 2015-08-21 at 14:29 +0530, Vasant Hegde wrote:
>> On 08/21/2015 01:55 PM, Stephen Rothwell wrote:
>>> Hi all,
>>>
>>> After merging the nvdimm tree, today's linux-next build (powerpc
>>>
On 08/21/2015 01:55 PM, Stephen Rothwell wrote:
> Hi all,
>
> After merging the nvdimm tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
Stephen,
Thanks for reporting! I checked powerpc tree.. This is because of commit
8a8d9181 in powerpc tree.. Basically Michael missed
On 08/22/2015 05:10 AM, Michael Ellerman wrote:
On Fri, 2015-08-21 at 14:29 +0530, Vasant Hegde wrote:
On 08/21/2015 01:55 PM, Stephen Rothwell wrote:
Hi all,
After merging the nvdimm tree, today's linux-next build (powerpc
allyesconfig) failed like this:
Stephen,
Thanks for reporting! I
On 08/21/2015 01:55 PM, Stephen Rothwell wrote:
Hi all,
After merging the nvdimm tree, today's linux-next build (powerpc
allyesconfig) failed like this:
Stephen,
Thanks for reporting! I checked powerpc tree.. This is because of commit
8a8d9181 in powerpc tree.. Basically Michael missed one
On 02/18/2015 05:33 AM, Stewart Smith wrote:
> This series fixes three possible warnings that OPAL firmware would emit
> when booting on hardware/simulator that didn't support certain functionality.
>
> The correct thing for Linux to do is to detect firmware capability
> by using the
On 02/18/2015 05:33 AM, Stewart Smith wrote:
This series fixes three possible warnings that OPAL firmware would emit
when booting on hardware/simulator that didn't support certain functionality.
The correct thing for Linux to do is to detect firmware capability
by using the OPAL_CHECK_TOKEN
On 02/12/2015 10:55 AM, Stewart Smith wrote:
> Not all OPAL platforms support resending system dumps, so check
> that current firmware supports it first. Otherwise we get firmware
> complaining:
> "OPAL: Called with bad token 91 !"
>
> Signed-off-by: Stewart Smi
On 02/12/2015 10:55 AM, Stewart Smith wrote:
> Otherwise firmware complains: "OPAL: Called with bad token 74 !"
> as not all OPAL systems have the ability to resend error logs.
>
> Signed-off-by: Stewart Smith
Acked-by: Vasant Hegde
-Vasant
> ---
> arch/po
On 02/12/2015 10:55 AM, Stewart Smith wrote:
> Correct use of REGISTER/UNREGISTER is to check if the token exists
> before calling. If we don't we get a "OPAL: Called with bad token 101 !"
> error, which is harmless but may be alarming to some.
>
> Signed-off-by: Stewart
On 02/12/2015 10:55 AM, Stewart Smith wrote:
Otherwise firmware complains: OPAL: Called with bad token 74 !
as not all OPAL systems have the ability to resend error logs.
Signed-off-by: Stewart Smith stew...@linux.vnet.ibm.com
Acked-by: Vasant Hegde hegdevas...@linux.vnet.ibm.com
-Vasant
-by: Vasant Hegde hegdevas...@linux.vnet.ibm.com
-Vasant
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Acked-by: Vasant Hegde hegdevas...@linux.vnet.ibm.com
-Vasant
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http
and unregister before doing kexec.
Signed-off-by: Vasant Hegde
Signed-off-by: Benjamin Herrenschmidt
---
arch/powerpc/include/asm/opal.h| 11 +++
arch/powerpc/platforms/powernv/opal-wrappers.S |2 ++
arch/powerpc/platforms/powernv/opal.c | 23
address
and size. This patch adds support to return log buffer address
and size.
Signed-off-by: Vasant Hegde
Signed-off-by: Benjamin Herrenschmidt
---
Next patch extends arch specific code to add log buffer to platform
dump.
Changes in v3:
As Andrew suggested changed function names and return
address
and size. This patch adds support to return log buffer address
and size.
Signed-off-by: Vasant Hegde hegdevas...@linux.vnet.ibm.com
Signed-off-by: Benjamin Herrenschmidt b...@kernel.crashing.org
---
Next patch extends arch specific code to add log buffer to platform
dump.
Changes in v3
and unregister before doing kexec.
Signed-off-by: Vasant Hegde hegdevas...@linux.vnet.ibm.com
Signed-off-by: Benjamin Herrenschmidt b...@kernel.crashing.org
---
arch/powerpc/include/asm/opal.h| 11 +++
arch/powerpc/platforms/powernv/opal-wrappers.S |2 ++
arch/powerpc
On 08/01/2014 03:52 AM, Andrew Morton wrote:
On Thu, 31 Jul 2014 21:05:48 +0530 Vasant Hegde
wrote:
Platforms like IBM Power Systems supports service processor
assisted dump. It provides interface to add memory region to
be captured when system is crashed.
During initialization/running we
On 08/01/2014 03:52 AM, Andrew Morton wrote:
On Thu, 31 Jul 2014 21:05:48 +0530 Vasant Hegde
hegdevas...@linux.vnet.ibm.com wrote:
Platforms like IBM Power Systems supports service processor
assisted dump. It provides interface to add memory region to
be captured when system is crashed
and unregister before doing kexec.
Signed-off-by: Vasant Hegde
---
arch/powerpc/include/asm/opal.h | 15 +
arch/powerpc/platforms/powernv/Makefile |2 -
arch/powerpc/platforms/powernv/opal-dump-region.c | 64 +
arch/powerpc/platforms/powernv
and unregister before doing kexec.
Signed-off-by: Vasant Hegde
---
arch/powerpc/include/asm/opal.h | 15 +
arch/powerpc/platforms/powernv/Makefile |2 -
arch/powerpc/platforms/powernv/opal-dump-region.c | 64 +
arch/powerpc/platforms/powernv
address
and size. This patch adds support to return log buffer address
and size.
Signed-off-by: Vasant Hegde
---
Next patch extends arch specific code to add log buffer to platform
dump.
-Vasant
include/linux/printk.h |3 +++
kernel/printk/printk.c | 12
2 files changed, 15
address
and size. This patch adds support to return log buffer address
and size.
Signed-off-by: Vasant Hegde
---
Next patch extends arch specific code to add log buffer to platform
dump.
-Vasant
include/linux/printk.h |3 +++
kernel/printk/printk.c | 12
2 files changed, 15
address
and size. This patch adds support to return log buffer address
and size.
Signed-off-by: Vasant Hegde hegdevas...@linux.vnet.ibm.com
---
Next patch extends arch specific code to add log buffer to platform
dump.
-Vasant
include/linux/printk.h |3 +++
kernel/printk/printk.c | 12
address
and size. This patch adds support to return log buffer address
and size.
Signed-off-by: Vasant Hegde hegdevas...@linux.vnet.ibm.com
---
Next patch extends arch specific code to add log buffer to platform
dump.
-Vasant
include/linux/printk.h |3 +++
kernel/printk/printk.c | 12
and unregister before doing kexec.
Signed-off-by: Vasant Hegde hegdevas...@linux.vnet.ibm.com
---
arch/powerpc/include/asm/opal.h | 15 +
arch/powerpc/platforms/powernv/Makefile |2 -
arch/powerpc/platforms/powernv/opal-dump-region.c | 64
and unregister before doing kexec.
Signed-off-by: Vasant Hegde hegdevas...@linux.vnet.ibm.com
---
arch/powerpc/include/asm/opal.h | 15 +
arch/powerpc/platforms/powernv/Makefile |2 -
arch/powerpc/platforms/powernv/opal-dump-region.c | 64
PowerNV platform is capable of capturing host memory region when system
crashes (because of host/firmware). We have new OPAL API to register
memory region to be capture when system crashes.
This patch adds support for new API and also registers kernel log buffer.
Signed-off-by: Vasant Hegde
address
and size. This patch adds support to return log buffer address
and size.
Signed-off-by: Vasant Hegde
---
Next patch extends arch specific code to add log buffer to platform
dump.
include/linux/printk.h |3 +++
kernel/printk/printk.c | 12
2 files changed, 15 insertions
address
and size. This patch adds support to return log buffer address
and size.
Signed-off-by: Vasant Hegde hegdevas...@linux.vnet.ibm.com
---
Next patch extends arch specific code to add log buffer to platform
dump.
include/linux/printk.h |3 +++
kernel/printk/printk.c | 12
2
PowerNV platform is capable of capturing host memory region when system
crashes (because of host/firmware). We have new OPAL API to register
memory region to be capture when system crashes.
This patch adds support for new API and also registers kernel log buffer.
Signed-off-by: Vasant Hegde
ke chip-id
information available to userspace).
Thanks, I'll send that to Linus asap.
Verified on today's Linus tree. This issue is fixed.
Thanks a lot.
-Vasant
Ben.
Export the missing symbol.
Cc: Vasant Hegde
Cc: Shivaprasad G Bhat
Signed-off-by: Guenter Roeck
---
arch/powerpc/ke
On 09/11/2013 04:20 AM, Guenter Roeck wrote:
On Wed, Sep 11, 2013 at 08:02:49AM +1000, Benjamin Herrenschmidt wrote:
On Mon, 2013-09-09 at 16:55 -0700, Asai Thambi S P wrote:
On 09/08/2013 5:28 PM, Guenter Roeck wrote:
Hi all,
Guenter, Ben,
Sorry for the inconvenience. I never realized my
On 09/11/2013 04:20 AM, Guenter Roeck wrote:
On Wed, Sep 11, 2013 at 08:02:49AM +1000, Benjamin Herrenschmidt wrote:
On Mon, 2013-09-09 at 16:55 -0700, Asai Thambi S P wrote:
On 09/08/2013 5:28 PM, Guenter Roeck wrote:
Hi all,
Guenter, Ben,
Sorry for the inconvenience. I never realized my
information available to userspace).
Thanks, I'll send that to Linus asap.
Verified on today's Linus tree. This issue is fixed.
Thanks a lot.
-Vasant
Ben.
Export the missing symbol.
Cc: Vasant Hegde hegdevas...@linux.vnet.ibm.com
Cc: Shivaprasad G Bhat sb...@linux.vnet.ibm.com
Signed-off
-by: Vasant Hegde
---
arch/powerpc/kernel/rtas_flash.c | 10 ++
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git a/arch/powerpc/kernel/rtas_flash.c b/arch/powerpc/kernel/rtas_flash.c
index 5b30224..2f3cdb0 100644
--- a/arch/powerpc/kernel/rtas_flash.c
+++ b/arch/powerpc/kernel
-off-by: Vasant Hegde hegdevas...@linux.vnet.ibm.com
---
arch/powerpc/kernel/rtas_flash.c | 10 ++
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git a/arch/powerpc/kernel/rtas_flash.c b/arch/powerpc/kernel/rtas_flash.c
index 5b30224..2f3cdb0 100644
--- a/arch/powerpc/kernel
On 05/01/2013 07:36 AM, Stephen Rothwell wrote:
Hi Al,
Today's linux-next merge of the vfs tree got a conflict in
arch/powerpc/kernel/rtas_flash.c between commit fb4696c39573
("powerpc/rtas_flash: Fix bad memory access") from the powerpc tree and
commits ad18a364f186 ("powerpc/rtas_flash: Free
On 05/01/2013 07:36 AM, Stephen Rothwell wrote:
Hi Al,
Today's linux-next merge of the vfs tree got a conflict in
arch/powerpc/kernel/rtas_flash.c between commit fb4696c39573
(powerpc/rtas_flash: Fix bad memory access) from the powerpc tree and
commits ad18a364f186 (powerpc/rtas_flash: Free
using.
Also removes rtas_block_ctor(), which is no longer required.
Signed-off-by: Vasant Hegde
---
arch/powerpc/kernel/rtas_flash.c | 14 --
1 file changed, 4 insertions(+), 10 deletions(-)
diff --git a/arch/powerpc/kernel/rtas_flash.c b/arch/powerpc/kernel/rtas_flash.c
index
makes sure memory is set to 0 before using.
Also removes rtas_block_ctor(), which is no longer required.
Signed-off-by: Vasant Hegde hegdevas...@linux.vnet.ibm.com
---
arch/powerpc/kernel/rtas_flash.c | 14 --
1 file changed, 4 insertions(+), 10 deletions(-)
diff --git a/arch/powerpc
On 04/16/2013 11:56 PM, David Howells wrote:
Supply accessor functions to set attributes in proc_dir_entry structs.
The following are supplied: proc_set_size() and proc_set_user().
Signed-off-by: David Howells
cc: linuxppc-...@lists.ozlabs.org
cc: linux-me...@vger.kernel.org
cc:
On 04/16/2013 11:57 PM, David Howells wrote:
Clean up the pseries scanlog driver's use of procfs:
(1) Don't need to save the proc_dir_entry pointer as we have the filename to
remove with.
(2) Save the scan log buffer pointer in a static variable (there is only one
of it) and
On 04/16/2013 11:57 PM, David Howells wrote:
Clean up some of the problems with the rtas_flash driver:
(1) It shouldn't fiddle with the internals of the procfs filesystem (altering
pde->count).
(2) If pid namespaces are in effect, then you can get multiple inodes
connected to a
On 04/16/2013 11:57 PM, David Howells wrote:
Clean up some of the problems with the rtas_flash driver:
(1) It shouldn't fiddle with the internals of the procfs filesystem (altering
pde-count).
(2) If pid namespaces are in effect, then you can get multiple inodes
connected to a
On 04/16/2013 11:57 PM, David Howells wrote:
Clean up the pseries scanlog driver's use of procfs:
(1) Don't need to save the proc_dir_entry pointer as we have the filename to
remove with.
(2) Save the scan log buffer pointer in a static variable (there is only one
of it) and
On 04/16/2013 11:56 PM, David Howells wrote:
Supply accessor functions to set attributes in proc_dir_entry structs.
The following are supplied: proc_set_size() and proc_set_user().
Signed-off-by: David Howellsdhowe...@redhat.com
cc: linuxppc-...@lists.ozlabs.org
cc: linux-me...@vger.kernel.org
On 04/24/2013 01:45 PM, Vasant Hegde wrote:
> On 04/24/2013 01:15 PM, Chen Gang wrote:
>> Hello Vasant Hegde:
>>
>> How about this patch, is it OK ?
>>
>> Thanks.
>>
>>
>> On 2013年03月25日 12:30, Chen Gang wrote:
>>> Hello Maintainer
On 04/24/2013 01:15 PM, Chen Gang wrote:
> Hello Vasant Hegde:
>
> How about this patch, is it OK ?
>
> Thanks.
>
>
> On 2013年03月25日 12:30, Chen Gang wrote:
>> Hello Maintainers:
>>
>>could you help check this patch whether is ok ?
>>
>&g
On 04/24/2013 12:33 PM, Chen Gang wrote:
On 2013年04月24日 14:28, Vasant Hegde wrote:
On 04/23/2013 08:42 AM, Chen Gang wrote:
need set '\0' for 'local_buffer'.
SPLPAR_MAXLENGTH is 1026, RTAS_DATA_BUF_SIZE is 4096. so the contents of
rtas_data_buf may truncated in memcpy.
if contents
On 04/23/2013 08:42 AM, Chen Gang wrote:
need set '\0' for 'local_buffer'.
SPLPAR_MAXLENGTH is 1026, RTAS_DATA_BUF_SIZE is 4096. so the contents of
rtas_data_buf may truncated in memcpy.
if contents are really truncated.
the splpar_strlen is more than 1026. the next while loop checking
On 04/23/2013 08:42 AM, Chen Gang wrote:
need set '\0' for 'local_buffer'.
SPLPAR_MAXLENGTH is 1026, RTAS_DATA_BUF_SIZE is 4096. so the contents of
rtas_data_buf may truncated in memcpy.
if contents are really truncated.
the splpar_strlen is more than 1026. the next while loop checking
On 04/24/2013 12:33 PM, Chen Gang wrote:
On 2013年04月24日 14:28, Vasant Hegde wrote:
On 04/23/2013 08:42 AM, Chen Gang wrote:
need set '\0' for 'local_buffer'.
SPLPAR_MAXLENGTH is 1026, RTAS_DATA_BUF_SIZE is 4096. so the contents of
rtas_data_buf may truncated in memcpy.
if contents
On 04/24/2013 01:15 PM, Chen Gang wrote:
Hello Vasant Hegde:
How about this patch, is it OK ?
Thanks.
On 2013年03月25日 12:30, Chen Gang wrote:
Hello Maintainers:
could you help check this patch whether is ok ?
thanks.
On 2013年02月17日 12:00, Chen Gang wrote:
Hello relative
On 04/24/2013 01:45 PM, Vasant Hegde wrote:
On 04/24/2013 01:15 PM, Chen Gang wrote:
Hello Vasant Hegde:
How about this patch, is it OK ?
Thanks.
On 2013年03月25日 12:30, Chen Gang wrote:
Hello Maintainers:
could you help check this patch whether is ok ?
thanks.
On 2013年02月17
59 matches
Mail list logo
