Hi Maciej,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on sound/for-next]
[also build test ERROR on v4.14 next-20171124]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux
Hi Maciej,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on sound/for-next]
[also build test ERROR on v4.14 next-20171124]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux
On Fri, 2017-11-24 at 17:37 +0100, christophe lombard wrote:
> You are right. We will insert a checking in the cxl driver to allow
> updating the TIDR if a P9 is present. This will be in the patch V2.
> Thanks
Best is to actually:
1) Add something to the device-tree in skiboot (and work with pHy
Le 24/11/2017 à 14:02, Benjamin Herrenschmidt a écrit :
On Fri, 2017-11-24 at 11:14 +0100, christophe lombard wrote:
To my knowledge, there is no property (or similar), somewhere, that
indicating that the TIDR is supported or not.
For the time being, if I am not wrong, the only check we have, is
On Fri, 2017-11-24 at 11:14 +0100, christophe lombard wrote:
> To my knowledge, there is no property (or similar), somewhere, that
> indicating that the TIDR is supported or not.
> For the time being, if I am not wrong, the only check we have, is
> this condition in the function set_thread_tidr(str
Hi Linus,
Please pull some powerpc fixes for 4.15.
These would be nice to have in rc1, but none of them are actually that
crucial. So they can wait until Monday if you're busy eating pumpkin
pie.
cheers
The following changes since commit 3ffa9d9e2a7c10127d8cbf91ea2be15390b450ed:
powerpc/64s
Le 23/11/2017 à 21:41, Benjamin Herrenschmidt a écrit :
On Thu, 2017-11-23 at 12:05 +0100, Christophe Lombard wrote:
The POWER9 core supports a new feature: ASB_Notify which requires the
support of the Special Purpose Register: TIDR.
The ASB_Notify command, generated by the AFU, will attempt to
From: Colin Ian King
Trival fix to spelling mistake in ERR message
Signed-off-by: Colin Ian King
---
drivers/usb/gadget/udc/fsl_udc_core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/gadget/udc/fsl_udc_core.c
b/drivers/usb/gadget/udc/fsl_udc_core.c
index d6
On Fri, 2017-11-24 at 03:51:02 UTC, Michael Ellerman wrote:
> The code that cleans up the IAMR/AMOR before kexec'ing failed to
> remember that when we're running as a guest AMOR is not writable, it's
> hypervisor privileged.
>
> They symptom is that the kexec stops before entering purgatory and
>
On Thu, 2017-11-23 at 03:38:57 UTC, Vaibhav Jain wrote:
> During an eeh a kernel-oops is reported if no vPHB is allocated to the
> AFU. This happens as during AFU init, an error in creation of vPHB is
> a non-fatal error. Hence afu->phb should always be checked for NULL
> before iterating over it f
On Wed, 2017-11-22 at 17:32:07 UTC, Mahesh J Salgaonkar wrote:
> From: Mahesh Salgaonkar
>
> Rebooting into a new kernel with kexec fails in trace_tlbie() which is
> called from native_hpte_clear(). This happens if the running kernel has
> CONFIG_LOCKDEP enabled. With lockdep enabled, the tracepo
On Wed, 2017-11-22 at 12:28:52 UTC, Michael Ellerman wrote:
> I got the logic wrong in the DT CPU features code when I added the
> Power9 DD2.1 feature. We should be setting the bit if we detect a
> DD2.1, not clearing it if we detect a DD2.0.
>
> This code isn't actually exercised at the moment s
On Wed, 2017-11-22 at 05:15:39 UTC, Madhavan Srinivasan wrote:
> IMC_MAX_PMU is used for static storage (per_nest_pmu_arr) which holds
> nest pmu information. Current value for the macro is 32 based on
> the initial number of nest pmu units supported by the nest microcode.
> But going forward, micr
On Wed, 2017-11-22 at 05:15:38 UTC, Madhavan Srinivasan wrote:
> "pmu_count" in opal_imc_counters_probe() is intended to hold
> the number of successful nest imc pmu registerations. But
> current code also counts other imc units like core_imc and
> thread_imc. Patch add a check to count only nest i
On Tue, 2017-11-21 at 14:28:20 UTC, Christophe Leroy wrote:
> On powerpc32, patch_instruction() is called by apply_feature_fixups()
> which is called from early_init()
>
> There is the following note in front of early_init():
> * Note that the kernel may be running at an address which is differen
On Mon, 2017-11-20 at 19:12:48 UTC, Sukadev Bhattiprolu wrote:
> >From 958f8db089f4b89407fc4b89bccd3eaef585aa96 Mon Sep 17 00:00:00 2001
> From: Sukadev Bhattiprolu
> Date: Mon, 20 Nov 2017 12:53:15 -0600
> Subject: [PATCH 1/1] powerpc/vas, export chip_to_vas_id()
>
> Export the symbol chip_to_va
On Fri, 2017-11-10 at 04:55:07 UTC, "Aneesh Kumar K.V" wrote:
> While computing slice mask for the free area we need make sure we only search
> in the addr limit applicable for this mmap. We update the slb_addr_limit
> after we request for a mmap above 128TB. But the following mmap request
> with h
On Sun, 2017-10-15 at 18:43:41 UTC, Madhavan Srinivasan wrote:
> ...
> [1069001518.00] [c03f95b3f770] [c00b2574]
> init_imc_pmu+0x1f4/0xc40
> [1069005374.00] [c03f95b3f850] [c008fec8]
> opal_imc_counters_probe+0x2e8/0x3e0
> [1069009426.00] [c03f95b3f950] [c
There is an unsafe signed to unsigned conversion in set_thread_tidr()
that may cause an error value to be assigned to SPRN_TIDR register and
used as thread-id.
The issue happens as assign_thread_tidr() returns an int and
thread.tidr is an unsigned-long. So a negative error code returned
from assig
If set_thread_tidr() is called twice for same task_struct then it will
allocate a new tidr value to it leaving the previous value still
dangling in the vas_thread_ida table.
To fix this the patch changes set_thread_tidr() to check if a tidr
value is already assigned to the task_struct and if yes t
20 matches
Mail list logo
