Signed-off-by: Nicholas Piggin
---
include/linux/nmi.h | 3 ---
1 file changed, 3 deletions(-)
diff --git a/include/linux/nmi.h b/include/linux/nmi.h
index aa3cd0878270..5e2e57536d98 100644
--- a/include/linux/nmi.h
+++ b/include/linux/nmi.h
@@ -12,9 +12,6 @@ extern void touch_softlockup_watchdo
This is the latest series to make the hardlockup watchdog more
easily replaceable by arch code. The last patch provides some
justification for why we want to do this (existing sparc watchdog
is another that could benefit).
Since last time, we tidied up the Kconfig approach so it was not
so jumbled
"Naveen N. Rao" writes:
> diff --git a/arch/powerpc/kernel/exceptions-64s.S
> b/arch/powerpc/kernel/exceptions-64s.S
> index ae418b85c17c..17ee701b8336 100644
> --- a/arch/powerpc/kernel/exceptions-64s.S
> +++ b/arch/powerpc/kernel/exceptions-64s.S
> @@ -1442,7 +1440,9 @@ do_hash_page:
>
> /*
Ravi Bangoria writes:
> When a kthread makes a call_usermodehelper() call the steps are:
> a. allocates current->mm
> b. load_elf_binary()
> c. populates current->thread.regs
>
> While doing this, interrupts are not disabled. If there is a perf
> interrupt in the middle of this process (i.e. s
Works like a charm with Milian's patch.
Acked-by: Ravi Bangoria
Note:
I still see very minor differences between libunwind and libdw. Also, second
last
function gets repeated two times in every callchain but it can be fixed later
on.
Otherwise all looks good!
Thanks,
-Ravi
On Thursday 15 Jun
Hi all,
On Fri, 16 Jun 2017 11:13:35 +1000 Stephen Rothwell
wrote:
>
> On Fri, 16 Jun 2017 10:57:22 +1000 Michael Ellerman
> wrote:
> >
> > "Rowand, Frank" writes:
> >
> > > On Thursday, June 15, 2017 2:25 AM, Abdul Haleem
> > > [mailto:abdha...@linux.vnet.ibm.com] wrote:
> > >>
> >
Thanks Naveen,
On Thursday 15 June 2017 08:57 PM, Naveen N. Rao wrote:
> Hmm... are you sure it's the same issue? The above commit only went into
> v4.7, which means we weren't able to use --call-graph=dwarf till v4.7.
Yes sorry. It's from v4.7 onwards.
-Ravi
Hi Michael,
On Fri, 16 Jun 2017 10:57:22 +1000 Michael Ellerman wrote:
>
> "Rowand, Frank" writes:
>
> > On Thursday, June 15, 2017 2:25 AM, Abdul Haleem
> > [mailto:abdha...@linux.vnet.ibm.com] wrote:
> >>
> >> On Thu, 2017-06-15 at 11:30 +0530, Abdul Haleem wrote:
> >>>
> >>> linux-next
"Rowand, Frank" writes:
> On Thursday, June 15, 2017 2:25 AM, Abdul Haleem
> [mailto:abdha...@linux.vnet.ibm.com] wrote:
>>
>> On Thu, 2017-06-15 at 11:30 +0530, Abdul Haleem wrote:
>>> Hi,
>>>
>>> linux-next fails to boot on powerpc Bare-metal with these warnings.
>>>
>>> machine booted fine o
On Thu, Jun 08, 2017 at 03:25:56PM +0200, Christoph Hellwig wrote:
> This implementation is simply bogus - hexagon only has a simple
> direct mapped DMA implementation and thus doesn't care about the
> address.
>
> Signed-off-by: Christoph Hellwig
> ---
> arch/hexagon/include/asm/dma-mapping.h |
On Thu, Jun 08, 2017 at 03:25:42PM +0200, Christoph Hellwig wrote:
> Signed-off-by: Christoph Hellwig
> ---
> arch/hexagon/include/asm/dma-mapping.h | 2 --
> arch/hexagon/kernel/dma.c | 12 +---
> arch/hexagon/kernel/hexagon_ksyms.c| 1 -
> 3 files changed, 9 insertion
On Thu, 2017-06-15 at 17:06 +, Rowand, Frank wrote:
> On Thursday, June 15, 2017 2:25 AM, Abdul Haleem
> [mailto:abdha...@linux.vnet.ibm.com] wrote:
> >
> > On Thu, 2017-06-15 at 11:30 +0530, Abdul Haleem wrote:
> > > Hi,
> > >
> > > linux-next fails to boot on powerpc Bare-metal with these
On Wed, 2017-06-14 at 04:47:50 UTC, Alistair Popple wrote:
> "4c3b89e powerpc/powernv: Add sanity checks to pnv_pci_get_{gpu|npu}_dev"
> introduced explicit warnings in pnv_pci_get_npu_dev() when a PCIe device
> has no associated device-tree node. However not all PCIe devices have an
> of_node and
On Wed, 2017-06-14 at 00:19:25 UTC, Benjamin Herrenschmidt wrote:
> Architecturally we should apply a 0x400 offset for these. Not doing
> it will break future HW implementations.
>
> Signed-off-by: Benjamin Herrenschmidt
Applied to powerpc fixes, thanks.
https://git.kernel.org/powerpc/c/2564270
The at24 driver allows to register I2C EEPROM chips using different vendor
and devices, but the I2C subsystem does not take the vendor into account
when matching using the I2C table since it only has device entries.
But when matching using an OF table, both the vendor and device has to be
taken in
The at24 driver allows to register I2C EEPROM chips using different vendor
and devices, but the I2C subsystem does not take the vendor into account
when matching using the I2C table since it only has device entries.
But when matching using an OF table, both the vendor and device has to be
taken in
The at24 driver allows to register I2C EEPROM chips using different vendor
and devices, but the I2C subsystem does not take the vendor into account
when matching using the I2C table since it only has device entries.
But when matching using an OF table, both the vendor and device has to be
taken in
The at24 driver allows to register I2C EEPROM chips using different vendor
and devices, but the I2C subsystem does not take the vendor into account
when matching using the I2C table since it only has device entries.
But when matching using an OF table, both the vendor and device has to be
taken in
The at24 driver allows to register I2C EEPROM chips using different vendor
and devices, but the I2C subsystem does not take the vendor into account
when matching using the I2C table since it only has device entries.
But when matching using an OF table, both the vendor and device has to be
taken in
Hello Wolfram,
This series is a follow-up to patch [0] that added an OF device ID table
to the at24 EEPROM driver. As you suggested [1], this version instead of
adding entries for every used tuple, only adds a single
entry for each chip type using the "atmel" vendor as a generic fallback.
The fi
On Thursday, June 15, 2017 2:25 AM, Abdul Haleem
[mailto:abdha...@linux.vnet.ibm.com] wrote:
>
> On Thu, 2017-06-15 at 11:30 +0530, Abdul Haleem wrote:
>> Hi,
>>
>> linux-next fails to boot on powerpc Bare-metal with these warnings.
>>
>> machine booted fine on next-20170613
>
> Thanks Michael, Y
On 2017/06/15 09:46AM, Anton Blanchard wrote:
> From: Anton Blanchard
>
> From POWER4 onwards, mfocrf() only places the specified CR field into
> the destination GPR, and the rest of it is set to 0. The PowerPC AS
> from version 3.0 now requires this behaviour.
>
> The emulation code currently p
On 2017/06/15 09:46AM, Anton Blanchard wrote:
> From: Anton Blanchard
>
> The mcrf emulation code was looking at the CR fields in the reverse
> order. It also relied on reserved fields being zero which is somewhat
> fragile, so fix that too.
Yikes! Amazing catch!
Acked-by: Naveen N. Rao
Thanks
On Wed, 2017-06-07 at 22:49 -0300, Thiago Jung Bauermann wrote:
> These changes are too small to warrant their own patches:
>
> The keyid and sig_size members of struct signature_v2_hdr are in BE format,
> so use a type that makes this assumption explicit. Also, use beXX_to_cpu
> instead of __beXX
On Wed, 2017-06-07 at 22:49 -0300, Thiago Jung Bauermann wrote:
> If the file doesn't have an xattr, ima_appraise_measurement sets cause to
> "missing-hash" while if there's an xattr but it's a digest instead of a
> signature it sets cause to "IMA-signature-required".
>
> Fix it by setting cause t
On Wed, 2017-06-07 at 22:49 -0300, Thiago Jung Bauermann wrote:
> If the func_tokens array uses the same indices as enum ima_hooks,
> policy_func_show can be a lot simpler, and the func_* enum becomes
> unnecessary.
>
> Also, if we use the same macro trick used by kernel_read_file_id_str we can
>
On 2017/06/15 09:19PM, Michael Ellerman wrote:
> "Naveen N. Rao" writes:
>
> > diff --git a/arch/powerpc/kernel/trace/ftrace_64_mprofile.S
> > b/arch/powerpc/kernel/trace/ftrace_64_mprofile.S
> > index fa0921410fa4..e6837e85ec28 100644
> > --- a/arch/powerpc/kernel/trace/ftrace_64_mprofile.S
> >
On 2017/06/15 07:16PM, Ravi Bangoria wrote:
> When a kthread makes a call_usermodehelper() call the steps are:
> a. allocates current->mm
> b. load_elf_binary()
> c. populates current->thread.regs
>
> While doing this, interrupts are not disabled. If there is a perf
> interrupt in the middle of
When a kthread makes a call_usermodehelper() call the steps are:
a. allocates current->mm
b. load_elf_binary()
c. populates current->thread.regs
While doing this, interrupts are not disabled. If there is a perf
interrupt in the middle of this process (i.e. step 'a' has completed
but not yet rea
Salut Christophe,
A few comments below, nothing major...
Le 14/06/2017 à 15:29, Christophe Lombard a écrit :
This patch exports a in-kernel 'library' API which can be called by
other drivers to help interacting with an IBM XSL on a POWER9 system.
The XSL (Translation Service Layer) is a stripp
On Thu, Jun 01, 2017 at 12:24:41PM +0200, Paolo Bonzini wrote:
> Porting PPC to libdw only needs an architecture-specific hook to move
> the register state from perf to libdw.
>
> The ARM and x86 architectures already use libdw, and it is useful to
> have as much common code for the unwinder as po
On Tue, 13 Jun 2017 23:05:51 +1000
Nicholas Piggin wrote:
> Idle code now always runs at the 0xc... effective address whether
> in real or virtual mode. This means rfid can be ditched, along
> with a lot of SRR manipulations.
>
> In the wakeup path, carry SRR1 around in r12. Use mtmsrd to change
"Naveen N. Rao" writes:
> diff --git a/arch/powerpc/kernel/trace/ftrace_64_mprofile.S
> b/arch/powerpc/kernel/trace/ftrace_64_mprofile.S
> index fa0921410fa4..e6837e85ec28 100644
> --- a/arch/powerpc/kernel/trace/ftrace_64_mprofile.S
> +++ b/arch/powerpc/kernel/trace/ftrace_64_mprofile.S
> @@ -9
On Thu, 2017-06-15 at 10:46 +0200, Milian Wolff wrote:
> Just a quick question: Have you guys applied my recent patch:
>
> commit 5ea0416f51cc93436bbe497c62ab49fd9cb245b6
> Author: Milian Wolff
> Date: Thu Jun 1 23:00:21 2017 +0200
>
> perf report: Include partial stacks unwound with libdw
On Thu, 2017-06-15 at 19:25 +1000, Michael Ellerman wrote:
> Alexey Kardashevskiy writes:
>
> > From: Yongji Xie
> >
> > Any IODA host bridge have the capability of IRQ remapping.
> > So we set PCI_BUS_FLAGS_MSI_REMAP when this kind of host birdge
> > is detected.
>
> Where's the code that act
On Thu, 2017-06-15 at 16:28 +1000, Michael Ellerman wrote:
> This reverts commit 45cb08f4791ce6a15c54598b4cb73db4b4b8294f.
>
> For some reason this is causing IRQ problems on Freescale Book3E
> machines, eg on my p5020ds:
This looks like a driver bug it could be that you get hammered by
an in
On Tuesday, June 13, 2017 5:55:09 PM CEST Ravi Bangoria wrote:
> Hi Mark,
>
> On Tuesday 13 June 2017 05:14 PM, Mark Wielaard wrote:
> > I see the same on very short runs. But when doing a slightly longer run,
> > even just using ls -lahR, which does some more work, then I do see user
> > backtrac
Nicholas Piggin writes:
> diff --git a/arch/powerpc/kernel/process.c b/arch/powerpc/kernel/process.c
> index baae104b16c7..f587c1fdf981 100644
> --- a/arch/powerpc/kernel/process.c
> +++ b/arch/powerpc/kernel/process.c
> @@ -1960,11 +1960,25 @@ void show_stack(struct task_struct *tsk, unsigned
>
On Thu, 2017-06-15 at 11:30 +0530, Abdul Haleem wrote:
> Hi,
>
> linux-next fails to boot on powerpc Bare-metal with these warnings.
>
> machine booted fine on next-20170613
Thanks Michael, Yes it is (75fe04e59 of: remove *phandle properties from
expanded device tree)
Frank, would you please ta
Alexey Kardashevskiy writes:
> From: Yongji Xie
>
> Any IODA host bridge have the capability of IRQ remapping.
> So we set PCI_BUS_FLAGS_MSI_REMAP when this kind of host birdge
> is detected.
Where's the code that actually enforces this property?
It would be good to have a comment in pnv_pci_i
On Thu, Jun 15, 2017 at 04:47:29PM +1000, Anton Blanchard wrote:
> > Maybe there should be (inline)
> > helper function to insert/extract CR fields?
>
> That would be nice, there are quite a few places that could use it.
Like patch 2/2, hint hint.
Segher
41 matches
Mail list logo
