From: christoffer.dall@linaro.org (Christoffer Dall)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH][next] arm64: KVM: GICv3: move system register access to msr_s/mrs_s
Date: Thu, 31 Jul 2014 15:32:27 +0200 [thread overview]
Message-ID: <20140731133227.GA589@cbox> (raw)
In-Reply-To: <20140731131947.GT26853@arm.com>
On Thu, Jul 31, 2014 at 02:19:47PM +0100, Will Deacon wrote:
> On Thu, Jul 31, 2014 at 02:16:39PM +0100, Marc Zyngier wrote:
> > Commit 72c583951526 (arm64: gicv3: Allow GICv3 compilation with
> > older binutils) changed the way we express the GICv3 system registers,
> > but couldn't change the occurences used by KVM as the code wasn't
> > merged yet.
> >
> > Just fix the accessors.
> >
> > Cc: Will Deacon <will.deacon@arm.com>
> > Cc: Catalin Marinas <catalin.marinas@arm.com>
> > Cc: Christoffer Dall <christoffer.dall@linaro.org>
> > Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
> > ---
> > -next is currently borked. I suggest we take this patch via the kvmarm tree,
> > and only send our PR once the arm64 tree has hit Linus' tree. It contains
> > the same dependency on the GIC tree anyway.
>
> I'm fine with that as long as Paulo doesn't mind waiting for the arm64 stuff
> to go in first (I have no reason to delay my pull request, so shouldn't be
> an issue).
>
> If it helps:
>
> Acked-by: Will Deacon <will.deacon@arm.com>
>
> I can't help but point out that we wouldn't be in this mess if you'd got
> your stuff into -next sooner ;)
>
Well yes, but it was hard to plan our holidays around the deadlines and
unfortunately I couldn't find time to verify the kvmarm branch to make
it ready for -next inclusion before I went on holiday this time. In any
case, this should be the exception rather than the rule, and I do try to
get the next branch ready as soon as possible usually.
-Christoffer
next prev parent reply other threads:[~2014-07-31 13:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-31 13:16 [PATCH][next] arm64: KVM: GICv3: move system register access to msr_s/mrs_s Marc Zyngier
2014-07-31 13:19 ` Will Deacon
2014-07-31 13:32 ` Christoffer Dall [this message]
2014-07-31 16:05 ` Will Deacon
2014-07-31 16:30 ` Christoffer Dall
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=20140731133227.GA589@cbox \
--to=christoffer.dall@linaro.org \
--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).