linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] arm64: add EFI stub
Date: Mon, 16 Dec 2013 15:46:01 +0000	[thread overview]
Message-ID: <20131216154601.GH17713@arm.com> (raw)
In-Reply-To: <1386341754.1861.188.camel@deneb.redhat.com>

On Fri, Dec 06, 2013 at 02:55:54PM +0000, Mark Salter wrote:
> On Thu, 2013-12-05 at 14:18 +0000, Catalin Marinas wrote:
> > On Fri, Nov 29, 2013 at 10:05:10PM +0000, Mark Salter wrote:
> > > +       add     x2, sp, 16
> > > +       str     x8, [x2]
> > > +       bl      efi_entry
> > > +       cmn     x0, #1
> > > +       b.eq    efi_load_fail
> > > +
> > > +       /*
> > > +        * efi_entry() will have relocated the kernel image if necessary
> > > +        * and we return here with device tree address in x0 and the kernel
> > > +        * entry point stored at *image_addr. Save those values in registers
> > > +        * which are preserved by __flush_dcache_all.
> > > +        */
> > > +       ldr     x1, [sp, #16]
> > > +       mov     x20, x0
> > > +       mov     x21, x1
> > > +
> > > +       bl      __flush_dcache_all
> > 
> > Regarding __flush_dcache_all, I plan to remove it for all cases apart
> > from power management with the MMU disabled. With MMU enabled, there is
> > no guarantee that this function does the right thing. It's even worse in
> > the guest context.
> 
> According to booting.txt, the dcache needs to be invalidated. Is there
> something existing I can use or do I need to write it?

The function will stay for a few cases where needed. But here the
D-cache and MMU are still on at this point and there is a slight chance
of speculative loads after the flush (though only clean lines). You
could move this after he MMU disabling (but still keep the I-cache on
for performance).

-- 
Catalin

  reply	other threads:[~2013-12-16 15:46 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-29 22:05 [PATCH 0/3] arm64: Add EFI stub and runtime services support Mark Salter
     [not found] ` < 1385762712-17043-2-git-send-email-msalter@redhat.com>
2013-11-29 22:05 ` [PATCH 1/3] arm64: add EFI stub Mark Salter
2013-12-03 18:38   ` Will Deacon
2013-12-03 19:31     ` Roy Franz
2013-12-03 19:31     ` Mark Salter
2013-12-05 14:18   ` Catalin Marinas
2013-12-05 14:43     ` Mark Salter
2013-12-05 15:28       ` Catalin Marinas
2013-12-06 12:25         ` Grant Likely
2013-12-06 13:34           ` Mark Salter
2013-12-06 13:38             ` Leif Lindholm
2013-12-06 13:51               ` Mark Salter
2013-12-06 14:55     ` Mark Salter
2013-12-16 15:46       ` Catalin Marinas [this message]
2013-12-06 12:12   ` Grant Likely
2013-11-29 22:05 ` [PATCH 2/3] doc: arm64: add description of EFI stub support Mark Salter
2013-12-05 12:53   ` Grant Likely
2013-11-29 22:05 ` [PATCH 3/3] arm64: add EFI runtime services Mark Salter
2013-12-05 15:25   ` Catalin Marinas
2013-12-05 15:52     ` Mark Salter
2013-12-05 15:59       ` Catalin Marinas
2013-12-06 14:34     ` Mark Salter
2013-12-09 13:52   ` Leif Lindholm
2013-12-10 17:58     ` Mark Salter

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=20131216154601.GH17713@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).