From: Christoffer Dall <christoffer.dall@linaro.org>
To: Andrew Jones <drjones@redhat.com>
Cc: kvm@vger.kernel.org, kvmarm@lists.cs.columbia.edu, pbonzini@redhat.com
Subject: Re: [PATCH 2/3] arm/arm64: speed up spinlocks and atomic ops
Date: Mon, 29 Jun 2015 12:28:32 +0200 [thread overview]
Message-ID: <20150629102832.GJ11332@cbox> (raw)
In-Reply-To: <1435248739-25425-3-git-send-email-drjones@redhat.com>
On Thu, Jun 25, 2015 at 06:12:18PM +0200, Andrew Jones wrote:
> spinlock torture tests made it clear that checking mmu_enabled()
> every time we call spin_lock is a bad idea.
why a bad idea? Does it break, is it slow?
> As most tests will
> want the MMU enabled the entire time, then just hard code
> mmu_enabled() to true. Tests that want to play with the MMU can
> be compiled with CONFIG_MAY_DISABLE_MMU to get the actual check
> back.
If we don't care about performance, why this added complexity?
>
> Signed-off-by: Andrew Jones <drjones@redhat.com>
> ---
> lib/arm/asm/mmu-api.h | 4 ++++
> lib/arm/mmu.c | 3 +++
> 2 files changed, 7 insertions(+)
>
> diff --git a/lib/arm/asm/mmu-api.h b/lib/arm/asm/mmu-api.h
> index 68dc707d67241..1a4d91163c398 100644
> --- a/lib/arm/asm/mmu-api.h
> +++ b/lib/arm/asm/mmu-api.h
> @@ -1,7 +1,11 @@
> #ifndef __ASMARM_MMU_API_H_
> #define __ASMARM_MMU_API_H_
> extern pgd_t *mmu_idmap;
> +#ifdef CONFIG_MAY_DISABLE_MMU
> extern bool mmu_enabled(void);
> +#else
> +#define mmu_enabled() (1)
> +#endif
> extern void mmu_set_enabled(void);
> extern void mmu_enable(pgd_t *pgtable);
> extern void mmu_enable_idmap(void);
> diff --git a/lib/arm/mmu.c b/lib/arm/mmu.c
> index 732000a8eb088..405717b6332bf 100644
> --- a/lib/arm/mmu.c
> +++ b/lib/arm/mmu.c
> @@ -15,11 +15,14 @@ extern unsigned long etext;
> pgd_t *mmu_idmap;
>
> static cpumask_t mmu_enabled_cpumask;
> +
> +#ifdef CONFIG_MAY_DISABLE_MMU
> bool mmu_enabled(void)
> {
> struct thread_info *ti = current_thread_info();
> return cpumask_test_cpu(ti->cpu, &mmu_enabled_cpumask);
> }
> +#endif
>
> void mmu_set_enabled(void)
> {
> --
> 2.4.3
>
next prev parent reply other threads:[~2015-06-29 10:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-25 16:12 [PATCH 0/3] arm/arm64: tcg_baremetal_tests inspired patches Andrew Jones
2015-06-25 16:12 ` [PATCH 1/3] arm/arm64: spinlocks: fix memory barriers Andrew Jones
2015-06-29 10:27 ` Christoffer Dall
2015-07-03 17:42 ` Paolo Bonzini
2015-06-25 16:12 ` [PATCH 2/3] arm/arm64: speed up spinlocks and atomic ops Andrew Jones
2015-06-25 16:23 ` Paolo Bonzini
2015-06-25 16:55 ` Andrew Jones
2015-06-29 10:28 ` Christoffer Dall [this message]
2015-06-29 10:44 ` Andrew Jones
2015-06-29 12:53 ` Christoffer Dall
2015-06-25 16:12 ` [PATCH 3/3] arm/arm64: allow building a single test Andrew Jones
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=20150629102832.GJ11332@cbox \
--to=christoffer.dall@linaro.org \
--cc=drjones@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=pbonzini@redhat.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;
as well as URLs for NNTP newsgroup(s).