Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
MIME-Version: 1.0
References: <20191015191821.11479-1-bigeasy@linutronix.de> <20191015191821.11479-7-bigeasy@linutronix.de>
 <CAJF2gTSVxgc5kw22dfotoHF91HxyTKC4ETYLTskEfyn3rf=kCw@mail.gmail.com> <20191016073905.yv4xqoovrdrnrbp7@linutronix.de>
In-Reply-To: <20191016073905.yv4xqoovrdrnrbp7@linutronix.de>
From:   Guo Ren <guoren@kernel.org>
Date:   Thu, 17 Oct 2019 07:31:23 +0800
Message-ID: <CAJF2gTTXNK9sOXWLKAOXghzS7EYwYgJ21AR7+Q=Do-xKnNMn2Q@mail.gmail.com>
Subject: Re: [PATCH 06/34] csky: Use CONFIG_PREEMPTION
To:     Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc:     Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        tglx@linutronix.de
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

Thx for explanation.

Acked-by: Guo Ren <guoren@kernel.org>

On Wed, Oct 16, 2019 at 3:39 PM Sebastian Andrzej Siewior
<bigeasy@linutronix.de> wrote:
>
> On 2019-10-16 07:29:34 [+0800], Guo Ren wrote:
> > Could CONFIG_PREEMPT_RT be supported in csky ? Any arch backend porting ?
>
> It could. HIGH_RES_TIMERS is useful and IRQ_FORCED_THREADING is
> required. You already have PREEMPT(ION) which is good. Then you would
> have to try and my guess would be that some of spinlock_t vs
> raw_spinlock_t could require changes but we should have lockdep support
> for that which would make things easier.
>
> Sebastian


-- 
Best Regards
 Guo Ren

ML: https://lore.kernel.org/linux-csky/