Hi Pingfan,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on v4.17]
[cannot apply to pci/next next-20180612]
[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/commits/Pingfan-L
On 12/06/2018 01:47, Finn Thain wrote:
> On Sun, 10 Jun 2018, Benjamin Herrenschmidt wrote:
...
> I don't know what the bootloader situation is, but it looks messy...
> http://nubus-pmac.sourceforge.net/#booters
>
> Laurent, does Emile work on these machines?
>
No, Emile doesn't work on pmac-nub
The Linux Device Driver Model allows a physical device to be handled
by only a single driver. But at present, both shpchp and portdrv_pci
claim PCI_CLASS_BRIDGE_PCI, and touch devices_kset. This causes a
few problems, one is the wrong shutdown seq of devices, owing to the
broken devices_kset.
I hi
On Fri, Jun 08, 2018 at 03:46:33PM +1000, Alexey Kardashevskiy wrote:
> At the moment we allocate the entire TCE table, twice (hardware part and
> userspace translation cache). This normally works as we normally have
> contigous memory and the guest will map entire RAM for 64bit DMA.
>
> However i
Hi Baoquan,
I love your patch! Perhaps something to improve:
[auto build test WARNING on linus/master]
[also build test WARNING on v4.17 next-20180608]
[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/co
On 12/06/18 06:29, Souptick Joarder wrote:
Use new return type vm_fault_t for fault handler. For
now, this is just documenting that the function returns
a VM_FAULT value rather than an errno. Once all instances
are converted, vm_fault_t will become a distinct type.
Ref-> commit 1c8f422059ae ("mm
Hi Baoquan,
I love your patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v4.17 next-20180608]
[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/commits/Ba
Hi Baoquan,
I love your patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v4.17 next-20180608]
[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/commits/Ba
On 06/12/18 at 11:28am, Baoquan He wrote:
> reparent_resources() is duplicated in arch/microblaze/pci/pci-common.c
> and arch/powerpc/kernel/pci-common.c, so move it to kernel/resource.c
> so that it's shared. Later its code also need be updated using list_head
> to replace singly linked list.
>
>
For kexec_file loading, if kexec_buf.top_down is 'true', the memory which
is used to load kernel/initrd/purgatory is supposed to be allocated from
top to down. This is what we have been doing all along in the old kexec
loading interface and the kexec loading is still default setting in some
distrib
This function, being a variant of walk_system_ram_res() introduced in
commit 8c86e70acead ("resource: provide new functions to walk through
resources"), walks through a list of all the resources of System RAM
in reversed order, i.e., from higher to lower.
It will be used in kexec_file code.
Signe
The struct resource uses singly linked list to link siblings, implemented
by pointer operation. Replace it with list_head for better code readability.
Based on this list_head replacement, it will be very easy to do reverse
iteration on iomem_resource's sibling list in later patch.
Besides, type o
reparent_resources() is duplicated in arch/microblaze/pci/pci-common.c
and arch/powerpc/kernel/pci-common.c, so move it to kernel/resource.c
so that it's shared. Later its code also need be updated using list_head
to replace singly linked list.
Signed-off-by: Baoquan He
Cc: Michal Simek
Cc: Benj
This patchset is doing:
1) Replace struct resource's sibling list from singly linked list to
list_head. Clearing out those pointer operation within singly linked
list for better code readability.
2) Based on list_head replacement, add a new function
walk_system_ram_res_rev() which can does reversed
Hi Diana,
> -Original Message-
> From: Diana Craciun [mailto:diana.crac...@nxp.com]
> Sent: Monday, June 11, 2018 6:23 PM
> To: linuxppc-dev@lists.ozlabs.org
> Cc: m...@ellerman.id.au; o...@buserror.net; Leo Li ;
> Bharat Bhushan ; Diana Madalina Craciun
>
> Subject: [PATCH v2 3/3] powerp
On Fri, Jun 08, 2018 at 03:46:32PM +1000, Alexey Kardashevskiy wrote:
> This moves actual pages allocation to a separate function which is going
> to be reused later in on-demand TCE allocation.
>
> While we are at it, remove unnecessary level size round up as the caller
> does this already.
>
>
On Fri, Jun 08, 2018 at 03:46:31PM +1000, Alexey Kardashevskiy wrote:
> We want to support sparse memory and therefore huge chunks of DMA windows
> do not need to be mapped. If a DMA window big enough to require 2 or more
> indirect levels, and a DMA window is used to map all RAM (which is
> a defa
Hi all,
Building Linus' tree, today's linux-next build (powerpc allyesconfig)
failed like this:
ld: net/bpfilter/bpfilter_umh.o: compiled for a little endian system and target
is big endian
ld: failed to merge target specific data of file net/bpfilter/bpfilter_umh.o
This has come to light since
On Sun, 10 Jun 2018, Benjamin Herrenschmidt wrote:
> Pre-PCI is basically "NUBUS" based even in absence of an actual NuBus
> slot :-) It has to do with the internal HW architecture. The only ones
> that aren't are the even older designs (the 68000 based ones).
>
There is already some disagreem
Hi all,
Building Linus' tree, today's linux-next build (powerpc ppc64_defconfig)
produced these warning:
ld: warning: orphan section `.gnu.hash' from `linker stubs' being placed in
section `.gnu.hash'.
ld: warning: orphan section `.gnu.hash' from `linker stubs' being placed in
section `.gnu.has
Use new return type vm_fault_t for fault handler. For
now, this is just documenting that the function returns
a VM_FAULT value rather than an errno. Once all instances
are converted, vm_fault_t will become a distinct type.
Ref-> commit 1c8f422059ae ("mm: change return type to vm_fault_t")
There i
Hi Meelis,
On Mon, Jun 11, 2018 at 1:21 PM Meelis Roos wrote:
>
> I am seeing this on PowerMac G4 with sungem ethernet driver. 4.17 was
> OK, 4.17.0-10146-gf0dc7f9c6dd9 is problematic.
Same here.
> [ 140.518664] eth0: hw csum failure
> [ 140.518699] CPU: 0 PID: 1237 Comm: postconf Not tainted
On Mon, Jun 11, 2018 at 07:29:33PM +0200, Florian Weimer wrote:
> On 06/11/2018 07:23 PM, Ram Pai wrote:
> >On Fri, Jun 08, 2018 at 07:53:51AM +0200, Florian Weimer wrote:
> >>On 06/08/2018 04:34 AM, Ram Pai wrote:
>
> So the remaining question at this point is whether the Intel
> beha
On Thu, Jun 07, 2018 at 05:20:43PM +0800, Yangbo Lu wrote:
> This patch is to add bindings description for DPAA
> FMan 1588 timer, and also remove its description in
> fsl-fman dt-bindings document.
>
> Signed-off-by: Yangbo Lu
> ---
> Changes for v2:
> - None.
> Changes for v3:
> - N
On 06/11/2018 07:23 PM, Ram Pai wrote:
On Fri, Jun 08, 2018 at 07:53:51AM +0200, Florian Weimer wrote:
On 06/08/2018 04:34 AM, Ram Pai wrote:
So the remaining question at this point is whether the Intel
behavior (default-deny instead of default-allow) is preferable.
Florian, remind me what b
On Fri, Jun 08, 2018 at 07:53:51AM +0200, Florian Weimer wrote:
> On 06/08/2018 04:34 AM, Ram Pai wrote:
> >>
> >>So the remaining question at this point is whether the Intel
> >>behavior (default-deny instead of default-allow) is preferable.
> >
> >Florian, remind me what behavior needs to fixed?
Hi Haiyan,
I don't have access to the same hardware you ran the test on, but I give a try
to those test on a Power8 system (2 sockets, 5 cores/s, 8 threads/c, 80 CPUs
32G).
I run each will-it-scale test 10 times and compute the average.
test THP enabled4.17.0-rc4-mm1 spf
Signed-off-by: Diana Craciun
---
arch/powerpc/Kconfig | 2 +-
arch/powerpc/kernel/security.c | 15 +++
2 files changed, 16 insertions(+), 1 deletion(-)
diff --git a/arch/powerpc/Kconfig b/arch/powerpc/Kconfig
index 940c955..a781d60 100644
--- a/arch/powerpc/Kconfig
+++ b/a
Implement the barrier_nospec as a isync;sync instruction sequence.
The implementation uses the infrastructure built for BOOK3S 64.
Signed-off-by: Diana Craciun
---
arch/powerpc/include/asm/barrier.h | 10 ++
arch/powerpc/include/asm/setup.h | 2 +-
arch/powerpc/kernel/Makefile |
Implement barrier_nospec for NXP PowerPC Book3E processors.
Diana Craciun (3):
Disable the speculation barrier from the command line
Add barrier_nospec implementation for NXP PowerPC Book3E
Implement cpu_show_spectre_v1/v2 for NXP PowerPC Book3E
arch/powerpc/Kconfig | 2 +-
The speculation barrier can be disabled from the command line
with the parameter: "nospectre_v1".
Signed-off-by: Diana Craciun
---
arch/powerpc/kernel/security.c | 12 +++-
1 file changed, 11 insertions(+), 1 deletion(-)
diff --git a/arch/powerpc/kernel/security.c b/arch/powerpc/kernel/
I am seeing this on PowerMac G4 with sungem ethernet driver. 4.17 was
OK, 4.17.0-10146-gf0dc7f9c6dd9 is problematic.
[ 140.518664] eth0: hw csum failure
[ 140.518699] CPU: 0 PID: 1237 Comm: postconf Not tainted
4.17.0-10146-gf0dc7f9c6dd9 #83
[ 140.518707] Call Trace:
[ 140.518734] [effefd90]
Hi Laurent,
Regression test for v11 patch serials have been run, some regression is found
by LKP-tools (linux kernel performance)
tested on Intel 4s skylake platform. This time only test the cases which have
been run and found regressions on
V9 patch serials.
The regression result is sorted by
33 matches
Mail list logo
