linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: afzal.mohd.ma@gmail.com (afzal mohammed)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: NOMMU: Setup VBAR/Hivecs for secondaries cores
Date: Thu, 21 Dec 2017 09:14:49 +0530	[thread overview]
Message-ID: <20171221034449.GB3944@afzalpc> (raw)
In-Reply-To: <db12818a-509f-2b28-7df0-dd923d956057@arm.com>

Hi,

On Wed, Dec 20, 2017 at 12:22:16PM +0000, Vladimir Murzin wrote:

> >> Additionally, patch is not about Hivec only, but VBAR as well and TBH I
> >> don't follow what is your proposal...
> > 
> > i was referring to the fact that vector remapping can't be done in
> > Cortex-R, as security extension is a requisite for this feature, which
> > Cortex-R don't have on ARMv7.
> 
> For instance, just think of ARMv7A with 1:1 MMU running in SMP...

Hmm, 3 things,
1. MMU on would not take the path being patched here
2. w/ MMU on, currently it is always Hivecs
3. w/ MMU on & 1:1 mapping & due to pt. 2 above, if there is no memory
 @0xFFFF0000, suspect things might go wrong.

afzal

      reply	other threads:[~2017-12-21  3:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-19 10:23 [PATCH] ARM: NOMMU: Setup VBAR/Hivecs for secondaries cores Vladimir Murzin
2017-12-19 11:29 ` afzal mohammed
2017-12-19 14:44   ` Vladimir Murzin
2017-12-20  4:52     ` afzal mohammed
2017-12-20  9:55       ` Vladimir Murzin
2017-12-20 11:49         ` afzal mohammed
2017-12-20 12:01           ` afzal mohammed
2017-12-20 12:22             ` Vladimir Murzin
2017-12-21  4:05               ` afzal mohammed
2017-12-20 12:12           ` afzal mohammed
2017-12-20 12:22           ` Vladimir Murzin
2017-12-21  3:44             ` afzal mohammed [this message]

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=20171221034449.GB3944@afzalpc \
    --to=afzal.mohd.ma@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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;
as well as URLs for NNTP newsgroup(s).