Re: [PATCH] powerpc: Build fix for non SPARSEMEM_VMEMAP config

"Aneesh Kumar K.V" writes: > On Wednesday 28 June 2017 12:48 PM, Alexey Kardashevskiy wrote: >> On 28/06/17 16:09, Aneesh Kumar K.V wrote: >>> We can use pfn_to_page in realmode for other configs. Hence remove the >>> CONFIG_FLATMEM ifdef >> >> For

[PATCH] net: ibm: ibmveth: constify dev_pm_ops structures.

dev_pm_ops are not supposed to change at runtime. All functions working with dev_pm_ops provided by work with const dev_pm_ops. So mark the non-const structs as const. File size before: textdata bss dec hex filename 154261256 0 16682412a

Re: [PATCH] powerpc: remapping too much memory

Dan Carpenter writes: > There is a cut and paste error here so we use "sizeof(struct mpc83xx_pmc)" > to remap the memory for "clock_regs". That sizeof() is 20 bytes and we > only need to remap 12 bytes. It presumably doesn't affect run time too > much... I don't know

Re: [PATCH] powerpc/powernv: Tell OPAL about our MMU mode

Benjamin Herrenschmidt writes: > On Wed, 2017-06-28 at 15:17 +1000, Michael Ellerman wrote: >> Which doesn't really make sense. FSP says it's running (runtime). >> >> The end of the OPAL log is below. >> >> I think your patch means we're now calling slw_reinit(),

Re: [PATCH 0/8] Support for 24x7 hcall interface version 2

Thiago Jung Bauermann writes: > Michael Ellerman writes: >> Thiago Jung Bauermann writes: >>> The hypervisor interface to access 24x7 performance counters (which collect >>> performance information from system power

Re: [v4.12-rc1 regression] mount ext4 fs results in kernel crash on PPC64le host

Hi Eryu, Thanks for the bug report. Eryu Guan writes: > Hi all, > > Li Wang and I are constantly seeing ppc64le hosts crashing due to bad I'm curious why you're seeing this and not other folks. What compiler are you using? > page access. But it's not reproducing on every

Re: [v4.12-rc1 regression] mount ext4 fs results in kernel crash on PPC64le host

On Thu, Jun 29, 2017 at 03:16:10AM +1000, Balbir Singh wrote: > On Wed, Jun 28, 2017 at 6:32 PM, Eryu Guan wrote: > > Hi all, > > > > Li Wang and I are constantly seeing ppc64le hosts crashing due to bad > > page access. But it's not reproducing on every ppc64le host we've > >

Re: [PATCH 2/2] selftests/ftrace: Update multiple kprobes test for powerpc

On Thu, 29 Jun 2017 00:13:24 +0530 "Naveen N. Rao" wrote: > On 2017/06/28 11:16PM, Masami Hiramatsu wrote: > > > > diff --git > > > > a/tools/testing/selftests/ftrace/test.d/kprobe/kprobe_eventname.tc > > > >

[PATCH v2 8/8] powerpc/perf/hv-24x7: Aggregate result elements on POWER9 SMT8

On POWER9 SMT8 the 24x7 API returns two result elements for physical core and virtual CPU events and we need to add their counts to get the final result. Signed-off-by: Thiago Jung Bauermann --- arch/powerpc/perf/hv-24x7.c | 54

[PATCH v2 7/8] powerpc/perf/hv-24x7: Support v2 of the hypervisor API

POWER9 introduces a new version of the hypervisor API to access the 24x7 perf counters. The new version changed some of the structures used for requests and results. Signed-off-by: Thiago Jung Bauermann --- arch/powerpc/perf/hv-24x7.c| 132

[PATCH v2 6/8] powerpc/perf/hv-24x7: Minor improvements

There's an H24x7_DATA_BUFFER_SIZE constant, so use it in init_24x7_request. There's also an HV_PERF_DOMAIN_MAX constant, so use it in h_24x7_event_init. This makes the comment above the check redundant, so remove it. In add_event_to_24x7_request, a statement is terminated with a comma instead of

[PATCH v2 5/8] powerpc/perf/hv-24x7: Fix return value of hcalls

The H_GET_24X7_CATALOG_PAGE hcall can return a signed error code, so fix this in the code. The H_GET_24X7_DATA hcall can return a signed error code, so fix this in the code. Also, don't truncate it to 32 bit to use as return value for make_24x7_request. In case of error h_24x7_event_commit_txn

[PATCH v2 4/8] powerpc-perf/hx-24x7: Don't log failed hcall twice

make_24x7_request already calls log_24x7_hcall if it fails, so callers don't have to do it again. In fact, since the latter is now only called from the former, there's no need for a separate log_24x7_hcall anymore so remove it. Signed-off-by: Thiago Jung Bauermann

[PATCH v2 3/8] powerpc/perf/hv-24x7: Properly iterate through results

hv-24x7.h has a comment mentioning that result_buffer->results can't be indexed as a normal array because it may contain results of variable sizes, so fix the loop in h_24x7_event_commit_txn to take the variation into account when iterating through results. Another problem in that loop is that it

[PATCH v2 2/8] powerpc/perf/hv-24x7: Fix off-by-one error in request_buffer check

request_buffer can hold 254 requests, so if it already has that number of entries we can't add a new one. Also, define constant to show where the number comes from. Fixes: e3ee15dc5d19 ("powerpc/perf/hv-24x7: Define add_event_to_24x7_request()") Signed-off-by: Thiago Jung Bauermann

[PATCH v2 1/8] powerpc/perf/hv-24x7: Fix passing of catalog version number

H_GET_24X7_CATALOG_PAGE needs to be passed the version number obtained from the first catalog page obtained previously. This is a 64 bit number, but create_events_from_catalog truncates it to 32-bit. This worked on POWER8, but POWER9 actually uses the upper bits so the call fails with H_P3

[PATCH v2 0/8] Support for 24x7 hcall interface version 2

Hello, The hypervisor interface to access 24x7 performance counters (which collect performance information from system power on to system power off) has been extended in POWER9 adding new fields to the request and result element structures. Also, results for some domains now return more than one

Re: [PATCH 0/8] Support for 24x7 hcall interface version 2

Michael Ellerman writes: > Thiago Jung Bauermann writes: >> The hypervisor interface to access 24x7 performance counters (which collect >> performance information from system power on to system power off) has been >> extended in POWER9 adding

Re: linux-next: build failure after merge of the block tree

Hi Jens, On Wed, 28 Jun 2017 09:11:32 -0600 Jens Axboe wrote: > > On 06/28/2017 08:01 AM, Jens Axboe wrote: > > But put_user() is fine? Just checking here, since the change adds > > both a u64 put and get user. Yes, put_user is fine (it does 2 4 byte moves. The asm is there

Re: [PATCH v11 07/10] powerpc/perf: PMU functions for Core IMC and hotplugging

On Thu, 29 Jun 2017, Anju T Sudhakar wrote: > +static void cleanup_all_core_imc_memory(struct imc_pmu *pmu_ptr) > +{ > + struct imc_mem_info *ptr; > + > + for (ptr = pmu_ptr->mem_info; ptr; ptr++) { > + if (ptr->vbase[0]) > + free_pages((u64)ptr->vbase[0],

[PATCH v11 09/10] powerpc/perf: Thread IMC PMU functions

Code to add PMU functions required for event initialization, read, update, add, del etc. for thread IMC PMU. Thread IMC PMUs are used for per-task monitoring.

[PATCH v11 07/10] powerpc/perf: PMU functions for Core IMC and hotplugging

From: Madhavan Srinivasan Code to add PMU function to initialize a core IMC event. It also adds cpumask initialization function for core IMC PMU.

[PATCH v11 05/10] powerpc/perf: IMC pmu cpumask and cpuhotplug support

Adds cpumask attribute to be used by each IMC pmu. Only one cpu (any online CPU) from each chip for nest PMUs is designated to read counters. On CPU hotplug, dying CPU is checked to see whether it

[PATCH v11 10/10] powerpc/perf: Thread imc cpuhotplug support

Code to add support for thread IMC on cpuhotplug. When a cpu goes offline, the LDBAR for that cpu is disabled, and when it comes back online the previous ldbar value is written back to the LDBAR for that cpu. To register the hotplug functions for thread_imc, a new state

[PATCH v11 08/10] powerpc/powernv: Thread IMC events detection

Code to add support for detection of thread IMC events. It adds a new domain IMC_DOMAIN_THREAD and it is determined with the help of the "type" property in the imc device-tree. Signed-off-by: Anju T Sudhakar Signed-off-by: Hemant Kumar

[PATCH v11 06/10] powerpc/powernv: Core IMC events detection

From: Madhavan Srinivasan This patch adds support for detection of core IMC events along with the Nest IMC events. It adds a new domain IMC_DOMAIN_CORE and its determined with the help of the "type" property in the IMC device tree. Signed-off-by: Anju T Sudhakar

[PATCH v11 04/10] powerpc/perf: Add generic IMC pmu group and event functions

Device tree IMC driver code parses the IMC units and their events. It passes the information to IMC pmu code which is placed in powerpc/perf as "imc-pmu.c". Patch adds a set of generic imc pmu related event functions to be used by each imc pmu unit. Add code to setup format attribute and to

[PATCH v11 03/10] powerpc/powernv: Detect supported IMC units and its events

From: Madhavan Srinivasan Parse device tree to detect IMC units. Traverse through each IMC unit node to find supported events and corresponding unit/scale files (if any). The device tree for IMC counters starts at the node "imc-counters". This node contains all the IMC

[PATCH v11 02/10] powerpc/powernv: Autoload IMC device driver module

Code to create platform device for the IMC counters. Paltform devices are created based on the IMC compatibility string. New Config flag "CONFIG_HV_PERF_IMC_CTRS" add to contain the IMC counter changes. Signed-off-by: Anju T Sudhakar Signed-off-by: Hemant Kumar

[PATCH v11 01/10] powerpc/powernv: Data structure and macros definitions for IMC

From: Madhavan Srinivasan Create a new header file to add the data structures and macros needed for In-Memory Collection (IMC) counter support. Signed-off-by: Anju T Sudhakar Signed-off-by: Hemant Kumar

[PATCH v11 00/10] IMC Instrumentation Support

Power9 has In-Memory-Collection (IMC) infrastructure which contains various Performance Monitoring Units (PMUs) at Nest level (these are on-chip but off-core), Core level and Thread level. The Nest PMU counters are handled by a Nest IMC microcode which runs in the OCC (On-Chip Controller)

Re: [PATCH 2/2] selftests/ftrace: Update multiple kprobes test for powerpc

On 2017/06/28 11:16PM, Masami Hiramatsu wrote: > > > diff --git > > > a/tools/testing/selftests/ftrace/test.d/kprobe/kprobe_eventname.tc > > > b/tools/testing/selftests/ftrace/test.d/kprobe/kprobe_eventname.tc > > > new file mode 100644 > > > index 000..d259031 > > > --- /dev/null > > > +++

Re: [v4.12-rc1 regression] mount ext4 fs results in kernel crash on PPC64le host

On Wed, Jun 28, 2017 at 6:32 PM, Eryu Guan wrote: > Hi all, > > Li Wang and I are constantly seeing ppc64le hosts crashing due to bad > page access. But it's not reproducing on every ppc64le host we've > tested, but it usually happened in filesystem testings. > > [ 207.403459]

[PATCH 3/3] cxlflash: Update debug prints in reset handlers

The device and host reset handler contain debug prints to help identify the entities being reset. Today these reset handlers are based on a SCSI EH design that uses a SCSI command reference as a means of identifying the target entity. As such, the debug trace includes the SCSI command pointer and

[PATCH 2/3] cxlflash: Update send_tmf() parameters

The current send_tmf() implementation is based on the caller providing a SCSI command reference. In reality all that is needed is a SCSI device reference as the routine uses a private command. Refactor send_tmf() to pass the private adapter configuration reference and a SCSI device reference. As

[PATCH 1/3] cxlflash: Avoid double free of character device

The device_unregister() service used when cleaning up the character device is already responsible for the internal state associated with the device upon successful creation. As the cxlflash driver does not obtain a second reference to the character device, the explicit call to put_device() is not

[PATCH 0/3] cxlflash: Minor fix and EH refactoring

This small series fixes a recently injected double free and also includes two patches to refactor the host and reset handlers to ease the burden of making this driver compatible with an updated SCSI EH framework. This series is intended for 4.13 and is bisectable. Matthew R. Ochs (3):

[PATCH v5 7/7] powerpc/Kconfig: Enable STRICT_KERNEL_RWX

We have the basic support in the form of patching R/O text sections, linker scripts for extending alignment of text data. We've also got mark_rodata_ro() NOTE: There is a temporary work-around for disabling STRICT_KERNEL_RWX if CONFIG_HIBERNATION is enabled Signed-off-by: Balbir Singh

[PATCH v5 6/7] mm/radix: Fix permissions correctly for interrupt_vectors

Commit 9abcc98 introduced marking kernel text as executable, but missed some bits of the changes from hash_utils_64.c, where under CONFIG_RELOCATABLE with CONFIG_RELOCATABLE_TEST or a kdump kernel, if the size of the mapping was less than 1G, we end up marking the first page (address range

[PATCH v5 5/7] powerpc/mm/radix: Implement mark_rodata_ro() for radix

The patch splits the linear page mapping such that the ones with kernel text are mapped as 2M and others are mapped with the largest possible size - 1G. The downside of this is that we split a 1G mapping into 512 2M mappings for the kernel, but in the absence of that we cannot support R/O areas in

[PATCH v5 4/7] powerpc/mm/hash: Implement mark_rodata_ro() for hash

With hash we update the bolted pte to mark it read-only. We rely on the MMU_FTR_KERNEL_RO to generate the correct permissions for read-only text. The radix implementation just prints a warning in this implementation Signed-off-by: Balbir Singh ---

[PATCH v5 3/7] powerpc/platform/pseries/lpar: Fix updatepp and updateboltedpp

PAPR has pp0 in bit 55, currently we assumed that bit pp0 is bit 0 (all bits in IBM order). This patch fixes the pp0 bits for both these routines that use H_PROTECT. Fixes (e58e87a powerpc/mm: Update _PAGE_KERNEL_RO) Signed-off-by: Balbir Singh ---

[PATCH v5 2/7] powerpc/vmlinux.lds: Align __init_begin to 16M

For CONFIG_STRICT_KERNEL_RWX align __init_begin to 16M. We use 16M since its the larger of 2M on radix and 16M on hash for our linear mapping. The plan is to have .text, .rodata and everything upto __init_begin marked as RX. Note we still have executable read only data. We could further align

[PATCH v5 1/7] powerpc/lib/code-patching: Use alternate map for patch_instruction()

This patch creates the window using text_poke_area, allocated via get_vm_area(). text_poke_area is per CPU to avoid locking. text_poke_area for each cpu is setup using late_initcall, prior to setup of these alternate mapping areas, we continue to use direct write to change/modify kernel text. With

[PATCH v5 0/7] Provide STRICT_KERNEL_RWX for powerpc

Provide STRICT_KERNEL_RWX for PPC64/BOOK3S These patches enable RX mappings of kernel text. rodata is mapped RX as well as a trade-off, there are more details in the patch description As a prerequisite for R/O text, patch_instruction is moved over to using a separate mapping that allows write to

Re: [1/1] powerpc/traps : Updated MC for E6500 L1D cache err

Scott, On Sun, Apr 30, 2017 at 2:01 AM, Scott Wood wrote: > On Thu, Apr 27, 2017 at 12:59:40PM -0500, Matt Weber wrote: >> This patch updates the machine check handler of Linux kernel to >> handle the e6500 architecture case. In e6500 core, L1 Data Cache Write >> Shadow Mode

[PATCH v2] powerpc/traps : Updated MC for E6500 L1D cache err

This patch updates the machine check handler of Linux kernel to handle the e6500 architecture case. In e6500 core, L1 Data Cache Write Shadow Mode (DCWS) register is not implemented but L1 data cache always runs in write shadow mode. So, on L1 data cache parity errors, hardware will automatically

[PATCH v2] powerpc/powernv: Tell OPAL about our MMU mode

From: Benjamin Herrenschmidt That will allow OPAL to configure the CPU in an optimal way. Signed-off-by: Benjamin Herrenschmidt Signed-off-by: Michael Neuling --- v2: Always set the hash bit since we always need hash for

Re: linux-next: build failure after merge of the block tree

On 06/28/2017 08:01 AM, Jens Axboe wrote: > On 06/28/2017 06:43 AM, Jens Axboe wrote: >> On 06/28/2017 02:04 AM, Stephen Rothwell wrote: >>> Hi Jens, >>> >>> After merging the block tree, today's linux-next build (powerpc >>> allnoconfig) failed like this: >>> >>> fs/fcntl.o: In function

[RFC PATCH] powerpc: allow compiling with GENERIC_MSI_IRQ

From: Laurentiu Tudor This allows building powerpc with the GENERIC_MSI_IRQ Kconfig by enabling the asm-generic msi.h in Kbuild. Without this, there's a compilation error [1] because powerpc, as most arches, doesn't provide an asm/msi.h. [1] In file included from

Re: [PATCH 2/2] selftests/ftrace: Update multiple kprobes test for powerpc

On Wed, 28 Jun 2017 14:58:46 +0530 "Naveen N. Rao" wrote: > On 2017/06/24 08:06PM, Masami Hiramatsu wrote: > > On Sat, 24 Jun 2017 02:30:21 +0900 > > Masami Hiramatsu wrote: > > > > > On Thu, 22 Jun 2017 22:33:25 +0530 > > > "Naveen N. Rao"

Re: linux-next: build failure after merge of the block tree

On 06/28/2017 06:43 AM, Jens Axboe wrote: > On 06/28/2017 02:04 AM, Stephen Rothwell wrote: >> Hi Jens, >> >> After merging the block tree, today's linux-next build (powerpc >> allnoconfig) failed like this: >> >> fs/fcntl.o: In function `do_fcntl': >> fcntl.c:(.text+0x6d4): undefined reference

Re: [PATCH v4 1/6] mm, x86: Add ARCH_HAS_ZONE_DEVICE to Kconfig

Oliver O'Halloran writes: > Currently ZONE_DEVICE depends on X86_64 and this will get unwieldly as > new architectures (and platforms) get ZONE_DEVICE support. Move to an > arch selected Kconfig option to save us the trouble. > > Cc: linux...@kvack.org > Acked-by: Ingo Molnar

Re: [PATCH] powerpc/powernv: Tell OPAL about our MMU mode

On Wed, 2017-06-28 at 15:17 +1000, Michael Ellerman wrote: > Which doesn't really make sense. FSP says it's running (runtime). > > The end of the OPAL log is below. > > I think your patch means we're now calling slw_reinit(), whereas > previously we would skip it? Ugh... and slw_reinit() is

Re: [PATCH] powerpc/powernv: Rework local TLB flush for boot and MCE on POWER9

On Wed, 2017-06-28 at 08:21 +0530, Aneesh Kumar K.V wrote: > > > I am not sure the new location of flushing the tlb is correct/perfect. For ex: > may be we should do it before htab_initialize() so that we start with > all everything flushed ? But otherwise Doesn't matter as long as you do it

Re: linux-next: build failure after merge of the block tree

On 06/28/2017 02:04 AM, Stephen Rothwell wrote: > Hi Jens, > > After merging the block tree, today's linux-next build (powerpc > allnoconfig) failed like this: > > fs/fcntl.o: In function `do_fcntl': > fcntl.c:(.text+0x6d4): undefined reference to `__get_user_bad' > fcntl.c:(.text+0x730):

Re: [PATCH] powernv:idle: Clear r12 on wakeup from stop lite

Nicholas Piggin writes: > On Wed, 28 Jun 2017 06:46:49 +0530 > Akshay Adiga wrote: > >> pnv_wakeup_noloss expects R12 to contain SRR1 value to determine if >> the wakeup reason is an HMI in CHECK_HMI_INTERRUPT. >> >> When we wakeup with

[PATCH 2/2] powerpc: use spin loop primitives in some functions

From: Nicholas Piggin Use the different spin loop primitives in some simple powerpc spin loops, including those which will spin as a common case. This will help to test the spin loop primitives before more conversions are done. Signed-off-by: Nicholas Piggin

[PATCH 1/2] powerpc/64: implement spin loop primitives

From: Nicholas Piggin Signed-off-by: Nicholas Piggin --- arch/powerpc/include/asm/processor.h | 20 1 file changed, 20 insertions(+) diff --git a/arch/powerpc/include/asm/processor.h b/arch/powerpc/include/asm/processor.h index

[PATCH] powerpc: remapping too much memory

There is a cut and paste error here so we use "sizeof(struct mpc83xx_pmc)" to remap the memory for "clock_regs". That sizeof() is 20 bytes and we only need to remap 12 bytes. It presumably doesn't affect run time too much... I changed them to both use "sizeof(*variable_name)" because that's the

Re: [PATCH] powerpc: Build fix for non SPARSEMEM_VMEMAP config

On Wednesday 28 June 2017 12:48 PM, Alexey Kardashevskiy wrote: On 28/06/17 16:09, Aneesh Kumar K.V wrote: We can use pfn_to_page in realmode for other configs. Hence remove the CONFIG_FLATMEM ifdef For CONFIG_SPARSEMEM and CONFIG_DISCONTIGMEM and others (I am struggling to find the full

Re: [PATCH] powerpc: conditionally compile platform-specific serial drivers

On Tue, Jun 27, 2017 at 04:29:51PM +0200, Hannes Reinecke wrote: > mpsc.c and mpc52xx-psc.c are platform-specific serial drivers, and > should be compiled for the respective platforms only. Yes, this is really dead code that gets compiled and copied needlessly, on all PPCs apart from those

Re: [PATCH 2/2] selftests/ftrace: Update multiple kprobes test for powerpc

On 2017/06/24 08:06PM, Masami Hiramatsu wrote: > On Sat, 24 Jun 2017 02:30:21 +0900 > Masami Hiramatsu wrote: > > > On Thu, 22 Jun 2017 22:33:25 +0530 > > "Naveen N. Rao" wrote: > > > > > On 2017/06/22 06:07PM, Masami Hiramatsu wrote: > > >

[v4.12-rc1 regression] mount ext4 fs results in kernel crash on PPC64le host

Hi all, Li Wang and I are constantly seeing ppc64le hosts crashing due to bad page access. But it's not reproducing on every ppc64le host we've tested, but it usually happened in filesystem testings. [ 207.403459] Unable to handle kernel paging request for unaligned access at address

Re: [PATCH] MAINTAINERS: cxl: update maintainership

Acked-by: Ian Munsie Excerpts from andrew.donnellan's message of 2017-06-28 17:22:30 +1000: > As Ian's stepping down from his maintainer role now that he's leaving IBM, > Frederic has asked me to add myself to the cxl maintainer list. Updating > accordingly. > > Cc:

Re: [PATCH] MAINTAINERS: Remove myself as cxl maintainer

Le 28/06/2017 à 08:19, Ian Munsie a écrit : From: Ian Munsie I am no longer employed by IBM and will no longer have access to cxl hardware, so remove myself as a cxl maintainer. If anyone needs to contact me in the future, please use my personal email address

Re: [PATCH] MAINTAINERS: cxl: update maintainership

Le 28/06/2017 à 09:22, Andrew Donnellan a écrit : As Ian's stepping down from his maintainer role now that he's leaving IBM, Frederic has asked me to add myself to the cxl maintainer list. Updating accordingly. Cc: Frederic Barrat Cc: Ian Munsie

linux-next: build failure after merge of the block tree

Hi Jens, After merging the block tree, today's linux-next build (powerpc allnoconfig) failed like this: fs/fcntl.o: In function `do_fcntl': fcntl.c:(.text+0x6d4): undefined reference to `__get_user_bad' fcntl.c:(.text+0x730): undefined reference to `__get_user_bad' Probably caused by commit

Re: [PATCH] MAINTAINERS: Remove myself as cxl maintainer

Hi Ian, As Andrew said, thanks for everything: CXL enablement was my introduction to the kernel - it was a great place to start, and it was a privilege to work with you. All the best for your future endeavours! Regards, Daniel Ian Munsie writes: > From: Ian Munsie

Re: [PATCH kernel 0/3 REPOST] vfio-pci: Add support for mmapping MSI-X table

On 24/06/17 01:17, Alex Williamson wrote: > On Fri, 23 Jun 2017 15:06:37 +1000 > Alexey Kardashevskiy wrote: > >> On 23/06/17 07:11, Alex Williamson wrote: >>> On Thu, 15 Jun 2017 15:48:42 +1000 >>> Alexey Kardashevskiy wrote: >>> Here is a patchset which

[PATCH] MAINTAINERS: cxl: update maintainership

As Ian's stepping down from his maintainer role now that he's leaving IBM, Frederic has asked me to add myself to the cxl maintainer list. Updating accordingly. Cc: Frederic Barrat Cc: Ian Munsie Signed-off-by: Andrew Donnellan

Re: [PATCH] powerpc: Build fix for non SPARSEMEM_VMEMAP config

On 28/06/17 16:09, Aneesh Kumar K.V wrote: > We can use pfn_to_page in realmode for other configs. Hence remove the > CONFIG_FLATMEM ifdef For CONFIG_SPARSEMEM and CONFIG_DISCONTIGMEM and others (I am struggling to find the full list :) )? Are you sure about that? If I recall correctly, at the

Re: [PATCH] MAINTAINERS: Remove myself as cxl maintainer

On 28/06/17 16:19, Ian Munsie wrote: From: Ian Munsie I am no longer employed by IBM and will no longer have access to cxl hardware, so remove myself as a cxl maintainer. If anyone needs to contact me in the future, please use my personal email address

Re: [RFC v4 09/17] powerpc: call the hash functions with the correct pkey value

On Tue, Jun 27, 2017 at 08:54:07PM +0530, Aneesh Kumar K.V wrote: > > > On Tuesday 27 June 2017 03:41 PM, Ram Pai wrote: > >Pass the correct protection key value to the hash functions on > >page fault. > > > >Signed-off-by: Ram Pai > >--- > >

Re: [PATCH v2] spin loop primitives for busy waiting

Nicholas Piggin writes: > Current busy-wait loops are implemented by repeatedly calling cpu_relax() > to give an arch option for a low-latency option to improve power and/or > SMT resource contention. > > This poses some difficulties for powerpc, which has SMT priority setting

[PATCH] MAINTAINERS: Remove myself as cxl maintainer

From: Ian Munsie I am no longer employed by IBM and will no longer have access to cxl hardware, so remove myself as a cxl maintainer. If anyone needs to contact me in the future, please use my personal email address darkstarsw...@gmail.com Signed-off-by: Ian Munsie

[PATCH] powerpc: Build fix for non SPARSEMEM_VMEMAP config

We can use pfn_to_page in realmode for other configs. Hence remove the CONFIG_FLATMEM ifdef Fixes: 8e0861fa3c4ed (powerpc: Prepare to support kernel handling of IOMMU map/unmap) Cc: Alexey Kardashevskiy Signed-off-by: Aneesh Kumar K.V ---