Re: [PATCH V2] powerpc/kernel/sysfs: disable writing to purr in non-powernv

2013-10-01 Thread Michael Ellerman
On Tue, Oct 01, 2013 at 05:50:30PM +1000, Benjamin Herrenschmidt wrote:
> On Tue, 2013-10-01 at 16:31 +1000, Michael Ellerman wrote:
> 
> > > 1)Changed the test for to hypervisor mode instead of platform
> > 
> > I think Ben's wrong about that.
> > 
> > Almost all existing code uses FW_FEATURE_LPAR to differentiate
> > hypervisor vs guest mode, so I think we should do the same here.
> 
> I didn't object to using the FW test, it's a reasonable way to do it, I
> objected to using the platform as an indication (powernv vs. pseries)

Yeah sorry I wasn't clear. You are right that it shouldn't use the
platform. So I think we agree FW_FEATURE is the right way to go.

cheers
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev


Re: [PATCH V2] powerpc/kernel/sysfs: disable writing to purr in non-powernv

2013-10-01 Thread Madhavan Srinivasan
On Tuesday 01 October 2013 12:01 PM, Michael Ellerman wrote:
> Hi Maddy,
> 
> On Fri, Sep 27, 2013 at 05:03:54PM +0530, Madhavan Srinivasan wrote:
>> powerpc/kernel/sysfs.c exports purr with write permission.
> 
> PURR
> 
>> This is only valid for kernel in hypervisor mode.
>> But writing to the file in PowerVM lpar causes crash.
> 
> In the kernel history/source we refer to it as "phyp". However in this

Will follow the convention.

> case it's not an issue with phyp, it's simply that you are not in
> hypervisor mode, ie. the same crash would occur under KVM.
> 
> So you should just say "writing to the file in guest mode .."
> 

Sure. Will make the changes.

>> # echo 0 > purr
>> cpu 0x0: Vector: 700 (Program Check) at [c0d072b0]
>> pc: c001770c: .write_purr+0x1c/0x40
>> lr: c0017708: .write_purr+0x18/0x40
>> sp: c0d07530
>>msr: 80049032
>>   current = 0xc0c53de0
>>   paca= 0xcec7softe: 0irq_happened: 0x01
>> pid   = 0, comm = swapper/0
>> enter ? for help
>> [c0d075b0] c00fba64
>> .generic_smp_call_function_single_interrupt+0x104/0x190
>> [c0d07650] c0037748 .smp_ipi_demux+0xa8/0xf0
>> [c0d076e0] c0035314 .doorbell_exception+0x74/0xb0
>> [c0d07760] c0002950 doorbell_super_common+0x150/0x180
>> --- Exception: a01 (Doorbell) at c0060904
>> .plpar_hcall_norets+0x84/0xd4
>> [link register   ] c006dbd4 .check_and_cede_processor+0x24/0x40
>> [c0d07a50] c1002558 (unreliable)
>> [c0d07ac0] c006dd0c .shared_cede_loop+0x2c/0x70
>> [c0d07b40] c06ae954 .cpuidle_enter_state+0x64/0x150
>> [c0d07c00] c06aeb30 .cpuidle_idle_call+0xf0/0x300
>> [c0d07cb0] c0062fa0 .pseries_lpar_idle+0x10/0x50
>> [c0d07d20] c0016d14 .arch_cpu_idle+0x64/0x150
>> [c0d07da0] c00e0060 .cpu_startup_entry+0x1a0/0x2c0
>> [c0d07e80] c000bca4 .rest_init+0x94/0xb0
>> [c0d07ef0] c0b54530 .start_kernel+0x478/0x494
>> [c0d07f90] c0009be0 .start_here_common+0x20/0x40
>> 0:mon>
>>
>> Changes:
>>
>> 1)Changed the test for to hypervisor mode instead of platform
> 
> I think Ben's wrong about that.
> 
> Almost all existing code uses FW_FEATURE_LPAR to differentiate
> hypervisor vs guest mode, so I think we should do the same here.
> 
> So it would be:
> 
>> +if (cpu_has_feature(CPU_FTR_PURR)) {
>> +if (!firmware_has_feature(FW_FEATURE_LPAR))
>> +add_write_permission_dev_attr((void *)&dev_attr_purr);
>>  device_create_file(s, &dev_attr_purr);
>> +}
>

Will modify the check.

> 
>> +static void add_write_permission_dev_attr(void *ptr)
>> +{
>> +struct device_attribute *attr = (struct device_attribute *)ptr;
>> +
>> +attr->attr.mode |= (unsigned short) 0200;
>> +}
> 
> Why does it take a void *, which then requires a cast at the call site?
>

just prefered to send the address as void.

> And do you need the cast to short? If so shouldn't you use umode_t
> directly?

No, not really.
Will make the changes and will resend the patch.

> 
> cheers
> 
Thanks for feedback.
Maddy

___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev


Re: [PATCH V2] powerpc/kernel/sysfs: disable writing to purr in non-powernv

2013-10-01 Thread Benjamin Herrenschmidt
On Tue, 2013-10-01 at 16:31 +1000, Michael Ellerman wrote:

> > 1)Changed the test for to hypervisor mode instead of platform
> 
> I think Ben's wrong about that.
> 
> Almost all existing code uses FW_FEATURE_LPAR to differentiate
> hypervisor vs guest mode, so I think we should do the same here.

I didn't object to using the FW test, it's a reasonable way to do it, I
objected to using the platform as an indication (powernv vs. pseries)

Ben.

> So it would be:
> 
> > +   if (cpu_has_feature(CPU_FTR_PURR)) {
> > +   if (!firmware_has_feature(FW_FEATURE_LPAR))
> > +   add_write_permission_dev_attr((void *)&dev_attr_purr);
> > device_create_file(s, &dev_attr_purr);
> > +   }
> 
> 
> > +static void add_write_permission_dev_attr(void *ptr)
> > +{
> > +   struct device_attribute *attr = (struct device_attribute *)ptr;
> > +
> > +   attr->attr.mode |= (unsigned short) 0200;
> > +}
> 
> Why does it take a void *, which then requires a cast at the call site?
> 
> And do you need the cast to short? If so shouldn't you use umode_t
> directly?
> 
> cheers


___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev


Re: [PATCH V2] powerpc/kernel/sysfs: disable writing to purr in non-powernv

2013-09-30 Thread Michael Ellerman
Hi Maddy,

On Fri, Sep 27, 2013 at 05:03:54PM +0530, Madhavan Srinivasan wrote:
> powerpc/kernel/sysfs.c exports purr with write permission.

PURR

> This is only valid for kernel in hypervisor mode.
> But writing to the file in PowerVM lpar causes crash.

In the kernel history/source we refer to it as "phyp". However in this
case it's not an issue with phyp, it's simply that you are not in
hypervisor mode, ie. the same crash would occur under KVM.

So you should just say "writing to the file in guest mode .."

> # echo 0 > purr
> cpu 0x0: Vector: 700 (Program Check) at [c0d072b0]
> pc: c001770c: .write_purr+0x1c/0x40
> lr: c0017708: .write_purr+0x18/0x40
> sp: c0d07530
>msr: 80049032
>   current = 0xc0c53de0
>   paca= 0xcec7 softe: 0irq_happened: 0x01
> pid   = 0, comm = swapper/0
> enter ? for help
> [c0d075b0] c00fba64
> .generic_smp_call_function_single_interrupt+0x104/0x190
> [c0d07650] c0037748 .smp_ipi_demux+0xa8/0xf0
> [c0d076e0] c0035314 .doorbell_exception+0x74/0xb0
> [c0d07760] c0002950 doorbell_super_common+0x150/0x180
> --- Exception: a01 (Doorbell) at c0060904
> .plpar_hcall_norets+0x84/0xd4
> [link register   ] c006dbd4 .check_and_cede_processor+0x24/0x40
> [c0d07a50] c1002558 (unreliable)
> [c0d07ac0] c006dd0c .shared_cede_loop+0x2c/0x70
> [c0d07b40] c06ae954 .cpuidle_enter_state+0x64/0x150
> [c0d07c00] c06aeb30 .cpuidle_idle_call+0xf0/0x300
> [c0d07cb0] c0062fa0 .pseries_lpar_idle+0x10/0x50
> [c0d07d20] c0016d14 .arch_cpu_idle+0x64/0x150
> [c0d07da0] c00e0060 .cpu_startup_entry+0x1a0/0x2c0
> [c0d07e80] c000bca4 .rest_init+0x94/0xb0
> [c0d07ef0] c0b54530 .start_kernel+0x478/0x494
> [c0d07f90] c0009be0 .start_here_common+0x20/0x40
> 0:mon>
> 
> Changes:
> 
> 1)Changed the test for to hypervisor mode instead of platform

I think Ben's wrong about that.

Almost all existing code uses FW_FEATURE_LPAR to differentiate
hypervisor vs guest mode, so I think we should do the same here.

So it would be:

> + if (cpu_has_feature(CPU_FTR_PURR)) {
> + if (!firmware_has_feature(FW_FEATURE_LPAR))
> + add_write_permission_dev_attr((void *)&dev_attr_purr);
>   device_create_file(s, &dev_attr_purr);
> + }


> +static void add_write_permission_dev_attr(void *ptr)
> +{
> + struct device_attribute *attr = (struct device_attribute *)ptr;
> +
> + attr->attr.mode |= (unsigned short) 0200;
> +}

Why does it take a void *, which then requires a cast at the call site?

And do you need the cast to short? If so shouldn't you use umode_t
directly?

cheers
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev


[PATCH V2] powerpc/kernel/sysfs: disable writing to purr in non-powernv

2013-09-27 Thread Madhavan Srinivasan
powerpc/kernel/sysfs.c exports purr with write permission.
This is only valid for kernel in hypervisor mode.
But writing to the file in PowerVM lpar causes crash.

# echo 0 > purr
cpu 0x0: Vector: 700 (Program Check) at [c0d072b0]
pc: c001770c: .write_purr+0x1c/0x40
lr: c0017708: .write_purr+0x18/0x40
sp: c0d07530
   msr: 80049032
  current = 0xc0c53de0
  paca= 0xcec7   softe: 0irq_happened: 0x01
pid   = 0, comm = swapper/0
enter ? for help
[c0d075b0] c00fba64
.generic_smp_call_function_single_interrupt+0x104/0x190
[c0d07650] c0037748 .smp_ipi_demux+0xa8/0xf0
[c0d076e0] c0035314 .doorbell_exception+0x74/0xb0
[c0d07760] c0002950 doorbell_super_common+0x150/0x180
--- Exception: a01 (Doorbell) at c0060904
.plpar_hcall_norets+0x84/0xd4
[link register   ] c006dbd4 .check_and_cede_processor+0x24/0x40
[c0d07a50] c1002558 (unreliable)
[c0d07ac0] c006dd0c .shared_cede_loop+0x2c/0x70
[c0d07b40] c06ae954 .cpuidle_enter_state+0x64/0x150
[c0d07c00] c06aeb30 .cpuidle_idle_call+0xf0/0x300
[c0d07cb0] c0062fa0 .pseries_lpar_idle+0x10/0x50
[c0d07d20] c0016d14 .arch_cpu_idle+0x64/0x150
[c0d07da0] c00e0060 .cpu_startup_entry+0x1a0/0x2c0
[c0d07e80] c000bca4 .rest_init+0x94/0xb0
[c0d07ef0] c0b54530 .start_kernel+0x478/0x494
[c0d07f90] c0009be0 .start_here_common+0x20/0x40
0:mon>

Changes:

1)Changed the test for to hypervisor mode instead of platform

Signed-off-by: Madhavan Srinivasan 
---
 arch/powerpc/kernel/sysfs.c |   20 ++--
 1 file changed, 18 insertions(+), 2 deletions(-)

diff --git a/arch/powerpc/kernel/sysfs.c b/arch/powerpc/kernel/sysfs.c
index 27a90b9..42becfa 100644
--- a/arch/powerpc/kernel/sysfs.c
+++ b/arch/powerpc/kernel/sysfs.c
@@ -17,6 +17,7 @@
 #include 
 #include 
 #include 
+#include 
 
 #include "cacheinfo.h"
 
@@ -179,15 +180,27 @@ SYSFS_PMCSETUP(spurr, SPRN_SPURR);
 SYSFS_PMCSETUP(dscr, SPRN_DSCR);
 SYSFS_PMCSETUP(pir, SPRN_PIR);
 
+/*
+  Lets only enable Read for Hyp resources and
+  enable Write when needed with a separate function.
+  Lets be conservative and default to pseries.
+*/
 static DEVICE_ATTR(mmcra, 0600, show_mmcra, store_mmcra);
 static DEVICE_ATTR(spurr, 0400, show_spurr, NULL);
 static DEVICE_ATTR(dscr, 0600, show_dscr, store_dscr);
-static DEVICE_ATTR(purr, 0600, show_purr, store_purr);
+static DEVICE_ATTR(purr, 0400, show_purr, store_purr);
 static DEVICE_ATTR(pir, 0400, show_pir, NULL);
 
 unsigned long dscr_default = 0;
 EXPORT_SYMBOL(dscr_default);
 
+static void add_write_permission_dev_attr(void *ptr)
+{
+   struct device_attribute *attr = (struct device_attribute *)ptr;
+
+   attr->attr.mode |= (unsigned short) 0200;
+}
+
 static ssize_t show_dscr_default(struct device *dev,
struct device_attribute *attr, char *buf)
 {
@@ -394,8 +407,11 @@ static void register_cpu_online(unsigned int cpu)
if (cpu_has_feature(CPU_FTR_MMCRA))
device_create_file(s, &dev_attr_mmcra);
 
-   if (cpu_has_feature(CPU_FTR_PURR))
+   if (cpu_has_feature(CPU_FTR_PURR)) {
+   if (mfmsr() & MSR_HV)
+   add_write_permission_dev_attr((void *)&dev_attr_purr);
device_create_file(s, &dev_attr_purr);
+   }
 
if (cpu_has_feature(CPU_FTR_SPURR))
device_create_file(s, &dev_attr_spurr);
-- 
1.7.10.4

___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev