abled
section")
Signed-off-by: Sebastian Andrzej Siewior
---
arch/powerpc/perf/imc-pmu.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/powerpc/perf/imc-pmu.c b/arch/powerpc/perf/imc-pmu.c
index 9d229ef7f86ef..ada817c49b722 100644
--- a/arch/powerpc/perf/imc-pmu.c
The RTAS work area allocator is using the generic memory allocator and
as such it must select it.
Select the generic memory allocator on pseries.
Fixes: 43033bc62d349 ("powerpc/pseries: add RTAS work area allocator")
Signed-off-by: Sebastian Andrzej Siewior
---
arch/powerpc/platfor
On 2022-09-01 16:24:09 [-0400], Kent Overstreet wrote:
> > --- a/include/linux/mmap_lock.h
> > +++ b/include/linux/mmap_lock.h
> > @@ -60,6 +60,18 @@ static inline void __mmap_lock_trace_released(struct
> > mm_struct *mm, bool write)
> >
> > #endif /* CONFIG_TRACING */
> >
> > +static inline
On 2022-06-15 17:41:45 [+0200], Arnd Bergmann wrote:
> Applied to the asm-generic tree with the above fixup, thanks!
Thank you Arnd.
> Arnd
Sebastian
Andrzej Siewior
---
Initially I aimed only for the asm-generic bits and arm since I have
most bits of the port ready. Arnd then suggested to do all arches at
once and here it is.
I tried to keep it minimal in sense that I didn't remove the dedicated
softirq-stacks on parisc or powerpc for instance
On 2022-06-09 15:46:04 [+], David Laight wrote:
> From: Sebastian Andrzej Siewior
> > Sent: 09 June 2022 16:03
> >
> > On 2022-05-30 16:15:11 [-0700], Davidlohr Bueso wrote:
> > > Tasklets have long been deprecated as being too heavy on the system
&
On 2022-05-30 16:15:11 [-0700], Davidlohr Bueso wrote:
> Tasklets have long been deprecated as being too heavy on the system
> by running in irq context - and this is not a performance critical
> path. If a higher priority process wants to run, it must wait for
> the tasklet to finish before doing
On 2022-05-30 16:15:10 [-0700], Davidlohr Bueso wrote:
> diff --git a/drivers/scsi/ibmvscsi/ibmvfc.c b/drivers/scsi/ibmvscsi/ibmvfc.c
> index d0eab5700dc5..31b1900489e7 100644
> --- a/drivers/scsi/ibmvscsi/ibmvfc.c
> +++ b/drivers/scsi/ibmvscsi/ibmvfc.c
> @@ -891,7 +891,7 @@ static void
On 2022-05-30 16:15:08 [-0700], Davidlohr Bueso wrote:
> diff --git a/drivers/scsi/ibmvscsi_tgt/ibmvscsi_tgt.c
> b/drivers/scsi/ibmvscsi_tgt/ibmvscsi_tgt.c
> index eee1a24f7e15..fafadb7158a3 100644
> --- a/drivers/scsi/ibmvscsi_tgt/ibmvscsi_tgt.c
> +++ b/drivers/scsi/ibmvscsi_tgt/ibmvscsi_tgt.c
>
ernel.org
Cc: linux...@vger.kernel.org
Cc: linux-xte...@linux-xtensa.org
Cc: linuxppc-dev@lists.ozlabs.org
Signed-off-by: Sebastian Andrzej Siewior
---
arch/alpha/include/asm/spinlock_types.h | 2 +-
arch/arm/include/asm/spinlock_types.h| 2 +-
arch/arm64/include/asm/spinlock_t
On 2021-08-03 17:30:40 [+0200], Hans de Goede wrote:
> Hi Sebastien,
Hi Hans,
> On 8/3/21 4:15 PM, Sebastian Andrzej Siewior wrote:
> > This is a tree wide replacement of the deprecated CPU hotplug functions
> > which are only wrappers around the actual functions.
&
This is a tree wide replacement of the deprecated CPU hotplug functions
which are only wrappers around the actual functions.
Each patch is independent and can be picked up by the relevant maintainer.
Cc: Alexander Shishkin
Cc: Amit Kucheria
Cc: Andrew Morton
Cc: Andy Lutomirski
Cc: Arnaldo
: Benjamin Herrenschmidt
Cc: Paul Mackerras
Cc: linuxppc-dev@lists.ozlabs.org
Cc: kvm-...@vger.kernel.org
Signed-off-by: Sebastian Andrzej Siewior
---
arch/powerpc/kernel/rtasd.c | 4 ++--
arch/powerpc/kvm/book3s_hv_builtin.c | 10 +-
arch/powerpc/platforms/powernv/idle.c
of linear_mapping_mutex to ifdef block where it is
used.
Fixes: 1f73ad3e8d755 ("powerpc/mm: print warning in
arch_remove_linear_mapping()")
Signed-off-by: Sebastian Andrzej Siewior
---
arch/powerpc/mm/mem.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/powerpc/
On 2021-01-09 01:33:52 [+0100], Thomas Bogendoerfer wrote:
> On Sat, Jan 09, 2021 at 12:58:05AM +0100, Thomas Bogendoerfer wrote:
> > On Fri, Jan 08, 2021 at 08:20:43PM +, Paul Cercueil wrote:
> > > Hi Thomas,
> > >
> > > 5.11 does not boot anymore on Ingenic SoCs, I bisected it to this
On 2020-11-12 09:10:34 [+0100], Marek Szyprowski wrote:
> I can do more tests to help fixing this issue. Just let me know what to do.
-> https://lkml.kernel.org/r/87y2j6n8mj@nanos.tec.linutronix.de
Sebastian
be conveyed in an argument passed by the caller,
which usually knows the context.
Use the `sched_napi' argument passed by the callback. It is set true if
called from the interrupt handler and NAPI should be scheduled.
Signed-off-by: Sebastian Andrzej Siewior
Cc: "Horia Geantă"
Cc: Aymen S
be conveyed in an argument passed by the caller,
which usually knows the context.
Use the `sched_napi' argument passed by the callback. It is set true if
called from the interrupt handler and NAPI should be scheduled.
Signed-off-by: Sebastian Andrzej Siewior
Cc: "Horia Geantă"
Cc: Aymen S
er including
`qman_cb_dqrr' typedef which is used by the dpaa and the crypto driver.
Signed-off-by: Sebastian Andrzej Siewior
Cc: "Horia Geantă"
Cc: Aymen Sghaier
Cc: Herbert XS
Cc: "David S. Miller"
Cc: Madalin Bucur
Cc: Jakub Kicinski
Cc: Li Yang
Cc: linu
On 2020-10-31 10:12:15 [-0700], Jakub Kicinski wrote:
> Nit: some networking drivers have a bool napi which means "are we
> running in napi context", the semantics here feel a little backwards,
> at least to me. But if I'm the only one thinking this, so be it.
I renamed it to `sched_napi'.
er including
`qman_cb_dqrr' typedef which is used by the dpaa and the crypto driver.
Signed-off-by: Sebastian Andrzej Siewior
Cc: "Horia Geantă"
Cc: Aymen Sghaier
Cc: Herbert Xu
Cc: "David S. Miller"
Cc: Madalin Bucur
Cc: Jakub Kicinski
Cc: Li Yang
Cc: linu
be conveyed in an argument passed by the caller,
which usually knows the context.
Use the `napi' argument passed by the callback. It is set true if
called from the interrupt handler and NAPI should be scheduled.
Signed-off-by: Sebastian Andrzej Siewior
Cc: "Horia Geantă"
Cc: Aymen Sghaier
Cc:
t_coex_supported_feature()
None of these have a caller. Welcome to the wonderful world of HALs and
onion layers.
Remove in_interrupt() check.
Signed-off-by: Sebastian Andrzej Siewior
Cc: Ping-Ke Shih
Cc: Kalle Valo
Cc: "David S. Miller"
Cc: Jakub Kicinski
Cc: linux-wirel...@vger.ker
be conveyed in an argument passed by the caller,
which usually knows the context.
Use the `napi' argument passed by the callback. It is set true if
called from the interrupt handler and NAPI should be scheduled.
Signed-off-by: Sebastian Andrzej Siewior
Cc: "Horia Geantă"
Cc: Aymen Sghaier
Cc:
pointless to
invoke schedule() if there is no request to reschedule.
Pass the may_sleep condition through the various call chains leading to
issuecommand().
Signed-off-by: Sebastian Andrzej Siewior
Cc: Kalle Valo
Cc: "David S. Miller"
Cc: Jakub Kicinski
Cc: linux-wirel...@vger.kernel.o
the code further use list_empty() instead of walking the list
and counting the entries just to check the count for > 0 at the end.
Signed-off-by: Sebastian Andrzej Siewior
Cc: Ping-Ke Shih
Cc: Kalle Valo
Cc: "David S. Miller"
Cc: Jakub Kicinski
Cc: linux-wirel...@vger.kerne
Sebastian Andrzej Siewior
Cc: Jouni Malinen
Cc: Kalle Valo
Cc: "David S. Miller"
Cc: Jakub Kicinski
Cc: linux-wirel...@vger.kernel.org
Cc: net...@vger.kernel.org
---
drivers/net/wireless/intersil/hostap/hostap_ioctl.c | 13 +
1 file changed, 1 insertion(+), 12 deletions(-)
Andrzej Siewior
Cc: Daniel Drake
Cc: Ulrich Kunitz
Cc: Kalle Valo
Cc: "David S. Miller"
Cc: Jakub Kicinski
Cc: linux-wirel...@vger.kernel.org
Cc: net...@vger.kernel.org
---
drivers/net/wireless/zydas/zd1211rw/zd_usb.c | 15 ---
1 file changed, 15 deletions(-)
diff --git
the context
through a quite large amount of functions.
As this is ancient hardware, avoid the churn and enforce the invocation of
those functions through the JOB machinery.
Signed-off-by: Sebastian Andrzej Siewior
Cc: Kalle Valo
Cc: "David S. Miller"
Cc: Jakub Kicinski
Cc: l
Andrzej Siewior
Cc: Saeed Mahameed
Cc: Leon Romanovsky
Cc: "David S. Miller"
Cc: Jakub Kicinski
Cc: linux-r...@vger.kernel.org
---
drivers/net/ethernet/mellanox/mlx5/core/eq.c | 18 +++---
1 file changed, 11 insertions(+), 7 deletions(-)
diff --git a/drivers/net/ethernet/mel
y.
Invoke airo_read_wireless_stats() directly from the callback and remove
the now unused JOB_WSTATS handling.
Signed-off-by: Sebastian Andrzej Siewior
Cc: Kalle Valo
Cc: "David S. Miller"
Cc: Jakub Kicinski
Cc: linux-wirel...@vger.kernel.org
Cc: net...@vger.kernel.org
---
driver
replace the warning and the lock assert with lockdep_assert_held().
Signed-off-by: Sebastian Andrzej Siewior
Cc: Rain River
Cc: Zhu Yanjun
Cc: "David S. Miller"
Cc: Jakub Kicinski
Cc: net...@vger.kernel.org
---
drivers/net/ethernet/nvidia/forcedeth.c | 6 +-
1 file changed, 1
(), tlan_mii_write_reg() and tlan_phy_print() are invoked
from interrupt and other contexts.
Split out the actual function body into helper variants which are called
from interrupt context and make the original functions wrappers which
acquire tlan_priv::lock unconditionally.
Signed-off-by: Sebastian Andrzej Siewior
()
s2io_set_multicast()
s2io_txpic_intr_handle()
s2io_link()
init_tti()
Add a may_sleep argument to wait_for_cmd_complete(), s2io_set_multicast()
and init_tti() and hand the context information in from the call sites.
Signed-off-by: Sebastian Andrzej Siewior
Cc: Jon Mason
Cc
in the invoked functions (always enabled or debug
option dependent) cover these conditions already, so the BUG_ON()'s do not
really provide additional value.
Just remove them.
Signed-off-by: Sebastian Andrzej Siewior
Cc: Kalle Valo
Cc: "David S. Miller"
Cc: Jakub Kicinski
Cc: l
Folks,
in the discussion about preempt count consistency across kernel configurations:
https://lore.kernel.org/r/20200914204209.256266...@linutronix.de/
Linus clearly requested that code in drivers and libraries which changes
behaviour based on execution context should either be split up so
Cc: linux-i...@vger.kernel.org
Reported-by: kbuild test robot
Signed-off-by: Sebastian Andrzej Siewior
---
arch/ia64/include/asm/uaccess.h | 1 -
arch/ia64/kernel/process.c | 1 +
arch/ia64/mm/ioremap.c | 1 +
3 files changed, 2 insertions(+), 1 deletion(-)
diff --git a/arch/ia64
Cc: Vincent Chen
Reported-by: kbuild test robot
Signed-off-by: Sebastian Andrzej Siewior
---
arch/nds32/include/asm/uaccess.h | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/nds32/include/asm/uaccess.h b/arch/nds32/include/asm/uaccess.h
index 8916ad9f9f139..3a9219f53ee0d 100644
...@vger.kernel.org
Reported-by: kbuild test robot
Signed-off-by: Sebastian Andrzej Siewior
---
arch/csky/include/asm/uaccess.h | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/csky/include/asm/uaccess.h b/arch/csky/include/asm/uaccess.h
index eaa1c3403a424..abefa125b93cf 100644
--- a/arch/csky
-hexa...@vger.kernel.org
Reported-by: kbuild test robot
Signed-off-by: Sebastian Andrzej Siewior
---
arch/hexagon/include/asm/uaccess.h | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/hexagon/include/asm/uaccess.h
b/arch/hexagon/include/asm/uaccess.h
index 00cb38faad0c4..c1019a736ff13
The following mini-series removes linux/mm.h from the asm/uaccess.h of
the individual architecture. The series has been compile tested with the
defconfig and additionally for ia64 with the "special" allmodconfig
supplied by the bot. The regular allmod for the architectures does not
compile (even
Reported-by: kbuild test robot
Signed-off-by: Sebastian Andrzej Siewior
---
arch/microblaze/include/asm/uaccess.h | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/microblaze/include/asm/uaccess.h
b/arch/microblaze/include/asm/uaccess.h
index a1f206b90753a..4916d5fbea5e3 100644
--- a/arch
On 2020-03-20 01:55:27 [-0700], Davidlohr Bueso wrote:
> diff --git a/include/linux/swait.h b/include/linux/swait.h
> index 73e06e9986d4..6e5b5d0e64fd 100644
> --- a/include/linux/swait.h
> +++ b/include/linux/swait.h
> @@ -39,7 +26,7 @@
> *sleeper state.
> *
> * - the !exclusive mode;
On 2020-03-20 01:55:25 [-0700], Davidlohr Bueso wrote:
> Let the caller know if wake_up_process() was actually called or not;
> some users can use this information for ad-hoc. Of course returning
> true does not guarantee that wake_up_process() actually woke anything
> up.
Wouldn't it make sense
On 2020-03-19 22:36:57 [-0700], Davidlohr Bueso wrote:
> On Wed, 18 Mar 2020, Thomas Gleixner wrote:
>
> Right now I'm not sure what the proper fix should be.
I though that v2 has it fixed with the previous commit (acpi: Remove
header dependency). The kbot just reported that everything is fine.
On 2020-03-19 03:04:59 [-0700], Christoph Hellwig wrote:
> But I wonder how alive the whole PS3 support is to start with..
OtherOS can only be used on "old" PS3 which do not have have their
firmware upgraded past version 3.21, released April 1, 2010 [0].
It was not possible to install OtherOS on
On 2020-03-18 21:43:09 [+0100], Thomas Gleixner wrote:
> --- a/arch/powerpc/platforms/ps3/device-init.c
> +++ b/arch/powerpc/platforms/ps3/device-init.c
> @@ -725,12 +728,12 @@ static int ps3_notification_read_write(s
> unsigned long flags;
> int res;
>
> -
On 2020-02-05 07:10:59 [+0530], maddy wrote:
> Yes, currently we dont have anything that prevents the timer
> callback to interrupt pmu::event_init. Nice catch. Thanks for
> pointing this out.
You are welcome.
> Looking at the code, per-cpu variable access are made to
> check for constraints and
I've been looking at usage of per-CPU variable cpu_hw_events in
arch/powerpc/perf/core-book3s.c.
power_pmu_enable() and power_pmu_disable() (pmu::pmu_enable() and
pmu::pmu_disable()) are accessing the variable and the callbacks are
invoked always with disabled interrupts.
power_pmu_event_init()
With CONFIG_QUICC_ENGINE enabled and CONFIG_UCC_GETH + CONFIG_SERIAL_QE
disabled we have an unused variable (np). The code won't compile with
-Werror.
Move the np variable to the block where it is actually used.
Signed-off-by: Sebastian Andrzej Siewior
---
arch/powerpc/platforms/85xx
On 2019-12-19 11:41:21 [+0100], Jason A. Donenfeld wrote:
> Hi folks,
Hi,
so this should duct tape it:
diff --git a/arch/powerpc/kernel/dbell.c b/arch/powerpc/kernel/dbell.c
index f17ff1200eaae..ec044bdf362a1 100644
--- a/arch/powerpc/kernel/dbell.c
+++ b/arch/powerpc/kernel/dbell.c
@@ -60,16
On 2019-12-05 20:01:41 [-0600], Frank Rowand wrote:
> Is there a memory usage issue for the systems that led to this thread?
No, no memory issue led to this thread. I was just testing my patch and
I assumed that I did something wrong in the counting/lock drop/lock
acquire/allocate path because
On 2019-12-03 10:56:35 [-0600], Rob Herring wrote:
> > Another possibility would be to make the cache be dependent
> > upon not CONFIG_PPC. It might be possible to disable the
> > cache with a minimal code change.
>
> I'd rather not do that.
>
> And yes, as mentioned earlier I don't like the
On 2019-11-29 20:14:47 [-0600], Frank Rowand wrote:
> The hash used is based on the assumptions you noted, and as stated in the
> code, that phandle property values are in a contiguous range of 1..n
> (not starting from zero), which is what dtc generates.
>
> We knew that for systems that do not
I've been looking at phandle_cache and noticed the following: The raw
phandle value as generated by dtc starts at zero and is incremented by
one for each phandle entry. The qemu pSeries model is using Slof (which
is probably the same thing as used on real hardware) and this looks like
a poiner
Cc: Michael Ellerman
Cc: linuxppc-dev@lists.ozlabs.org
Signed-off-by: Thomas Gleixner
[bigeasy: +Kconfig]
Signed-off-by: Sebastian Andrzej Siewior
---
v2…v3: Don't mention die.c changes in the description.
v1…v2: Remove the changes to die.c.
arch/powerpc/Kconfig | 2 +-
arch/powerpc
Herrenschmidt
Cc: Paul Mackerras
Cc: Michael Ellerman
Cc: linuxppc-dev@lists.ozlabs.org
Signed-off-by: Thomas Gleixner
[bigeasy: +Kconfig]
Signed-off-by: Sebastian Andrzej Siewior
---
v1…v2: Remove the changes to die.c
arch/powerpc/Kconfig | 2 +-
arch/powerpc/kernel/entry_32.S | 4
On 2019-10-16 20:33:08 [+1100], Michael Ellerman wrote:
> Christophe Leroy writes:
> > Le 15/10/2019 à 21:17, Sebastian Andrzej Siewior a écrit :
> >> From: Thomas Gleixner
> >>
> >> CONFIG_PREEMPTION is selected by CONFIG_PREEMPT and by CONFIG_PREEMPT_
On 2019-10-16 06:57:48 [+0200], Christophe Leroy wrote:
>
>
> Le 15/10/2019 à 21:17, Sebastian Andrzej Siewior a écrit :
> > From: Thomas Gleixner
> >
> > CONFIG_PREEMPTION is selected by CONFIG_PREEMPT and by CONFIG_PREEMPT_RT.
> > Both PREEMPT and PREEMPT_
Herrenschmidt
Cc: Paul Mackerras
Cc: Michael Ellerman
Cc: linuxppc-dev@lists.ozlabs.org
Signed-off-by: Thomas Gleixner
[bigeasy: +traps.c, Kconfig]
Signed-off-by: Sebastian Andrzej Siewior
---
arch/powerpc/Kconfig | 2 +-
arch/powerpc/kernel/entry_32.S | 4 ++--
arch/powerpc/kernel
On 2019-04-05 02:25:44 [+1000], Nicholas Piggin wrote:
> Sebastian, are you able to test if this patch solves your problem?
yes, it does.
Tested-by: Sebastian Andrzej Siewior
> Thanks,
> Nick
Sebastian
On 2019-03-29 16:20:51 [+1100], Suraj Jitindar Singh wrote:
>
> Yeah the kernel must have used msgsndp which isn't implemented for TCG
> yet. We use doorbells in linux but only for threads which are on the
> same core.
It is msgsndp as per instruction decode.
> And when I try to construct a
With qemu-system-ppc64le -machine pseries -smp 4 I get:
|# chrt 1 hackbench
|Running in process mode with 10 groups using 40 file descriptors each (== 400
tasks)
|Each sender will pass 100 messages of 100 bytes
| Oops: Exception in kernel mode, sig: 4 [#1]
| LE PAGE_SIZE=64K MMU=Hash PREEMPT
crashing.org>
Cc: Paul Mackerras <pau...@samba.org>
Cc: Michael Ellerman <m...@ellerman.id.au>
Cc: kvm-...@vger.kernel.org
Cc: k...@vger.kernel.org
Cc: linuxppc-dev@lists.ozlabs.org
Signed-off-by: Anna-Maria Gleixner <anna-ma...@linutronix.de>
Signed-off-by: Sebastian Andrzej Siewior
the hotplug call symmetric.
Cc: Benjamin Herrenschmidt <b...@kernel.crashing.org>
Cc: Paul Mackerras <pau...@samba.org>
Cc: Michael Ellerman <m...@ellerman.id.au>
Cc: linuxppc-dev@lists.ozlabs.org
Signed-off-by: Sebastian Andrzej Siewior <bige...@linutronix.de>
---
arch/pow
Install the callbacks via the state machine.
Cc: Benjamin Herrenschmidt <b...@kernel.crashing.org>
Cc: Paul Mackerras <pau...@samba.org>
Cc: Michael Ellerman <m...@ellerman.id.au>
Cc: linuxppc-dev@lists.ozlabs.org
Signed-off-by: Sebastian Andrzej Siewior <bige...@linutronix.
or online callback twice due to
rollback.
Cc: Benjamin Herrenschmidt <b...@kernel.crashing.org>
Cc: Paul Mackerras <pau...@samba.org>
Cc: Michael Ellerman <m...@ellerman.id.au>
Cc: linuxppc-dev@lists.ozlabs.org
Signed-off-by: Sebastian Andrzej Siewior <bige...@linutronix.de>
---
Install the callbacks via the state machine and let the core invoke
the callbacks on the already online CPUs.
v1…v2: manual callback invocation on boot-CPU (cpuhp is not up yet and
we need them all before additional CPUs are up).
Signed-off-by: Sebastian Andrzej Siewior <b
* Anton Blanchard | 2016-07-15 10:28:25 [+1000]:
>Hi Anna-Maria,
Hi Anton,
>> >> Install the callbacks via the state machine and let the core invoke
>> >> the callbacks on the already online CPUs.
>> >
>> > This is causing an oops on ppc64le QEMU, looks like a NULL
>> > pointer:
>>
>> Did
On 03/30/2016 02:41 AM, Michael Ellerman wrote:
> The merge window just closed, I'm still recovering.
>
> I've got it in my fixes branch locally, I'll probably push that today to
> linux-next.
Thank you.
>
> cheers
>
Sebastian
___
Linuxppc-dev
On 2016-03-10 01:04:24 [+0530], Aneesh Kumar K.V wrote:
> Sebastian Andrzej Siewior <bige...@linutronix.de> writes:
*ping*
http://patchwork.ozlabs.org/patch/593943/
> > [ text/plain ]
> > hugepd_free() used __get_cpu_var() once. Nothing ensured that the code
> >
c: <sta...@vger.kernel.org>
Signed-off-by: Sebastian Andrzej Siewior <bige...@linutronix.de>
---
v1…v2: - use get_cpu_var() instead of get_cpu_ptr()
- correct indentation of put_cpu_var()
arch/powerpc/mm/hugetlbpage.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
On 03/08/2016 12:41 AM, Benjamin Herrenschmidt wrote:
> On Mon, 2016-03-07 at 21:04 +0530, Aneesh Kumar K.V wrote:
>> Sebastian Andrzej Siewior <bige...@linutronix.de> writes:
>>
>> While you are there, can you also fix the wrong indentation on line
>> 423
>&g
* Bogdan Purcareata | 2015-04-24 15:53:11 [+]:
0001: converts the openpic spinlock to a raw spinlock, in order to circumvent
0002: disables in-kernel MPIC emulation for guest running on RT, in order to
Scott, I'm asking here for your explicit Acked-by on those two patches.
That you want it
* Bogdan Purcareata | 2015-04-24 15:53:13 [+]:
While converting the openpic emulation code to use a raw_spinlock_t enables
guests to run on RT, there's still a performance issue. For interrupts sent in
Signed-off-by: Bogdan Purcareata bogdan.purcare...@freescale.com
Applied with Scott's
On 02/26/2015 02:02 PM, Paolo Bonzini wrote:
On 24/02/2015 00:27, Scott Wood wrote:
This isn't a host PIC driver. It's guest PIC emulation, some of which
is indeed not suitable for a rawlock (in particular, openpic_update_irq
which loops on the number of vcpus, with a loop body that calls
* Scott Wood | 2015-02-23 17:27:31 [-0600]:
This isn't a host PIC driver. It's guest PIC emulation, some of which
is indeed not suitable for a rawlock (in particular, openpic_update_irq
which loops on the number of vcpus, with a loop body that calls
IRQ_check() which loops over all pending
On 02/20/2015 03:12 PM, Paolo Bonzini wrote:
Thomas, what is the usual approach for patches like this? Do you take
them into your rt tree or should they get integrated to upstream?
Patch 1 is definitely suitable for upstream, that's the reason why we
have raw_spin_lock vs. raw_spin_unlock.
On 02/20/2015 03:57 PM, Paolo Bonzini wrote:
On 20/02/2015 15:54, Sebastian Andrzej Siewior wrote:
Usually you see scheduling while atomic on -RT and convert them to
raw locks if it is appropriate.
Bogdan wrote in 2/2 that he needs to limit the number of CPUs in oder
not cause a DoS
On 02/20/2015 04:10 PM, Paolo Bonzini wrote:
On 20/02/2015 16:06, Sebastian Andrzej Siewior wrote:
On 02/20/2015 03:57 PM, Paolo Bonzini wrote:
Yes, but large latencies just mean the code has to be rewritten (x86
doesn't anymore do event injection in an atomic regions for example).
Until
On 02/18/2015 10:32 AM, Bogdan Purcareata wrote:
Due to the introduction of the raw_spinlock for the KVM openpic, guests with a
high number of VCPUs may induce great latencies on the underlying RT Linux
system (e.g. cyclictest reports latencies of ~15ms for guests with 24 VCPUs).
This can be
On 11/03/2014 11:18 PM, Scott Wood wrote:
Is it really necessary for the virqs to be contiguous? How is the
availability of multiple MSIs communicated to the driver? Is there an
example of a driver that currently uses multiple MSIs?
I used this in PCI and after enabling 2^x, I allocated an
On 10/31/2014 09:12 AM, Johannes Thumshirn wrote:
On Thu, Oct 30, 2014 at 02:51:57PM +1100, Michael Ellerman wrote:
Why would you not use MSI-X ?
If I'm not mistaken, a PCI-E requirement is to support MSI but MSI-X is
optional. And with MSI you can have multiple interrupts per single
device
On 02/20/2014 10:06 PM, Scott Wood wrote:
On Thu, 2014-02-20 at 21:53 +0100, Sebastian Andrzej Siewior wrote:
A MSI device may have multiple interrupts. That means that the
interrupts numbers should be continuos so that pdev-irq refers to the
first interrupt, pdev-irq + 1 to the second and so
on irq_create_mapping() but due to the
number argument there is very little in common now.
Cc: Thomas Gleixner t...@linutronix.de
Signed-off-by: Sebastian Andrzej Siewior bige...@linutronix.de
---
Scott, this is what you suggested. I must admit, it does not look that
bad. It is just compile tested.
v1
If CONFIG_UCC_GETH or CONFIG_SERIAL_QE is not defined then we get a
warning about an used variable which leads to a build error.
Signed-off-by: Sebastian Andrzej Siewior bige...@linutronix.de
---
arch/powerpc/platforms/85xx/mpc85xx_rdb.c | 5 +
1 file changed, 1 insertion(+), 4 deletions
powerpc uses early_init_dt_scan_chosen() from common fdt code. By
enabling this option, the common code can take the built in
command line over the one that is comming from bootloader / DT.
Signed-off-by: Sebastian Andrzej Siewior bige...@linutronix.de
---
arch/powerpc/Kconfig | 9 +
1
on irq_create_mapping() but due to the
number argument there is very little in common now.
Cc: Thomas Gleixner t...@linutronix.de
Signed-off-by: Sebastian Andrzej Siewior bige...@linutronix.de
---
include/linux/irqdomain.h | 2 ++
kernel/irq/irqdomain.c| 61
This series adds support for multiple MSI interrupts on FSL's MPIC. The
code has been tested on v3.2 with custom FPGA device on PCIe and then
forward ported. Patch #1 has been created from scratch during porting,
patch #2 almost applied as-it.
Sebastian
Cc: Brian King brk...@linux.vnet.ibm.com
Cc: Anton Blanchard an...@samba.org
Cc: Scott Wood scottw...@freescale.com
Cc: Minghuan Lian minghuan.l...@freescale.com
Cc: Kumar Gala ga...@kernel.crashing.org
Signed-off-by: Sebastian Andrzej Siewior bige...@linutronix.de
---
arch/powerpc/kernel/msi.c
* Hong H. Pham | 2013-12-07 09:06:33 [-0500]:
On PPC32, only SMP kernels are affected.
On PPC64, only SMP kernels with 4K page size are affected.
$ uname -a
Linux mpc8536-1 3.12.1-rt3-00281-g9de268d #76 SMP PREEMPT RT Fri Nov 22
16:53:05 CET 2013 ppc GNU/Linux
$ uptime
22:01:10 up 22 days,
to know WHICH critical irq failed,
not which level it had.
Signed-off-by: Wolfram Sang w...@the-dreams.de
Cc: Sebastian Andrzej Siewior bige...@linutronix.de
Cc: Anatolij Gustschin ag...@denx.de
Acked-by: Sebastian Andrzej Siewior bige...@linutronix.de
Sebastian
On 10/01/2013 09:03 PM, Wolfram Sang wrote:
Yup. But I just remembered a better solution:
From: Wolfram Sang w...@the-dreams.de Subject: [PATCH] ppc:
mpc52xx: silence false positive from old GCC
So people can compile with -Werror.
Signed-off-by: Wolfram Sang w...@the-dreams.de ---
it was
not in the case statement? l2 holds the number, l1 the level.
Signed-off-by: Wolfram Sang w...@the-dreams.de
Cc: Sebastian Andrzej Siewior bige...@linutronix.de
Cc: Anatolij Gustschin ag...@denx.de
---
Have I been on CC when the original patch was sent?
You were but your email bounced. I wasn't
On 10/01/2013 11:11 AM, Wolfram Sang wrote:
Hi,
Hi Wolfram,
Well, if you insist, I'd prefer the following patch.
From: Wolfram Sang w...@the-dreams.de Subject: [PATCH] ppc:
mpc52xx: silence false positive from old GCC
So people can compile with -Werror (RT patchset).
Why do you mention
since this is
the number that is evaluated.
Signed-off-by: Sebastian Andrzej Siewior bige...@linutronix.de
---
arch/powerpc/platforms/52xx/mpc52xx_pic.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/arch/powerpc/platforms/52xx/mpc52xx_pic.c
b/arch/powerpc/platforms/52xx
From: Thomas Gleixner t...@linutronix.de
These low level handlers cannot be threaded. Mark them NO_THREAD
Reported-by: leroy christophe christophe.le...@c-s.fr
Tested-by: leroy christophe christophe.le...@c-s.fr
Signed-off-by: Thomas Gleixner t...@linutronix.de
Signed-off-by: Sebastian Andrzej
On 06/29/2013 01:43 AM, Santosh Shilimkar wrote:
Sebastian,
Apart from waste of 32bit, what is the other concern you
have ?
You pass a u64 as a physical address which is represented in other
parts of the kernel (for a good reason) by phys_addr_t.
I really want to converge on this patch
On 07/01/2013 09:59 AM, Geert Uytterhoeven wrote:
That's actual the original reason: DT has it as 64 bit, and passes it to a
32 bit kernel when running in 32 bit mode without PAE.
And I think the DT code should check if the u64 fits in phys_addr_t and
if does not it should write an error
On 06/27/2013 10:54 PM, Rob Herring wrote:
Rob,
Are you ok with phys_addr_t since your concern was about rest
of the memory specific bits of the device-tree code use u64 ?
No. I still think it should be u64 for same reasons I said originally.
The physical address space is represented by
1 - 100 of 182 matches
Mail list logo
