public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64/efi: efistub: jump to 'stext' directly, not through the header
Date: Tue, 15 Jul 2014 12:31:38 +0100	[thread overview]
Message-ID: <20140715113138.GZ26465@leverpostej> (raw)
In-Reply-To: <CAKv+Gu_PUJVXbDqp5Y3jdVouWhSqPVzaOi_6bpFM6BaLVrwvTQ@mail.gmail.com>

> >> diff --git a/arch/arm64/kernel/efi-entry.S b/arch/arm64/kernel/efi-entry.S
> >> index 619b1dd7bcde..6ef541731d9e 100644
> >> --- a/arch/arm64/kernel/efi-entry.S
> >> +++ b/arch/arm64/kernel/efi-entry.S
> >> @@ -61,7 +61,7 @@ ENTRY(efi_stub_entry)
> >>        */
> >>       mov     x20, x0         // DTB address
> >>       ldr     x0, [sp, #16]   // relocated _text address
> >> -     mov     x21, x0
> >> +     add     x21, x0, #:lo12:stext_offset
> >
> > I think we can drop the :lo12: here, which will allow us to have a
> > warning if stext_offset is unexpectedly large (I believe this will
> > currently silently mask bits were that to happen?).
> >
> 
> There is no alternative lo12 relocation that errors out when the value
> does not fit, so it would have to use a literal instead.

Ah, that's a shame. What happens when the value doesn't fit if the
linker / assembler don't error out?

That sounds like a toolchain bug if they're silently doing the wrong
thing.

Cheers,
Mark.

  reply	other threads:[~2014-07-15 11:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-15  9:10 [PATCH] arm64/efi: efistub: jump to 'stext' directly, not through the header Ard Biesheuvel
2014-07-15  9:57 ` Mark Rutland
2014-07-15 10:22   ` Ard Biesheuvel
2014-07-15 11:31     ` Mark Rutland [this message]
2014-07-15 11:49       ` Ard Biesheuvel
2014-07-15 12:44         ` Mark Rutland

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=20140715113138.GZ26465@leverpostej \
    --to=mark.rutland@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