On 06/19/2014 10:22 AM, Masami Hiramatsu wrote:
> (2014/06/19 10:30), Michael Ellerman wrote:
>> On Wed, 2014-06-18 at 17:46 +0900, Masami Hiramatsu wrote:
>>> (2014/06/18 16:56), Michael Ellerman wrote:
On Fri, 2014-06-06 at 15:38 +0900, Masami Hiramatsu wrote:
> Ping?
>
> I guess
On 06/19/2014 03:30 PM, bharat.bhus...@freescale.com wrote:
>
>
>> -Original Message-
>> From: Linuxppc-dev [mailto:linuxppc-dev-
>> bounces+bharat.bhushan=freescale@lists.ozlabs.org] On Behalf Of Alexey
>> Kardashevskiy
>> Sent: Thursday, June 19, 2014 9:18 AM
>> To: Alex Williamson
On 06/19/2014 11:55 AM, Michael Ellerman wrote:
On Thu, 2014-06-19 at 10:18 +0800, Mike Qiu wrote:
On 06/19/2014 09:32 AM, Michael Ellerman wrote:
On Wed, 2014-06-18 at 17:02 +0800, Mike Qiu wrote:
On 06/18/2014 03:54 PM, Michael Ellerman wrote:
On Wed, 2014-06-18 at 11:27 +0800, Mike Qiu wro
> -Original Message-
> From: Linuxppc-dev [mailto:linuxppc-dev-
> bounces+bharat.bhushan=freescale@lists.ozlabs.org] On Behalf Of Alexey
> Kardashevskiy
> Sent: Thursday, June 19, 2014 9:18 AM
> To: Alex Williamson
> Cc: k...@vger.kernel.org; Nikunj A Dadhania; linux-ker...@vger.kerne
(2014/06/19 10:30), Michael Ellerman wrote:
> On Wed, 2014-06-18 at 17:46 +0900, Masami Hiramatsu wrote:
>> (2014/06/18 16:56), Michael Ellerman wrote:
>>> On Fri, 2014-06-06 at 15:38 +0900, Masami Hiramatsu wrote:
Ping?
I guess this should go to 3.16 branch, shouldn't it?
>>>
>
On Thu, 2014-06-19 at 10:18 +0800, Mike Qiu wrote:
> On 06/19/2014 09:32 AM, Michael Ellerman wrote:
> > On Wed, 2014-06-18 at 17:02 +0800, Mike Qiu wrote:
> >> On 06/18/2014 03:54 PM, Michael Ellerman wrote:
> >>> On Wed, 2014-06-18 at 11:27 +0800, Mike Qiu wrote:
> Anyone has a idea on this
On 06/19/2014 11:50 AM, Alexey Kardashevskiy wrote:
> On 06/19/2014 10:50 AM, Alexey Kardashevskiy wrote:
>> On 06/19/2014 04:35 AM, Alex Williamson wrote:
>>> On Wed, 2014-06-18 at 21:36 +1000, Alexey Kardashevskiy wrote:
VFIO exposes BARs to user space as a byte stream so userspace can
On Wed, Jun 18, 2014 at 07:26:27PM +0100, Grant Likely wrote:
>On Tue, Jun 10, 2014 at 2:56 AM, Wei Yang wrote:
>> Currently, powernv platform is not aware of VFs. This means no dev-node
>> represents a VF. Also, VF PCI device is created when PF driver want to enable
>> it. This leads to the pdn->
On 06/19/2014 09:32 AM, Michael Ellerman wrote:
On Wed, 2014-06-18 at 17:02 +0800, Mike Qiu wrote:
On 06/18/2014 03:54 PM, Michael Ellerman wrote:
On Wed, 2014-06-18 at 11:27 +0800, Mike Qiu wrote:
Anyone has a idea on this issue?
Did it ever work? If so which kernel version?
It works for 3.
On 06/19/2014 09:32 AM, Michael Ellerman wrote:
On Wed, 2014-06-18 at 17:02 +0800, Mike Qiu wrote:
On 06/18/2014 03:54 PM, Michael Ellerman wrote:
On Wed, 2014-06-18 at 11:27 +0800, Mike Qiu wrote:
Anyone has a idea on this issue?
Did it ever work? If so which kernel version?
It works for 3.
On 06/19/2014 09:32 AM, Michael Ellerman wrote:
On Wed, 2014-06-18 at 17:02 +0800, Mike Qiu wrote:
On 06/18/2014 03:54 PM, Michael Ellerman wrote:
On Wed, 2014-06-18 at 11:27 +0800, Mike Qiu wrote:
Anyone has a idea on this issue?
Did it ever work? If so which kernel version?
It works for 3.
On 06/19/2014 10:50 AM, Alexey Kardashevskiy wrote:
> On 06/19/2014 04:35 AM, Alex Williamson wrote:
>> On Wed, 2014-06-18 at 21:36 +1000, Alexey Kardashevskiy wrote:
>>> VFIO exposes BARs to user space as a byte stream so userspace can
>>> read it using pread()/pwrite(). Since this is a byte strea
On 06/19/2014 10:50 AM, Alexey Kardashevskiy wrote:
> On 06/19/2014 04:35 AM, Alex Williamson wrote:
>> On Wed, 2014-06-18 at 21:36 +1000, Alexey Kardashevskiy wrote:
>>> VFIO exposes BARs to user space as a byte stream so userspace can
>>> read it using pread()/pwrite(). Since this is a byte strea
On Wed, 2014-06-18 at 17:02 +0800, Mike Qiu wrote:
> On 06/18/2014 03:54 PM, Michael Ellerman wrote:
> > On Wed, 2014-06-18 at 11:27 +0800, Mike Qiu wrote:
> >> Anyone has a idea on this issue?
> > Did it ever work? If so which kernel version?
> It works for 3.15, but failed with linux version 3.1
On Wed, 2014-06-18 at 17:46 +0900, Masami Hiramatsu wrote:
> (2014/06/18 16:56), Michael Ellerman wrote:
> > On Fri, 2014-06-06 at 15:38 +0900, Masami Hiramatsu wrote:
> >> Ping?
> >>
> >> I guess this should go to 3.16 branch, shouldn't it?
> >
> >>> diff --git a/arch/powerpc/include/asm/types.h
On 06/19/2014 04:35 AM, Alex Williamson wrote:
> On Wed, 2014-06-18 at 21:36 +1000, Alexey Kardashevskiy wrote:
>> VFIO exposes BARs to user space as a byte stream so userspace can
>> read it using pread()/pwrite(). Since this is a byte stream, VFIO should
>> not do byte swapping and simply return
Hi Laurent,
> The commit 71ec7c55ed91 introduced the magic symbol ".TOC." for ELFv2
> ABI. This symbol is built manually and has no CRC value computed. A
> zero value is put in the CRC section to avoid modpost complaining
> about a missing CRC. Unfortunately, this breaks the kernel module
> loadi
On Tue, 17 Jun 2014 10:25:07 +0900 Joonsoo Kim wrote:
> > >v2:
> > > - Although this patchset looks very different with v1, the end result,
> > > that is, mm/cma.c is same with v1's one. So I carry Ack to patch 6-7.
> > >
> > >This patchset is based on linux-next 20140610.
> >
> > Thanks for
On Wed, 2014-06-18 at 19:26 +0100, Grant Likely wrote:
> I don't think this is the right way to handle this. Unless it is a
> fixup to a buggy devicetree provided by firmware, I don't want to see
> any code modifying the devicetree to describe stuff that is able to be
> directly enumerated. Really
On Mon, 16 Jun 2014 14:40:46 +0900 Joonsoo Kim wrote:
> PPC KVM's CMA area management requires arbitrary bitmap granularity,
> since they want to reserve very large memory and manage this region
> with bitmap that one bit for several pages to reduce management overheads.
> So support arbitrary bi
Hi Nathan and Tyrel,
I'm looking into lifecycle issues on nodes modified by OF_DYNAMIC, and
I'm hoping you can help me. Right now, pseries seems to be the only
user of OF_DYNAMIC, but making OF_DYNAMIC work has a huge impact on
the entire kernel because it requires all DT code to manage reference
On Wed, 2014-06-18 at 21:36 +1000, Alexey Kardashevskiy wrote:
> VFIO exposes BARs to user space as a byte stream so userspace can
> read it using pread()/pwrite(). Since this is a byte stream, VFIO should
> not do byte swapping and simply return values as it gets them from
> PCI device.
>
> Inste
On Tue, Jun 10, 2014 at 2:56 AM, Wei Yang wrote:
> Currently, powernv platform is not aware of VFs. This means no dev-node
> represents a VF. Also, VF PCI device is created when PF driver want to enable
> it. This leads to the pdn->pdev and pdn->pe_number an invalid value.
>
> This patch create/re
On 18.06.14 17:33, Adrian Cox wrote:
- Original Message -
From: "Christian Zigotzky"
Christian
But my opinion is, that's normal for the SB600 south bridge to
presents itself as multiple devices on the PCIe bus on x86 PCs. I
see
a lot of PCs with SB600 south bridge on the internet. An
On Wed, 2014-06-18 at 10:15 +0300, Mihai Caraman wrote:
> On vcpu schedule, the condition checked for tlb pollution is too loose.
> The tlb entries of a vcpu become polluted (vs stale) only when a different
> vcpu within the same logical partition runs in-between. Optimize the tlb
> invalidation co
> -Original Message-
> From: Mihai Caraman [mailto:mihai.cara...@freescale.com]
> Sent: Wednesday, June 18, 2014 9:15 PM
> To: kvm-...@vger.kernel.org
> Cc: k...@vger.kernel.org; linuxppc-dev@lists.ozlabs.org; Caraman Mihai
> Claudiu-
> B02008; Bhushan Bharat-R65777
> Subject: [PATCH] KV
The patch 08c9a188d0d0fc0f0c5e17d89a06bb59c493110f
kvm: powerpc: use caching attributes as per linux pte
do not handle properly the error case, letting mmu_lock locked. The lock
will further generate a RCU stall from kvmppc_e500_emul_tlbwe() caller.
In case of an error go to out label.
Si
On Friday, June 13, 2014 7:09 AM Martijn de Gouw
[mailto:martijn.de.gouw@prodrive-
technologies.com] wrote:
> Add support for mapping and unmapping of inbound rapidio windows.
>
> Signed-off-by: Martijn de Gouw
> ---
... skip ...
> +
> +int fsl_map_inb_mem(struct rio_mport *mport, dma_addr_t l
Hello Mark, thanks for your reply!
2014-06-18 17:37 GMT+04:00 Mark Rutland :
> On Wed, Jun 18, 2014 at 11:48:10AM +0100, Alexander Popov wrote:
>> Introduce a device tree binding document for the MPC512x DMA controller
>>
>> Signed-off-by: Alexander Popov
>> ---
>> .../devicetree/bindings/dma/mp
On Wed, Jun 18, 2014 at 11:48:10AM +0100, Alexander Popov wrote:
> Introduce a device tree binding document for the MPC512x DMA controller
>
> Signed-off-by: Alexander Popov
> ---
> .../devicetree/bindings/dma/mpc512x-dma.txt| 31
> ++
> 1 file changed, 31 insertions
On Thu, Jun 05, 2014 at 08:21:09PM -0700, Sukadev Bhattiprolu wrote:
SNIP
> index 7409ac8..3f97cf2 100644
> --- a/tools/perf/util/machine.c
> +++ b/tools/perf/util/machine.c
> @@ -1288,8 +1288,10 @@ static int machine__resolve_callchain_sample(struct
> machine *machine,
> {
> u8 cpumode =
On Wed, 2014-06-18 at 17:56 +1000, Alexey Kardashevskiy wrote:
> On 06/06/2014 06:44 PM, Alexey Kardashevskiy wrote:
> > Here is what I got for powernv in order to support variable page size
> > in iommu_table.
> >
> > I am very uncertain about Patch #4 "Add @it_owner to iommu_table struct"
> > an
On 06/18/2014 01:43 AM, Neelesh Gupta wrote:
+}
+
+static void __init get_sensor_index_attr(const char *name, u32 *index, char
*attr)
+{
+char *hash_pos = strchr(name, '#');
+char *dash_pos;
+u32 copy_len;
+char buf[8];
+
+memset(buf, 0, sizeof(buf));
+*index = 0;
+
VFIO exposes BARs to user space as a byte stream so userspace can
read it using pread()/pwrite(). Since this is a byte stream, VFIO should
not do byte swapping and simply return values as it gets them from
PCI device.
Instead, the existing code assumes that byte stream in read/write is
little-endi
Register the controller for device tree based lookup of DMA channels
(non-fatal for backwards compatibility with older device trees) and
provide the '#dma-cells' property in the shared mpc5121.dtsi file
Signed-off-by: Alexander Popov
---
arch/powerpc/boot/dts/mpc5121.dtsi | 1 +
drivers/dma/mpc
This patch adds a new common OF dma xlate callback function which will match a
channel by it's id. The binding expects one integer argument which it will use
to
lookup the channel by the id.
Unlike of_dma_simple_xlate this function is able to handle a system with
multiple DMA controllers. When re
Introduce a device tree binding document for the MPC512x DMA controller
Signed-off-by: Alexander Popov
---
.../devicetree/bindings/dma/mpc512x-dma.txt| 31 ++
1 file changed, 31 insertions(+)
create mode 100644 Documentation/devicetree/bindings/dma/mpc512x-dma.txt
d
This patch series introduces a device tree binding document for
the MPC512x DMA controller and adds device tree based DMA channel lookup
for it.
This version has improved device tree binding document.
Alexander Popov (3):
dmaengine: mpc512x: add device tree binding document
dmaengine: of: add
Am 18.06.14 10:57, schrieb Christian Zigotzky:
Am 18.06.14 08:51, schrieb Michael Ellerman:
On Tue, 2014-06-10 at 15:20 +0200, Christian Zigotzky wrote:
Hi All,
Could you help me to remove the changes of the PCI code, please? Or
which patches shall I remove to get the old PCI code?
Hi Christi
Am 18.06.14 08:51, schrieb Michael Ellerman:
On Tue, 2014-06-10 at 15:20 +0200, Christian Zigotzky wrote:
Hi All,
Could you help me to remove the changes of the PCI code, please? Or
which patches shall I remove to get the old PCI code?
Hi Christian,
Thanks for doing the bisect. It wasn't clea
On 06/18/2014 03:54 PM, Michael Ellerman wrote:
On Wed, 2014-06-18 at 11:27 +0800, Mike Qiu wrote:
Anyone has a idea on this issue?
Did it ever work? If so which kernel version?
It works for 3.15, but failed with linux version 3.16.0-rc1-next-20140617
The config file can be simply get from /b
(2014/06/18 16:56), Michael Ellerman wrote:
> On Fri, 2014-06-06 at 15:38 +0900, Masami Hiramatsu wrote:
>> Ping?
>>
>> I guess this should go to 3.16 branch, shouldn't it?
>
>>> diff --git a/arch/powerpc/include/asm/types.h
>>> b/arch/powerpc/include/asm/types.h
>>> index bfb6ded..8b89d65 100644
+}
+
+static void __init get_sensor_index_attr(const char *name, u32
*index, char *attr)
+{
+char *hash_pos = strchr(name, '#');
+char *dash_pos;
+u32 copy_len;
+char buf[8];
+
+memset(buf, 0, sizeof(buf));
+*index = 0;
+*attr = '\0';
+
+if (hash_pos) {
+
This patch adds basic kernel enablement for reading power values, fan
speed rpm, voltage and temperature data on powernv platforms which will
be exported to user space through sysfs interface.
Test results:
-
[root@ltctul57a-p1 ~]# sensors
ibmpowernv-isa-
Adapter: ISA adapter
fan1:
On Thu, 2014-06-12 at 16:53 +1000, Paul Mackerras wrote:
> Some people see things like "Exception: 501" in stack traces in dmesg
> and assume that means that something has gone badly wrong, when in
> fact "Exception: 501" just means a device interrupt was taken.
> This changes "Exception" to "inter
On 06/06/2014 06:44 PM, Alexey Kardashevskiy wrote:
> Here is what I got for powernv in order to support variable page size
> in iommu_table.
>
> I am very uncertain about Patch #4 "Add @it_owner to iommu_table struct"
> and wonder if there any better way to get PE from iommu_table.
>
> Please co
On Fri, 2014-06-06 at 15:38 +0900, Masami Hiramatsu wrote:
> Ping?
>
> I guess this should go to 3.16 branch, shouldn't it?
> > diff --git a/arch/powerpc/include/asm/types.h
> > b/arch/powerpc/include/asm/types.h
> > index bfb6ded..8b89d65 100644
> > --- a/arch/powerpc/include/asm/types.h
> > ++
On Wed, 2014-06-18 at 11:27 +0800, Mike Qiu wrote:
> Anyone has a idea on this issue?
Did it ever work? If so which kernel version?
Can you attach your actual .config.
You could try building without CONFIG_PPC_POWERNV.
cheers
___
Linuxppc-dev mailin
On vcpu schedule, the condition checked for tlb pollution is too loose.
The tlb entries of a vcpu become polluted (vs stale) only when a different
vcpu within the same logical partition runs in-between. Optimize the tlb
invalidation condition keeping last_vcpu per logical partition id.
With the ne
49 matches
Mail list logo
