From: jason@lakedaemon.net (Jason Cooper)
To: linux-arm-kernel@lists.infradead.org
Subject: next build: 629 warnings 1 failures (next/next-20140723)
Date: Thu, 24 Jul 2014 18:48:36 -0400 [thread overview]
Message-ID: <20140724224836.GY23220@titan.lakedaemon.net> (raw)
In-Reply-To: <20140724132448.GB13371@arm.com>
On Thu, Jul 24, 2014 at 02:24:48PM +0100, Catalin Marinas wrote:
> On Thu, Jul 24, 2014 at 11:43:18AM +0100, Catalin Marinas wrote:
> > On Thu, Jul 24, 2014 at 09:50:37AM +0100, Will Deacon wrote:
> > > On Thu, Jul 24, 2014 at 12:27:30AM +0100, Olof Johansson wrote:
> > > > I'm building with a vanilla gcc 4.8.2 / binutils 2.23.2. That
> > > > shouldn't be broken like this, so those changes should be fixed (or
> > > > minimal toolchain expecations need to be documented -- but there
> > > > really is no good reason to require 4.9.0/2.24).
> > >
> > > These all come from the GICv3 driver, so it's not going to be a lot of fun
> > > fixing them. You'd have to introduce a macro for generating the system-reg
> > > accesses (for both C and asm), then switch the GIC driver and the arch code
> > > over to using that.
> >
> > We may need to document that enabling GICv3 requires a newer toolchain.
> >
> > Otherwise, my years old macros ;) (adapted here and untested):
> [...]
> > But I'll let Marc comment when he gets back from holiday (I'm pretty
> > sure he will enjoy it ;))
>
> Saving Marc some time:
>
> ------------8<--------------------------------
>
> From 3acb8b49aeba9f48153a2d719dec05d0b862e285 Mon Sep 17 00:00:00 2001
> From: Catalin Marinas <catalin.marinas@arm.com>
> Date: Thu, 24 Jul 2014 14:14:42 +0100
> Subject: [PATCH] arm64: gicv3: Allow GICv3 compilation with older binutils
>
> GICv3 introduces new system registers accessible with the full msr/mrs
> syntax (e.g. mrs x0, Sx_op0_op1_CRm_CRn_op2). However, only recent
> binutils understand the new syntax. This patch introduces msr_s/mrs_s
> assembly macros which generate the equivalent instructions above and
> converts the existing GICv3 code (both drivers/irqchip/ and
> arch/arm64/kernel/).
>
> Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
> Suggested-by: Mark Rutland <mark.rutland@arm.com>
> Reported-by: Olof Johansson <olof@lixom.net>
> Cc: Will Deacon <will.deacon@arm.com>
> Cc: Marc Zyngier <marc.zyngier@arm.com>
> ---
> arch/arm64/include/asm/sysreg.h | 60 ++++++++++++++++++++++++++++++++++++++
> arch/arm64/kernel/head.S | 6 ++--
> drivers/irqchip/irq-gic-v3.c | 16 +++++-----
> include/linux/irqchip/arm-gic-v3.h | 42 +++++++++++++-------------
> 4 files changed, 93 insertions(+), 31 deletions(-)
> create mode 100644 arch/arm64/include/asm/sysreg.h
I'm going to assume this goes on top of Marc's series, and that you'll
take it through arm64:
Acked-by: Jason Cooper <jason@lakedaemon.net>
thx,
Jason.
next prev parent reply other threads:[~2014-07-24 22:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <53cf8323.e4b6440a.7d37.4f75@mx.google.com>
2014-07-23 23:27 ` next build: 629 warnings 1 failures (next/next-20140723) Olof Johansson
2014-07-24 8:50 ` Will Deacon
2014-07-24 10:43 ` Catalin Marinas
2014-07-24 13:24 ` Catalin Marinas
2014-07-24 16:08 ` Olof Johansson
2014-07-24 22:48 ` Jason Cooper [this message]
2014-07-25 9:01 ` Catalin Marinas
2014-07-25 11:26 ` Jason Cooper
2014-07-25 12:14 ` Catalin Marinas
2014-07-28 8:23 ` Marc Zyngier
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=20140724224836.GY23220@titan.lakedaemon.net \
--to=jason@lakedaemon.net \
--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).