From: Julia Lawall julia.law...@lip6.fr
The semantic patch that fixes this problem is as follows:
(http://coccinelle.lip6.fr/)
// smpl
@r@
type T;
identifier f;
@@
static T f (...) { ... }
@@
identifier r.f;
declarer name EXPORT_SYMBOL;
@@
-EXPORT_SYMBOL(f);
// /smpl
Furthermore, the
On 3/9/2015 5:08 PM, Martin Hicks wrote:
On Mon, Mar 9, 2015 at 6:16 AM, Horia Geantă horia.gea...@freescale.com
wrote:
On 3/3/2015 7:44 PM, Martin Hicks wrote:
On Tue, Mar 3, 2015 at 10:44 AM, Horia Geantă
horia.gea...@freescale.com wrote:
For talitos, there are two cases:
1. request
These patches remove EXPORT_SYMBOL or EXPORT_SYMBOL_GPL declarations on
static functions.
This was done using the following semantic patch:
(http://coccinelle.lip6.fr/)
// smpl
@r@
type T;
identifier f;
@@
static T f (...) { ... }
@@
identifier r.f;
declarer name EXPORT_SYMBOL;
@@
Currently, the FDT blob needs to be in the same naturally aligned
512 MB region as the kernel, so that it can be mapped into the
kernel virtual memory space very early on using a minimal set of
statically allocated translation tables.
Now that we have early fixmap support, we can relax this
This series came about after Mark Rutland brought up the fact that the current
FDT placement logic used by the EFI stub is flawed. But actually, it turned out
that the documentation for both the Image and FDT placement was incorrect as
well, or confusing at the very least.
So this series does two
With the relaxed FDT placement requirements in place, we can change
the allocation strategy used by the stub to put the FDT image higher
up in memory. At the same time, reduce the minimal alignment to a
power of 2 upper bound of the size: this way, we are still guaranteed
not to cross a 2 MB
This splits off the reservation of the memory occupied by the FDT
binary itself from the processing of the memory reservations it
contains. This is necessary because the physical address of the FDT,
which is needed to perform the reservation, may not be known to the
FDT driver core, i.e., it may
The early init code maps the kernel image using statically
allocated page tables. This means that we can only allow
Image to be placed such that we can map its entire static
footprint using a single table entry at all but the lowest
level. So update the documentation to reflect that the Image
Replace one line asm-generic include files declared in
arch/powerpc/include/asm/ by generic-y declaration
which creates arch/powerpc/include/generated/asm equivalent.
Signed-off-by: Fabian Frederick f...@skynet.be
---
arch/powerpc/include/asm/Kbuild | 4 +++-
arch/powerpc/include/asm/div64.h
On Wed, Mar 4, 2015 at 5:27 PM, Kees Cook keesc...@chromium.org wrote:
Most architectures don't need to do much special for the strict-mode
seccomp syscall entries. Remove the redundant headers and reduce the
others.
Signed-off-by: Kees Cook keesc...@chromium.org
Hi Andrew,
Just a quick
Madhavan Srinivasan ma...@linux.vnet.ibm.com writes:
Nest Counters can be configured via PORE Engine and OPAL
provides an interface call to it. PORE Engine also does the
work of moving the counter data to memory.
Do you have the associated skiboot patch that implements this firmware
call? I
On Tue, 2015-03-03 at 10:47 +0530, Bharat Bhushan wrote:
This patch allows a context (different from kernel context)
to reserve a MSI bank for itself. And then the devices in the
context will share the MSI bank.
VFIO meta driver is one of typical user of these APIs. It will
reserve a MSI
On Wed, Mar 11, 2015 at 08:55:07AM -0500, Bjorn Helgaas wrote:
On Wed, Mar 04, 2015 at 01:19:07PM +0800, Wei Yang wrote:
On PHB3, PF IOV BAR will be covered by M64 window to have better PE
isolation. The total_pe number is usually different from total_VFs, which
can lead to a conflict between
On Tue, Mar 10, 2015 at 09:51:25PM -0500, Bjorn Helgaas wrote:
On Mon, Mar 02, 2015 at 03:41:32PM +0800, Wei Yang wrote:
On Tue, Feb 24, 2015 at 02:52:34AM -0600, Bjorn Helgaas wrote:
On Tue, Feb 24, 2015 at 02:34:42AM -0600, Bjorn Helgaas wrote:
From: Wei Yang weiy...@linux.vnet.ibm.com
On Tue, Mar 10, 2015 at 09:47:37PM -0500, Bjorn Helgaas wrote:
On Mon, Mar 02, 2015 at 03:50:37PM +0800, Wei Yang wrote:
On Tue, Feb 24, 2015 at 02:46:53AM -0600, Bjorn Helgaas wrote:
On Tue, Feb 24, 2015 at 02:34:35AM -0600, Bjorn Helgaas wrote:
From: Wei Yang weiy...@linux.vnet.ibm.com
The patch adds one more EEH sub-command (VFIO_EEH_PE_INJECT_ERR)
to inject the specified EEH error, which is represented by
(struct vfio_eeh_pe_err), to the indicated PE for testing purpose.
Signed-off-by: Gavin Shan gws...@linux.vnet.ibm.com
---
Documentation/vfio.txt| 47
The patch defines PCI error types and functions in eeh.h and
exports function eeh_pe_inject_err(), which will be called by
VFIO driver to inject the specified PCI error to the indicated
PE for testing purpose.
Signed-off-by: Gavin Shan gws...@linux.vnet.ibm.com
---
arch/powerpc/include/asm/eeh.h
Thomas Huth th...@linux.vnet.ibm.com writes:
On Wed, 11 Mar 2015 17:26:32 +1100
Alexey Kardashevskiy a...@ozlabs.ru wrote:
At the moment SLOF adds a device_type property automatically for
every single PCI device based on its class even if there is no SLOF
driver for such a device. OF1275
On 11/03/15 06:38, Kevin Hao wrote:
On Tue, Mar 10, 2015 at 02:23:12PM +0200, Tomi Valkeinen wrote:
I just sent out a v2 [1] a few hours earlier with some minor updates. We
plan
to merge this patch series via the powerpc tree in 4.1 cycle if I can
collect
all the acks from the
On Wed, 2015-03-11 at 08:50 +0100, Thomas Huth wrote:
- Graphic cards should get the display device_type ... I guess
that's
missing now?
At least the code for qemu-vga does it
- pci bus nodes (like bridges) should get the pci device_type
according to the Open Firmware PCI binding, is
At the moment SLOF adds a device_type property automatically for
every single PCI device based on its class even if there is no SLOF
driver for such a device. OF1275 says that device_type is for
implemented interfaces only. A side effect of this is virtio-balloon
getting device_type==memory while
On 03/11/2015 11:13 AM, Benjamin Herrenschmidt wrote:
On Wed, 2015-03-11 at 11:08 +0530, Anshuman Khandual wrote:
On 03/10/2015 04:25 PM, Michael Ellerman wrote:
On Tue, 2015-03-10 at 20:34 +1100, Benjamin Herrenschmidt wrote:
On Tue, 2015-03-10 at 18:36 +1100, Michael Ellerman wrote:
We
On Tue, Mar 10, 2015 at 09:55:19PM -0500, Bjorn Helgaas wrote:
On Wed, Mar 04, 2015 at 11:01:24AM +0800, Wei Yang wrote:
On Tue, Feb 24, 2015 at 03:00:37AM -0600, Bjorn Helgaas wrote:
On Tue, Feb 24, 2015 at 02:34:57AM -0600, Bjorn Helgaas wrote:
From: Wei Yang weiy...@linux.vnet.ibm.com
From: Igal Liberman igal.liber...@freescale.com
Signed-off-by: Igal Liberman igal.liber...@freescale.com
---
drivers/soc/fsl/fman/Kconfig|6 +
drivers/soc/fsl/fman/Makefile |1 +
drivers/soc/fsl/fman/rtc/Makefile |3 +
drivers/soc/fsl/fman/rtc/fman_rtc.c | 353
From: Igal Liberman igal.liber...@freescale.com
Signed-off-by: Igal Liberman igal.liber...@freescale.com
---
drivers/soc/fsl/fman/fm.c | 38 +++
drivers/soc/fsl/fman/fm.h |1 +
drivers/soc/fsl/fman/fm_common.h | 32 +++
drivers/soc/fsl/fman/fm_drv.c |
From: Madalin Bucur madalin.bu...@freescale.com
---
drivers/soc/fsl/fman/flib/fsl_enet.h | 275 ++
drivers/soc/fsl/fman/flib/fsl_fman_dtsec.h | 1016
drivers/soc/fsl/fman/flib/fsl_fman_dtsec_mii_acc.h | 103 ++
From: Igal Liberman igal.liber...@freescale.com
Signed-off-by: Igal Liberman igal.liber...@freescale.com
---
drivers/soc/fsl/fman/Kconfig|6 +
drivers/soc/fsl/fman/Makefile |1 +
drivers/soc/fsl/fman/pcd/Makefile |3 +
drivers/soc/fsl/fman/pcd/fman_kg.c | 849
On Wed, 11 Mar 2015 17:26:32 +1100
Alexey Kardashevskiy a...@ozlabs.ru wrote:
At the moment SLOF adds a device_type property automatically for
every single PCI device based on its class even if there is no SLOF
driver for such a device. OF1275 says that device_type is for
implemented
On Wed, 11 Mar 2015 19:21:02 +1100
Benjamin Herrenschmidt b...@kernel.crashing.org wrote:
On Wed, 2015-03-11 at 08:50 +0100, Thomas Huth wrote:
- Graphic cards should get the display device_type ... I guess
that's
missing now?
At least the code for qemu-vga does it
Ah, right, I
From: Igal Liberman igal.liber...@freescale.com
Signed-off-by: Igal Liberman igal.liber...@freescale.com
---
drivers/soc/fsl/fman/Kconfig |6 +
drivers/soc/fsl/fman/Makefile |1 +
drivers/soc/fsl/fman/mac/Makefile |5 +
From: Igal Liberman igal.liber...@freescale.com
Signed-off-by: Igal Liberman igal.liber...@freescale.com
---
drivers/soc/fsl/fman/fm_sp_common.h | 112 +
drivers/soc/fsl/fman/sp/Makefile|2 +-
drivers/soc/fsl/fman/sp/fm_sp.c | 429 +++
3
From: Igal Liberman igal.liber...@freescale.com
The Freescale Data Path Acceleration Architecture (DPAA) is a set of
hardware components on specific QorIQ multicore processors. This
architecture provides the infrastructure to support simplified
sharing of networking interfaces and accelerators by
On Wed, 2015-03-11 at 19:54 +1100, Alexey Kardashevskiy wrote:
+/* Page size flags for ibm,query-pe-dma-window */
+#define DDW_PGSIZE_4K 0x01
+#define DDW_PGSIZE_64K 0x02
+#define DDW_PGSIZE_16M 0x04
+#define DDW_PGSIZE_32M 0x08
+#define
On 03/10/2015 01:07 AM, Alexey Kardashevskiy wrote:
This extends iommu_table_group_ops by a set of callbacks to support dynamic
DMA windows management.
query() returns IOMMU capabilities such as default DMA window address and
supported number of DMA windows and TCE table levels.
create_table()
From: Igal Liberman igal.liber...@freescale.com
The Freescale Data Path Acceleration Architecture (DPAA) is a set of
hardware components on specific QorIQ multicore processors. This
architecture provides the infrastructure to support simplified
sharing of networking interfaces and accelerators by
From: Madalin Bucur madalin.bu...@freescale.com
---
drivers/soc/fsl/fman/flib/fsl_fman_kg.h | 505 ++
drivers/soc/fsl/fman/flib/fsl_fman_prs.h | 106 +++
2 files changed, 611 insertions(+)
create mode 100644 drivers/soc/fsl/fman/flib/fsl_fman_kg.h
create mode
From: Madalin Bucur madalin.bu...@freescale.com
---
drivers/soc/fsl/fman/flib/fsl_fman_rtc.h | 414 ++
1 file changed, 414 insertions(+)
create mode 100644 drivers/soc/fsl/fman/flib/fsl_fman_rtc.h
diff --git a/drivers/soc/fsl/fman/flib/fsl_fman_rtc.h
On 03/11/2015 07:21 PM, Benjamin Herrenschmidt wrote:
On Wed, 2015-03-11 at 08:50 +0100, Thomas Huth wrote:
- Graphic cards should get the display device_type ... I guess
that's
missing now?
At least the code for qemu-vga does it
- pci bus nodes (like bridges) should get the pci
From: Igal Liberman igal.liber...@freescale.com
The Freescale Data Path Acceleration Architecture (DPAA) is a set of
hardware components on specific QorIQ multicore processors. This
architecture provides the infrastructure to support simplified
sharing of networking interfaces and accelerators by
From: Igal Liberman igal.liber...@freescale.com
Signed-off-by: Igal Liberman igal.liber...@freescale.com
---
drivers/soc/fsl/fman/Kconfig | 10 +
drivers/soc/fsl/fman/Makefile |2 +
drivers/soc/fsl/fman/port/Makefile|3 +
drivers/soc/fsl/fman/port/fman_port.c |
From: Igal Liberman igal.liber...@freescale.com
Add Frame Manager Multi-User RAM support.
Signed-off-by: Igal Liberman igal.liber...@freescale.com
---
drivers/soc/fsl/fman/Kconfig|1 +
drivers/soc/fsl/fman/Makefile |5 +-
drivers/soc/fsl/fman/fm_muram.c |
From: Igal Liberman igal.liber...@freescale.com
Signed-off-by: Igal Liberman igal.liber...@freescale.com
---
drivers/soc/fsl/fman/Makefile |1 +
drivers/soc/fsl/fman/sp/Makefile |3 +
drivers/soc/fsl/fman/sp/fman_sp.c | 203 +
3 files changed,
On Tue, Mar 10, 2015 at 09:36:58PM -0500, Bjorn Helgaas wrote:
On Mon, Mar 02, 2015 at 03:32:47PM +0800, Wei Yang wrote:
On Tue, Feb 24, 2015 at 02:41:52AM -0600, Bjorn Helgaas wrote:
On Tue, Feb 24, 2015 at 02:34:06AM -0600, Bjorn Helgaas wrote:
From: Wei Yang weiy...@linux.vnet.ibm.com
From: Igal Liberman igal.liber...@freescale.com
Signed-off-by: Igal Liberman igal.liber...@freescale.com
---
drivers/soc/fsl/fman/fm_drv.c | 98
drivers/soc/fsl/fman/fm_drv.h |9 +-
drivers/soc/fsl/fman/inc/fm_rtc_ext.h | 398
From: Igal Liberman igal.liber...@freescale.com
Signed-off-by: Igal Liberman igal.liber...@freescale.com
---
drivers/soc/Kconfig |1 +
drivers/soc/Makefile |1 +
drivers/soc/fsl/Kconfig |1 +
drivers/soc/fsl/Makefile |1 +
From: Madalin Bucur madalin.bu...@freescale.com
---
drivers/soc/fsl/fman/flib/fman_common.h | 73
drivers/soc/fsl/fman/flib/fsl_fman_port.h | 601 +
drivers/soc/fsl/fman/flib/fsl_fman_sp.h | 132 +++
3 files changed, 806 insertions(+)
create mode
From: Igal Liberman igal.liber...@freescale.com
Signed-off-by: Igal Liberman igal.liber...@freescale.com
---
drivers/soc/fsl/fman/Kconfig | 10 +
drivers/soc/fsl/fman/inc/mac.h | 142
drivers/soc/fsl/fman/mac/Makefile |3 +-
drivers/soc/fsl/fman/mac/mac-api.c | 671
Patch adds the foundation code enable nest pmu. It defines
various init routines and these are based on Intel's uncore
framework. But it does differ since box structure abstraction
is not implemented here.
Signed-off-by: Madhavan Srinivasan ma...@linux.vnet.ibm.com
---
Patch enables POWER8 specific nest pmu support. It defines
pmu functions in a generic way that it can be shared across
different nest units. Event id is used, to identify the
offset in memory to read from. And the offset information
is saved in the per-chip data strucutres which are populated
at
Nest counter unit informations are passed on as part of device-tree
to kernel. Here is the Device-tree layout.
DT root folder /:
/
|
-uncore@chip-id
|
-phb --dt node for pcie host bridge (uncore pmu type)
-...
-mcs --dt node for memory controller (uncore pmu type)
|
Patch to enable the nest pmu code files in Makefile.
Signed-off-by: Madhavan Srinivasan ma...@linux.vnet.ibm.com
---
arch/powerpc/perf/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/powerpc/perf/Makefile b/arch/powerpc/perf/Makefile
index f9c083a..4b0bfd8
This patchset enables Nest Instrumentation support on powerpc.
POWER8 has per-chip Nest Intrumentation which provides various
per-chip utilisation metrics like memory bandwidth, IO bandwidth
and many other component metrics.
Nest Instrumentation provides an interface (via PORE Engine)
to
Patch adds the data structures and macros
needed for nest pmu support. type structure will
hold each nest unit and sub-unit information.
Signed-off-by: Madhavan Srinivasan ma...@linux.vnet.ibm.com
---
arch/powerpc/perf/uncore_pmu.h | 89 ++
1 file
Nest Counters can be configured via PORE Engine and OPAL
provides an interface call to it. PORE Engine also does the
work of moving the counter data to memory.
Signed-off-by: Madhavan Srinivasan ma...@linux.vnet.ibm.com
---
arch/powerpc/include/asm/opal.h| 3 +++
On Wed, Mar 11, 2015 at 1:22 AM, Wei Yang weiy...@linux.vnet.ibm.com wrote:
On Tue, Mar 10, 2015 at 09:51:25PM -0500, Bjorn Helgaas wrote:
On Mon, Mar 02, 2015 at 03:41:32PM +0800, Wei Yang wrote:
On Tue, Feb 24, 2015 at 02:52:34AM -0600, Bjorn Helgaas wrote:
On Tue, Feb 24, 2015 at 02:34:42AM
Sasha Levin sasha.le...@oracle.com writes:
As discussed on LSF/MM, kill kmemcheck.
Damn: I literally added CONFIG_KMEMCHECK support to virtio yesterday!
Will try Kasan now.
Thanks for the heads-up,
Rusty.
___
Linuxppc-dev mailing list
This runs a bit faster and removes another use of perl from
the kernel build.
Signed-off-by: Stephen Rothwell s...@canb.auug.org.au
---
arch/powerpc/Makefile| 4 +--
arch/powerpc/relocs_check.pl | 66
arch/powerpc/relocs_check.sh | 58
On Tue, 2015-03-03 at 10:47 +0530, Bharat Bhushan wrote:
With this patch a context can allocate a MSI bank and use the
allocated MSI-bank for the devices in that context.
kernel/host context is NULL, So all devices owned by kernel
will share a MSI bank allocated with context = NULL.
This
On Wed, Mar 04, 2015 at 01:19:07PM +0800, Wei Yang wrote:
On PHB3, PF IOV BAR will be covered by M64 window to have better PE
isolation. The total_pe number is usually different from total_VFs, which
can lead to a conflict between MMIO space and the PE number.
For example, if total_VFs is
On Thu, Mar 12, 2015 at 02:16:42PM +1100, Gavin Shan wrote:
On Thu, Mar 12, 2015 at 11:57:21AM +1100, David Gibson wrote:
On Wed, Mar 11, 2015 at 05:34:11PM +1100, Gavin Shan wrote:
The patch adds one more EEH sub-command (VFIO_EEH_PE_INJECT_ERR)
to inject the specified EEH error, which is
On Wed, 2015-03-11 at 07:43 -0400, Sasha Levin wrote:
As discussed on LSF/MM, kill kmemcheck.
KASan is a replacement that is able to work without the limitation of
kmemcheck (single CPU, slow). KASan is already upstream.
We are also not aware of any users of kmemcheck (or users who don't
On Thu, Mar 12, 2015 at 03:21:29PM +1100, David Gibson wrote:
On Thu, Mar 12, 2015 at 02:16:42PM +1100, Gavin Shan wrote:
On Thu, Mar 12, 2015 at 11:57:21AM +1100, David Gibson wrote:
On Wed, Mar 11, 2015 at 05:34:11PM +1100, Gavin Shan wrote:
The patch adds one more EEH sub-command
On Mon, Mar 09, 2015 at 10:34:04AM +0800, Yijing Wang wrote:
Now we could pass PCI domain combined with bus number
in u32 argu. Because in arm/arm64, PCI domain number
is assigned by pci_bus_assign_domain_nr(). So we leave
pci_scan_root_bus() and pci_create_root_bus() in arm/arm64
unchanged.
Use %pS for actual addresses, otherwise you'll get bad output
on arches like ppc64 where %pF expects a function descriptor. Even on
other architectures, refrain from setting a bad example that people
copy.
Signed-off-by: Scott Wood scottw...@freescale.com
Cc: linuxppc-dev@lists.ozlabs.org
---
On Wed, Mar 11, 2015 at 05:34:11PM +1100, Gavin Shan wrote:
The patch adds one more EEH sub-command (VFIO_EEH_PE_INJECT_ERR)
to inject the specified EEH error, which is represented by
(struct vfio_eeh_pe_err), to the indicated PE for testing purpose.
Signed-off-by: Gavin Shan
On Thu, Mar 12, 2015 at 11:57:21AM +1100, David Gibson wrote:
On Wed, Mar 11, 2015 at 05:34:11PM +1100, Gavin Shan wrote:
The patch adds one more EEH sub-command (VFIO_EEH_PE_INJECT_ERR)
to inject the specified EEH error, which is represented by
(struct vfio_eeh_pe_err), to the indicated PE for
66 matches
Mail list logo
