From: Mark Rutland <mark.rutland@arm.com>
To: James Morse <james.morse@arm.com>
Cc: Pratyush Anand <panand@redhat.com>,
geoff@infradead.org, kexec@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2] arm64: Add enable/disable d-cache support for purgatory
Date: Wed, 14 Dec 2016 11:28:06 +0000 [thread overview]
Message-ID: <20161214112806.GD17982@leverpostej> (raw)
In-Reply-To: <585129F7.6070704@arm.com>
On Wed, Dec 14, 2016 at 11:16:07AM +0000, James Morse wrote:
> Hi Pratyush,
> On 14/12/16 09:38, Pratyush Anand wrote:
> > On Saturday 26 November 2016 12:00 AM, James Morse wrote:
> >> On 22/11/16 04:32, Pratyush Anand wrote:
> >>> +/*
> >>> + * disable_dcache: Disable D-cache and flush RAM locations
> >>> + * ram_start - Start address of RAM
> >>> + * ram_end - End address of RAM
> >>> + */
> >>> +void disable_dcache(uint64_t ram_start, uint64_t ram_end)
> >>> +{
> >>> + switch(get_current_el()) {
> >>> + case 2:
> >>> + reset_sctlr_el2();
> >>> + break;
> >>> + case 1:
> >>> + reset_sctlr_el1();
> >>
> >> You have C code running between disabling the MMU and cleaning the cache. The
> >> compiler is allowed to move data on and off the stack in here, but after
> >> disabling the MMU it will see whatever was on the stack before we turned the MMU
> >> on. Any data written at the beginning of this function is left in the caches.
> >>
> >> I'm afraid this sort of stuff needs to be done in assembly!
> >
> > All these routines are self coded in assembly even though they are called
> > from C, so should be safe I think. Anyway, I can keep all of them in
> > assembly as well.
>
> You can't tell the compiler that the stack data is inaccessible until the dcache
> clean call completes. Some future version may do really crazy things in here.
> You can decompile what your compiler version produces to check it doesn't
> load/store to the stack, but that doesn't mean my compiler version does the
> same. This is the kind of thing that is extremely difficult to debug, its best
> not to take the risk.
FWIW, I completely agree.
We've been bitten in the past; see commit 5e051531447259e5 ("arm64:
convert part of soft_restart() to assembly") for an example.
Thanks,
Mark.
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] arm64: Add enable/disable d-cache support for purgatory
Date: Wed, 14 Dec 2016 11:28:06 +0000 [thread overview]
Message-ID: <20161214112806.GD17982@leverpostej> (raw)
In-Reply-To: <585129F7.6070704@arm.com>
On Wed, Dec 14, 2016 at 11:16:07AM +0000, James Morse wrote:
> Hi Pratyush,
> On 14/12/16 09:38, Pratyush Anand wrote:
> > On Saturday 26 November 2016 12:00 AM, James Morse wrote:
> >> On 22/11/16 04:32, Pratyush Anand wrote:
> >>> +/*
> >>> + * disable_dcache: Disable D-cache and flush RAM locations
> >>> + * ram_start - Start address of RAM
> >>> + * ram_end - End address of RAM
> >>> + */
> >>> +void disable_dcache(uint64_t ram_start, uint64_t ram_end)
> >>> +{
> >>> + switch(get_current_el()) {
> >>> + case 2:
> >>> + reset_sctlr_el2();
> >>> + break;
> >>> + case 1:
> >>> + reset_sctlr_el1();
> >>
> >> You have C code running between disabling the MMU and cleaning the cache. The
> >> compiler is allowed to move data on and off the stack in here, but after
> >> disabling the MMU it will see whatever was on the stack before we turned the MMU
> >> on. Any data written at the beginning of this function is left in the caches.
> >>
> >> I'm afraid this sort of stuff needs to be done in assembly!
> >
> > All these routines are self coded in assembly even though they are called
> > from C, so should be safe I think. Anyway, I can keep all of them in
> > assembly as well.
>
> You can't tell the compiler that the stack data is inaccessible until the dcache
> clean call completes. Some future version may do really crazy things in here.
> You can decompile what your compiler version produces to check it doesn't
> load/store to the stack, but that doesn't mean my compiler version does the
> same. This is the kind of thing that is extremely difficult to debug, its best
> not to take the risk.
FWIW, I completely agree.
We've been bitten in the past; see commit 5e051531447259e5 ("arm64:
convert part of soft_restart() to assembly") for an example.
Thanks,
Mark.
next prev parent reply other threads:[~2016-12-14 11:28 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-22 4:32 [PATCH 0/2] kexec-tools: arm64: Add dcache enabling facility Pratyush Anand
2016-11-22 4:32 ` Pratyush Anand
2016-11-22 4:32 ` [PATCH 1/2] arm64: Add enable/disable d-cache support for purgatory Pratyush Anand
2016-11-22 4:32 ` Pratyush Anand
2016-11-25 18:30 ` James Morse
2016-11-25 18:30 ` James Morse
2016-12-14 9:38 ` Pratyush Anand
2016-12-14 9:38 ` Pratyush Anand
2016-12-14 10:12 ` Pratyush Anand
2016-12-14 10:12 ` Pratyush Anand
2016-12-14 11:16 ` James Morse
2016-12-14 11:16 ` James Morse
2016-12-14 11:37 ` Mark Rutland
2016-12-14 11:37 ` Mark Rutland
2016-12-14 12:11 ` James Morse
2016-12-14 12:11 ` James Morse
2016-12-14 12:21 ` Pratyush Anand
2016-12-14 12:21 ` Pratyush Anand
2016-12-14 13:44 ` Mark Rutland
2016-12-14 13:44 ` Mark Rutland
2016-12-14 14:13 ` Pratyush Anand
2016-12-14 14:13 ` Pratyush Anand
2016-12-14 12:13 ` Pratyush Anand
2016-12-14 12:13 ` Pratyush Anand
2016-12-14 11:16 ` James Morse
2016-12-14 11:16 ` James Morse
2016-12-14 11:28 ` Mark Rutland [this message]
2016-12-14 11:28 ` Mark Rutland
2016-11-22 4:32 ` [PATCH 2/2] arm64: Pass RAM boundary and enable-dcache flag to purgatory Pratyush Anand
2016-11-22 4:32 ` Pratyush Anand
2016-11-22 18:57 ` Geoff Levand
2016-11-22 18:57 ` Geoff Levand
2016-11-23 1:46 ` Pratyush Anand
2016-11-23 1:46 ` Pratyush Anand
2016-11-23 2:03 ` Dave Young
2016-11-23 2:03 ` Dave Young
2016-11-23 2:11 ` Pratyush Anand
2016-11-23 2:11 ` Pratyush Anand
2016-11-23 8:08 ` Simon Horman
2016-11-23 8:08 ` Simon Horman
2016-11-23 8:17 ` Pratyush Anand
2016-11-23 8:17 ` Pratyush Anand
2016-11-22 18:56 ` [PATCH 0/2] kexec-tools: arm64: Add dcache enabling facility Geoff Levand
2016-11-22 18:56 ` Geoff Levand
2016-11-23 1:39 ` Pratyush Anand
2016-11-23 1:39 ` Pratyush Anand
2016-11-25 18:30 ` James Morse
2016-11-25 18:30 ` James Morse
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=20161214112806.GD17982@leverpostej \
--to=mark.rutland@arm.com \
--cc=geoff@infradead.org \
--cc=james.morse@arm.com \
--cc=kexec@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=panand@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.