On 10/04/2017 08:59 PM, Pavel Tatashin wrote:
> This patch fixes another existing issue on systems that have holes in
> zones i.e CONFIG_HOLES_IN_ZONE is defined.
>
> In for_each_mem_pfn_range() we have code like this:
>
> if (!pfn_valid_within(pfn)
> goto free_range;
>
> Note: 'page' is n
Use the NMI IPI rather than smp_call_function for smp_send_stop.
Have stopped CPUs hard disable interrupts rather than just soft
disable.
This function is used in crash/panic/shutdown paths to bring other
CPUs down as quickly and reliably as possible, and minimizing their
potential to cause troubl
Currently powernv reboot and shutdown requests just leave secondaries
to do their own things. This is undesirable because they can trigger
any number of watchdogs while waiting for reboot, but also we don't
know what else they might be doing, or they might be stuck somewhere
causing trouble.
The o
OPAL boot does not insert secondaries at 0x60 to wait at the secondary
hold spinloop. Instead it keeps them held in firmware until the
opal_start_cpu call is made, which directs them where the caller
specifies. Linux inserts them into generic_secondary_smp_init(), which
is after the secondary hold
Hi,
These are a couple of improvements to powernv/opal boot and
shutdown paths. Also a patch to move smp_send_stop over to
use NMI IPIs, which gives us a significantly better chance to
stop secondaries on platforms which support it (pSeries and
PowerNV POWER9 so far).
Patch 1 in particular it wou
On Thursday 05 October 2017 06:13 PM, Torsten Duwe wrote:
On Wed, Oct 04, 2017 at 11:25:16AM -0400, Kamalesh Babulal wrote:
Both the failures with REL24 livepatch symbols relocation, can be
resolved by constructing a new livepatch stub. The newly setup klp_stub
mimics the functionality of entry
On Thursday 05 October 2017 06:13 PM, Torsten Duwe wrote:
On Wed, Oct 04, 2017 at 11:25:16AM -0400, Kamalesh Babulal wrote:
Both the failures with REL24 livepatch symbols relocation, can be
resolved by constructing a new livepatch stub. The newly setup klp_stub
mimics the functionality of entry
Nathan Fontenot writes:
> On 10/04/2017 03:21 PM, Daniel Henrique Barboza wrote:
...
>> It appears that the hot unplug is failing because lmb_is_removable(lmb) is
>> returning
>> false inside dlpar_remove_lmb, triggering the hotplug of the LMBs again:
...
>>
>> I am not aware of anything that I
Michael Neuling writes:
> Each POWER9 core is made of two super slices. Each super slice can
> only have one thread at a time in TM suspend mode. The super slice
> restricts ever entering a state where both threads are in suspend by
> aborting transactions on tsuspend or exceptions into the kerne
On Thu, 2017-10-05 at 22:29 +0200, Michal Suchánek wrote:
> I do not expect the kernel to generate a
> stack trace every time memory allocation fails. With all the hooks in
> the code it is hard to tell, though.
All [kv].alloc failures without __GFP_NOWARN call dump_stack()
On 27/09/17 16:52, Alexey Kardashevskiy wrote:
> In order to make generic IOV code work, the physical function IOV BAR
> should start from offset of the first VF. Since M64 segments share
> PE number space across PHB, and some PEs may be in use at the time
> when IOV is enabled, the existing code s
> > This patch blocks this from happening on POWER9 but sanity checking
> > sigcontexts passed in.
>
> Should 'but' say 'by'?
Thanks
Mikey
Abdul Haleem writes:
> Hi,
>
> linux-next kernel panic while DLPAR CPU add/remove operation in a loop.
>
> Test: CPU hot-unplug
> Machine Type: Power8 PowerVM LPAR
> kernel: 4.14.0-rc2-next-20170928
> gcc : 5.2.1
>
> trace logs
> --
> cpu 10 (hwid 10) Ready to die...
> cpu 11 (hwid 11) Re
Paste on POWER9 only works on accelerators and no longer on real
memory. Hence this test is broken so remove it.
Signed-off-by: Michael Neuling
---
tools/testing/selftests/powerpc/Makefile | 1 -
.../selftests/powerpc/context_switch/.gitignore| 1 -
.../selftests/powerpc/contex
On Wed, Oct 04, 2017 at 08:50:49AM +0200, Laurent Dufour wrote:
> On 25/09/2017 18:27, Alexei Starovoitov wrote:
> > On Mon, Sep 18, 2017 at 12:15 AM, Laurent Dufour
> > wrote:
> >> Despite the unprovable lockdep warning raised by Sergey, I didn't get any
> >> feedback on this series.
> >>
> >> Is
Kees Cook writes:
> On Thu, Oct 5, 2017 at 10:21 AM, Abdul Haleem
> wrote:
>> Hi,
>>
>> CPU off on in a loop for single cpu results in kernel panic for
>> 4.14.0-rc2-next-20170929
>>
>> Machine: Power 8 PowerVM LPAR
>> Kernel: 4.14.0-rc2-next-20170929
>> gcc: 5.1.1
>> config : attached
>>
>> Ste
On Thu, 5 Oct 2017 22:19:15 + (UTC)
Mathieu Desnoyers wrote:
> AFAIU the scheduler rq->lock is held while preemption is disabled.
> synchronize_sched() is used here to ensure that all pre-existing
> preempt-off critical sections have completed.
>
> So saying that we use synchronize_sched() t
Architectures without membarrier hooks don't need to emit the
empty membarrier_arch_switch_mm() static inline when
CONFIG_MEMBARRIER=y.
Adapt the CONFIG_MEMBARRIER=n counterpart to only emit the empty
membarrier_arch_switch_mm() for architectures with membarrier hooks.
Reported-by: Nicholas Piggi
Threads targeting the same VM but which belong to different thread
groups is a tricky case. It has a few consequences:
It turns out that we cannot rely on get_nr_threads(p) to count the
number of threads using a VM. We can use
(atomic_read(&mm->mm_users) == 1 && get_nr_threads(p) == 1)
instead to
- On Oct 5, 2017, at 5:40 PM, Mathieu Desnoyers
mathieu.desnoy...@efficios.com wrote:
> Threads targeting the same VM but which belong to different thread
> groups is a tricky case. It has a few consequences:
>
> It turns out that we cannot rely on get_nr_threads(p) to count the
> number of
On Fri, Oct 6, 2017 at 6:03 AM, Kees Cook wrote:
> When available, CONFIG_KERNEL_RWX should be default-enabled for PPC64.
> On PPC32, there is a performance trade-off.
>
> Cc: Benjamin Herrenschmidt
> Cc: Paul Mackerras
> Cc: Michael Ellerman
> Cc: Christophe LEROY
> Cc: Balbir Singh
> Cc: li
- On Oct 5, 2017, at 6:02 PM, Andrea Parri parri.and...@gmail.com wrote:
> On Thu, Oct 05, 2017 at 04:02:06PM +, Mathieu Desnoyers wrote:
>> - On Oct 5, 2017, at 8:12 AM, Peter Zijlstra pet...@infradead.org wrote:
>>
>> > On Wed, Oct 04, 2017 at 02:37:53PM -0700, Paul E. McKenney wrot
- On Oct 5, 2017, at 12:21 PM, Peter Zijlstra pet...@infradead.org wrote:
> On Thu, Oct 05, 2017 at 04:02:06PM +, Mathieu Desnoyers wrote:
>> - On Oct 5, 2017, at 8:12 AM, Peter Zijlstra pet...@infradead.org wrote:
>>
>> > On Wed, Oct 04, 2017 at 02:37:53PM -0700, Paul E. McKenney wro
Threads targeting the same VM but which belong to different thread
groups is a tricky case. It has a few consequences:
It turns out that we cannot rely on get_nr_threads(p) to count the
number of threads using a VM. We can use
(atomic_read(&mm->mm_users) == 1 && get_nr_threads(p) == 1)
instead to
Architectures without membarrier hooks don't need to emit the
empty membarrier_arch_switch_mm() static inline when
CONFIG_MEMBARRIER=y.
Adapt the CONFIG_MEMBARRIER=n counterpart to only emit the empty
membarrier_arch_switch_mm() for architectures with membarrier hooks.
Reported-by: Nicholas Piggi
On Thu, Oct 5, 2017 at 2:25 PM, Michael Neuling wrote:
> Each POWER9 core is made of two super slices. Each super slice can
> only have one thread at a time in TM suspend mode. The super slice
> restricts ever entering a state where both threads are in suspend by
> aborting transactions on tsuspen
Add an optimized mm_zero_struct_page(), so struct page's are zeroed without
calling memset(). We do eight to ten regular stores based on the size of
struct page. Compiler optimizes out the conditions of switch() statement.
SPARC-M6 with 15T of memory, single thread performance:
To optimize the performance of struct page initialization,
vmemmap_populate() will no longer zero memory.
Therefore, we must use a new interface to allocate and map kasan shadow
memory, that also zeroes memory for us.
Signed-off-by: Pavel Tatashin
---
arch/arm64/mm/kasan_init.c | 12 ++-
During early boot, kasan uses vmemmap_populate() to establish its shadow
memory. But, that interface is intended for struct pages use.
Because of the current project, vmemmap won't be zeroed during allocation,
but kasan expects that memory to be zeroed. We are adding a new
kasan_map_populate() fun
* A new variant of memblock_virt_alloc_* allocations:
memblock_virt_alloc_try_nid_raw()
- Does not zero the allocated memory
- Does not panic if request cannot be satisfied
* optimize early system hash allocations
Clients can call alloc_large_system_hash() with flag: HASH_ZERO to specify
vmemmap_alloc_block() will no longer zero the block, so zero memory
at its call sites for everything except struct pages. Struct page memory
is zero'd by struct page initialization.
Replace allocators in sprase-vmemmap to use the non-zeroing version. So,
we will get the performance improvement by
Without deferred struct page feature (CONFIG_DEFERRED_STRUCT_PAGE_INIT),
flags and other fields in "struct page"es are never changed prior to first
initializing struct pages by going through __init_single_page().
With deferred struct page feature enabled there is a case where we set some
fields pr
To optimize the performance of struct page initialization,
vmemmap_populate() will no longer zero memory.
Therefore, we must use a new interface to allocate and map kasan shadow
memory, that also zeroes memory for us.
Signed-off-by: Pavel Tatashin
---
arch/x86/mm/kasan_init_64.c | 8
1
Some memory is reserved but unavailable: not present in memblock.memory
(because not backed by physical pages), but present in memblock.reserved.
Such memory has backing struct pages, but they are not initialized by going
through __init_single_page().
In some cases these struct pages are accessed
Remove duplicating code by using common functions
vmemmap_pud_populate and vmemmap_pgd_populate.
Signed-off-by: Pavel Tatashin
Reviewed-by: Steven Sistare
Reviewed-by: Daniel Jordan
Reviewed-by: Bob Picco
Acked-by: David S. Miller
Acked-by: Michal Hocko
---
arch/sparc/mm/init_64.c | 23
Changelog:
v10 - v9
- Addressed new comments from Michal Hocko.
- Sent "mm: deferred_init_memmap improvements" as a separate patch as
it is also fixing existing problem.
- Merged "mm: stop zeroing memory during allocation in vmemmap" with
"mm: zero struct pages during initialization".
- Added m
Without deferred struct page feature (CONFIG_DEFERRED_STRUCT_PAGE_INIT),
flags and other fields in "struct page"es are never changed prior to first
initializing struct pages by going through __init_single_page().
With deferred struct page feature enabled, however, we set fields in
register_page_bo
On Thu, 5 Oct 2017, Bjorn Helgaas wrote:
> From: Bjorn Helgaas
>
> Remove these unused declarations:
>
> pcibios_config_init() # never defined anywhere
> pcibios_scan_root()# only defined by x86
> pcibios_get_irq_routing_table()# only defined by x86
> pc
On Thu, 5 Oct 2017, Bjorn Helgaas wrote:
> From: Bjorn Helgaas
>
> All users of pcibios_set_master() include , which already has
> a declaration. Remove the unnecessary declarations from the
> files.
>
> Signed-off-by: Bjorn Helgaas
Reviewed-by: Thomas Gleixner
From: Markus Elfring
Date: Thu, 5 Oct 2017 22:40:39 +0200
Replace the specification of data structures by pointer dereferences
as the parameter for the operator "sizeof" to make the corresponding size
determination a bit safer according to the Linux coding style convention.
This issue was detect
From: Markus Elfring
Date: Thu, 5 Oct 2017 22:30:29 +0200
Omit an extra message for a memory allocation failure in this function.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
arch/powerpc/platforms/powermac/low_i2c.c | 5 +
1 file changed, 1
From: Markus Elfring
Date: Thu, 5 Oct 2017 22:48:22 +0200
Two update suggestions were taken into account
from static source code analysis.
Markus Elfring (2):
Delete an error message for a failed memory allocation in kw_i2c_host_init()
Improve a size determination in five functions
arch/po
From: Bjorn Helgaas
pdev_save_srm_config() and struct pdev_srm_saved_conf are only used in
arch/alpha/kernel/pci.c, so make them static there.
Signed-off-by: Bjorn Helgaas
---
arch/alpha/kernel/pci.c | 11 ++-
arch/alpha/kernel/pci_impl.h |8
2 files changed, 10 ins
From: Bjorn Helgaas
Remove these unused declarations:
pcibios_config_init() # never defined anywhere
pcibios_scan_root()# only defined by x86
pcibios_get_irq_routing_table()# only defined by x86
pcibios_set_irq_routing() # only defined by x86
Si
From: Bjorn Helgaas
defines struct pci_bus and struct pci_dev and includes the
struct resource definition before including . Nobody includes
directly, so they don't need their own declarations.
Remove the redundant struct pci_dev, pci_bus, resource declarations.
Signed-off-by: Bjorn Helgaas
From: Bjorn Helgaas
All users of pcibios_set_master() include , which already has
a declaration. Remove the unnecessary declarations from the
files.
Signed-off-by: Bjorn Helgaas
---
arch/alpha/include/asm/pci.h |2 --
arch/cris/include/asm/pci.h|1 -
arch/frv/include/asm/pci.h
Sorry for the long cc list. These are pretty trivial; they just remove
some unnecessary declarations across several arches.
---
Bjorn Helgaas (4):
PCI: Remove redundant pcibios_set_master() declarations
PCI: Remove redundant pci_dev, pci_bus, resource declarations
PCI: Remove u
On Thu, 5 Oct 2017 22:06:11 +0200 (CEST)
Julia Lawall wrote:
> On Thu, 5 Oct 2017, Michal Suchánek wrote:
>
> > Hello,
> >
> > On Thu, 5 Oct 2017 21:36:26 +0200
> > SF Markus Elfring wrote:
> >
> > > From: Markus Elfring
> > > Date: Thu, 5 Oct 2017 21:04:30 +0200
> > >
> > > Omit extra messa
On Thu, 5 Oct 2017, Michal Suchánek wrote:
> Hello,
>
> On Thu, 5 Oct 2017 21:36:26 +0200
> SF Markus Elfring wrote:
>
> > From: Markus Elfring
> > Date: Thu, 5 Oct 2017 21:04:30 +0200
> >
> > Omit extra messages for a memory allocation failure in these
> > functions.
>
> this is bogus. All th
Hello,
On Thu, 5 Oct 2017 21:36:26 +0200
SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Thu, 5 Oct 2017 21:04:30 +0200
>
> Omit extra messages for a memory allocation failure in these
> functions.
this is bogus. All these functions return -1 on any error. Until they
reflect the error
From: Markus Elfring
Date: Thu, 5 Oct 2017 21:12:41 +0200
Replace the specification of data structures by pointer dereferences
as the parameter for the operator "sizeof" to make the corresponding size
determination a bit safer according to the Linux coding style convention.
This issue was detect
From: Markus Elfring
Date: Thu, 5 Oct 2017 21:04:30 +0200
Omit extra messages for a memory allocation failure in these functions.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
arch/powerpc/platforms/cell/axon_msi.c | 5 +
arch/powerpc/platfo
From: Markus Elfring
Date: Thu, 5 Oct 2017 21:25:43 +0200
Two update suggestions were taken into account
from static source code analysis.
Markus Elfring (2):
Delete an error message for a failed memory allocation in three functions
Improve a size determination in three functions
arch/powe
Thanks, Markus.
SF Markus Elfring writes:
> From: Markus Elfring
> Date: Thu, 5 Oct 2017 18:02:05 +0200
>
> Omit an extra message for a memory allocation failure in this function.
>
> This issue was detected by using the Coccinelle software.
>
> Signed-off-by: Markus Elfring
> ---
> arch/pow
On Thu, Oct 5, 2017 at 10:21 AM, Abdul Haleem
wrote:
> Hi,
>
> CPU off on in a loop for single cpu results in kernel panic for
> 4.14.0-rc2-next-20170929
>
> Machine: Power 8 PowerVM LPAR
> Kernel: 4.14.0-rc2-next-20170929
> gcc: 5.1.1
> config : attached
>
> Steps to recreate:
> -
When available, CONFIG_KERNEL_RWX should be default-enabled for PPC64.
On PPC32, there is a performance trade-off.
Cc: Benjamin Herrenschmidt
Cc: Paul Mackerras
Cc: Michael Ellerman
Cc: Christophe LEROY
Cc: Balbir Singh
Cc: linuxppc-dev@lists.ozlabs.org
Signed-off-by: Kees Cook
---
v2:
- dep
On Thu, Oct 5, 2017 at 11:57 AM, christophe leroy
wrote:
>
>
> Le 05/10/2017 à 19:30, Kees Cook a écrit :
>>
>> On Thu, Oct 5, 2017 at 12:49 AM, Christophe LEROY
>> wrote:
>>>
>>>
>>>
>>> Le 05/10/2017 à 05:45, Kees Cook a écrit :
When available, CONFIG_KERNEL_RWX should be default
Le 05/10/2017 à 19:30, Kees Cook a écrit :
On Thu, Oct 5, 2017 at 12:49 AM, Christophe LEROY
wrote:
Le 05/10/2017 à 05:45, Kees Cook a écrit :
When available, CONFIG_KERNEL_RWX should be default-enabled.
On PPC32, this option implies deactivating BATs and/or LTLB mapping of the
linear
Thiago,
On Thu, 5 Oct 2017, Thiago Jung Bauermann wrote:
> Thomas Gleixner writes:
> It doesn't look like powerpc uses arch_update_cpu_topology differently
> than other arches. Are you saying that all callers of the function
> should be holding cpu_hotplug_lock?
No. I didn't check as I was lazy
Hello Thomas,
Thanks for your comments.
Thomas Gleixner writes:
> On Wed, 4 Oct 2017, Thiago Jung Bauermann wrote:
>
>> It turns out that not all paths calling arch_update_cpu_topology hold
>> cpu_hotplug_lock, but that's ok because those paths aren't supposed to race
>> with any concurrent ho
On Thu, Oct 5, 2017 at 12:49 AM, Christophe LEROY
wrote:
>
>
> Le 05/10/2017 à 05:45, Kees Cook a écrit :
>>
>> When available, CONFIG_KERNEL_RWX should be default-enabled.
>
>
> On PPC32, this option implies deactivating BATs and/or LTLB mapping of the
> linear kernel address space, hence a signi
On Thu, Oct 05, 2017 at 04:02:06PM +, Mathieu Desnoyers wrote:
> - On Oct 5, 2017, at 8:12 AM, Peter Zijlstra pet...@infradead.org wrote:
>
> > On Wed, Oct 04, 2017 at 02:37:53PM -0700, Paul E. McKenney wrote:
> >> diff --git a/arch/powerpc/kernel/membarrier.c
> >> b/arch/powerpc/kernel/m
On Tue, Oct 03, 2017 at 07:27:01PM +, Thomas Gleixner wrote:
> On Tue, 3 Oct 2017, Thomas Gleixner wrote:
> > On Tue, 3 Oct 2017, Thomas Gleixner wrote:
> > > On Tue, 3 Oct 2017, Michael Ellerman wrote:
> > > > Hmm, I tried that patch, it makes the warning go away. But then I
> > > > triggered
From: Markus Elfring
Date: Thu, 5 Oct 2017 18:02:05 +0200
Omit an extra message for a memory allocation failure in this function.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
arch/powerpc/perf/hv-24x7.c | 1 -
1 file changed, 1 deletion(-)
diff
- On Oct 5, 2017, at 8:24 AM, Peter Zijlstra pet...@infradead.org wrote:
> On Thu, Oct 05, 2017 at 02:12:50PM +0200, Peter Zijlstra wrote:
>> On Wed, Oct 04, 2017 at 02:37:53PM -0700, Paul E. McKenney wrote:
>> > diff --git a/arch/powerpc/kernel/membarrier.c
>> > b/arch/powerpc/kernel/membar
- On Oct 5, 2017, at 8:12 AM, Peter Zijlstra pet...@infradead.org wrote:
> On Wed, Oct 04, 2017 at 02:37:53PM -0700, Paul E. McKenney wrote:
>> diff --git a/arch/powerpc/kernel/membarrier.c
>> b/arch/powerpc/kernel/membarrier.c
>> new file mode 100644
>> index ..b0d79a5f5981
>> --
- On Oct 5, 2017, at 8:22 AM, Avi Kivity a...@scylladb.com wrote:
> On 10/05/2017 07:23 AM, Nicholas Piggin wrote:
>> On Wed, 4 Oct 2017 14:37:53 -0700
>> "Paul E. McKenney" wrote:
>>
>>> From: Mathieu Desnoyers
>>>
>>> Provide a new command allowing processes to register their intent to us
- On Oct 5, 2017, at 12:23 AM, Nicholas Piggin npig...@gmail.com wrote:
> On Wed, 4 Oct 2017 14:37:53 -0700
> "Paul E. McKenney" wrote:
>
>> From: Mathieu Desnoyers
>>
>> Provide a new command allowing processes to register their intent to use
>> the private expedited command.
>>
>> This
On 10/04/2017 03:21 PM, Daniel Henrique Barboza wrote:
> Hi,
>
> I've stumbled in a LMB hot unplug problem when running a guest with 4.13+
> kernel using QEMU 2.10. When trying to hot unplug a recently hotplugged LMB
> this is what I got, using an upstream kernel:
>
> ---
> QEMU cmd
From: Markus Elfring
Date: Thu, 5 Oct 2017 17:18:33 +0200
Replace the specification of data structures by pointer dereferences
as the parameter for the operator "sizeof" to make the corresponding size
determination a bit safer according to the Linux coding style convention.
This issue was detect
From: Markus Elfring
Date: Thu, 5 Oct 2017 17:10:11 +0200
Omit extra messages for a memory allocation failure in these functions.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
arch/powerpc/oprofile/cell/spu_task_sync.c | 8
arch/powerpc/o
From: Markus Elfring
Date: Thu, 5 Oct 2017 17:32:10 +0200
Two update suggestions were taken into account
from static source code analysis.
Markus Elfring (2):
Delete an error message for a failed memory allocation in three functions
Improve a size determination in two functions
arch/powerp
On Thu, Oct 5, 2017 at 1:26 AM, Kees Cook wrote:
> Remove uses of init_timer_on_stack() with open-coded function and data
> assignments that could be expressed using timer_setup_on_stack(). Several
> were removed from the stack entirely since there was a one-to-one mapping
> of parent structure to
On Wed, Oct 04, 2017 at 11:25:16AM -0400, Kamalesh Babulal wrote:
>
> Both the failures with REL24 livepatch symbols relocation, can be
> resolved by constructing a new livepatch stub. The newly setup klp_stub
> mimics the functionality of entry_64.S::livepatch_handler introduced by
> commit 85baa
On Wed, 4 Oct 2017, Thiago Jung Bauermann wrote:
> It turns out that not all paths calling arch_update_cpu_topology hold
> cpu_hotplug_lock, but that's ok because those paths aren't supposed to race
> with any concurrent hotplug events.
>
> Callers of arch_update_cpu_topology are expected to know
On Thu, Oct 05, 2017 at 02:12:50PM +0200, Peter Zijlstra wrote:
> On Wed, Oct 04, 2017 at 02:37:53PM -0700, Paul E. McKenney wrote:
> > diff --git a/arch/powerpc/kernel/membarrier.c
> > b/arch/powerpc/kernel/membarrier.c
> > new file mode 100644
> > index ..b0d79a5f5981
> > --- /dev/nu
On Wed, Oct 04, 2017 at 02:37:53PM -0700, Paul E. McKenney wrote:
> diff --git a/arch/powerpc/kernel/membarrier.c
> b/arch/powerpc/kernel/membarrier.c
> new file mode 100644
> index ..b0d79a5f5981
> --- /dev/null
> +++ b/arch/powerpc/kernel/membarrier.c
> @@ -0,0 +1,45 @@
> +void memb
I get these warnings:
../arch/powerpc/boot/mpsc.c: In function 'mpsc_get_virtreg_of_phandle':
../arch/powerpc/boot/mpsc.c:113:35: warning: cast from pointer to
integer of different size [-Wpointer-to-int-cast]
../arch/powerpc/boot/mpsc.c: In function 'mpsc_console_init':
../arch/powerpc/boot/mpsc
From: Markus Elfring
Date: Thu, 5 Oct 2017 13:16:51 +0200
Omit an extra message for a memory allocation failure in this function.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
arch/powerpc/kvm/book3s_64_mmu_hv.c | 1 -
1 file changed, 1 deletion(-
Hi Santosh,
On Thursday 05 October 2017 03:20 PM, Santosh Sivaraj wrote:
* Anju T Sudhakar wrote (on 2017-10-04 06:50:52
+):
Nest/core pmu units are enabled only when it is used. A reference count is
maintained for the events which uses the nest/core pmu units. Currently in
*_imc_counte
* Anju T Sudhakar wrote (on 2017-10-04 06:50:52
+):
> Nest/core pmu units are enabled only when it is used. A reference count is
>
> maintained for the events which uses the nest/core pmu units. Currently in
>
> *_imc_counters_release function a WARN() is used for notification
* Madhavan Srinivasan wrote (on 2017-10-03 12:25:15
+):
> Most of the power processor generation performance monitoring
> unit (PMU) driver code is bundled in the kernel and one of those
> is enabled/registered based on the oprofile_cpu_type check at
> the boot.
>
> But things get little tr
>>> I haven't yet because I fail to understand why the decrementer is not
>>> interrupting the dying CPU under xics as it is the case under XIVE.
>>
>> Oh.. ok. This sounds very similar to the problem Nikunj hit under TCG
>> with decrementer interrupts waking up a supposedly dead CPU. He had a
>
On Thu, Oct 5, 2017 at 1:27 AM, Kees Cook wrote:
> Drop the arguments from the macro and adjust all callers with the
> following script:
>
> perl -pi -e 's/DEFINE_TIMER\((.*), 0, 0\);/DEFINE_TIMER($1);/g;' \
> $(git grep DEFINE_TIMER | cut -d: -f1 | sort -u | grep -v timer.h)
>
> Signed-off-
Le 05/10/2017 à 05:45, Kees Cook a écrit :
When available, CONFIG_KERNEL_RWX should be default-enabled.
On PPC32, this option implies deactivating BATs and/or LTLB mapping of
the linear kernel address space, hence a significant performance
degradation.
So at least on PPC32, it should rema
85 matches
Mail list logo
