From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Magnus Damm <magnus.damm@gmail.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
SH-Linux <linux-sh@vger.kernel.org>,
"Simon Horman [Horms]" <horms@verge.net.au>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] clocksource: sh_tmu: Set cpu_possible_mask to fix SMP broadcast
Date: Fri, 19 Dec 2014 00:46:37 +0000 [thread overview]
Message-ID: <2833437.mUHC45LYXV@avalon> (raw)
In-Reply-To: <CANqRtoQbtp_vgmcooiWpUvBMP7txGeYVGT-oLkRfMiM6Y51BQg@mail.gmail.com>
Hi Magnus,
On Friday 19 December 2014 09:03:00 Magnus Damm wrote:
> On Wed, Dec 17, 2014 at 11:08 AM, Laurent Pinchart wrote:
> > Magnus, you have told me that you've performed tests on Marzen with
> > CONFIG_PREEMPT_NONE and with both TWD enabled and disabled. If you could
> > perform the same tests with CONFIG_PREEMPT instead without noticing any
> > regression I think we can merge your patch. Whatever breakage it has
> > caused in the past is likely hidden somewhere beyond eyesight.
>
> I've now successfully boot tested the different PREEMPT settings on
> r8a7779 Marzen multiplatform. Everything seems to work as expected.
>
> Compared to before I've been a bit more lazy, so I've kept the timer
> config to default which means TWD and TMU enabled.
If your test setup is still around could you quickly test PREEMPT + TMU
without TWD ?
> The kernel tree is renesas-devel-20141218-v3.18 which is v3.18 plus local
> integration stuff including TWD DT. I've applied this patch too.
--
Regards,
Laurent Pinchart
WARNING: multiple messages have this Message-ID (diff)
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Magnus Damm <magnus.damm@gmail.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
SH-Linux <linux-sh@vger.kernel.org>,
"Simon Horman [Horms]" <horms@verge.net.au>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] clocksource: sh_tmu: Set cpu_possible_mask to fix SMP broadcast
Date: Fri, 19 Dec 2014 02:46:37 +0200 [thread overview]
Message-ID: <2833437.mUHC45LYXV@avalon> (raw)
In-Reply-To: <CANqRtoQbtp_vgmcooiWpUvBMP7txGeYVGT-oLkRfMiM6Y51BQg@mail.gmail.com>
Hi Magnus,
On Friday 19 December 2014 09:03:00 Magnus Damm wrote:
> On Wed, Dec 17, 2014 at 11:08 AM, Laurent Pinchart wrote:
> > Magnus, you have told me that you've performed tests on Marzen with
> > CONFIG_PREEMPT_NONE and with both TWD enabled and disabled. If you could
> > perform the same tests with CONFIG_PREEMPT instead without noticing any
> > regression I think we can merge your patch. Whatever breakage it has
> > caused in the past is likely hidden somewhere beyond eyesight.
>
> I've now successfully boot tested the different PREEMPT settings on
> r8a7779 Marzen multiplatform. Everything seems to work as expected.
>
> Compared to before I've been a bit more lazy, so I've kept the timer
> config to default which means TWD and TMU enabled.
If your test setup is still around could you quickly test PREEMPT + TMU
without TWD ?
> The kernel tree is renesas-devel-20141218-v3.18 which is v3.18 plus local
> integration stuff including TWD DT. I've applied this patch too.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2014-12-19 0:46 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-16 9:48 [PATCH] clocksource: sh_tmu: Set cpu_possible_mask to fix SMP broadcast Magnus Damm
2014-12-16 9:48 ` Magnus Damm
2014-12-16 11:14 ` Daniel Lezcano
2014-12-16 11:14 ` Daniel Lezcano
2014-12-16 11:20 ` Laurent Pinchart
2014-12-16 11:20 ` Laurent Pinchart
2014-12-16 11:25 ` Laurent Pinchart
2014-12-16 11:25 ` Laurent Pinchart
2014-12-16 11:29 ` Daniel Lezcano
2014-12-16 11:29 ` Daniel Lezcano
2014-12-16 11:46 ` Magnus Damm
2014-12-16 11:46 ` Magnus Damm
2014-12-16 11:54 ` Daniel Lezcano
2014-12-16 11:54 ` Daniel Lezcano
2014-12-17 0:44 ` Laurent Pinchart
2014-12-17 0:44 ` Laurent Pinchart
2014-12-16 12:40 ` Geert Uytterhoeven
2014-12-16 12:40 ` Geert Uytterhoeven
2014-12-17 1:30 ` Magnus Damm
2014-12-17 1:30 ` Magnus Damm
2014-12-17 2:08 ` Laurent Pinchart
2014-12-17 2:08 ` Laurent Pinchart
2014-12-17 8:30 ` Geert Uytterhoeven
2014-12-17 8:30 ` Geert Uytterhoeven
2014-12-17 9:42 ` Geert Uytterhoeven
2014-12-17 9:42 ` Geert Uytterhoeven
2014-12-17 12:04 ` Laurent Pinchart
2014-12-17 12:04 ` Laurent Pinchart
2014-12-17 12:11 ` Geert Uytterhoeven
2014-12-17 12:11 ` Geert Uytterhoeven
2014-12-17 12:14 ` Laurent Pinchart
2014-12-17 12:14 ` Laurent Pinchart
2014-12-17 11:31 ` Laurent Pinchart
2014-12-17 11:31 ` Laurent Pinchart
2014-12-17 13:23 ` Magnus Damm
2014-12-17 13:23 ` Magnus Damm
2014-12-19 0:03 ` Magnus Damm
2014-12-19 0:03 ` Magnus Damm
2014-12-19 0:46 ` Laurent Pinchart [this message]
2014-12-19 0:46 ` Laurent Pinchart
2014-12-17 8:25 ` Geert Uytterhoeven
2014-12-17 8:25 ` Geert Uytterhoeven
2014-12-17 0:43 ` Laurent Pinchart
2014-12-17 0:43 ` Laurent Pinchart
2014-12-17 13:59 ` Geert Uytterhoeven
2014-12-17 14:43 ` Laurent Pinchart
2014-12-17 15:34 ` Laurent Pinchart
2014-12-17 15:44 ` Geert Uytterhoeven
2014-12-17 15:46 ` Magnus Damm
2014-12-18 3:29 ` Laurent Pinchart
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2833437.mUHC45LYXV@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=daniel.lezcano@linaro.org \
--cc=geert@linux-m68k.org \
--cc=horms@verge.net.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.