On 11/08/16 07:45, Mauricio Faria de Oliveira wrote:
This patch leverages 'struct pci_host_bridge' from the PCI subsystem
in order to free the pci_controller only after the last reference to
its devices is dropped (avoiding an oops in pcibios_release_device()
if the last reference is dropped
Balbir Singh writes:
> On 09/08/16 04:27, Reza Arbab wrote:
>> Signed-off-by: Reza Arbab
>> ---
>> .../bindings/powerpc/opal/hotplug-aperture.txt | 26
>> ++
>> 1 file changed, 26 insertions(+)
>> create mode 100644
>>
On 09/08/16 04:27, Reza Arbab wrote:
> Signed-off-by: Reza Arbab
> ---
> .../bindings/powerpc/opal/hotplug-aperture.txt | 26
> ++
> 1 file changed, 26 insertions(+)
> create mode 100644
>
Radim Krčmář writes:
> 2016-08-03 13:36+0200, Paolo Bonzini:
>> hmi.c functions are unused unless sibling_subcore_state is nonzero, and
>> that in turn happens only if KVM is in use. So move the code to
>> arch/powerpc/kvm/, putting it under CONFIG_KVM_BOOK3S_64_HANDLER
>>
Hi all,
I have made Mailman work mostly with DKIM (and therefore DMARC). The
one remaining trick is this: Mailman will "simplify" mail addresses in
Cc (and maybe From and To) headers in some circumstances - which breaks
DKIM signatures.
So, for an email address like:
Name
--
Cheers,
Stephen Rothwell
--
Cheers,
Stephen Rothwell
This condenses the opal node searching into a single function that finds
all compatible nodes, instead of just searching the ibm,opal children,
for ipmi, flash, and prd similar to how opal-i2c nodes are found.
Signed-off-by: Jack Miller
---
On Wed, 10 Aug 2016, Gabriel Paubert wrote:
> Just a question, does sleep work on your PowerBook?
Oh, this PowerBook is on 24/7, it's a small home server and I don't think
I ever used any sleep or hibernation modes on this machine. Sorry :\
C.
--
BOFH excuse #145:
Flat tire on station wagon
On 08/10/2016 06:45 PM, Mauricio Faria de Oliveira wrote:
Changelog:
- v3: different approach: struct pci_host_bridge.release_fn()
- v2: different approach: struct pci_controller.refcount
Oops, the v3 submission has no cover letter, so the subject changed
a bit from what was in v2. This is
On 08/10/2016 10:53 AM, Mauricio Faria de Oliveira wrote:
I'll go down that path for a PATCH v3.
That is,
'powerpc/pseries: use pci_host_bridge.release_fn() to kfree(phb)'
--
Mauricio Faria de Oliveira
IBM Linux Technology Center
This patch leverages 'struct pci_host_bridge' from the PCI subsystem
in order to free the pci_controller only after the last reference to
its devices is dropped (avoiding an oops in pcibios_release_device()
if the last reference is dropped after pcibios_free_controller()).
The patch relies on
On Mon, Aug 08, 2016 at 01:27:20PM -0500, Reza Arbab wrote:
> Signed-off-by: Reza Arbab
> ---
> .../bindings/powerpc/opal/hotplug-aperture.txt | 26
> ++
> 1 file changed, 26 insertions(+)
> create mode 100644
>
On Wed, Aug 10, 2016 at 08:30:28PM +1000, Michael Ellerman wrote:
Reza Arbab writes:
Node hotplug is not supported on power [1].
But maybe it should be?
Doing so will involve, at the very least, reverting the commit I cited,
3af229f2071f ("powerpc/numa: Reset
2016-08-03 13:36+0200, Paolo Bonzini:
> hmi.c functions are unused unless sibling_subcore_state is nonzero, and
> that in turn happens only if KVM is in use. So move the code to
> arch/powerpc/kvm/, putting it under CONFIG_KVM_BOOK3S_64_HANDLER
> rather than CONFIG_PPC_BOOK3S_64. The
On Thu, Aug 04, 2016 at 10:24:04AM +0100, Mel Gorman wrote:
[1.713998] Unable to handle kernel paging request for data at address
0xff7a1
[1.714164] Faulting instruction address: 0xc0270cd0
[1.714304] Oops: Kernel access of bad area, sig: 11 [#1]
[1.714414] SMP
On 08/01/2016 07:42 PM, Michael Bringmann wrote:
> hotplug_init: Simplify the code needed for runtime memory hotplug and
> maintenance with a conversion routine that transforms the compressed
> property "ibm,dynamic-memory-v2" to the form of "ibm,dynamic-memory"
> within the
On 08/01/2016 07:42 PM, Michael Bringmann wrote:
> powerpc/memory: Add parallel routines to parse the new property
> "ibm,dynamic-memory-v2" property when it is present, and then to
> finish initialization of the relevant memory structures with the
> operating system. This code is shared between
On Wed, 10 Aug 2016 15:37:17 +1000
Alexey Kardashevskiy wrote:
> On 09/08/16 22:16, Alex Williamson wrote:
> > On Tue, 9 Aug 2016 15:19:39 +1000
> > Alexey Kardashevskiy wrote:
> >
> >> On 09/08/16 02:43, Alex Williamson wrote:
> >>> On Wed, 3 Aug 2016
On 08/01/2016 08:24 PM, Michael Bringmann wrote:
> powerpc/memory: Add parallel routines to parse the new property
> "ibm,dynamic-memory-v2" property when it is present, and then to
> register the relevant memory blocks with the operating system.
> This property format is intended to provide a
On 16-08-10 14:40:13, David Laight wrote:
> From: Linuxppc-dev
> [mailto:linuxppc-dev-bounces+david.laight=aculab@lists.ozlabs.org] On
> Behalf Of
> > > > So given what you have above, you'd use something like:
> > > >
> > > > struct ima_kexec_hdr {
> > > > u16 version;
> > > >
From: Linuxppc-dev
[mailto:linuxppc-dev-bounces+david.laight=aculab@lists.ozlabs.org] On
Behalf Of
> > > So given what you have above, you'd use something like:
> > >
> > > struct ima_kexec_hdr {
> > > u16 version;
> > > u16 _reserved0;
> > > u32 _reserved1;
> > > u64 buffer_size;
>
On 08/10/2016 05:30 AM, Michael Ellerman wrote:
> Reza Arbab writes:
>
>> These changes enable onlining memory into ZONE_MOVABLE on power, and the
>> creation of discrete nodes of movable memory.
>>
>> Node hotplug is not supported on power [1].
>
> But maybe it should
On 16-08-10 08:54:36, Mimi Zohar wrote:
> On Wed, 2016-08-10 at 19:52 +1000, Michael Ellerman wrote:
> > Thiago Jung Bauermann writes:
> >
> > > Am Mittwoch, 10 August 2016, 13:41:08 schrieb Michael Ellerman:
> > >> Thiago Jung Bauermann
On 08/09/2016 10:45 PM, Andrew Donnellan wrote:
I'm currently working on a cxl defect found by an IBM test team where we
run into this - will review this patch more thoroughly and test it shortly.
Gavin provided a review/suggestions via chat, pointing to rely on the
refcount that already
On 08/10, Denys Vlasenko wrote:
>
> Currently, to support 32-bit binaries with PLT in BSS kernel maps *entire
> brk area* with executable rights for all binaries, even --secure-plt ones.
>
> Stop doing that.
Can't really review this patch, but at least the change in mm/mmap.c looks
technically
On 32-bit powerpc the ELF PLT sections of binaries (built with --bss-plt,
or with a toolchain which defaults to it) look like this:
[17] .sbss NOBITS 0002aff8 01aff8 14 00 WA 0 0 4
[18] .plt NOBITS 0002b00c 01aff8 84 00 WAX 0 0 4
On 08/10/2016 12:43 AM, Kees Cook wrote:
-static int do_brk(unsigned long addr, unsigned long len)
+static int do_brk_flags(unsigned long addr, unsigned long len, unsigned long
flags)
{
struct mm_struct *mm = current->mm;
struct vm_area_struct *vma, *prev;
- unsigned long
On Wed, 2016-08-10 at 19:52 +1000, Michael Ellerman wrote:
> Thiago Jung Bauermann writes:
>
> > Am Mittwoch, 10 August 2016, 13:41:08 schrieb Michael Ellerman:
> >> Thiago Jung Bauermann writes:
> >> > Am Dienstag, 09 August 2016,
On Wed, 2016-10-08 at 05:44:46 UTC, Cyril Bur wrote:
> There was an assumption that flush_tmregs_to_thread() would only be
> called for a task which is not current. And a warning could be shown
> to indicate that current is being ptraced.
>
> In the event of a core dump the current threads state
On Tue, 2016-09-08 at 05:09:13 UTC, Mahesh Salgaonkar wrote:
> From: Mahesh Salgaonkar
>
> When machine check occurs with MSR(RI=0), it means MC interrupt is
> unrecoverable and kernel goes down to panic path. But the console
> message still shows it as recovered. This
On Fri, 2016-08-07 at 05:55:43 UTC, Benjamin Herrenschmidt wrote:
> The generic allocation code may sometimes decide to assign a prefetchable
> 64-bit BAR to the M32 window. In fact it may also decide to allocate
> a 64-bit non-prefetchable BAR to the M64 one ! So using the resource
> flags as a
On Tue, 2016-02-08 at 08:07:05 UTC, Christophe Leroy wrote:
> commit 7aef4136566b0 ("powerpc32: rewrite csum_partial_copy_generic()
> based on copy_tofrom_user()") introduced a bug when destination
> address is odd and initial csum is not null
>
> In that (rare) case the initial csum value has to
On Mon, 2016-08-08 at 09:57:48 UTC, Frederic Barrat wrote:
> Switch the setting of psl_fir_cntl from debug to production
> environment recommended value. It mostly affects the PSL behavior when
> an error is raised in psl_fir1/2.
>
> Tested with cxlflash.
>
> Signed-off-by: Frederic Barrat
"Rafael J. Wysocki" writes:
> On Wednesday, August 10, 2016 02:28:47 PM Michael Ellerman wrote:
>>
>> Who's merging this?
>
> I am.
Thanks!
On 08/10/2016 12:35 AM, Andrew Donnellan wrote:
if (phb->controller_ops.release_device)
phb->controller_ops.release_device(dev);
+
+if (unlikely(!phb))
+pr_warn("%s: PCI device %s has null PHB; refcount bug!",
+__func__, dev_name(>dev)); /* WARN_ON ahead */
On 08/10/2016 06:36 AM, Michael Ellerman wrote:
Denys Vlasenko writes:
On 32-bit powerps the ELF PLT sections of binaries (built with --bss-plt,
or with a toolchain which defaults to it) look like this:
...
arch/powerpc/include/asm/page.h| 10 +-
On 08/09/2016 10:45 PM, Andrew Donnellan wrote:
[snip] Notably, only
the pseries platform calls pcibios_free_controller() for some purpose
other than to release the pci_controller in case of errors just after
the call to pcibios_alloc_controller() (i.e., 'goto error' scenarios).
cxl's vPHB API
Hi all,
my MPC5200 still does not boot even with the fix bellow applied. I dug a
bit into it and now it seems that commit
309b315b6ec686ce050758cc4e29f6ad1125a83f is to blame.
commit 309b315b6ec686ce050758cc4e29f6ad1125a83f
Author: Aneesh Kumar K.V
Date: Sat
On Wednesday, August 10, 2016 02:28:47 PM Michael Ellerman wrote:
> Viresh Kumar writes:
>
> > On 04-08-16, 20:59, Akshay Adiga wrote:
> >> 'commit 09ca4c9b5958 ("cpufreq: powernv: Replacing pstate_id with
> >> frequency table index")' changes calc_global_pstate() to use
MCE must not enable MSR_RI until PACA_EXMC is no longer being used.
---
arch/powerpc/kernel/exceptions-64s.S | 21 -
1 file changed, 20 insertions(+), 1 deletion(-)
diff --git a/arch/powerpc/kernel/exceptions-64s.S
b/arch/powerpc/kernel/exceptions-64s.S
index
MCE must not use PACA_EXGEN. When a general exception enables MSR_RI,
that means SPRN_SRR[01] and SPRN_SPRG are no longer used. However the
PACA save area is still in use.
---
arch/powerpc/kernel/exceptions-64s.S | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git
I noticed a couple of potential issues with MCE handling. I
haven't been able to test this yet, but I would like to get
some second opinions on it. I know a few people have been looking
at the MCE handler recently.
Thanks,
Nick
Reza Arbab writes:
> These changes enable onlining memory into ZONE_MOVABLE on power, and the
> creation of discrete nodes of movable memory.
>
> Node hotplug is not supported on power [1].
But maybe it should be?
cheers
Le 10/08/2016 à 10:56, Gabriel Paubert a écrit :
On Fri, Aug 05, 2016 at 01:28:02PM +0200, Christophe Leroy wrote:
Signed-off-by: Christophe Leroy
---
arch/powerpc/kernel/misc_32.S | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git
On Tuesday 09 August 2016 05:06 PM, Wolfram Sang wrote:
The core will do this for us now.
For i2c-tegra.c
Acked-by: Laxman Dewangan
When fadump is enabled, by default 5% of system RAM is reserved for
fadump kernel. While that works for most cases, it is not good enough
for every case.
Currently, to override the default value, fadump supports specifying
memory to reserve with fadump_reserve_mem=size, where only a fixed size
crashkernel parameter supports different syntaxes to specify the amount
of memory to be reserved for kdump kernel. Below is one of the supported
syntaxes that needs parsing to find the memory size to reserve, based on
memory range:
crashkernel=:[,:,...]
While such parsing is implemented
This patchset adds support to input system memory range based memory size
for fadump reservation. The crashkernel parameter already supports such
syntax. The first patch refactors the parsing code of crashkernel parameter
for reuse. The second patch uses the newly refactored parsing code to
Thiago Jung Bauermann writes:
> Am Mittwoch, 10 August 2016, 13:41:08 schrieb Michael Ellerman:
>> Thiago Jung Bauermann writes:
>> > Am Dienstag, 09 August 2016, 09:01:13 schrieb Mimi Zohar:
>> >> On Tue, 2016-08-09 at 20:59 +1000,
On Fri, Aug 05, 2016 at 01:28:02PM +0200, Christophe Leroy wrote:
> Signed-off-by: Christophe Leroy
> ---
> arch/powerpc/kernel/misc_32.S | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/arch/powerpc/kernel/misc_32.S
Benjamin Herrenschmidt writes:
> It's all the jump label cruft that landed in apply_feature_fixups()
>
> You can't call random call there. On ppc32, it's running in that
> weirdo environment where the kernel isn't running at its linked
> address and we need to manually
On Wed, Aug 10, 2016 at 01:17:55AM -0700, Christian Kujau wrote:
> On Wed, 10 Aug 2016, Benjamin Herrenschmidt wrote:
> > We cannot do those initializations from apply_feature_fixups() as
> > this function runs in a very restricted environment in 32-bit where
> > the kernel isn't running at its
* Michael Ellerman [2016-08-10 16:57:57]:
> Srikar Dronamraju writes:
>
> >>
> >> > Conceptually it would be cleaner, if expensive, to calculate the real
> >> > memblock reserves if HASH_EARLY and ditch the dma_reserve, memory_reserve
> >> > and
On 08/09/2016 01:36 PM, Wolfram Sang wrote:
> The core will do this for us now.
>
> Signed-off-by: Wolfram Sang
> ---
(...)
> drivers/i2c/busses/i2c-exynos5.c| 4 +---
> drivers/i2c/busses/i2c-s3c2410.c| 1 -
For Exynos and S3C2410:
Acked-by:
On Wed, 10 Aug 2016, Benjamin Herrenschmidt wrote:
> We cannot do those initializations from apply_feature_fixups() as
> this function runs in a very restricted environment in 32-bit where
> the kernel isn't running at its linked address and the PTRRELOC()
> macro must be used for any global
On Wed, Aug 10, 2016 at 04:02:47PM +1000, Michael Ellerman wrote:
> > Conceptually it would be cleaner, if expensive, to calculate the real
> > memblock reserves if HASH_EARLY and ditch the dma_reserve, memory_reserve
> > and nr_kernel_pages entirely.
>
> Why is it expensive? memblock tracks the
On 08/09/2016 01:36 PM, Wolfram Sang wrote:
> Since v4.8-rc1, the I2C core will print detailed information when adding an
> I2C
> adapter fails. So, drivers can skip this now.
>
> I am still undecided if I apply this as a single patch or break it out. But
> for
> reviewing, avoiding the patch
We don't identify the machine type anymore...
Signed-off-by: Benjamin Herrenschmidt
---
diff --git a/arch/powerpc/kernel/setup_32.c b/arch/powerpc/kernel/setup_32.c
index c3e861d..f10a975 100644
--- a/arch/powerpc/kernel/setup_32.c
+++ b/arch/powerpc/kernel/setup_32.c
This makes it easier to debug crashes that happen very early before
the kernel takes over Open Firmware by allowing us to relate the OF
reported crashing addresses to offsets within the kernel.
Signed-off-by: Benjamin Herrenschmidt
---
diff --git
We cannot do those initializations from apply_feature_fixups() as
this function runs in a very restricted environment in 32-bit where
the kernel isn't running at its linked address and the PTRRELOC()
macro must be used for any global accesss.
Instead, split them into a separtate
On Wed, 2016-08-10 at 14:58 +1000, Michael Ellerman wrote:
> Benjamin Herrenschmidt writes:
>
> >
> > On Tue, 2016-08-09 at 02:06 -0700, Christian Kujau wrote:
> > >
> > > On Mon, 8 Aug 2016, Christian Kujau wrote:
> > > >
> > > >
> > > > while trying to upgrade
Christian Kujau writes:
> On Wed, 10 Aug 2016, Michael Ellerman wrote:
>> Benjamin Herrenschmidt writes:
>> > On Tue, 2016-08-09 at 02:06 -0700, Christian Kujau wrote:
>> >> On Mon, 8 Aug 2016, Christian Kujau wrote:
>> >> >
>> >> > while trying
The PCI adapter's firmware isn't fully functional when the PCIe bus
link is up. 1.8 seconds are needed for the firmware to be completely
functional according to the PCI bus settlement time (after reset)
we have in EEH code (EEH_PE_RST_SETTLE_TIME). Without the delay, the
driver fails to initialize
Srikar Dronamraju writes:
>>
>> > Conceptually it would be cleaner, if expensive, to calculate the real
>> > memblock reserves if HASH_EARLY and ditch the dma_reserve, memory_reserve
>> > and nr_kernel_pages entirely.
>>
>> Why is it expensive? memblock tracks the
Cyril Bur writes:
> There was an assumption that flush_tmregs_to_thread() would only be
> called for a task which is not current. And a warning could be shown
> to indicate that current is being ptraced.
>
> In the event of a core dump the current threads state is needed.
>
> > Conceptually it would be cleaner, if expensive, to calculate the real
> > memblock reserves if HASH_EARLY and ditch the dma_reserve, memory_reserve
> > and nr_kernel_pages entirely.
>
> Why is it expensive? memblock tracks the totals for all memory and
> reserved memory AFAIK, so it should
On Tue, Aug 09, 2016 at 01:36:17PM +0200, Wolfram Sang wrote:
> The core will do this for us now.
>
> Signed-off-by: Wolfram Sang
> ---
[...]
> drivers/i2c/busses/i2c-at91.c | 2 --
Acked-by: Ludovic Desroches
[...]
>
Mel Gorman writes:
> On Fri, Aug 05, 2016 at 07:25:03PM +1000, Michael Ellerman wrote:
>> > One way to do that would be to walk through the different memory
>> > reserved blocks and calculate the size. But Mel feels thats an
>> > overhead (from his reply to the other
69 matches
Mail list logo