OPAL returns OPAL_WRONG_STATE for XSCOM operations
done to read any core FIR which is sleeping, offline.
On Friday 27 January 2017 05:47 AM, Michael Ellerman wrote:
Vipin K Parashar writes:
Added check for OPAL_WRONG_STATE error code returned from OPAL.
Currently Linux flashes "unexpected e
On 27/01/17 16:52, Andrew Donnellan wrote:
basic-block.h includes tm.h, and I don't believe we can remove that. I'm
not convinced there's a way around this.
Includes via function.h, I should say.
--
Andrew Donnellan OzLabs, ADL Canberra
andrew.donnel...@au1.ibm.com IBM Australia
On 09/12/16 21:59, PaX Team wrote:
the specific problem addressed here can (and IMHO should) be solved in
another way: remove the inclusion of the offending headers in gcc-common.h
as neither tm.h nor c-common.h are needed by existing plugins. for background,
We can't build without tm.h: http:/
The branch from hmi_exception_early to hmi_exception_realmode must use
a "relocatable-style" branch, because it is branching from unrelocated
exception code to beyond __end_interrupts.
Signed-off-by: Nicholas Piggin
---
This applies after the KVM RELOCATABLE series, and was split out
from patch
On Fri, 27 Jan 2017 13:50:19 +1100
Paul Mackerras wrote:
> On Thu, Dec 22, 2016 at 04:29:27AM +1000, Nicholas Piggin wrote:
> > 64-bit Book3S exception handlers must find the dynamic kernel base
> > to add to the target address when branching beyond __end_interrupts,
> > in order to support kerne
On Wed, Jan 18, 2017 at 11:19:26AM +0530, Mahesh Jagannath Salgaonkar wrote:
> On 01/16/2017 10:05 AM, Paul Mackerras wrote:
> > On Fri, Jan 13, 2017 at 04:51:45PM +0530, Aravinda Prasad wrote:
[snip]
> >>case BOOK3S_INTERRUPT_MACHINE_CHECK:
> >> + /* Exit to guest with KVM_EXIT_NMI
On Thu, Dec 22, 2016 at 04:29:27AM +1000, Nicholas Piggin wrote:
> 64-bit Book3S exception handlers must find the dynamic kernel base
> to add to the target address when branching beyond __end_interrupts,
> in order to support kernel running at non-0 physical address.
>
> Support this in KVM by br
On Thu, Dec 22, 2016 at 04:29:26AM +1000, Nicholas Piggin wrote:
> A subsequent patch to make KVM handlers relocation-safe makes them
> unusable from within alt section "else" cases (due to the way fixed
> addresses are taken from within fixed section head code).
>
> Stop open-coding the KVM handl
On Thu, Dec 22, 2016 at 04:29:25AM +1000, Nicholas Piggin wrote:
> Change the calling convention to put the trap number together with
> CR in two halves of r12, which frees up HSTATE_SCRATCH2 in the HV
> handler.
>
> The 64-bit PR handler entry translates the calling convention back
> to match the
On Thu, 2017-01-26 at 17:42 -0800, Tyrel Datwyler wrote:
> On 01/26/2017 12:22 PM, Michal Suchánek wrote:
> > Hello,
> >
> > building ibmvtpm I noticed gcc warning complaining that second word
> > of
> > struct ibmvtpm_crq in tpm_ibmvtpm_suspend is uninitialized.
> >
> > The structure is defined
On 01/26/2017 12:22 PM, Michal Suchánek wrote:
> Hello,
>
> building ibmvtpm I noticed gcc warning complaining that second word of
> struct ibmvtpm_crq in tpm_ibmvtpm_suspend is uninitialized.
>
> The structure is defined as
>
> struct ibmvtpm_crq {
> u8 valid;
> u8 msg;
>
On 27/01/17 11:40, Michael Ellerman wrote:
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/14a3ae34bfd0bcb1cc12d55b06a858
Will fix the remaining locking issue in a follow up patch...
--
Andrew Donnellan OzLabs, ADL Canberra
andrew.donnel...@au1.ibm.com IBM Aust
Adding Vicky from IBM.
On 01/26/2017 04:05 PM, Jason Gunthorpe wrote:
On Thu, Jan 26, 2017 at 09:22:48PM +0100, Michal Such??nek wrote:
This is repeated a few times in the driver so I added memset to quiet
gcc and make behavior deterministic in case the unused fields get some
meaning in the f
On 01/25/2017 06:00 PM, Anton Blanchard wrote:
> Hi,
>
> gcc trunk has failed to build PowerPC64 kernels for a month or so. The issue
> is in oprofile, which is common code but ends up being sucked into
> arch/powerpc and therefore subject to the -Werror applied to arch/powerpc:
>
> linux/arch/p
On Wed, 2016-08-24 at 20:36:54 UTC, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Wed, 24 Aug 2016 22:26:37 +0200
>
> A multiplication for the size determination of a memory allocation
> indicated that an array data structure should be processed.
> Thus reuse the corresponding function
On Sat, 2017-01-21 at 14:45:19 UTC, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Sat, 21 Jan 2017 15:30:15 +0100
>
> * Return directly after a call of the function "address_ok" failed
> in a case block.
>
> This issue was detected by using the Coccinelle software.
>
> * Delete tw
On Wed, 2016-12-14 at 04:39:45 UTC, "Aneesh Kumar K.V" wrote:
> We don't do this for other page table entries. So lets keep this simple
> and always return false for hugepd check on a 64K page size config.
>
> Signed-off-by: Aneesh Kumar K.V
Applied to powerpc next, thanks.
https://git.kernel.o
On Sat, 2017-01-21 at 15:24:58 UTC, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Sat, 21 Jan 2017 16:10:50 +0100
>
> * Return directly after a call of the function "__copy_from_user"
> failed here.
>
> This issue was detected by using the Coccinelle software.
>
> * Delete the jum
On Fri, 2017-01-13 at 03:53:49 UTC, Joel Stanley wrote:
> The OPAL memory console is reported to be size zero, as we do not
> initialise the struct attr with any size information due to the size
> being variable. This leads users to think that the console is empty.
>
> Instead report the maximum s
On Thu, 2016-12-08 at 03:42:13 UTC, "Aneesh Kumar K.V" wrote:
> In commit a4b349540a26af ("powerpc/mm: Cleanup LPCR defines") we updated
> LPCR_VRMASD wrongly as below.
>
> -#define LPCR_VRMASD (0x1ful << (63-16))
> +#define LPCR_VRMASD_SH 47
> +#define LPCR_VRMASD (ASM_CONST
On Wed, 2017-01-04 at 02:49:12 UTC, "Aneesh Kumar K.V" wrote:
> We now support THP with both 64k and 4K page size configuration
> for radix. (hash only support THP with 64K page size). Hence we
> will have CONFIG_TRANSPARENT_HUGEPAGE enabled for both PPC_64K
> and PPC_4K config. Since we only need
On Fri, 2016-12-09 at 06:18:50 UTC, Andrew Donnellan wrote:
> During EEH recovery, we deconfigure all AFUs whilst leaving the
> corresponding vPHB and virtual PCI device in place.
>
> If something attempts to interact with the AFU's PCI config space (e.g.
> running lspci) after the AFU has been de
On Wed, 2017-01-04 at 06:18:52 UTC, Vaibhav Jain wrote:
> This change adds a force psl data cache flush during device shutdown
> callback. This should reduce a possibility of psl holding a dirty
> cache line while the CAPP is being reinitialized, which may result in
> a UE [load/store] machine chec
On Thu, 2017-01-19 at 10:50:10 UTC, Greg Kurz wrote:
> The kernel API does not use anything from this header file.
>
> Signed-off-by: Greg Kurz
> Reviewed-by: Andrew Donnellan
> Acked-by: Frederic Barrat
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/0e17166d377e74164e4067a
On Fri, 2017-01-13 at 17:10:01 UTC, "Naveen N. Rao" wrote:
> With bpf_jit_binary_alloc(), we allocate at a page granularity and fill
> the rest of the space with illegal instructions to mitigate BPF spraying
> attacks, while having the actual JIT'ed BPF program at a random location
> within the all
On Thu, 2016-11-03 at 05:15:42 UTC, Paul Mackerras wrote:
> Currently we have optimized hand-coded assembly checksum routines
> for big-endian 64-bit systems, but for little-endian we use the
> generic C routines. This modifies the optimized routines to work
> for little-endian. With this, we no
On Mon, 2017-01-23 at 22:49:52 UTC, Gavin Shan wrote:
> This removes the unnecessary nested if statements in function
> rtas_initialize(), to simplify the code. No functional changes
> introduced.
>
> Signed-off-by: Gavin Shan
Series applied to powerpc next, thanks.
https://git.kernel.org/power
On Fri, 2017-01-13 at 17:10:00 UTC, "Naveen N. Rao" wrote:
> From: Daniel Borkmann
>
> We have a check earlier to ensure we don't proceed if image is NULL. As
> such, the redundant check can be removed.
>
> Signed-off-by: Daniel Borkmann
> [Added similar changes for classic BPF JIT]
> Signed-of
On Thu, 2016-11-03 at 05:10:55 UTC, Paul Mackerras wrote:
> These functions compute an IP checksum by computing a 64-bit sum and
> folding it to 32 bits (the "nofold" in their names refers to folding
> down to 16 bits). However, doing (u32) (s + (s >> 32)) is not
> sufficient to fold a 64-bit sum
On Thu, 2017-01-19 at 03:19:10 UTC, Anton Blanchard wrote:
> From: Anton Blanchard
>
> IBM bit 31 (for the rest of us - bit 0) is a reserved field in the
> instruction definition of mtspr and mfspr. Hardware is encouraged to
> (and does) ignore it.
>
> As a result, if userspace executes an mtspr
On Mon, 2017-01-23 at 19:42:54 UTC, Darren Stevens wrote:
> prom_init.c calls 'instance-to-package' twice, but the return
> is not checked during prom_find_boot_cpu(). The result is then
> passed to prom_getprop, which could be PROM_ERROR.
> Add a return check to prevent this.
>
> This was found o
On Wed, 2017-01-18 at 23:10:16 UTC, Gavin Shan wrote:
> In __eeh_clear_pe_frozen_state(), we should pass the flag's value
> instead of its address to eeh_unfreeze_pe(). The isolated flag is
> cleared if no error returned from __eeh_clear_pe_frozen_state().
> We never observed the error from the fun
Vipin K Parashar writes:
> Added check for OPAL_WRONG_STATE error code returned from OPAL.
> Currently Linux flashes "unexpected error" over console for this
> error. This will avoid throwing such message and return I/O error
> for such OPAL failures.
Why do we expect to get OPAL_WRONG_STATE ?
On 26 January 2017 at 23:05, Jason Gunthorpe
wrote:
> On Thu, Jan 26, 2017 at 09:22:48PM +0100, Michal Such??nek wrote:
>
>> This is repeated a few times in the driver so I added memset to quiet
>> gcc and make behavior deterministic in case the unused fields get some
>> meaning in the future.
>
>
On Thu, Jan 26, 2017 at 09:22:48PM +0100, Michal Such??nek wrote:
> This is repeated a few times in the driver so I added memset to quiet
> gcc and make behavior deterministic in case the unused fields get some
> meaning in the future.
Yep, reserved certainly needs to be zeroed.. Can you send a p
Hello,
building ibmvtpm I noticed gcc warning complaining that second word of
struct ibmvtpm_crq in tpm_ibmvtpm_suspend is uninitialized.
The structure is defined as
struct ibmvtpm_crq {
u8 valid;
u8 msg;
__be16 len;
__be32 data;
__be64 reserved;
} __attr
On 01/26/2017 12:28 PM, Stephen Hemminger wrote:
> On Wed, 25 Jan 2017 15:02:19 -0600
> Thomas Falcon wrote:
>
>> static irqreturn_t ibmvnic_interrupt(int irq, void *instance)
>> {
>> struct ibmvnic_adapter *adapter = instance;
>> +unsigned long flags;
>> +
>> +spin_lock_irqsave(&ad
On 01/26/2017 11:56 AM, David Miller wrote:
> From: Thomas Falcon
> Date: Thu, 26 Jan 2017 10:44:22 -0600
>
>> On 01/25/2017 10:04 PM, David Miller wrote:
>>> From: Thomas Falcon
>>> Date: Wed, 25 Jan 2017 15:02:19 -0600
>>>
Move most interrupt handler processing into a tasklet, and
int
On Wed, 25 Jan 2017 15:02:19 -0600
Thomas Falcon wrote:
> static irqreturn_t ibmvnic_interrupt(int irq, void *instance)
> {
> struct ibmvnic_adapter *adapter = instance;
> + unsigned long flags;
> +
> + spin_lock_irqsave(&adapter->crq.lock, flags);
> + vio_disable_interrupts(a
On Thu, Jan 26, 2017 at 02:56:03PM +0100, Petr Mladek wrote:
> On Thu 2017-01-19 09:46:09, Josh Poimboeuf wrote:
> > For live patching and possibly other use cases, a stack trace is only
> > useful if it can be assured that it's completely reliable. Add a new
> > save_stack_trace_tsk_reliable() fu
From: Thomas Falcon
Date: Thu, 26 Jan 2017 10:44:31 -0600
> On 01/25/2017 10:05 PM, David Miller wrote:
>> From: Thomas Falcon
>> Date: Wed, 25 Jan 2017 15:02:20 -0600
>>
>>> In the current driver, the MTU is set to the maximum value
>>> capable for the backing device. This patch sets the MTU to
From: Thomas Falcon
Date: Thu, 26 Jan 2017 10:44:22 -0600
> On 01/25/2017 10:04 PM, David Miller wrote:
>> From: Thomas Falcon
>> Date: Wed, 25 Jan 2017 15:02:19 -0600
>>
>>> Move most interrupt handler processing into a tasklet, and
>>> introduce a delay after re-enabling interrupts to fix timi
On Wed, Jan 25, 2017 at 8:38 PM, Sukadev Bhattiprolu
wrote:
>
> Move the GET_FIELD and SET_FIELD macros to vas.h as VAS and other
> users of VAS, including NX-842 can use those macros.
>
> Signed-off-by: Sukadev Bhattiprolu
Reviewed-by: Dan Streetman
> ---
> arch/powerpc/include/asm/vas.h
On 01/25/2017 10:05 PM, David Miller wrote:
> From: Thomas Falcon
> Date: Wed, 25 Jan 2017 15:02:20 -0600
>
>> In the current driver, the MTU is set to the maximum value
>> capable for the backing device. This patch sets the MTU to the
>> default value for a Linux net device.
> Why are you doing t
On 01/25/2017 10:04 PM, David Miller wrote:
> From: Thomas Falcon
> Date: Wed, 25 Jan 2017 15:02:19 -0600
>
>> Move most interrupt handler processing into a tasklet, and
>> introduce a delay after re-enabling interrupts to fix timing
>> issues encountered in hardware testing.
>>
>> Signed-off-by:
On 26.01.17 10:46:43, William Cohen wrote:
> From 7e46dbd7dc5bc941926a4a63c28ccebf46493e8d Mon Sep 17 00:00:00 2001
> From: William Cohen
> Date: Thu, 26 Jan 2017 10:33:59 -0500
> Subject: [PATCH] Avoid hypthetical string truncation in oprofile stats buffer
> MIME-Version: 1.0
> Content-Type: text
From: Mark Marshall
The commit 7a654172161c ("mtd/ifc: Add support for IFC controller
version 2.0") added support for version 2.0 of the IFC controller.
The version 2.0 controller has the ECC status registers at a different
location to the previous versions.
Correct the fsl_ifc_nand structure so
On Thu 2017-01-19 09:46:09, Josh Poimboeuf wrote:
> For live patching and possibly other use cases, a stack trace is only
> useful if it can be assured that it's completely reliable. Add a new
> save_stack_trace_tsk_reliable() function to achieve that.
> diff --git a/arch/x86/kernel/stacktrace.c
On Thu, Jan 26, 2017 at 12:00 PM, David Laight wrote:
> From: Anton Blanchard
>> Sent: 25 January 2017 23:01
>> gcc trunk has failed to build PowerPC64 kernels for a month or so. The issue
>> is in oprofile, which is common code but ends up being sucked into
>> arch/powerpc and therefore subject t
From: Anton Blanchard
> Sent: 25 January 2017 23:01
> gcc trunk has failed to build PowerPC64 kernels for a month or so. The issue
> is in oprofile, which is common code but ends up being sucked into
> arch/powerpc and therefore subject to the -Werror applied to arch/powerpc:
...
> linux/arch/power
Bhumika Goyal writes:
> Declare usb_ep_ops structures as const as they are only stored in the
> ops field of an usb_ep structure. This field is of type const, so
> usb_ep_ops structures having this property can be made const too.
> Done using Coccinelle( A smaller version of the script)
For pxa2
-VAS/20170126-095706
config: powerpc-allmodconfig (attached as .config)
compiler: powerpc64-linux-gnu-gcc (Debian 6.1.1-9) 6.1.1 20160705
reproduce:
wget
https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross
-O ~/bin/make.cross
chmod +x ~/bin/make.cross
52 matches
Mail list logo
