From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: Add SWP/SWPB emulation for ARMv7 processors (v3)
Date: Thu, 07 Jan 2010 09:59:08 +0000 [thread overview]
Message-ID: <1262858349.2695.7.camel@pc1117.cambridge.arm.com> (raw)
In-Reply-To: <20100106181705.GD11773@shareable.org>
On Wed, 2010-01-06 at 18:17 +0000, Jamie Lokier wrote:
> Catalin Marinas wrote:
> > > Is there any reason why this wasn't always like that?
> >
> > On ARMv6 onwards (where this user RO, kernel RO is supported) we cannot
> > easily differentiate between the vectors page and a normal kernel page
> > unless we use another L_PTE_ bit. We need the vectors page to be
> > writable if there is no TLS register in hardware (I guess we could use
> > domain switching to override this though). But on ARMv7 we always have a
> > TLS register, so no need to write to the vectors page.
>
> Could you map the TLS page writable (kernel access only) at another
> address at the same time, carefully choosing an aliasing address so
> that no cache flush is needed after writing?
It could be but I'm not sure it's worth. Leif's patch is intended for
ARMv7 where we always have a hardware TLS register. The FIQ handler
installation could probably be done by first calling set_fs(KERNEL_DS).
--
Catalin
next prev parent reply other threads:[~2010-01-07 9:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-05 18:24 [PATCH] ARM: Add SWP/SWPB emulation for ARMv7 processors (v3) Leif Lindholm
2010-01-05 19:43 ` Jamie Lokier
2010-01-06 16:23 ` Catalin Marinas
2010-01-06 16:32 ` Russell King - ARM Linux
2010-01-06 16:58 ` Catalin Marinas
2010-01-06 18:17 ` Jamie Lokier
2010-01-07 9:59 ` Catalin Marinas [this message]
2010-01-08 14:19 ` Jamie Lokier
2010-01-06 19:19 ` Leif Lindholm
2010-01-06 19:36 ` Russell King - ARM Linux
2010-01-14 13:08 ` Leif Lindholm
-- strict thread matches above, loose matches on Subject: below --
2010-01-06 21:53 Jamie Lokier
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=1262858349.2695.7.camel@pc1117.cambridge.arm.com \
--to=catalin.marinas@arm.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).