Hi all,
Today's linux-next merge of the akpm-current tree got a conflict in:
mm/huge_memory.c
between commit:
ff20c2e0acc5 ("mm: Some arch may want to use HPAGE_PMD related values as
variables")
from the powerpc tree and commit:
82fdbe051e29 ("mm: make optimistic check for swapin reada
This patch fixes a regression that causes any usage of hugetlb
on e5500 to oops.
The following changes since commit fb822e6076d972691c5dd33431c10f82dda94ae9:
powerpc/hw_breakpoint: Fix oops when destroying hw_breakpoint event
(2016-03-03 22:06:08 +1100)
are available in the git repository at:
* Petr Mladek [2016-03-03 17:52:01]:
> From: Balbir Singh
>
> Changelog v4:
> 1. Renamed klp_matchaddr() to klp_get_ftrace_location()
> and used it just to convert the function address.
> 2. Synced klp_write_module_reloc() with s390(); made it
> inline, no error me
On 03/04/2016 10:19 AM, Aneesh Kumar K.V wrote:
> Anshuman Khandual writes:
>
>> On 03/02/2016 05:40 PM, Michael Ellerman wrote:
>>> On Wed, 2016-02-03 at 08:46:12 UTC, Anshuman Khandual wrote:
For partition running on PHYP, there can be a adjunct partition
which shares the virtual addr
On Thu, Mar 3, 2016 at 5:41 PM, Anshuman Khandual
wrote:
> On 03/03/2016 12:31 PM, Li Zhang wrote:
>> From: Li Zhang
>>
>> This patch is based on Mel Gorman's old patch in the mailing list,
>> https://lkml.org/lkml/2015/5/5/280 which is dicussed but it is
>
> Typo here ...
Current comment added in pmao_restore_workaround() for
hard_irq_disable is misleading. Comment should say to hard
"disable" interrupts instead of "enable" it. Patch to fix the typo.
Signed-off-by: Madhavan Srinivasan
---
arch/powerpc/perf/core-book3s.c | 2 +-
1 file changed, 1 insertion(+), 1 d
Current comment in the early_setup_secondary() for
paca->soft_enabled update is misleading. Comment should say to
Mark interrupts "disabled" insteads of "enable".
Patch to fix the typo.
Signed-off-by: Madhavan Srinivasan
---
arch/powerpc/kernel/setup_64.c | 2 +-
1 file changed, 1 insertion(+),
Anshuman Khandual writes:
> On 03/02/2016 05:40 PM, Michael Ellerman wrote:
>> On Wed, 2016-02-03 at 08:46:12 UTC, Anshuman Khandual wrote:
>>> For partition running on PHYP, there can be a adjunct partition
>>> which shares the virtual address range with the operating system.
>>> Virtual address
Hi all,
Today's linux-next merge of the kvm tree got a conflict in:
arch/powerpc/kvm/book3s_64_vio_hv.c
between commit:
f64e8084c94b ("powerpc/mm: Move hash related mmu-*.h headers to book3s/")
from the powerpc tree and commit:
d3695aa4f452 ("KVM: PPC: Add support for multiple-TCE hcall
On 03/02/2016 05:40 PM, Michael Ellerman wrote:
> On Wed, 2016-02-03 at 08:46:12 UTC, Anshuman Khandual wrote:
>> For partition running on PHYP, there can be a adjunct partition
>> which shares the virtual address range with the operating system.
>> Virtual address ranges which can be used by the a
Acked-by: Ian Munsie
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
On 03/01/2016 07:47 PM, Michael Ellerman wrote:
> On Wed, 2016-03-02 at 10:02 +1100, Michael Ellerman wrote:
>> On Wed, 2016-10-02 at 17:13:29 UTC, Nathan Fontenot wrote:
>>> Now that the DLPAR add/remove flow updates the ibm,dynamic-memory device
>>> tree property each time we add or remove a LMB
On 03/03/16 15:26, Michael Ellerman wrote:
> From: Torsten Duwe
>
> The gcc switch -mprofile-kernel defines a new ABI for calling _mcount()
> very early in the function with minimal overhead.
>
> Although mprofile-kernel has been available since GCC 3.4, there were
> bugs which were only fixed r
On 03/03/16 15:26, Michael Ellerman wrote:
> Move the logic to work out the kernel toc pointer into a header. This is
> a good cleanup, and also means we can use it elsewhere in future.
>
> Reviewed-by: Kamalesh Babulal
> Reviewed-by: Torsten Duwe
> Signed-off-by: Michael Ellerman
>
Reviewed-
On Tue, 2016-01-03 at 07:29:21 UTC, "Aneesh Kumar K.V" wrote:
> Signed-off-by: Aneesh Kumar K.V
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/ee3b93ebfbed6279f7a3290014
cheers
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs
On Tue, 2016-01-03 at 04:15:14 UTC, "Aneesh Kumar K.V" wrote:
> From: "Kirill A. Shutemov"
>
> With next generation power processor, we are having a new mmu model
> [1] that require us to maintain a different linux page table format.
>
> Inorder to support both current and future ppc64 systems w
On Tue, 2016-01-03 at 07:29:20 UTC, "Aneesh Kumar K.V" wrote:
> Signed-off-by: Aneesh Kumar K.V
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/f64e8084c94bb0449177364856
cheers
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs
On Tue, 2016-01-03 at 04:15:13 UTC, "Aneesh Kumar K.V" wrote:
> This is needed so that we can support both hash and radix page table
> using single kernel. Radix kernel uses a 4 level table.
>
> We now use physical address in upper page table tree levels. Even though
> they are aligned to their si
On Tue, 2016-01-03 at 07:29:18 UTC, "Aneesh Kumar K.V" wrote:
> We don't need to update linux page table entry with _PAGE_HASHPTE early
> in hash pte fault. A parallel pte update will loop via _PAGE_BUSY
> and look at _PAGE_HASHPTE for a required hpte flush only if
> _PAGE_BUSY is cleared. That ens
On Tue, 2016-01-03 at 04:15:12 UTC, "Aneesh Kumar K.V" wrote:
> We remove real_pte_t out of STRICT_MM_TYPESCHECK.
>
> Reviewed-by: Paul Mackerras
> Signed-off-by: Aneesh Kumar K.V
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/ae9a71afa4d7cf29a816fbc387
cheers
_
On Tue, 2016-01-03 at 07:29:17 UTC, "Aneesh Kumar K.V" wrote:
> We are updating pte in those functions.
>
> Signed-off-by: Aneesh Kumar K.V
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/e9a681478ce535b4a0263a760a
cheers
___
Linuxp
On Tue, 2016-01-03 at 04:15:11 UTC, "Aneesh Kumar K.V" wrote:
> We move the page table accessors into a separate header. We will
> later add a big endian variant of the table which is needed for radix.
> No functionality change only code movement.
>
> Reviewed-by: Paul Mackerras
> Signed-off-by:
eeh.h could be included when we have following condition. Then we
run into build error as below: (CONFIG_PPC64 && !CONFIG_EEH) ||
(!CONFIG_PPC64 && !CONFIG_EEH)
In file included from arch/powerpc/kernel/of_platform.c:30:0:
./arch/powerpc/include/asm/eeh.h:344:48: error: ‘struct pci_dn’ \
declared
On 4 Mar 2016 03:52, "Petr Mladek" wrote:
>
> From: Balbir Singh
>
> Changelog v4:
> 1. Renamed klp_matchaddr() to klp_get_ftrace_location()
>and used it just to convert the function address.
> 2. Synced klp_write_module_reloc() with s390(); made it
>inline
On Fri, Mar 04, 2016 at 11:01:36AM +1100, Gavin Shan wrote:
>On Wed, Mar 02, 2016 at 02:03:36PM +1100, Michael Ellerman wrote:
>>On Wed, 2016-03-02 at 13:28 +1100, Gavin Shan wrote:
>>
>>> Those patches are based on the series of patches supporting EEH for VF,
>>> which is pending for merging: http
On Wed, Mar 02, 2016 at 02:03:36PM +1100, Michael Ellerman wrote:
>On Wed, 2016-03-02 at 13:28 +1100, Gavin Shan wrote:
>
>> Those patches are based on the series of patches supporting EEH for VF,
>> which is pending for merging: https://patchwork.ozlabs.org/patch/581315/
>
>I haven't merged them y
On Wed, Feb 10, 2016 at 05:02:48PM +1100, Gavin Shan wrote:
In this series, there're some issues on attempt to recover errors on
pass-throu VFs. Updated series (v15) with more patches sent to address
the issues:
So please ignore this series and look at v15.
Thanks,
Gavin
>This applies to linux-
From: Wei Yang
This adds weak function pcibios_bus_add_device() for arch dependent
code could do proper setup. For example, powerpc could setup EEH
related resources for SRIOV VFs.
Signed-off-by: Wei Yang
Reviewed-by: Gavin Shan
Acked-by: Bjorn Helgaas
---
drivers/pci/bus.c | 3 +++
includ
When EEH error happened to the parent PE of those PEs that have
been passed through to guest, the error is propagated to guest
domain and the VFIO driver's error handlers are called. It's not
correct as the error in the host domain shouldn't be propagated
to guests and affect them.
This adds one m
When passing through SRIOV VFs to guest, we possibly encounter EEH
error on PF. In this case, the VF PEs are put into frozen state.
The error could be reported to guest before it's captured by the
host. That means the guest could attempt to recover errors on VFs
before host gets chance to recover e
From: Wei Yang
After PE reset, OPAL API opal_pci_reinit() is called on all devices
contained in the PE to reinitialize them. While skiboot is not aware of
VFs, we have to implement the function in kernel to reinitialize VFs after
reset on PE for VFs.
In this patch, two functions pnv_pci_fixup_vf
From: Wei Yang
PFs are enumerated on PCI bus, while VFs are created by PF's driver.
In EEH recovery, it has two cases:
1. Device and driver is EEH aware, error handlers are called.
2. Device and driver is not EEH aware, un-plug the device and plug it again
by enumerating it.
The special thing h
When we have partial hotplug as part of the error recovery on PF,
the VFs that are bound with vfio-pci driver will experience hotplug.
That's not allowed.
This checks if the VF PE is passed or not. If it does, we leave
the VF without removing it.
Signed-off-by: Gavin Shan
Reviewed-by: Russell Cu
From: Wei Yang
VFs and their corresponding pdn are created and released dynamically
when their PF's SRIOV capability is enabled and disabled. This creates
and releases EEH devices for VFs when creating and releasing their pdn
instances, which means EEH devices and pdn instances have same life
cyc
From: Wei Yang
This creates PEs for VFs in the weak function pcibios_bus_add_device().
Those PEs for VFs are identified with newly introduced flag EEH_PE_VF
so that we treat them differently during EEH recovery.
Signed-off-by: Wei Yang
Acked-by: Gavin Shan
---
arch/powerpc/include/asm/eeh.h
From: Wei Yang
PEs for VFs don't have primary bus. So they have to have their own reset
backend, which is used during EEH recovery. The patch implements the reset
backend for VF's PE by issuing FLR or AF FLR to the VFs, which are contained
in the PE.
Signed-off-by: Wei Yang
Acked-by: Gavin Shan
From: Wei Yang
During EEH recovery, hotplug is applied to the devices which don't
have drivers or their drivers don't support EEH. However, the hotplug,
which was implemented based on PCI bus, can't be applied to VF directly.
Instead, we unplug and plug individual PCI devices (VFs).
This renames
From: Wei Yang
As commit ac205b7bb72f ("PCI: make sriov work with hotplug remove")
indicates, VFs which is on the same PCI bus as their PF, should be
removed before the PF. Otherwise, we might run into kernel crash
at PCI unplugging time.
This applies the above pattern to powerpc PCI hotplug pat
This patchset enables EEH on SRIOV VFs. The general idea is to create proper
VF edev and VF PE and handle them properly.
Different from the Bus PE, VF PE just contain one VF. This introduces the
difference of EEH error handling on a VF PE. Generally, it has several
differences.
First, the VF's re
From: Wei Yang
This restricts the EEH address cache to use only the first 7 BARs. This
makes __eeh_addr_cache_insert_dev() ignore PCI bridge window and IOV BARs.
As the result of this change, eeh_addr_cache_get_dev() will return VFs from
VF's resource addresses instead of parent PFs.
This also r
On 29/02/16 16:40, Vaibhav Jain wrote:
Add a check at the beginning of cxl_probe function to ignore virtual pci
devices created for each afu registered. This fixes the the errors
messages logged about missing CXL vsec, when cxl probe is unable to
find necessary vsec entries in device pci config s
Currently it doesn't appear the resulting binary actually uses any Altivec
or VSX instructions the solution is to explicitly tell GCC to use vector
instructions and use vector types in the code.
Part of this this issue can be GCC version specific:
GCC 4.9.x is happy to use Altivec and VSX instruc
Signed-off-by: Cyril Bur
---
tools/testing/selftests/powerpc/benchmarks/context_switch.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/tools/testing/selftests/powerpc/benchmarks/context_switch.c
b/tools/testing/selftests/powerpc/benchmarks/context_switch.c
index 7b785
On Wed, 2016-03-02 at 13:16 +0100, Alessio Igor Bogani wrote:
> Signed-off-by: Alessio Igor Bogani
> ---
> v2 -> v3
> Use appropriate git format-patch flag "-M" to detect renames
>
> v1 -> v2
> Address suggestion made by Scott Wood
> Split the second patch in two
> Don
Several properties in the DRC device tree format are replaced by
more compact representations to allow, for example, for the encoding
of vast amounts of memory, and or reduced duplication of information
in related data structures.
"ibm,drc-info": This property, when present, replaces the followin
From: Balbir Singh
Changelog v4:
1. Renamed klp_matchaddr() to klp_get_ftrace_location()
and used it just to convert the function address.
2. Synced klp_write_module_reloc() with s390(); made it
inline, no error message, return -ENOSYS
3. Added an err
On Fri 2016-03-04 00:11:55, Balbir Singh wrote:
>
> Changelog v3:
> 1. Moved -ENOSYS to -EINVAL in klp_write_module_reloc
> 2. Moved klp_matchaddr to use ftrace_location_range
Ah, I have been working on it in parallel. It took me longer
because I was busy with some other stuff previou
Changelog v3:
1. Moved -ENOSYS to -EINVAL in klp_write_module_reloc
2. Moved klp_matchaddr to use ftrace_location_range
Changelog v2:
1. Implement review comments by Michael
2. The previous version compared _NIP from the
wrong location to check for whethe
On 03/03/16 23:46, Balbir Singh wrote:
> Changelog v3:
> 1. Removed spurious kgdb patch
> 2. Moved -ENOSYS to -EINVAL in klp_write_module_reloc
> 3. Moved klp_matchaddr to use ftrace_location_range
>
Please ignore -- wrong patch!
Balbir
Changelog v3:
1. Removed spurious kgdb patch
2. Moved -ENOSYS to -EINVAL in klp_write_module_reloc
3. Moved klp_matchaddr to use ftrace_location_range
Changelog v2:
1. Implement review comments by Michael
2. The previous version compared _NIP from the
On Mon, 2016-29-02 at 06:29:55 UTC, Suraj Jitindar Singh wrote:
> LTO can cause GCC to inline some functions which have attributes set. The
> act of inlining the functions can lead to GCC forgetting about the
> attributes which leads to incorrect tests.
> Notable example being: __attribute__((__tar
On Wed, 2016-02-03 at 12:44:31 UTC, Michael Ellerman wrote:
> Gcc helpfully points out that we're accessing past the end of the gprs
> array:
>
> tm-signal-msr-resv.c: In function 'signal_usr1':
> tm-signal-msr-resv.c:43:37: error: array subscript is above array bounds
> [-Werror=array-bounds
On Mon, 2016-29-02 at 06:53:43 UTC, Cyril Bur wrote:
> Test that the non volatile floating point and Altivec registers get
> correctly preserved across the fork() syscall.
>
> fork() works nicely for this purpose, the registers should be the same for
> both parent and child
>
> Signed-off-by: Cyr
On Thu, Mar 03, 2016 at 08:23:38PM +1100, Michael Ellerman wrote:
> On Wed, 2016-03-02 at 12:59 +0100, Peter Zijlstra wrote:
>
> > On Wed, Mar 02, 2016 at 10:53:24PM +1100, Michael Ellerman wrote:
>
> > > Peterz, acme, do you guys want to take this? Or should I?
> >
> > I'm not too happy its touc
* Balbir Singh [2016-03-03 18:00:54]:
> Changelog:
> 1. Implement review comments by Michael
> 2. The previous version compared _NIP from the
> wrong location to check for whether we
> are going to a patched location
>
> This applies on top of the patches posted by
On 03/03/2016 12:31 PM, Li Zhang wrote:
> From: Li Zhang
>
> This patch is based on Mel Gorman's old patch in the mailing list,
> https://lkml.org/lkml/2015/5/5/280 which is dicussed but it is
Typo here
> fixed with a completion to wait for all memo
On Wed, 2016-03-02 at 12:59 +0100, Peter Zijlstra wrote:
> On Wed, Mar 02, 2016 at 10:53:24PM +1100, Michael Ellerman wrote:
> > Peterz, acme, do you guys want to take this? Or should I?
>
> I'm not too happy its touching event->ctx at all. It really should not
> be doing that.
Hmm OK.
It's bee
On Thu, Mar 03, 2016 at 03:01:41PM +0800, Li Zhang wrote:
> From: Li Zhang
>
> Parallel initialisation has been enabled for X86,
> boot time is improved greatly.
> On Power8, for small memory, it is improved greatly.
> Here is the result from my test on Power8 platform:
>
> For 4GB memory: 57% i
On Thu, Mar 03, 2016 at 03:01:40PM +0800, Li Zhang wrote:
> From: Li Zhang
>
> This patch is based on Mel Gorman's old patch in the mailing list,
> https://lkml.org/lkml/2015/5/5/280 which is dicussed but it is
> fixed with a completion to wait for all memory initialised in
> page_alloc_init_late
59 matches
Mail list logo
