This patch adds a test case to verify that the changed DSCR value
inside any process would be inherited to it's child across the fork
and exec system call.
Acked-by: Shuah Khan
Signed-off-by: Anshuman Khandual
Signed-off-by: Anton Blanchard
---
tools/testing/selftests/powerpc/dscr/Makefile
This patch adds a test which modifies the DSCR using mtspr instruction
and verifies the change using mfspr instruction. It uses both the
privilege state SPR as well as the problem state SPR for the purpose.
Acked-by: Shuah Khan
Signed-off-by: Anshuman Khandual
Signed-off-by: Anton Blanchard
---
This patch adds a new documentation file explaining the DSCR
support on powerpc platforms. This explains DSCR related data
structure, code paths and also available user interfaces. Any
further functional changes to the DSCR support in the kernel
should definitely update the documentation here.
Sig
This patch adds a test which verifies that the DSCR privilege and
problem state SPR read & write accesses while making sure that the
results are always the same irrespective of which SPR number is
being used.
Acked-by: Shuah Khan
Signed-off-by: Anshuman Khandual
Signed-off-by: Anton Blanchard
-
This patch adds a test to verify that the changed DSCR value inside
any process would be inherited to it's child process across the fork
system call.
Acked-by: Shuah Khan
Signed-off-by: Anshuman Khandual
Signed-off-by: Anton Blanchard
---
tools/testing/selftests/powerpc/dscr/Makefile | 3
This patch adds .gitignore for all the newly added DSCR tests.
Signed-off-by: Anshuman Khandual
---
tools/testing/selftests/powerpc/dscr/.gitignore | 7 +++
1 file changed, 7 insertions(+)
create mode 100644 tools/testing/selftests/powerpc/dscr/.gitignore
diff --git a/tools/testing/selftes
This patch adds a test case for the system wide DSCR default
value, which when changed through it's sysfs interface must
be visible to all threads reading DSCR either through the
privilege state SPR or the problem state SPR. The DSCR value
change should be immediate as well.
Acked-by: Shuah Khan
PACA_DSCR offset macro tracks dscr_default element in the paca
structure. Better change the name of this macro to match that
of the data element it tracks. Makes the code more readable.
Signed-off-by: Anshuman Khandual
---
arch/powerpc/kernel/asm-offsets.c | 2 +-
arch/powerpc/kernel/entry
This patch series has patches for POWER DSCR fixes, improvements,
in code documentaion, kernel support user documentation and selftest based
test cases. It has got five test cases which are derived from Anton's DSCR
test bucket which can be listed as follows.
(1) http://ozlabs.org/~anton/j
This patch adds a test to update the system wide DSCR value repeatedly
and then verifies that any thread on any given CPU on the system must
be able to see the same DSCR value whether its is being read through
the problem state based SPR or the privilege state based SPR.
Acked-by: Shuah Khan
Sign
This patch adds some in-code documentation to the DSCR related
code to make it more readable without having any functional
change to it.
Signed-off-by: Anshuman Khandual
---
arch/powerpc/include/asm/processor.h | 9 +
arch/powerpc/kernel/sysfs.c | 38 +++
This test continuously updates the system wide DSCR default value
in the sysfs interface and makes sure that the same is reflected
across all the sysfs interfaces for each individual CPUs present
on the system.
Acked-by: Shuah Khan
Signed-off-by: Anshuman Khandual
---
tools/testing/selftests/po
Currently DSCR (Data Stream Control Register) can be accessed with
mfspr or mtspr instructions inside a thread via two different SPR
numbers. One being the user accessible problem state SPR number 0x03
and the other being the privilege state SPR number 0x11. All access
through the privilege state S
The process context switch code no longer uses dscr_default variable
from the sysfs.c file. The variable became unused when we started
storing the CPU specific DSCR value in the PACA structure instead.
This patch just removes this extern declaration. It was originally
added by the following commit.
On Wed, 2015-05-20 at 14:17 -0700, Brian Norris wrote:
> You might run this through checkpatch, as it caught several small
> things.
>
Hi Brian,
Oops, sorry absolutely should have done checkpatch!
Thanks for the review, everything you've said is great, I've addressed
all that - I'll post a v2.
Hi Brian,
> While I have Jeremy's attention, let me plug a friendly reminder for
> this unrelated comment:
>
> http://patchwork.ozlabs.org/patch/413355/
>
> Jeremy, you still haven't updated patchwork.git for your last round of
> supposed "merges".
Ah, thanks for the reminder - I've just done t
Andi Kleen [a...@linux.intel.com] wrote:
| If you need something else in vfm to identify the CPU
| can't you just add it there? I wouldn't really call it vfm, it's
| really a "abstract cpu identifier per architecture". So if you
| need pvr just add it there.
Ok. I will change vfm to cpuid_str and
Export the "AFU Error Buffer" via sysfs attribute (afu_err_buf). AFU
error buffer is used by the AFU to report application specific
errors. The contents of this buffer are AFU specific and are intended to
be interpreted by the application interacting with the afu.
Testing:
- Build against
> On 21-May-2015, at 05:16, Michael Neuling wrote:
>
> + */
>> +ssize_t cxl_afu_read_err_buffer(struct cxl_afu *afu, char *buf,
>> +loff_t off, size_t count)
>> +{
>> +loff_t aligned_off;
>> +size_t aligned_count;
>> +const void __iomem *ebuf = afu->afu_desc_mmio + af
Hi Scott,
On 05/13/2015 08:52 AM, Scott Wood wrote:
On Tue, 2015-05-12 at 21:34 +0530, Hemant Kumar wrote:
Hi Scott,
On 05/12/2015 03:38 AM, Scott Wood wrote:
On Fri, 2015-05-08 at 06:37 +0530, Hemant Kumar wrote:
diff --git a/arch/powerpc/include/uapi/asm/kvm_perf.h
b/arch/powerpc/include/
powerpc provides hcall events that also provides insights into guest
behaviour. Enhance perf kvm to record and analyze hcall events.
- To trace hcall events :
perf kvm stat record
- To show the results :
perf kvm stat report --event=hcall
The result shows the number of hypervisor calls fro
From: Srikar Dronamraju
perf kvm can be used to analyze guest exit reasons. This support already
exists in x86. Hence, porting it to powerpc.
- To trace KVM events :
perf kvm stat record
If many guests are running, we can track for a specific guest by using
--pid as in : perf kvm stat rec
On Mon, 2015-05-18 at 16:26 +0530, Anshuman Khandual wrote:
> This patch series has patches for POWER DSCR fixes, improvements,
> in code documentaion, kernel support user documentation and selftest based
> test cases. It has got five test cases which are derived from Anton's DSCR
> test buck
On Thu, 2015-05-21 at 09:06 +0530, trigg wrote:
>
>
> > On 21-May-2015, at 05:16, Michael Neuling wrote:
> >
> > + */
> > > +ssize_t cxl_afu_read_err_buffer(struct cxl_afu *afu, char *buf,
> > > +loff_t off, size_t count)
> > > +{
> > > +loff_t aligned_off;
> > > +size_t
For perf to analyze the KVM events like hcalls, we need the
hypervisor calls and their codes to be exported through uapi.
This patch moves most of the pSeries hcall codes from
arch/powerpc/include/asm/hvcall.h to
arch/powerpc/include/uapi/asm/pseries_hcalls.h.
It also moves the mapping from
arch/
This patch adds an exit reason "RETURN_TO_HOST" for the return code
0x0. Note that this is not related to any interrupt vector address, but
this is added just to make sure that perf doesn't complain if and when a
kvm exit happens with a trap code as 0x0.
Signed-off-by: Hemant Kumar
---
arch/powe
To analyze the kvm exits with perf, we will need to map the exit codes
with the exit reasons. Such a mapping exists today in trace_book3s.h.
Currently its not exported to perf.
This patch moves these kvm exit reasons and their mapping from
"arch/powerpc/kvm/trace_book3s.h" to
"arch/powerpc/include
On Tue, 2015-05-19 at 04:27 -0500, Liberman Igal-B31950 wrote:
> Hi Scott,
> I understand your point, let me please explain more about the hardware
> configuration and suggest another solution.
> I'm referring only to external ports (TX/RX), not OP.
> In FMan V3 we have maximum of 8 Port, it depen
> Obviously, that does not fit into the VFM field. We could either
> add a new PVR field to the mapfile:
>
> [vfm, version, type, pvr]
>
> or, as the patch currently does, let architectures intepret the
> "version" field as they see fit?
>
> IOW, leave it to architectures to keep arch_pmu_
On Wed, May 20, 2015 at 05:35:08PM -0500, Scott Wood wrote:
>
> It's nominally a 64-bit register, but the upper 32 bits are reserved in
> ISA 2.06. Do newer ISAs or certain implementations define things in the
> upper 32 bits, or is this just about the asm accesses being wrong on
> big-endian?
I
From: Jaiprakash Singh
IFC IO accressor are set at run time based
on IFC IP registers endianness.IFC node in
DTS file contains information about
endianness.
Signed-off-by: Jaiprakash Singh
Signed-off-by: Scott Wood
---
v5: I'm assuming it's the same as v4, but I didn't send v4, and this
comes
Andi Kleen [a...@linux.intel.com] wrote:
| > +/*
| > + * Return TRUE if the CPU identified by @vfm, @version, and @type
| > + * matches the current CPU. vfm refers to [Vendor, Family, Model],
| > + *
| > + * Return FALSE otherwise.
| > + *
| > + * For Powerpc, we only compare @version to the proce
> +/*
> + * Return TRUE if the CPU identified by @vfm, @version, and @type
> + * matches the current CPU. vfm refers to [Vendor, Family, Model],
> + *
> + * Return FALSE otherwise.
> + *
> + * For Powerpc, we only compare @version to the processor PVR.
> + */
> +bool arch_pmu_events_match_cpu(cons
+ */
> +ssize_t cxl_afu_read_err_buffer(struct cxl_afu *afu, char *buf,
> + loff_t off, size_t count)
> +{
> + loff_t aligned_off;
> + size_t aligned_count;
> + const void __iomem *ebuf = afu->afu_desc_mmio + afu->eb_offset;
> +
> + if (!afu->eb_len || co
From 955102eacf035b19080dc659a15d9b8fbd8fae7f Mon Sep 17 00:00:00 2001
From: Sukadev Bhattiprolu
Date: Tue, 28 Apr 2015 18:47:58 -0400
Subject: [PATCH 1/1] powerpc/perf/hv-24x7: Check support before registering
PMU
We currently try to register the 24x7 PMU unconditionally. Not all
Power systems
On Wed, 2015-05-20 at 15:26 +1000, Sam Bobroff wrote:
> In 64 bit kernels, the Fixed Point Exception Register (XER) is a 64
> bit field (e.g. in kvm_regs and kvm_vcpu_arch) and in most places it is
> accessed as such.
>
> This patch corrects places where it is accessed as a 32 bit field by a
> 64
On Wed, May 20, 2015 at 03:26:12PM +1000, Sam Bobroff wrote:
> In 64 bit kernels, the Fixed Point Exception Register (XER) is a 64
> bit field (e.g. in kvm_regs and kvm_vcpu_arch) and in most places it is
> accessed as such.
>
> This patch corrects places where it is accessed as a 32 bit field by
Alexey,
Can you send me boot messages so I can see everything the lpfc driver
may have done ?
And you're using 10.5.0.0 verbatim ?
-- james
On 5/20/2015 9:11 AM, James Smart wrote:
Not sure - I'll go look.
-- james
On 5/19/2015 11:55 PM, Alexey Kardashevskiy wrote:
On 05/06/2015 07:46 A
On Wed, May 20, 2015 at 05:40:39PM +0800, Jiang Liu wrote:
> diff --git a/arch/arm/kernel/irq.c b/arch/arm/kernel/irq.c
> index 350f188c92d2..baf8edebe26f 100644
> --- a/arch/arm/kernel/irq.c
> +++ b/arch/arm/kernel/irq.c
> @@ -140,7 +140,7 @@ int __init arch_probe_nr_irqs(void)
> static bool migr
On Wed, 20 May 2015, Jiang Liu wrote:
> Introduce helper function irq_data_get_affinity_mask() and
> irq_get_affinity_mask() to hide implementation details,
That patch does way more than introducing the functions. Again:
Patch 1: Introduce helpers
Patch 2-n: Convert users subsystem wise
Thanks
Not sure - I'll go look.
-- james
On 5/19/2015 11:55 PM, Alexey Kardashevskiy wrote:
On 05/06/2015 07:46 AM, Sebastian Herbszt wrote:
James Smart wrote:
Reviewed-By: James Smart
Alexey, Sebastian,
Yes - this section needs to be reverted. This patch is good.
-- james s
Reviewed-by: S
You might run this through checkpatch, as it caught several small
things.
On Mon, May 04, 2015 at 04:42:19PM +1000, Cyril Bur wrote:
> Powerpc powernv platforms allow access to certain system flash devices
> through a firmwarwe interface. This change adds an mtd driver for these
> flash devices.
>
On Fri, 15 May 2015 21:12:29 +0530 "Aneesh Kumar K.V"
wrote:
> Also move the pmd_trans_huge check to generic code.
>
> ...
>
> --- a/include/asm-generic/pgtable.h
> +++ b/include/asm-generic/pgtable.h
> @@ -196,7 +196,12 @@ static inline pmd_t pmdp_collapse_flush(struct
> vm_area_struct *vma,
On Wed, May 20, 2015 at 10:58:42PM +0530, Shreyas B Prabhu wrote:
>
>
> On Wednesday 20 May 2015 10:43 PM, Jack Miller wrote:
> > pnv_alloc_idle_core_states is iterating over PACAs based on the
> > configured maximum number of CPUs (NR_CPUS), but PACAs are only
> > initialized up to nr_cpu_ids, s
On Wednesday 20 May 2015 10:43 PM, Jack Miller wrote:
> pnv_alloc_idle_core_states is iterating over PACAs based on the
> configured maximum number of CPUs (NR_CPUS), but PACAs are only
> initialized up to nr_cpu_ids, so rein in loops to keep from overwriting
> adjacent memory.
>
Hi Jack,
Jan
Export the "AFU Error Buffer" via sysfs attribute (afu_err_buf). AFU
error buffer is used by the AFU to report application specific
errors. The contents of this buffer are AFU specific and are intended to
be interpreted by the application interacting with the afu.
Testing:
- Build against
pnv_alloc_idle_core_states is iterating over PACAs based on the
configured maximum number of CPUs (NR_CPUS), but PACAs are only
initialized up to nr_cpu_ids, so rein in loops to keep from overwriting
adjacent memory.
Signed-off-by: Jack Miller
---
arch/powerpc/platforms/powernv/setup.c | 26
On Wed, 2015-05-20 at 22:31 +1000, Michael Neuling wrote:
> On Wed, 2015-05-20 at 22:12 +1000, Michael Neuling wrote:
> > On Wed, 2015-05-20 at 16:26 +0530, Vaibhav Jain wrote:
> > > Export the "AFU Error Buffer" via sysfs attribute (afu_err_buf). AFU
> > > error buffer is used by the AFU to report
Signed-off-by: Madalin Bucur
---
arch/powerpc/boot/dts/t1024rdb.dts | 45 ++
1 file changed, 45 insertions(+)
diff --git a/arch/powerpc/boot/dts/t1024rdb.dts
b/arch/powerpc/boot/dts/t1024rdb.dts
index 0984ae8..860e4c7 100644
--- a/arch/powerpc/boot/dts/t1024r
Signed-off-by: Madalin Bucur
---
arch/powerpc/boot/dts/t1024rdb.dts | 28
1 file changed, 28 insertions(+)
diff --git a/arch/powerpc/boot/dts/t1024rdb.dts
b/arch/powerpc/boot/dts/t1024rdb.dts
index eb1d51b..0984ae8 100644
--- a/arch/powerpc/boot/dts/t1024rdb.dts
+++
Signed-off-by: Madalin Bucur
---
arch/powerpc/boot/dts/fsl/qoriq-fman3l-0.dtsi | 94 +++
arch/powerpc/boot/dts/fsl/t1023si-post.dtsi | 27
arch/powerpc/boot/dts/fsl/t102xsi-pre.dtsi| 6 ++
arch/powerpc/boot/dts/t1023rdb.dts| 40
4 f
Signed-off-by: Madalin Bucur
---
arch/powerpc/boot/dts/fsl/t1023si-post.dtsi | 109
arch/powerpc/boot/dts/t1023rdb.dts | 29
2 files changed, 138 insertions(+)
diff --git a/arch/powerpc/boot/dts/fsl/t1023si-post.dtsi
b/arch/powerpc/boot/dts/fsl/t1
These patches depend upon several other patches that are now in review:
[1] powerpc/mpc85xx: Add DPAA Ethernet QMan support to the device tree(s)
[2] powerpc/mpc85xx: Create dts components for the FSL QorIQ DPAA FMan
[3] powerpc/fsl-booke: Add T1023 RDB board support
[3] powerpc/fsl-booke: Add T10
On Wed, 2015-05-20 at 22:12 +1000, Michael Neuling wrote:
> On Wed, 2015-05-20 at 16:26 +0530, Vaibhav Jain wrote:
> > Export the "AFU Error Buffer" via sysfs attribute (afu_err_buf). AFU
> > error buffer is used by the AFU to report application specific
> > errors. The contents of this buffer are
From: Emil Medve
Signed-off-by: Emil Medve
---
arch/powerpc/boot/dts/b4qds.dtsi | 1 +
arch/powerpc/boot/dts/fsl/qoriq-dpaa-res1.dtsi | 77 ++
arch/powerpc/boot/dts/fsl/qoriq-dpaa-res2.dtsi | 56 +++
arch/powerpc/boot/dts/fsl/qoriq-dpaa-res
From: Emil Medve
Signed-off-by: Emil Medve
---
arch/powerpc/boot/dts/b4qds.dtsi | 1 +
arch/powerpc/boot/dts/fsl/qoriq-dpaa-res1.dtsi | 77 ++
arch/powerpc/boot/dts/fsl/qoriq-dpaa-res2.dtsi | 56 +++
arch/powerpc/boot/dts/fsl/qoriq-dpaa-res
On Wed, 2015-05-20 at 16:26 +0530, Vaibhav Jain wrote:
> Export the "AFU Error Buffer" via sysfs attribute (afu_err_buf). AFU
> error buffer is used by the AFU to report application specific
> errors. The contents of this buffer are AFU specific and are intended to
> be interpreted by the applicati
Export the "AFU Error Buffer" via sysfs attribute (afu_err_buf). AFU
error buffer is used by the AFU to report application specific
errors. The contents of this buffer are AFU specific and are intended to
be interpreted by the application interacting with the afu.
Testing:
- Build against
On Fri, 2015-05-15 at 18:29 +1000, Michael Ellerman wrote:
> In order to support seccomp-filter we need to be able to cope with
> seccomp potentially setting a return value for the syscall.
>
> Currently this doesn't work, because we assume any failure from
> do_syscall_trace_enter() should result
Introduce helper function irq_data_get_affinity_mask() and
irq_get_affinity_mask() to hide implementation details,
so we could move field 'affinity' from struct irq_data into
struct irq_common_data later.
Signed-off-by: Jiang Liu
---
arch/alpha/kernel/irq.c |2 +-
arch/arm/
Now most IRQ flow handlers make no use of the first parameter 'irq'.
And for those who do make use of 'irq', we could easily get the irq
number through irq_desc->irq_data->irq. So kill the first parameter
'irq' of irq_flow_handler_t.
To ease review, I have split the changes into several parts, tho
Use irq_desc_get_xxx() to avoid redundant lookup of irq_desc while we
already have a pointer to corresponding irq_desc.
Signed-off-by: Jiang Liu
---
arch/powerpc/platforms/52xx/mpc52xx_gpt.c |2 +-
arch/powerpc/platforms/cell/axon_msi.c|2 +-
arch/powerpc/platforms/embedded6x
Use irq_data access helper to access irq_data->msi_desc, so we could
move msi_desc from struct irq_data into struct irq_common_data later.
Signed-off-by: Jiang Liu
---
arch/ia64/kernel/msi_ia64.c |2 +-
arch/ia64/sn/kernel/msi_sn.c|2 +-
arch/powerpc/sysdev/xics/ics-opal.
On Tue, May 19, 2015 at 01:27:07PM +1000, Michael Ellerman wrote:
> On Mon, 2015-05-18 at 14:29 +0200, Jiri Kosina wrote:
> >
> > ftrace already handles recursion protection by itself (depending on the
> > per-ftrace-ops FTRACE_OPS_FL_RECURSION_SAFE flag).
>
> OK, so I wonder why that's not work
64 matches
Mail list logo