Re: [PATCH] cxl: Remove duplicate #defines

On 04/05/16 14:48, Ian Munsie wrote: From: Ian Munsie These defines are not used, but other equivalent definitions (CXL_SPA_SW_CMD_*) are used. Remove the unused defines. Signed-off-by: Ian Munsie They definitely look unused. Reviewed-by: Andrew

Re: [PATCH v9 12/26] powerpc/powernv/ioda1: M64 support on P7IOC

On Tue, 3 May 2016 15:41:31 Gavin Shan wrote: > This enables M64 window on P7IOC, which has been enabled on PHB3. Have we tested that this works with an adaptor? This looks to be enabling support for something that didn't previously work (64-bit BARs on P7IOC)? Regards, Alistair > Different

[PATCH] cxl: Handle num_of_processes larger than can fit in the SPA

From: Ian Munsie num_of_process is a 16 bit field, theoretically allowing an AFU to support 16K processes, however the scheduled process area currently has a maximum size of 1MB, which limits the maximum number of processes to 7704. Some AFUs may not necessarily care what

[PATCH] cxl: Remove duplicate #defines

From: Ian Munsie These defines are not used, but other equivalent definitions (CXL_SPA_SW_CMD_*) are used. Remove the unused defines. Signed-off-by: Ian Munsie --- drivers/misc/cxl/cxl.h | 9 - 1 file changed, 9 deletions(-) diff --git

Re: [PATCH v9 20/26] powerpc/pci: Move pci_find_bus_by_node() around

On 03/05/16 15:41, Gavin Shan wrote: This moves pci_find_bus_by_node() from arch/powerpc/platforms/ pseries/pci_dlpar.c to arch/powerpc/kernel/pci-hotplug.c so that the function can be used by pSeries and PowerNV platform at the same time. Also, below cleanup applied. No functional changes

Re: [PATCH v9 18/26] powerpc/pci: Rename pcibios_{add,remove}_pci_devices()

On Wed, May 04, 2016 at 02:10:47PM +1000, Alistair Popple wrote: >On Tue, 3 May 2016 15:41:37 Gavin Shan wrote: >> This renames pcibios_{add,remove}_pci_devices() to avoid conflicts >> with names of the weak functions in PCI subsystem, which have the >> prefix "pcibios". No logical changes

[PATCH] cxl: Ensure PSL interrupt is configured for contexts with no AFU IRQs

From: Ian Munsie In the cxl kernel API, it is possible to create a context and start it without allocating any interrupts. Since we assign or allocate the PSL interrupt when allocating AFU interrupts this will lead to a situation where we start the context with no means to

Re: [PATCH v9 18/26] powerpc/pci: Rename pcibios_{add, remove}_pci_devices()

On 03/05/16 15:41, Gavin Shan wrote: This renames pcibios_{add,remove}_pci_devices() to avoid conflicts with names of the weak functions in PCI subsystem, which have the prefix "pcibios". No logical changes introduced. Signed-off-by: Gavin Shan Looks fine to me.

Re: [PATCH v9 07/26] powerpc/powernv: Fix initial IO and M32 segmap

On Wed, May 04, 2016 at 01:31:04PM +1000, Alistair Popple wrote: >On Tue, 3 May 2016 15:41:26 Gavin Shan wrote: >> There are two arrays for IO and M32 segment maps on every PHB. >> The index of the arrays are segment number and the value stored >> in the corresponding element is PE number,

Re: [PATCH v9 06/26] powerpc/powernv: Data type unsigned int for PE number

I had a quick look at the surrounding code and couldn't see anything obvious that would result in a behaviour change. Reviewed-By: Alistair Popple On Tue, 3 May 2016 15:41:25 Gavin Shan wrote: > This changes the data type of PE number from "int" to "unsigned int" > in

Re: [PATCH v9 07/26] powerpc/powernv: Fix initial IO and M32 segmap

On Tue, 3 May 2016 15:41:26 Gavin Shan wrote: > There are two arrays for IO and M32 segment maps on every PHB. > The index of the arrays are segment number and the value stored > in the corresponding element is PE number, indicating the segment > is assigned to the PE. Initially, all elements in

Re: [PATCH v9 08/26] powerpc/powernv: Simplify pnv_ioda_setup_pe_seg()

On Tue, 3 May 2016 15:41:27 Gavin Shan wrote: > pnv_ioda_setup_pe_seg() associates the IO and M32 segments with the > owner PE. The code mapping segments should be fixed and immune from > logic changes introduced to pnv_ioda_setup_pe_seg(). > > This moves the code mapping segments to helper

Re: [PATCH v9 14/26] powerpc/powernv/ioda1: Introduce PNV_IODA1_DMA32_SEGSIZE

On Tue, 3 May 2016 15:41:33 Gavin Shan wrote: > Currently, there is one macro (TCE32_TABLE_SIZE) representing the > TCE table size for one DMA32 segment. The constant representing > the DMA32 segment size (1 << 28) is still used in the code. > > This defines PNV_IODA1_DMA32_SEGSIZE representing

Re: [PATCH v9 18/26] powerpc/pci: Rename pcibios_{add, remove}_pci_devices()

On Tue, 3 May 2016 15:41:37 Gavin Shan wrote: > This renames pcibios_{add,remove}_pci_devices() to avoid conflicts > with names of the weak functions in PCI subsystem, which have the > prefix "pcibios". No logical changes introduced. I'm guessing this is just protecting against future weak PCI

[v9, 7/7] mmc: sdhci-of-esdhc: fix host version for T4240-R1.0-R2.0

The eSDHC of T4240-R1.0-R2.0 has incorrect vender version and spec version. Acturally the right version numbers should be VVN=0x13 and SVN = 0x1. This patch adds the GUTS driver support for eSDHC driver to get SVR(System version register). And fix host version to avoid that incorrect version

[v9, 6/7] MAINTAINERS: add entry for Freescale SoC driver

Add maintainer entry for Freescale SoC driver including the QE library and the GUTS driver now. Also add maintainer for QE library. Signed-off-by: Yangbo Lu --- Changes for v8: - Added this patch Changes for v9: - Added linux-arm mail list - Removed

[v9, 5/7] powerpc/fsl: move mpc85xx.h to include/linux/fsl

Move mpc85xx.h to include/linux/fsl and rename it to svr.h as a common header file. It has been used for mpc85xx and it will be used for ARM-based SoC as well. Signed-off-by: Yangbo Lu Acked-by: Wolfram Sang Acked-by: Stephen Boyd

[v9, 4/7] dt: move guts devicetree doc out of powerpc directory

Move guts devicetree doc to Documentation/devicetree/bindings/soc/fsl/ since it's used by not only PowerPC but also ARM. And add a specification for 'little-endian' property. Signed-off-by: Yangbo Lu Acked-by: Scott Wood Acked-by: Rob Herring

[v9, 3/7] soc: fsl: add GUTS driver for QorIQ platforms

The global utilities block controls power management, I/O device enabling, power-onreset(POR) configuration monitoring, alternate function selection for multiplexed signals,and clock control. This patch adds GUTS driver to manage and access global utilities block. Signed-off-by: Yangbo Lu

[v9, 2/7] ARM64: dts: ls2080a: add device configuration node

Add the dts node for device configuration unit that provides general purpose configuration and status for the device. Signed-off-by: Yangbo Lu Acked-by: Scott Wood --- Changes for v5: - Added this patch Changes for v6: - None Changes for v7:

[v9, 1/7] Documentation: DT: update Freescale DCFG compatible

Update Freescale DCFG compatible with 'fsl,-dcfg' instead of 'fsl,ls1021a-dcfg' to include more chips such as ls1021a, ls1043a, and ls2080a. Signed-off-by: Yangbo Lu --- Changes for v8: - Added this patch Changes for v9: - Added a list for the possible

[v9, 0/7] Fix eSDHC host version register bug

This patchset is used to fix a host version register bug in the T4240-R1.0-R2.0 eSDHC controller. To get the SoC version and revision, it's needed to add the GUTS driver to access the global utilities registers. So, the first four patches are to add the GUTS driver. The following patches except

RE: [v8, 6/7] MAINTAINERS: add entry for Freescale SoC specific driver

Hi Leo and Scott, > -Original Message- > From: Leo Li [mailto:pku@gmail.com] > Sent: Wednesday, May 04, 2016 4:06 AM > To: Yangbo Lu > Cc: Scott Wood; Yang-Leo Li; linux-...@vger.kernel.org; linuxppc- > d...@lists.ozlabs.org; linux-arm-ker...@lists.infradead.org; linux- >

Re: [PATCH 2/2] powerpc: Update of_remove_property() call sites to remove null checking

On 04/27/2016 10:34 PM, Suraj Jitindar Singh wrote: > After obtaining a property from of_find_property() and before calling > of_remove_property() most code checks to ensure that the property > returned from of_find_property() is not null. The previous patch > moved this check to the start of the

Re: VDSO unmap and remap support for additional architectures

On 04/29/2016 09:55 AM, Dmitry Safonov wrote: > On 04/29/2016 04:22 PM, Christopher Covington wrote: >> On 04/28/2016 02:53 PM, Andy Lutomirski wrote: >>> Also, at some point, possibly quite soon, x86 will want a way for >>> user code to ask the kernel to map a specific vdso variant at a specific

Radeon 77xx xorg issue on cyrus+ Varisys

This are my logs of experience on a 7750HD 2GB I attached my dmesg radeon,drm and Xorg logs for gave better investigating to the devs. I see on Xorg.1.log where the radeon config was called there is a crash on radeonsi a drm:.si_dpm_set_power_state] *ERROR* too. Hope it will help for have a

Re: [v8, 6/7] MAINTAINERS: add entry for Freescale SoC specific driver

On Mon, Apr 25, 2016 at 10:12 PM, Yangbo Lu wrote: > Hi Scott and Leo, > > >> -Original Message- >> From: linux-mmc-ow...@vger.kernel.org [mailto:linux-mmc- >> ow...@vger.kernel.org] On Behalf Of Scott Wood >> Sent: Saturday, April 23, 2016 7:23 AM >> To: Yangbo Lu;

Re: [PATCH 4/4] net: ethernet: fec_mpc52xx: move to new ethtool api {get|set}_link_ksettings

From: Philippe Reynes Date: Sun, 1 May 2016 17:08:11 +0200 > The ethtool api {get|set}_settings is deprecated. > We move the fec_mpc52xx driver to new api {get|set}_link_ksettings. > > Signed-off-by: Philippe Reynes Applied.

Re: [PATCH 3/4] net: ethernet: fs-enet: move to new ethtool api {get|set}_link_ksettings

From: Philippe Reynes Date: Sun, 1 May 2016 17:08:10 +0200 > The ethtool api {get|set}_settings is deprecated. > We move the fs-enet driver to new api {get|set}_link_ksettings. > > Signed-off-by: Philippe Reynes Applied.

Re: [PATCH 2/4] net: ethernet: ucc: move to new ethtool api {get|set}_link_ksettings

From: Philippe Reynes Date: Sun, 1 May 2016 17:08:09 +0200 > The ethtool api {get|set}_settings is deprecated. > We move the ucc driver to new api {get|set}_link_ksettings. > > Signed-off-by: Philippe Reynes Applied.

Re: [PATCH 1/4] net: ethernet: gianfar: move to new ethtool api {get|set}_link_ksettings

From: Philippe Reynes Date: Sun, 1 May 2016 17:08:08 +0200 > The ethtool api {get|set}_settings is deprecated. > We move the gianfar driver to new api {get|set}_link_ksettings. > > Signed-off-by: Philippe Reynes Applied.

[PATCH 1/1] cxlflash: Fix to resolve dead-lock during EEH recovery

From: "Manoj N. Kumar" When a cxlflash adapter goes into EEH recovery and multiple processes (each having established its own context) are active, the EEH recovery can hang if the processes attempt to recover in parallel. The symptom logged after a couple of minutes is:

[PATCH 0/1] cxlflash: Fix in EEH recovery

This patch addresses a deadlock issue seen during EEH recovery and is intended for 4.7. Manoj N. Kumar (1): cxlflash: Fix to resolve dead-lock during EEH recovery drivers/scsi/cxlflash/superpipe.c | 15 +++ 1 file changed, 15 insertions(+) -- 2.1.0

[PATCH-next v2 0/2] cpufreq: powernv: Fixes for Global pstate management

Fixes are based on patch https://patchwork.ozlabs.org/patch/612058/ which is in Rafael's linux-next. - Patch [1] fixes WARN_ON in powernv_target_index() - Patch [2] Deleting any pending timer to saves an unnecessary irq call in powernv_target_index() Akshay Adiga (2): cpufreq: powernv: Move

[PATCH-next v2 1/2] cpufreq: powernv: Move smp_call_function_any() out of irq safe block

Fix a WARN_ON caused by smp_call_function_any() when irq is disabled, because of changes made in the patch ('cpufreq: powernv: Ramp-down global pstate slower than local-pstate') https://patchwork.ozlabs.org/patch/612058/ WARNING: CPU: 0 PID: 4 at kernel/smp.c:291

[PATCH-next v2 2/2] cpufreq: powernv: del_timer_sync when global and local pstate are equal

When global and local pstate are equal in a powernv_target_index() call, we don't queue a timer. But we may have timer already queued for future. This could cause the timer to fire one additional time for no use. Signed-off-by: Akshay Adiga --- Patch is based on

[PATCH 0/7] powerpc/8xx: Optimisation of TLB handling for IMMR and RAM

The purpose of this set of patches is to continue on TLB handling optimisation on the 8xx with the handling of IMMR area as a single 512k area instead of multiple 4k pages. This set includes a rework of linear RAM mapping in order to not use page table but direct linear mapping. The result is

[PATCH 7/7] powerpc/8xx: add CONFIG_PIN_TLB_IMMR

CONFIG_PIN_TLB maps IMMR area and the first 24 Mbytes of memory. In some circunstances it might be more interesting to not map IMMR and to map 32 Mbytes of memory instead. Therefore we add config option CONFIG_PIN_TLB_IMMR to select if IMMR shall be pinned or not, hence whether we pin 24 or 32

[PATCH 6/7] powerpc/8xx: Rework CONFIG_PIN_TLB handling

On recent kernels, with some debug options like for instance CONFIG_LOCKDEP, the BSS requires more than 8M memory, allthough the kernel code fits in the first 8M. Today, it is necessary to activate CONFIG_PIN_TLB to get more than 8M at startup, allthough pinning TLB is not necessary for that. We

[PATCH 2/7] powerpc/8xx: Map IMMR area with 512k page at a fixed address

Once the linear memory space has been mapped with 8Mb pages, as seen in the related commit, we get 11 millions DTLB missed during the reference 600s period. 77% of the misses are on user addresses and 23% are on kernel addresses (1 fourth for linear address space and 3 fourth for virtual address

[PATCH v9 02/22] powerpc/pci: Override pcibios_setup_bridge()

This overrides pcibios_setup_bridge() that is called to update PCI bridge windows when PCI resource assignment is completed, to assign PE and setup various (resource) mapping for the PE in subsequent patches. Signed-off-by: Gavin Shan Reviewed-by: Alexey Kardashevskiy

Re: [PATCH kernel v4 11/11] powerpc/powernv/npu: Enable NVLink pass through

Hi Alexey, On Fri, 29 Apr 2016 18:55:24 Alexey Kardashevskiy wrote: > IBM POWER8 NVlink systems come with Tesla K40-ish GPUs each of which > also has a couple of fast speed links (NVLink). The interface to links > is exposed as an emulated PCI bridge which is included into the same > IOMMU group

[PATCH v9 12/22] powerpc/pci: Delay populating pdn

The pdn (struct pci_dn) instances are allocated from memblock or bootmem when creating PCI controller (hoses) in setup_arch(). PCI hotplug, which will be supported by proceeding patches, releases PCI device nodes and their corresponding pdn on unplugging event. The memory chunks for pdn instances

Re: [RFC PATCH v2 13/18] livepatch: separate enabled and patched states

On Tue, May 03, 2016 at 11:30:12AM +0200, Petr Mladek wrote: > On Thu 2016-04-28 15:44:44, Josh Poimboeuf wrote: > > Once we have a consistency model, patches and their objects will be > > enabled and disabled at different times. For example, when a patch is > > disabled, its loaded objects'

[PATCH v9 11/22] powerpc/pci: Update bridge windows on PCI plug

On the PCI plugging event, PCI slot's subordinate devices are scanned and their (IO and MMIO) resources are assigned. Platform dependent resources (PE#, IO/MMIO/DMA windows) are allocated or created on updating windows of the slot's upstream bridge. This updates the windows of the hot plugged

[PATCH v9 19/22] drivers/of: Specify parent node in of_fdt_unflatten_tree()

This adds one more argument to of_fdt_unflatten_tree() to specify the parent node of the FDT blob that is going to be unflattened. In the result, the function can be used to unflatten FDT blob that represents device sub-tree in PowerNV PCI hotplug driver. Cc: Jyri Sarha

[PATCH v9 20/22] drivers/of: Return allocated memory from of_fdt_unflatten_tree()

This returns the allocate memory chunk, storing the unflattened device tree, from of_fdt_unflatten_tree() so that memory chunk can be released on demand in PowerNV PCI hotplug driver. Signed-off-by: Gavin Shan Acked-by: Rob Herring ---

[PATCH v9 22/22] PCI/hotplug: PowerPC PowerNV PCI hotplug driver

This adds standalone driver to support PCI hotplug for PowerPC PowerNV platform that runs on top of skiboot firmware. The firmware identifies hotpluggable slots and marked their device tree node with proper "ibm,slot-pluggable" and "ibm,reset-by-firmware". The driver scans device tree nodes to

[PATCH v9 16/22] drivers/of: Split unflatten_dt_node()

The function unflatten_dt_node() is called recursively to unflatten device nodes and properties in the FDT blob. It looks complicated and hard to be understood. This splits the function into 3 functions: populate_properties(), populate_node() and unflatten_dt_node(). populate_properties(), which

[PATCH v9 09/22] powerpc/powernv: Make pnv_ioda_deconfigure_pe() visible

pnv_ioda_deconfigure_pe() is visible only when CONFIG_PCI_IOV is enabled. The function will be used to tear down PE's associated mapping in PCI hotplug path that doesn't depend on CONFIG_PCI_IOV. This makes pnv_ioda_deconfigure_pe() visible and not depend on CONFIG_PCI_IOV. Signed-off-by: Gavin

[PATCH v9 01/22] PCI: Add pcibios_setup_bridge()

Currently, PowerPC PowerNV platform utilizes ppc_md.pcibios_fixup(), which is called for once after PCI probing and resource assignment are completed, to allocate platform required resources for PCI devices: PE#, IO and MMIO mapping, DMA address translation (TCE) table etc. Obviously, it's not

[PATCH v9 14/22] powerpc/powernv: Use PCI slot reset infrastructure

The (OPAL) firmware might provide the PCI slot reset capability which is identified by property "ibm,reset-by-firmware" on the PCI slot associated device node. This routes the reset request to firmware if "ibm,reset-by-firmware" exists in the PCI slot device node. Otherwise, the reset is done

[PATCH v9 07/22] powerpc/powernv: Setup PE for root bus

There is no parent bridge for root bus, meaning pcibios_setup_bridge() isn't invoked for root bus. The PE for root bus is the ancestor of other PEs in PELTV. It means we need PE for root bus populated before all others. This populates the PE for root bus in pcibios_setup_bridge() path if it's not

[PATCH v9 03/22] powerpc/powernv: Move pnv_pci_ioda_setup_opal_tce_kill() around

pnv_pci_ioda_setup_opal_tce_kill() called by pnv_ioda_setup_dma() to remap the TCE kill regiter. What's done in pnv_ioda_setup_dma() will be covered in pcibios_setup_bridge() which is invoked on each PCI bridge. It means we will possibly remap the TCE kill register for multiple times and it's

[PATCH v9 13/22] powerpc/powernv: Support PCI slot ID

The reset and poll functionality from (OPAL) firmware supports PHB and PCI slot at same time. They are identified by ID. This supports PCI slot ID by: * Rename the argument name for opal_pci_reset() and opal_pci_poll() accordingly * Rename pnv_eeh_phb_poll() to pnv_eeh_poll() and

[PATCH v9 06/22] powerpc/powernv: Create PEs in pcibios_setup_bridge()

Currently, the PEs and their associated resources are assigned in ppc_md.pcibios_fixup() except those used by SRIOV VFs. The function is called for once after PCI probing and resources assignment is completed. So it's obviously not hotplug friendly. This creates PEs dynamically in

[PATCH v9 04/22] powerpc/powernv: Increase PE# capacity

Each PHB maintains an array helping to translate 2-bytes Request ID (RID) to PE# with the assumption that PE# takes one byte, meaning that we can't have more than 256 PEs. However, pci_dn->pe_number already had 4-bytes for the PE#. This extends the PE# capacity for every PHB. After that, the PE

[PATCH v9 18/22] drivers/of: Rename unflatten_dt_node()

This renames unflatten_dt_node() to unflatten_dt_nodes() as it populates multiple device nodes from FDT blob. No logical changes introduced. Signed-off-by: Gavin Shan Acked-by: Rob Herring --- drivers/of/fdt.c | 14 +++--- 1 file changed, 7

[PATCH v9 17/22] drivers/of: Avoid recursively calling unflatten_dt_node()

In current implementation, unflatten_dt_node() is called recursively to unflatten device nodes in FDT blob. It's stress to limited stack capacity, especially to adopt the function to unflatten device sub-tree that possibly has multiple root nodes. In that case, we runs out of stack and the system

[PATCH v9 21/22] drivers/of: Export of_detach_node()

This exports of_detach_node() for PowerPC PowerNV PCI hotplug driver. No functional changes introduced. Signed-off-by: Gavin Shan --- drivers/of/dynamic.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/of/dynamic.c b/drivers/of/dynamic.c index

[PATCH v9 15/22] powerpc/powernv: Functions to get/set PCI slot state

This exports 4 functions, which base on the corresponding OPAL APIs to get/set PCI slot status. Those functions are going to be used by PowerNV PCI hotplug driver: pnv_pci_get_device_tree()opal_get_device_tree() pnv_pci_get_presence_state() opal_pci_get_presence_state()

[PATCH v9 10/22] powerpc/powernv: Dynamically release PE

This supports releasing PEs dynamically. A reference count is introduced to PE representing number of PCI devices associated with the PE. The reference count is increased when PCI device joins the PE and decreased when PCI device leaves the PE in pnv_pci_release_device(). When the count becomes

[PATCH v9 05/22] powerpc/powernv: Allocate PE# in reverse order

PE number for one particular PE can be allocated dynamically or reserved according to the consumed M64 (64-bits prefetchable) segments of the PE. The M64 segment can't be remapped to arbitrary PE, meaning the PE number is determined according to the index of the consumed M64 segment. As below

[PATCH v9 08/22] powerpc/powernv: Extend PCI bridge resources

The PCI slots are associated with root port or downstream ports of the PCIe switch connected to root port. When adapter is hot added to the PCI slot, it usually requests more IO or memory resource from the directly connected parent bridge (port) and update the bridge's windows accordingly. The

[PATCH v9 00/22] powerpc/powernv: PCI hotplug support

The series is split from "[PATCH v8 00/45] powerpc/powernv: PCI hotplug support". Another series (A) sent to linux-ppc-dev maillist as it's only related to PowerPC. Besides, this series needs the firmware patches (B) to work. Without the firmware patches, the PCI hotplug driver won't detect and

Re: [PATCH -next 1/2] cpufreq: powernv: Move smp_call_function_any() out of irq safe block

Hi Viresh, On 05/03/2016 05:19 PM, Viresh Kumar wrote: On 03-05-16, 15:10, Akshay Adiga wrote: Fixing a WARN_ON caused by smp_call_function_any() when irq is disabled, because of changes made in the patch ('cpufreq: powernv: Ramp-down global pstate slower than local-pstate')

Re: [PATCH 1/2] drivers/of: Add check for null property in of_remove_property()

On Thu, Apr 28, 2016 at 12:34 AM, Suraj Jitindar Singh wrote: > The validity of the property input argument to of_remove_property() is > never checked within the function and thus it is possible to pass a null > value. It happens that this will be picked up in

[PATCH v1 1/1] powerpc/86xx: Fix PCI interrupt map definition

Fix PCI interrupt map definition from 2 to 4 cells. Move interrupt-map and interrupt-map-mask and clone interrupts into the pcie child nodes. Signed-off-by: Alessio Igor Bogani --- This patch requires

Re: powerpc: create_zero_mask() has bad inline assembly constraint

On Fri, 2016-29-04 at 22:29:27 UTC, Unknown sender due to SPF wrote: > In create_zero_mask() we have: > > addi%1,%2,-1 > andc%1,%1,%2 > popcntd %0,%1 > > using the "r" constraint for %2. r0 is a valid register in the "r" set, > but addi X,r0,X turns it into an li: > >

Re: [RFC PATCH v2 10/18] livepatch/powerpc: add TIF_PATCH_PENDING thread flag

On Tue, 3 May 2016, Petr Mladek wrote: > On Thu 2016-04-28 15:44:41, Josh Poimboeuf wrote: > > Add the TIF_PATCH_PENDING thread flag to enable the new livepatch > > per-task consistency model for powerpc. The bit getting set indicates > > the thread has a pending patch which needs to be applied

Re: [PATCH -next 1/2] cpufreq: powernv: Move smp_call_function_any() out of irq safe block

On 03-05-16, 15:10, Akshay Adiga wrote: > Fixing a WARN_ON caused by smp_call_function_any() when irq is disabled, > because of changes made in the patch > ('cpufreq: powernv: Ramp-down global pstate slower than local-pstate') > https://patchwork.ozlabs.org/patch/612058/ > > WARNING: CPU: 0 PID:

Re: [PATCH v3 12/16] rtc: powerpc: provide rtc_class_ops directly

On Tuesday 03 May 2016 14:05:09 Michael Ellerman wrote: > On Thu, 2016-04-28 at 00:34 +0200, Arnd Bergmann wrote: > > > The rtc-generic driver provides an architecture specific > > wrapper on top of the generic rtc_class_ops abstraction, > > and powerpc has another abstraction on top, which is a

Re: [PATCH v3 00/16] genrtc removal

On Tuesday 03 May 2016 09:24:18 Alexandre Belloni wrote: > Hi Arnd, > > I see you didn't copy Greg on that series (that may explain his > confusion on the previous patch), do you expect me to take it > through the RTC tree? That is fine but I'd like some acks from him. Yes, that was a mistake. I

[PATCH -next 0/2] cpufreq: powernv: Fixes for Global pstate management

Fixes are based on patch https://patchwork.ozlabs.org/patch/612058/ which is in Rafael's linux-next. - Patch [1] fixes WARN_ON in powernv_target_index() - Patch [2] Deleting any pending timer to saves an unnecessary irq call in powernv_target_index() Akshay Adiga (2): cpufreq: powernv: Move

[PATCH -next 2/2] cpufreq: powernv: del_timer_sync when global and local pstate are equal

Deleting pending gpstates->timer for the policy when global and local pstate are equal while executing target_index(). This saves an unnecessary irq call. Signed-off-by: Akshay Adiga --- Patch is based on Rafael's linux-next drivers/cpufreq/powernv-cpufreq.c | 2

[PATCH -next 1/2] cpufreq: powernv: Move smp_call_function_any() out of irq safe block

Fixing a WARN_ON caused by smp_call_function_any() when irq is disabled, because of changes made in the patch ('cpufreq: powernv: Ramp-down global pstate slower than local-pstate') https://patchwork.ozlabs.org/patch/612058/ WARNING: CPU: 0 PID: 4 at kernel/smp.c:291

Re: [RFC PATCH v2 15/18] livepatch: move patching functions into patch.c

On Thu 2016-04-28 15:44:46, Josh Poimboeuf wrote: > Move functions related to the actual patching of functions and objects > into a new patch.c file. > > diff --git a/kernel/livepatch/patch.c b/kernel/livepatch/patch.c > new file mode 100644 > index 000..782fbb5 > --- /dev/null > +++

Re: [RFC PATCH v2 13/18] livepatch: separate enabled and patched states

On Thu 2016-04-28 15:44:44, Josh Poimboeuf wrote: > Once we have a consistency model, patches and their objects will be > enabled and disabled at different times. For example, when a patch is > disabled, its loaded objects' funcs can remain registered with ftrace > indefinitely until the

Re: [PATCH] powerpc/mm/radix: fix STD_MMU_64 typo

Valentin Rothberg writes: > s/MMU_STD_64/STD_MMU_64/ > > Fixes: 11ffc1cfa4c2 ("powerpc/mm/radix: Use STD_MMU_64 to properly > isolate hash related code") > Signed-off-by: Valentin Rothberg Reviewed-by: Aneesh Kumar

Re: [RFC PATCH v2 10/18] livepatch/powerpc: add TIF_PATCH_PENDING thread flag

On Thu 2016-04-28 15:44:41, Josh Poimboeuf wrote: > Add the TIF_PATCH_PENDING thread flag to enable the new livepatch > per-task consistency model for powerpc. The bit getting set indicates > the thread has a pending patch which needs to be applied when the thread > exits the kernel. > > The bit

Re: [RFC 1/7] powerpc/mm: Make vmemmap_populate accommodate ZONE_DEVICE memory

On 05/03/2016 01:34 PM, Balbir Singh wrote: > > > On 03/05/16 16:29, Anshuman Khandual wrote: >> Change the vmemmap_populate function to detect device memory through >> to_vmemmap_altmap and then call generic the __vmmemap_alloc_block_buf >> function instead of vmemmap_alloc_block as the earlier

[PATCH v2 9/9] powerpc/powernv: Use deepest stop state when cpu is offlined

If hardware supports stop state, use the deepest stop state when the cpu is offlined. Signed-off-by: Shreyas B. Prabhu --- arch/powerpc/platforms/powernv/idle.c| 15 +-- arch/powerpc/platforms/powernv/powernv.h | 1 +

[PATCH v2 8/9] cpuidle/powernv: Add support for POWER ISA v3 idle states

POWER ISA v3 defines a new idle processor core mechanism. In summary, a) new instruction named stop is added. b) new per thread SPR named PSSCR is added which controls the behavior of stop instruction. Supported idle states and value to be written to PSSCR register to enter any idle

[PATCH v2 7/9] powerpc/powernv: Add platform support for stop instruction

POWER ISA v3 defines a new idle processor core mechanism. In summary, a) new instruction named stop is added. This instruction replaces instructions like nap, sleep, rvwinkle. b) new per thread SPR named PSSCR is added which controls the behavior of stop instruction. PSSCR has

[PATCH v2 6/9] powerpc/powernv: set power_save func after the idle states are initialized

pnv_init_idle_states discovers supported idle states from the device tree and does the required initialization. Set power_save function pointer only after this initialization is done Signed-off-by: Shreyas B. Prabhy --- arch/powerpc/platforms/powernv/idle.c | 3 +++

[PATCH v2 5/9] powerpc/powernv: Move idle related macros to cpuidle.h

Move idle related macros to a common location asm/cpuidle.h so that they can be used for stop instruction support. Signed-off-by: Shreyas B. Prabhy --- arch/powerpc/include/asm/cpuidle.h | 27 +++ arch/powerpc/kernel/idle_power7.S | 26

[PATCH v2 4/9] powerpc/powernv: Make power7_powersave_common more generic

power7_powersave_common does common steps needed before entering idle state and eventually changes MSR to MSR_IDLE and does rfid to power7_enter_nap_mode. Make it more generic by passing the rfid address as a function parameter. Also make function name more generic. Signed-off-by: Shreyas B.

[PATCH v2 3/9] powerpc/powernv: Move idle code usable by multiple hardware to common location

CPU-idle related code like context save/restore functions idle_power7.S can reused for adding stop instruction support. Move this code to a new commonly accessible location. Signed-off-by: Shreyas B. Prabhu --- arch/powerpc/kernel/Makefile| 1 +

[PATCH v2 2/9] powerpc/kvm: make hypervisor state restore a function

In the current code, when the thread wakes up in reset vector, some of the state restore code and check for whether a thread needs to branch to kvm is duplicated. Reorder the code such that this duplication is avoided. At a higher level this is what the change looks like- Before this patch -

[PATCH v2 1/9] powerpc/powernv: Move CHECK_HMI_INTERRUPT to exception-64s header

CHECK_HMI_INTERRUPT is used to check for HMI's in reset vector. Move the macro to a common location (exception-64s.h) This patch does not change any functionality. Signed-off-by: Shreyas B. Prabhu --- arch/powerpc/include/asm/exception-64s.h | 18 ++

[PATCH v2 0/9] powerpc/powernv/cpuidle: Add support for POWER ISA v3 idle states

POWER ISA v3 defines a new idle processor core mechanism. In summary, a) new instruction named stop is added. This instruction replaces instructions like nap, sleep, rvwinkle. b) new per thread SPR named PSSCR is added which controls the behavior of stop instruction.

Re: [RFC 7/7] TEST: Driver to test device memory through ZONE_DEVICE

On 03/05/16 16:29, Anshuman Khandual wrote: > This is an example driver with little bit of kernel hack to test > ZONE_DEVICE based device memory management on POWER. > I think this should be under CONFIG_DEBUG/CONFIG_DEBUG_VM or something No? If you are exporting the functions from the

Re: [RFC 4/7] powerpc/mm: Set MAX_ZONE_PFN to 0 for all zones beyond TOP_ZONE

On 03/05/16 16:29, Anshuman Khandual wrote: > From: Oliver O'Halloran > > All the memory zones past TOP_ZONE are managed by generic mm code. Zone > max PFN should be set to 0 instead of ~0UL since that's what the generic > mm code expects. Without this, kernel assigns all

Re: [RFC 3/7] powerpc/mm: Define TOP_ZONE as a constant

On 03/05/16 16:29, Anshuman Khandual wrote: > From: Oliver O'Halloran > > The zone that contains the top of the memory will be either ZONE_NORMAL > or ZONE_HIGHMEM depending on the kernel config. There are two functions > in there which require this information and both of

Re: [RFC 1/7] powerpc/mm: Make vmemmap_populate accommodate ZONE_DEVICE memory

On 03/05/16 16:29, Anshuman Khandual wrote: > Change the vmemmap_populate function to detect device memory through > to_vmemmap_altmap and then call generic the __vmmemap_alloc_block_buf > function instead of vmemmap_alloc_block as the earlier can allocate > physical memory from the device range

Re: [PATCH kernel v4 10/11] powerpc/powernv/npu: Rework TCE Kill handling

On Fri, 29 Apr 2016 18:55:23 Alexey Kardashevskiy wrote: > The pnv_ioda_pe struct keeps an array of peers. At the moment it is only > used to link GPU and NPU for 2 purposes: > > 1. Access NPU quickly when configuring DMA for GPU - this was addressed > in the previos patch by removing use of it

Re: [PATCH] vfio-pci: Allow to mmap sub-page MMIO BARs if the mmio page is exclusive

On 2016/5/3 14:11, Tian, Kevin wrote: From: Yongji Xie [mailto:xyj...@linux.vnet.ibm.com] Sent: Tuesday, May 03, 2016 1:52 PM + + if (!(res->start & ~PAGE_MASK)) { + /* +* Add shadow resource for sub-page bar whose mmio +

Re: [PATCH 5/5] vfio-pci: Allow to mmap MSI-X table if interrupt remapping is supported

On 2016/5/3 14:22, Tian, Kevin wrote: From: Yongji Xie [mailto:xyj...@linux.vnet.ibm.com] Sent: Tuesday, May 03, 2016 2:08 PM On 2016/5/3 13:34, Tian, Kevin wrote: From: Yongji Xie Sent: Wednesday, April 27, 2016 8:43 PM This patch enables mmapping MSI-X tables if hardware supports

Re: [PATCH v3 00/16] genrtc removal

Hi Arnd, I see you didn't copy Greg on that series (that may explain his confusion on the previous patch), do you expect me to take it through the RTC tree? That is fine but I'd like some acks from him. On 28/04/2016 at 00:34:14 +0200, Arnd Bergmann wrote : > I ended up stuffing the two patch

[PATCH] powerpc/mm/radix: fix STD_MMU_64 typo

s/MMU_STD_64/STD_MMU_64/ Fixes: 11ffc1cfa4c2 ("powerpc/mm/radix: Use STD_MMU_64 to properly isolate hash related code") Signed-off-by: Valentin Rothberg --- I only compile tested this change. The issue has been detected with

  1   2   >