From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] arm64: boot fixes/updates
Date: Fri, 13 Mar 2015 16:14:33 +0000 [thread overview]
Message-ID: <1426263277-9827-1-git-send-email-mark.rutland@arm.com> (raw)
Hi all,
The following patches address a few boot related issues I spotted
recently.
The first patch fixes alternatives for !SMP kernels, the second fixes a
potential issue with boot mode detection, and the final patches give us
some better logging of the boot mode, fixing a latent bug in mismatch
detection (though until now this has not been a problem).
Ard, Marc, I guess our recent boot patches are all going to clash. Do we
need to sort that out between us or are we relying on the arm64
maintainers? ;)
Thanks,
Mark.
Mark Rutland (4):
arm64: apply alternatives for !SMP kernels
arm64: head.S: fix __boot_cpu_mode alignment
arm64: fix hyp mode mismatch detection
arm64: log CPU boot modes
arch/arm64/Kconfig | 4 ++++
arch/arm64/include/asm/smp_plat.h | 2 ++
arch/arm64/kernel/head.S | 4 ++--
arch/arm64/kernel/setup.c | 25 +++++++++++++++++++++++++
arch/arm64/kernel/smp.c | 2 +-
5 files changed, 34 insertions(+), 3 deletions(-)
--
1.9.1
next reply other threads:[~2015-03-13 16:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-13 16:14 Mark Rutland [this message]
2015-03-13 16:14 ` [PATCH 1/4] arm64: apply alternatives for !SMP kernels Mark Rutland
2015-03-17 16:01 ` Ard Biesheuvel
2015-03-13 16:14 ` [PATCH 2/4] arm64: head.S: fix __boot_cpu_mode alignment Mark Rutland
2015-03-13 16:14 ` [PATCH 3/4] arm64: fix hyp mode mismatch detection Mark Rutland
2015-03-13 20:21 ` Ard Biesheuvel
2015-03-16 10:56 ` Mark Rutland
2015-03-16 11:03 ` Marc Zyngier
2015-03-16 11:05 ` Ard Biesheuvel
2015-03-17 15:58 ` Ard Biesheuvel
2015-03-13 16:14 ` [PATCH 4/4] arm64: log CPU boot modes Mark Rutland
2015-03-17 15:58 ` Ard Biesheuvel
2015-03-14 7:59 ` [PATCH 0/4] arm64: boot fixes/updates Ard Biesheuvel
2015-03-16 10:53 ` 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=1426263277-9827-1-git-send-email-mark.rutland@arm.com \
--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;
as well as URLs for NNTP newsgroup(s).