public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: afzal mohammed <afzal.mohd.ma@gmail.com>
To: Russell King <linux@armlinux.org.uk>
Cc: linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
	"Catalin Marinas" <catalin.marinas@arm.com>,
	"Greg Ungerer" <gerg@linux-m68k.org>,
	"Vladimir Murzin" <vladimir.murzin@arm.com>
Subject: [RFC PATCH 0/2] ARM: !MMU v7 Cortex-M preemption support
Date: Mon, 30 Dec 2019 17:24:02 +0530	[thread overview]
Message-ID: <cover.1577705829.git.afzal.mohd.ma@gmail.com> (raw)

Hi,

[ cc'ing those who added long back !MMU support & Cortex-M support as
   well, though some not working anymore on these ]

An attempt to add preemption support to the !MMU, ARM Cortex-M platform.
With these changes, there is some effect, but not enough to make it
usable.

Though as of now i don't have much clue on what the issue could be, it
is being debugged. Meanwhile sending the series as RFC, to get feedback
on what could be missing or whether there is anything inherent in !MMU
and/or Cortex-M platforms that could prevent supporting preemption, etc.

Details on the problems, the way it was tested etc. are mentioned in
2/2. 1/2 is just a change made so as to have a clear diff for easy
review of the preemption support changes.

Regards
afzal

afzal mohammed (2):
  ARM: !MMU: v7-M: prepare preemption support
  ARM: !MMU: v7-M: preemption support

 arch/arm/kernel/entry-v7m.S | 22 +++++++++++++++++++---
 1 file changed, 19 insertions(+), 3 deletions(-)


base-commit: fd6988496e79a6a4bdb514a4655d2920209eb85d
-- 
2.24.1


             reply	other threads:[~2019-12-30 11:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-30 11:54 afzal mohammed [this message]
2019-12-30 11:54 ` [RFC PATCH 1/2] ARM: !MMU: v7-M: prepare preemption support afzal mohammed
2019-12-30 11:55 ` [RFC PATCH 2/2] ARM: !MMU: v7-M: " afzal mohammed
2019-12-31 15:37   ` afzal mohammed

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=cover.1577705829.git.afzal.mohd.ma@gmail.com \
    --to=afzal.mohd.ma@gmail.com \
    --cc=catalin.marinas@arm.com \
    --cc=gerg@linux-m68k.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=u.kleine-koenig@pengutronix.de \
    --cc=vladimir.murzin@arm.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox