All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hollis Blanchard <hollisb@us.ibm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Avi Kivity <avi@redhat.com>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: KVM: powerpc: Fix BUILD_BUG_ON condition
Date: Mon, 02 Nov 2009 08:42:31 -0800	[thread overview]
Message-ID: <1257180151.11206.3.camel@slab> (raw)
In-Reply-To: <20091102170815.86e2daf7.sfr@canb.auug.org.au>

On Mon, 2009-11-02 at 17:08 +1100, Stephen Rothwell wrote:
> Hi Hollis, Avi,
> 
> This commit was added to the kvm tree recently:
> 
> > Author: Hollis Blanchard <hollisb@us.ibm.com>
> > Date:   Fri Oct 23 00:35:30 2009 +0000
> > 
> >     KVM: powerpc: Fix BUILD_BUG_ON condition
> >     
> >     The old BUILD_BUG_ON implementation didn't work with __builtin_constant_p().
> >     Fixing that revealed this test had been inverted for a long time without
> >     anybody noticing...
> >     
> >     Signed-off-by: Hollis Blanchard <hollisb@us.ibm.com>
> >     Signed-off-by: Avi Kivity <avi@redhat.com>
> > 
> > diff --git a/arch/powerpc/kvm/timing.h b/arch/powerpc/kvm/timing.h
> > index bb13b1f..a550f0f 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++;
> 
> It is OK as far as it goes.  It still does not build, though, due to the
> new BUILD_BUG_ON macro.

Correct.

> So I have still commented out the BUILD_BUG_ON in linux-next.

I've pointed out a few times that Rusty's patch (Subject "BUILD_BUG_ON:
make it handle more cases", Date "Tue, 20 Oct 2009 14:15:33 +1030") is
needed to fix the problem with BUILD_BUG_ON().

So far I haven't seen anybody acknowledge the patch or indicate it will
actually be committed.

-- 
Hollis Blanchard
IBM Linux Technology Center

      reply	other threads:[~2009-11-02 16:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-02  6:08 KVM: powerpc: Fix BUILD_BUG_ON condition Stephen Rothwell
2009-11-02 16:42 ` Hollis Blanchard [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=1257180151.11206.3.camel@slab \
    --to=hollisb@us.ibm.com \
    --cc=avi@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.