On Tue, Aug 27, 2013 at 02:22:42PM +1000, Benjamin Herrenschmidt wrote:
> On Tue, 2013-08-27 at 14:19 +1000, Benjamin Herrenschmidt wrote:
> > On Mon, 2013-08-26 at 15:37 +0300, Gleb Natapov wrote:
> > > > Gleb, any chance you can put this (and the next one) into a tree to
> > > > "lock in" the num
/proc/powerpc/lparcfg is an ancient facility (though still actively used)
which allows access to some informations relative to the partition when
running underneath a PAPR compliant hypervisor.
It makes no sense on non-pseries machines. However, currently, not only
can it be created on these if th
On Tue, Aug 27, 2013 at 02:19:58PM +1000, Benjamin Herrenschmidt wrote:
> On Mon, 2013-08-26 at 15:37 +0300, Gleb Natapov wrote:
> > > Gleb, any chance you can put this (and the next one) into a tree to
> > > "lock in" the numbers ?
> > >
> > Applied it. Sorry for slow response, was on vocation an
On 64-bit, __pa(&static_var) gets miscompiled by recent versions of
gcc as something like:
addis 3,2,.LANCHOR1+4611686018427387904@toc@ha
addi 3,3,.LANCHOR1+4611686018427387904@toc@l
This ends up effectively ignoring the offset, since its bottom 32 bits
are zero, and means that th
The "rmci" stuff only exists on 64-bit
Signed-off-by: Benjamin Herrenschmidt
---
arch/powerpc/kernel/btext.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/powerpc/kernel/btext.c b/arch/powerpc/kernel/btext.c
index 0428992..41c011c 100644
--- a/arch/powerpc/kernel/b
On Friday 23 August 2013 04:47 AM, Luck, Tony wrote:
<1>[ 383.209057] RIP [] sysrq_handle_crash+0x16/0x20
<4>[ 383.209057] RSP
<4>[ 383.209057] CR2:
<4>[ 383.209057] ---[ end trace 04a1cddad37b4b33 ]---
<3>[ 383.209057] pstore: compression failed for Part 2 returned -5
<3
On Tue, 2013-08-27 at 14:19 +1000, Benjamin Herrenschmidt wrote:
> On Mon, 2013-08-26 at 15:37 +0300, Gleb Natapov wrote:
> > > Gleb, any chance you can put this (and the next one) into a tree to
> > > "lock in" the numbers ?
> > >
> > Applied it. Sorry for slow response, was on vocation and still
On Mon, 2013-08-26 at 15:37 +0300, Gleb Natapov wrote:
> > Gleb, any chance you can put this (and the next one) into a tree to
> > "lock in" the numbers ?
> >
> Applied it. Sorry for slow response, was on vocation and still go
> through the email backlog.
Thanks. Since it's not in a topic branch
On Mon, 2013-08-19 at 21:53 -0500, Nathan Fontenot wrote:
> Previous commit 46723bfa540... introduced a new config option
> HAVE_BOOTMEM_INFO_NODE that ended up breaking memory hot-remove for ppc
> when sparse vmemmap is not defined.
>
> This patch defines HAVE_BOOTMEM_INFO_NODE for ppc and adds t
Hi Rafael,
Today's linux-next merge of the pm tree got a conflict in
arch/powerpc/kernel/prom.c between commit dc0e643afc50 ("powerpc: Make
prom.c device tree accesses endian safe") from the powerpc tree and
commits 819d596568d8 ("powerpc: refactor of_get_cpu_node to support other
architectures")
> > > > + };
> > > > + pll1: pll1@820 {
> > > > + #clock-cells = <1>;
> > > > + reg = <0x820>;
> > > > + compatible = "fsl,core-pll-clock";
> > > > + clocks = <&clockgen>;
> > > > +
On Fri, Aug 23, 2013 at 08:13:53PM +0100, Mark Brown wrote:
> On Fri, Aug 23, 2013 at 01:08:28PM -0600, Stephen Warren wrote:
> > On 08/23/2013 02:04 AM, Nicolin Chen wrote:
> > > This patch implements a device-tree-only machine driver for Freescale
> > > i.MX series Soc. It works with spdif_transm
On Mon, 2013-08-26 at 11:53 -0700, Eugene Surovegin wrote:
> This solves a problem observed in kexec'ed kernel where 200ms timeout is
> too short and bootconsole fails to initialize. Console did eventually
> become workable but much later into the boot process.
>
> Observed timeout was around 260m
On Mon, 2013-08-26 at 20:29 +0200, Martin Hinner wrote:
> On Mon, Aug 26, 2013 at 7:14 PM, Scott Wood wrote:
> >> that kernel must be at location 0. Another problem was that interrupts
> >> got re-enabled during execution of my bootloader (I am doing some
> >> syscalls -> goes to Cisco rom),
> >
From: Mahesh Salgaonkar
Add basic error handling in machine check exception handler.
- If MSR_RI isn't set, we can not recover.
- Check if disposition set to OpalMCE_DISPOSITION_RECOVERED.
- Check if address at fault is inside kernel address space, if not then send
SIGBUS to process if we hit
From: Mahesh Salgaonkar
When machine check real mode handler can not continue into host kernel
in V mode, it returns from the interrupt and we loose MCE event which
never gets logged. In such a situation queue up the MCE event so that
we can log it later when we get back into host kernel with r1
From: Mahesh Salgaonkar
Now that we are ready to handle machine check directly in linux, do not
register with firmware to handle machine check exception.
Signed-off-by: Mahesh Salgaonkar
---
arch/powerpc/platforms/powernv/opal.c |8 ++--
1 file changed, 2 insertions(+), 6 deletions(-)
From: Mahesh Salgaonkar
Now that we handle machine check in linux, the MCE decoding should also
take place in linux host. This info is crucial to log before we go down
in case we can not handle the machine check errors. This patch decodes
and populates a machine check event which contain high lev
From: Mahesh Salgaonkar
This patch handles the memory errors on power8. If we get a machine check
exception due to SLB or TLB errors, then flush SLBs/TLBs and reload SLBs to
recover.
Signed-off-by: Mahesh Salgaonkar
---
arch/powerpc/include/asm/mce.h |3 +++
arch/powerpc/kernel/cputable.c
From: Mahesh Salgaonkar
If we get a machine check exception due to SLB or TLB errors, then flush
SLBs/TLBs and reload SLBs to recover. We do this in real mode before turning
on MMU. Otherwise we would run into nested machine checks.
If we get a machine check when we are in guest, then just flush
From: Mahesh Salgaonkar
This patch introduces flush_tlb operation in cpu_spec structure. This will
help us to invoke appropriate CPU-side flush tlb routine. This patch
adds the foundation to invoke CPU specific flush routine for respective
architectures. Currently this patch introduce flush_tlb f
From: Mahesh Salgaonkar
This patch adds the early machine check function pointer in cputable for
CPU specific early machine check handling. The early machine handle routine
will be called in real mode to handle SLB and TLB errors. This patch just
sets up a mechanism invoke CPU specific handler. T
From: Mahesh Salgaonkar
We can get machine checks from any context. We need to make sure that
we handle all of them correctly. Once we decode MCE reason and generate
MCE event, we continue in host kernel in virtual mode so that we can
log/display it later. But before going to virtual mode we need
From: Mahesh Salgaonkar
Move machine check entry point into Linux. So far we were dependent on
firmware to decode MCE error details and handover the high level info to OS.
This patch introduces early machine check routine that saves the MCE
information (srr1, srr0, dar and dsisr) to the emergenc
From: Mahesh Salgaonkar
This patch introduces exclusive emergency stack for machine check exception.
We use emergency stack to handle machine check exception so that we can save
MCE information (srr1, srr0, dar and dsisr) before turning on ME bit and be
ready for re-entrancy. This helps us to pre
From: Mahesh Salgaonkar
This patch splits the common exception prolog logic into two parts to
facilitate reuse of existing code in the next patch. The second part will
be reused in the machine check exception routine in the next patch.
Please note that this patch does not introduce or change exi
Hi,
Please find the patch set that performs the machine check handling inside linux
host. The design is to be able to handle re-entrancy so that we do not clobber
the machine check information during nested machine check interrupt.
The patch 2 introduces separate emergency stack in paca structure
This solves a problem observed in kexec'ed kernel where 200ms timeout is
too short and bootconsole fails to initialize. Console did eventually
become workable but much later into the boot process.
Observed timeout was around 260ms, but I decided to make it a little bigger
for more reliability.
Th
On Mon, Aug 26, 2013 at 7:14 PM, Scott Wood wrote:
>> that kernel must be at location 0. Another problem was that interrupts
>> got re-enabled during execution of my bootloader (I am doing some
>> syscalls -> goes to Cisco rom),
> Do you mean you're calling into the rom after Linux has already st
On Sat, 2013-08-24 at 19:15 +0200, Martin Hinner wrote:
> Hello again,
>
> just a quick update: I have spent some more time on this and now I
> can boot into kernel (it works even with initramfs and simple assembly
> HelloWorld, so it's time to compile userland now). The problem was
> that kerne
On Sun, 2013-08-25 at 21:42 -0500, Tang Yuantian-B29983 wrote:
> > >
> > > clockgen: global-utilities@e1000 {
> > > - compatible = "fsl,b4420-clockgen", "fsl,qoriq-clockgen-2.0";
> > > + compatible = "fsl,b4420-clockgen", "fsl,qoriq-clockgen-2.0",
> > > +
On Mon, 2013-08-26 at 09:03 +0800, Zhang Haijun wrote:
> On 08/23/2013 11:40 PM, Scott Wood wrote:
>
> > On Fri, 2013-08-23 at 14:39 +0800, Zhang Haijun wrote:
> > > Hi, Anton and all
> > >
> > > Is there any advice on these two patches ?
> > >
> > > [PATCH 2/4 V2] mmc: esdhc: workaround for dma
On Fri, 2013-08-23 at 20:07 -0500, Scott Wood wrote:
> The following changes since commit afbcdd97bf117bc2d01b865a32f78f662437a4d8:
>
> powerpc/wsp: Fix early debug build (2013-08-16 10:59:27 +1000)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git
On Wed, Aug 14, 2013 at 10:51:14AM +1000, Benjamin Herrenschmidt wrote:
> On Thu, 2013-08-01 at 14:44 +1000, Alexey Kardashevskiy wrote:
> > This is to reserve a capablity number for upcoming support
> > of H_PUT_TCE_INDIRECT and H_STUFF_TCE pseries hypercalls
> > which support mulptiple DMA map/un
Alexander Graf writes:
> On 26.08.2013, at 05:28, Aneesh Kumar K.V wrote:
>
>> Alexander Graf writes:
>>
>>> On 23.08.2013, at 04:31, Aneesh Kumar K.V wrote:
>>>
Alexander Graf writes:
> On 22.08.2013, at 12:37, Aneesh Kumar K.V wrote:
>
>> From: "Aneesh Kumar K.V"
>>
On 26.08.2013, at 05:28, Aneesh Kumar K.V wrote:
> Alexander Graf writes:
>
>> On 23.08.2013, at 04:31, Aneesh Kumar K.V wrote:
>>
>>> Alexander Graf writes:
>>>
On 22.08.2013, at 12:37, Aneesh Kumar K.V wrote:
> From: "Aneesh Kumar K.V"
Isn't this you?
>>>
>>> Ye
On 08/25/2013 12:19 PM, Chris Ball wrote:
Hi Haijun,
On Sun, Aug 11 2013, Haijun Zhang wrote:
Using function mmc_of_parse_voltage() to get voltage-ranges.
Signed-off-by: Haijun Zhang
The patchset contains patches 1-3 of 3, and also this unnumbered patch
v3. Which order should I use to apply
On 08/26/2013 09:03 AM, Zhang Haijun wrote:
On 08/23/2013 11:40 PM, Scott Wood wrote:
On Fri, 2013-08-23 at 14:39 +0800, Zhang Haijun wrote:
Hi, Anton and all
Is there any advice on these two patches ?
[PATCH 2/4 V2] mmc: esdhc: workaround for dma err in the last system
transaction
[PATCH 3/4
On 08/23/2013 11:40 PM, Scott Wood wrote:
On Fri, 2013-08-23 at 14:39 +0800, Zhang Haijun wrote:
Hi, Anton and all
Is there any advice on these two patches ?
[PATCH 2/4 V2] mmc: esdhc: workaround for dma err in the last system
transaction
[PATCH 3/4 V3] mmc: esdhc: Correct host version of T424
Hi All,
First of all thank you all for taking your time out to reply
On Fri, Aug 23, 2013 at 3:59 AM, Ira W. Snyder wrote:
> On Thu, Aug 22, 2013 at 02:43:38PM -0700, David Hawkins wrote:
> > Hi S.Saravanan,
> >
> > > I have a custom board with four MPC8640 nodes connected over
> >
On 08/23/2013 11:17 AM, Hongbo Zhang wrote:
On 08/22/2013 07:16 AM, Stephen Warren wrote:
On 08/21/2013 05:00 PM, Scott Wood wrote:
On Wed, 2013-08-21 at 16:40 -0600, Stephen Warren wrote:
On 07/29/2013 04:49 AM, hongbo.zh...@freescale.com wrote:
+- reg :
+- int
On Sat, Aug 24, 2013 at 10:14:06PM +0200, Yann Droneaud wrote:
> Hi,
>
> Following a patchset asking to change calls to get_unused_flag() [1]
> to use O_CLOEXEC, Alex Williamson [2][3] decided to change VFIO
> to use the flag.
>
> Since it's a related subsystem to KVM, using O_CLOEXEC for
> file
Le 26.08.2013 09:39, Paolo Bonzini a écrit :
Il 25/08/2013 17:04, Alexander Graf ha scritto:
On 24.08.2013, at 21:14, Yann Droneaud wrote:
This patch set O_CLOEXEC flag on all file descriptors created
with anon_inode_getfd() to not leak file descriptors across exec().
Signed-off-by: Yann Dro
Il 26/08/2013 10:23, Yann Droneaud ha scritto:
>
> Sounds a lot like InfiniBand subsystem behavor: IB file descriptors
> are of no use accross exec() since memory mappings tied to those fds
> won't be available in the new process:
>
> https://lkml.org/lkml/2013/7/8/380
> http://mid.gmane.org/f585
Il 25/08/2013 17:04, Alexander Graf ha scritto:
>
> On 24.08.2013, at 21:14, Yann Droneaud wrote:
>
>> KVM uses anon_inode_get() to allocate file descriptors as part
>> of some of its ioctls. But those ioctls are lacking a flag argument
>> allowing userspace to choose options for the newly opened
45 matches
Mail list logo
