From: Michael Ellerman <michaele@au1.ibm.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org,
"paulus\@samba.org" <paulus@samba.org>,
kvm@vger.kernel.org, kvm-ppc@vger.kernel.org,
"linuxppc-dev\@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Cc: tglx@linutronix.de, bobby.prani@gmail.com, peterz@infradead.org,
fweisbec@gmail.com, jiangshanlai@gmail.com,
josh@joshtriplett.org, rostedt@goodmis.org, oleg@redhat.com,
dhowells@redhat.com, edumazet@google.com,
mathieu.desnoyers@efficios.com, dipankar@in.ibm.com,
akpm@linux-foundation.org, mingo@kernel.org
Subject: Re: powerpc KVM build break in linux-next (was Re: [PATCH tip/core/rcu 40/40] srcu: Parallelize callback handling)
Date: Fri, 21 Apr 2017 12:13:49 +1000 [thread overview]
Message-ID: <87tw5itsma.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <24c85d26-bb4b-892d-5837-6d02af570e0e@redhat.com>
Paolo Bonzini <pbonzini@redhat.com> writes:
> Michael, if you want to move the two srcu structs at the end of struct
> kvm, that would be fine by me. Please send a patch yourself so you can
> test it on PPC. Thanks,
Paul beat me to it :)
I've confirmed it fixes the build break and the resulting kernel can
boot a KVM guest happily.
cheers
prev parent reply other threads:[~2017-04-21 2:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170412174003.GA23207@linux.vnet.ibm.com>
[not found] ` <1492018825-25634-40-git-send-email-paulmck@linux.vnet.ibm.com>
2017-04-20 3:40 ` powerpc KVM build break in linux-next (was Re: [PATCH tip/core/rcu 40/40] srcu: Parallelize callback handling) Michael Ellerman
2017-04-20 14:19 ` Paul E. McKenney
2017-04-20 15:28 ` Paolo Bonzini
2017-04-21 0:38 ` Paul E. McKenney
2017-04-21 1:42 ` Michael Ellerman
2017-04-21 4:17 ` Paul E. McKenney
2017-04-21 7:27 ` Paolo Bonzini
2017-04-21 12:51 ` Paul E. McKenney
2017-04-22 6:09 ` Michael Ellerman
2017-04-21 2:13 ` Michael Ellerman [this message]
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=87tw5itsma.fsf@concordia.ellerman.id.au \
--to=michaele@au1.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=bobby.prani@gmail.com \
--cc=dhowells@redhat.com \
--cc=dipankar@in.ibm.com \
--cc=edumazet@google.com \
--cc=fweisbec@gmail.com \
--cc=jiangshanlai@gmail.com \
--cc=josh@joshtriplett.org \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=paulus@samba.org \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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