From: vladimir.murzin@arm.com (Vladimir Murzin)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/8] ARM: V7M: Support caches
Date: Tue, 30 Aug 2016 09:26:11 +0100 [thread overview]
Message-ID: <57C54323.7080007@arm.com> (raw)
In-Reply-To: <CAGhQ9Vxn3cC4RiYfiYJh9Buh+3i_n_gJ+3zeth150xF=ZLGAMw@mail.gmail.com>
Hi Joachim,
On 27/08/16 17:53, Joachim Eastwood wrote:
> Hi Vladimir,
>
> On 18 August 2016 at 16:57, Vladimir Murzin <vladimir.murzin@arm.com> wrote:
>> On 18/08/16 15:53, Russell King - ARM Linux wrote:
>>> On Thu, Aug 18, 2016 at 01:45:52PM +0100, Vladimir Murzin wrote:
>>>> This patch set allows M-class cpus benefit of optional cache support.
>>>> It originally was written by Jonny, I've been keeping it locally mainly
>>>> rebasing over Linux versions.
>>>>
>>>> The original idea behind patches was to reuse existing cache handling
>>>> code from v7A/R with help of extra macros to factor out cache handling
>>>> logic (v7M cache operations are provided via memory mapped interface
>>>> rather than co-processor instructions).
>>>> However, that idea was rejected and starting form this (v2) version
>>>> V7M cache logic lives into file and macros to indirect memory-mapped
>>>> operations stay there locally since they make it easier to follow the
>>>> code.
>>>>
>>>> Along with the v7M cache support the first user (Cortex-M7) is
>>>> introduced.
>>>>
>>>> Patches were tested on MPS2 platform with Cortex-M3/M4/M7. The later
>>>> one showed significant boot speed-up.
>>>
>>> >From a quick read through, the approach looks sane, and I think I'm
>>> now happy with these.
>>>
>>
>> Thanks!
>>
>> Is it acceptable if patches hang on a list for awhile, so people (I'm
>> looking at Alex and Szemz?) can test them?
>
> These patches doesn't seem to break anything on the cache-less
> Cortex-M4 NXP LPC4357.
>
Great!
> So FWIW:
> Tested-by: Joachim Eastwood <manabian@gmail.com>
>
Thanks a lot for testing!
Cheers
Vladimir
>
> regards,
> Joachim Eastwood
>
>
next prev parent reply other threads:[~2016-08-30 8:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-18 12:45 [PATCH v2 0/8] ARM: V7M: Support caches Vladimir Murzin
2016-08-18 12:45 ` [PATCH v2 1/8] ARM: factor out CSSELR/CCSIDR operations that use cp15 directly Vladimir Murzin
2016-08-18 12:45 ` [PATCH v2 2/8] ARM: V7M: Add addresses for mem-mapped V7M cache operations Vladimir Murzin
2016-08-18 12:45 ` [PATCH v2 3/8] ARM: V7M: Add support for reading the CTR with read_cpuid_cachetype() Vladimir Murzin
2016-08-18 12:45 ` [PATCH v2 4/8] ARM: V7M: fix notrace variant of save_and_disable_irqs Vladimir Murzin
2016-08-18 12:45 ` [PATCH v2 5/8] ARM: V7M: introduce cache operations Vladimir Murzin
2016-08-18 12:45 ` [PATCH v2 6/8] ARM: V7M: Wire up caches for V7M processors with cache support Vladimir Murzin
2016-08-18 12:45 ` [PATCH v2 7/8] ARM: V7M: Indirect proc_info construction for V7M CPUs Vladimir Murzin
2016-08-18 12:46 ` [PATCH v2 8/8] ARM: V7M: Add support for the Cortex-M7 processor Vladimir Murzin
2016-08-18 14:53 ` [PATCH v2 0/8] ARM: V7M: Support caches Russell King - ARM Linux
2016-08-18 14:57 ` Vladimir Murzin
2016-08-18 15:11 ` Russell King - ARM Linux
2016-08-30 16:40 ` Vladimir Murzin
2016-08-25 10:15 ` Szemző András
2016-08-25 10:24 ` Vladimir Murzin
2016-08-27 16:53 ` Joachim Eastwood
2016-08-30 8:26 ` Vladimir Murzin [this message]
2016-08-30 15:47 ` Alexandre Torgue
2016-08-30 16:39 ` Vladimir Murzin
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=57C54323.7080007@arm.com \
--to=vladimir.murzin@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).