Kernel KVM-PPC virtualization development
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: ppc-dev <linuxppc-dev@lists.ozlabs.org>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Jan Beulich <JBeulich@novell.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Hollis Blanchard <hollisb@us.ibm.com>,
	kvm-ppc@vger.kernel.org
Subject: linux-next: tree build failure
Date: Thu, 24 Sep 2009 05:21:02 +0000	[thread overview]
Message-ID: <20090924152102.8d7d40cf.sfr@canb.auug.org.au> (raw)

Hi all,

Today's linux-next build (powerpc ppc44x_defconfig) failed like this:

In file included from arch/powerpc/kvm/booke.c:31:
arch/powerpc/kvm/timing.h: In function 'kvmppc_account_exit_stat':
arch/powerpc/kvm/timing.h:51: error: bit-field '<anonymous>' width not an integer constant
In file included from arch/powerpc/kvm/booke.h:26,
                 from arch/powerpc/kvm/booke_emulate.c:23:
arch/powerpc/kvm/timing.h: In function 'kvmppc_account_exit_stat':
arch/powerpc/kvm/timing.h:51: error: bit-field '<anonymous>' width not an integer constant

Presumably caused by commit 8c87df457cb58fe75b9b893007917cf8095660a0
("BUILD_BUG_ON(): fix it and a couple of bogus uses of it").

I applied the following patch for today.  This inline function is
only called from one place in one file ...

From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Thu, 24 Sep 2009 15:13:20 +1000
Subject: [PATCH] powerpc/kvm: build fix for new BUILD_BUG_ON

Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
---
 arch/powerpc/kvm/timing.h |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/arch/powerpc/kvm/timing.h b/arch/powerpc/kvm/timing.h
index bb13b1f..4c34099 100644
--- a/arch/powerpc/kvm/timing.h
+++ b/arch/powerpc/kvm/timing.h
@@ -48,7 +48,7 @@ static inline void kvmppc_set_exit_type(struct kvm_vcpu *vcpu, int type) {}
 static inline void kvmppc_account_exit_stat(struct kvm_vcpu *vcpu, int type)
 {
 	/* type has to be known at build time for optimization */
-	BUILD_BUG_ON(__builtin_constant_p(type));
+	//BUILD_BUG_ON(__builtin_constant_p(type));
 	switch (type) {
 	case EXT_INTR_EXITS:
 		vcpu->stat.ext_intr_exits++;
-- 
1.6.4.3


-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

             reply	other threads:[~2009-09-24  5:21 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-24  5:21 Stephen Rothwell [this message]
2009-09-29  0:00 ` linux-next: tree build failure Hollis Blanchard
2009-09-29  9:28 ` Jan Beulich
2009-09-29  9:51   ` roel kluin
2009-09-30  6:29     ` Jan Beulich
2009-09-29 23:39   ` Hollis Blanchard
2009-09-30  6:35     ` Jan Beulich
2009-10-02 15:48       ` Hollis Blanchard
2009-10-05  6:58         ` Jan Beulich
2009-10-09 19:14           ` Hollis Blanchard
2009-10-14 22:57             ` Hollis Blanchard
2009-10-15  7:27               ` Jan Beulich
2009-10-19 18:19                 ` Hollis Blanchard
2009-10-20  1:24                   ` Rusty Russell
2009-10-20  1:29                     ` Hollis Blanchard
2009-10-20  3:57                       ` [PATCH] BUILD_BUG_ON: make it handle more cases Rusty Russell
2009-10-20 13:58                         ` Américo Wang
2009-10-20 14:43                           ` Alan Jenkins
2009-10-23  1:50                             ` Américo Wang
2009-10-22 21:04                         ` Hollis Blanchard
2009-10-29 21:30                         ` Hollis Blanchard
2009-11-05  0:20                         ` Stephen Rothwell
2009-11-05  6:40                           ` Rusty Russell
2009-11-05  6:38                             ` Stephen Rothwell
2009-11-06  6:42                               ` Rusty Russell
2009-11-05  6:49                             ` Rusty Russell
2009-11-05  6:01                         ` Benjamin Herrenschmidt

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=20090924152102.8d7d40cf.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=JBeulich@novell.com \
    --cc=akpm@linux-foundation.org \
    --cc=hollisb@us.ibm.com \
    --cc=kvm-ppc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.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