On Mon, Apr 28, 2014 at 11:35:32PM +1000, Alexey Kardashevskiy wrote:
>On 04/23/2014 12:26 PM, Wei Yang wrote:
>> During the EEH hotplug event, iommu_add_device() will be invoked three times
>> and two of them will trigger warning or error.
>>
>> The three times to invoke the iommu_add_device() ar
> -Original Message-
> From: Wood Scott-B07421
> Sent: Tuesday, April 29, 2014 9:32 AM
> To: linuxppc-dev@lists.ozlabs.org
> Cc: Wood Scott-B07421; Liu Gang-B34182
> Subject: [PATCH] powerpc/fsl-rio: Fix fsl_rio_setup error paths and use-
> after-unmap
>
> Several of the error paths from
On Sun, 2014-04-27 at 21:59 -0700, Cody P Schafer wrote:
> On 04/27/2014 09:47 PM, Benjamin Herrenschmidt wrote:
> > On Tue, 2014-04-15 at 10:10 -0700, Cody P Schafer wrote:
> >> The catalog version number was changed from a be32 (with proceeding
> >> 32bits of padding) to a be64, update the code t
Madhavan Srinivasan writes:
> diff --git a/arch/powerpc/platforms/pseries/setup.c
> b/arch/powerpc/platforms/pseries/setup.c
> index 2db8cc6..c87e6b6 100644
> --- a/arch/powerpc/platforms/pseries/setup.c
> +++ b/arch/powerpc/platforms/pseries/setup.c
> @@ -74,6 +74,8 @@ int CMO_SecPSP = -1;
> un
Philippe Bergheaud writes:
> Anton Blanchard wrote:
>> Here are the ABIv2 patches rebased against 3.15-rc2.
>
> After recompiling 3.15-rc2 with the ABIv2 patches,
> I see the following line in Modules.symvers:
>
> 0x TOC. vmlinux EXPORT_SYMBOL
>
> Kernel will not load modules because
Several of the error paths from fsl_rio_setup are missing error
messages.
Worse, fsl_rio_setup initializes several global pointers and does not
NULL them out after freeing/unmapping on error. This caused
fsl_rio_mcheck_exception() to crash when accessing rio_regs_win which
was non-NULL but had be
powerpc: crtsaveres.o needed only when -Os flag is enabled
Currently on powerpc arch, out-of-tree module fails to build without
crtsaveres.o, even when the module has no dependency on the symbols
provided by the file; when built without the -Os flag.
BTW: '-Os' flag is
On Mon, Apr 28, 2014 at 04:39:00PM +0200, Philippe Bergheaud wrote:
> Kernel will not load modules because TOC. has no CRC.
> Is this expected ? Shouldn't TOC. have a CRC ?
TOC. is really .TOC. (The kernel build process strips off a leading
dot from symbol names.) .TOC. is a special symbol givin
Hi,
On Mon, Apr 28 2014, Stephen Warren wrote:
> The series,
> Tested-by: Stephen Warren
>
> (On an NVIDIA Tegra "Jetson TK1" board, with the patches applied on top
> of next-20140428, also with Andrew Bresticker's Tegra SDHCI patches
> "mmc: tegra: d
Having COMMAND_LINE_SIZE a kernel config option is a cleaner way to modify the
value if needed. Currently defines need to be changed within the architecture
specific header files.
The default COMMAND_LINE_SIZE for asm-generic is still set by a define in
include/asm-generic/setup.h.
Signed-off-
I'm sending this out as a RFC to get feedback and see which way folks would
like to go. Patch 1 of this patch set makes COMMAND_LINE_SIZE a seperate
config option for each architecture. However, an alternative to that would be
to create a single default size(Possibly 2048 to satisfy patchs 2 a
The powerpc architecture currently uses asm-generic to set the value of
COMMAND_LINE_SIZE. This change will allow the value of COMMAND_LINE_SIZE to be
set specifically for powerpc without affecting other architectures that may use
asm-generic.
Signed-off-by: Joseph Salisbury
---
arch/powerpc
BugLink: http://bugs.launchpad.net/bugs/1306677
While booting the PPC64EL kernel, the command line gets truncated to 512
characters. This is due to a limit of 512 defined for COMMAND_LINE_SIZE. It
would be beneficial to have a command line longer than 512 characters, as iscsi
targets and cloud
th a view to getting them merged.
The series,
Tested-by: Stephen Warren
(On an NVIDIA Tegra "Jetson TK1" board, with the patches applied on top
of next-20140428, also with Andrew Bresticker's Tegra SDHCI patches
"mmc: tegr
Anton Blanchard wrote:
Here are the ABIv2 patches rebased against 3.15-rc2.
After recompiling 3.15-rc2 with the ABIv2 patches,
I see the following line in Modules.symvers:
0x TOC. vmlinux EXPORT_SYMBOL
Kernel will not load modules because TOC. has no CRC.
Is this expected ? Should
From: Mahesh Salgaonkar
Currently we forward MCEs to guest which have been recovered by guest.
And for unhandled errors we do not deliver the MCE to guest. It looks like
with no support of FWNMI in qemu, guest just panics whenever we deliver the
recovered MCEs to guest. Also, the existig code use
From: Mahesh Salgaonkar
Currently machine check handler does not check for stack overflow for
nested machine check. If we hit another MCE while inside the machine check
handler repeatedly from same address then we get into risk of stack
overflow which can cause huge memory corruption. This patch
From: Mahesh Salgaonkar
We don't see MCE counter getting increased in /proc/interrupts which gives
false impression of no MCE occurred even when there were MCE events.
The machine check early handling was added for PowerKVM and we missed to
increment the MCE count in the early handler.
We also i
From: Mahesh Salgaonkar
Current code does not check for unhandled/unrecovered errors and return from
interrupt if it is recoverable exception which in-turn triggers same machine
check exception in a loop causing hypervisor to be unresponsive.
This patch fixes this situation and forces hypervisor
On 04/23/2014 12:26 PM, Wei Yang wrote:
> During the EEH hotplug event, iommu_add_device() will be invoked three times
> and two of them will trigger warning or error.
>
> The three times to invoke the iommu_add_device() are:
>
> pci_device_add
>...
>set_iommu_table_base_and_g
On 04/26/2014 05:12 AM, Pedro Alves wrote:
> On 04/02/2014 08:02 AM, Anshuman Khandual wrote:
>> This patch adds following new sets of ptrace request macros for transactional
>> memory expanding the existing ptrace ABI on PowerPC.
>>
>> /* TM special purpose registers */
>> PTRACE_GETTM_S
Madhavan Srinivasan wrote:
> Kirill A. Shutemov with 8c6e50b029 commit introduced
> vm_ops->map_pages() for mapping easy accessible pages around
> fault address in hope to reduce number of minor page faults.
>
> This patch creates infrastructure to modify the FAULT_AROUND_ORDER
> value using mm/Kc
On Mon, 2014-04-28 at 09:06 +, David Laight wrote:
> > Ah, yes, the stack here is obviously at a much higher address than
> 4GB.
>
> Are we talking of physical or virtual addresses here?
> (or even user?)
Real.
> Is there a re-entrancy problem using kernel static data?
Not for this code. Th
From: Li Zhong
> On Fri, 2014-04-25 at 22:18 +1000, Anton Blanchard wrote:
> > Hi,
> >
> > > When trying offline cpus, I noticed following Oops in
> > > rtas_stop_self(), and it seems caused by commit 41dd03a9. The Oops
> > > disappears after reverting this commit.
> > >
> > > After reading the cod
On Mon, Apr 28, 2014 at 02:31:29PM +0530, Madhavan Srinivasan wrote:
> +unsigned int fault_around_order = CONFIG_FAULT_AROUND_ORDER;
__read_mostly?
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
Performance data for different FAULT_AROUND_ORDER values from 4 socket
Power7 system (128 Threads and 128GB memory). perf stat with repeat of 5
is used to get the stddev values. Test ran in v3.14 kernel (Baseline) and
v3.15-rc1 for different fault around order values.
FAULT_AROUND_ORDER Basel
Kirill A. Shutemov with 8c6e50b029 commit introduced
vm_ops->map_pages() for mapping easy accessible pages around
fault address in hope to reduce number of minor page faults.
This patch creates infrastructure to modify the FAULT_AROUND_ORDER
value using mm/Kconfig. This will enable architecture ma
Kirill A. Shutemov with 8c6e50b029 commit introduced
vm_ops->map_pages() for mapping easy accessible pages around
fault address in hope to reduce number of minor page faults.
This patch creates infrastructure to modify the FAULT_AROUND_ORDER
value using mm/Kconfig. This will enable architecture ma
28 matches
Mail list logo
