public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Caraman Mihai Claudiu-B02008 <B02008@freescale.com>
Cc: Wood Scott-B07421 <B07421@freescale.com>,
	Alexander Graf <agraf@suse.de>,
	"kvm-ppc@vger.kernel.org" <kvm-ppc@vger.kernel.org>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [PATCH] kvm/ppc/booke64: fix build breakage from Altivec, and disable e6500
Date: Fri, 10 May 2013 12:37:17 -0500	[thread overview]
Message-ID: <1368207437.19683.1@snotra> (raw)
In-Reply-To: <300B73AA675FCE4A93EB4FC1D42459FF3FE2FA@039-SN2MPN1-011.039d.mgd.msft.net> (from B02008@freescale.com on Fri May 10 04:40:01 2013)

On 05/10/2013 04:40:01 AM, Caraman Mihai Claudiu-B02008 wrote:
> > -----Original Message-----
> > From: Wood Scott-B07421
> > Sent: Friday, May 10, 2013 6:15 AM
> > To: Alexander Graf
> > Cc: kvm-ppc@vger.kernel.org; kvm@vger.kernel.org; Wood Scott-B07421;
> > Caraman Mihai Claudiu-B02008
> > Subject: [PATCH] kvm/ppc/booke64: fix build breakage from Altivec,  
> and
> > disable e6500
> >
> > BookE altivec support brought two new exceptions, but KVM was not
> > updated, so the build broke for all 64-bit booke with KVM enabled.
> 
> We couldn't do that in KVM before having  
> BOOKE_INTERRUPT_ALTIVEC_UNAVAIL/
> BOOKE_INTERRUPT_ALTIVEC_ASSIST. As Tiejun noticed earlier we should  
> have
> done this in Kumar's tree but we missed that chance. We will face  
> similar
> issues every time an exception handler will be added.

Exceptions don't get handled all that often, and ideally we catch it  
when it's added rather than after-the-fact.

> > diff --git a/arch/powerpc/kvm/bookehv_interrupts.S
> > b/arch/powerpc/kvm/bookehv_interrupts.S
> > index e8ed7d6..6397613 100644
> > --- a/arch/powerpc/kvm/bookehv_interrupts.S
> > +++ b/arch/powerpc/kvm/bookehv_interrupts.S
> > @@ -309,6 +309,10 @@ kvm_handler BOOKE_INTERRUPT_DOORBELL_CRITICAL,
> > EX_PARAMS(CRIT), \
> >  	SPRN_CSRR0, SPRN_CSRR1, 0
> >  kvm_handler BOOKE_INTERRUPT_HV_PRIV, EX_PARAMS(GEN), \
> >  	SPRN_SRR0, SPRN_SRR1, NEED_EMU
> > +kvm_handler BOOKE_INTERRUPT_ALTIVEC_UNAVAIL, EX_PARAMS(GEN), \
> > +	SPRN_SRR0, SPRN_SRR1, 0
> > +kvm_handler BOOKE_INTERRUPT_ALTIVEC_ASSIST, EX_PARAMS(GEN), \
> > +	SPRN_SRR0, SPRN_SRR1, 0
> 
> Why not NEED_ESR as we did in our SDK?

This is just to fix the build break -- we don't need ESR yet.  Though I  
did look at the ESR documentation and didn't see where Altivec  
exceptions used it (I do see a couple places now).

-Scott

      parent reply	other threads:[~2013-05-10 17:37 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-10  3:14 [PATCH] kvm/ppc/booke64: fix build breakage from Altivec, and disable e6500 Scott Wood
2013-05-10  9:40 ` Caraman Mihai Claudiu-B02008
2013-05-10 13:15   ` Alexander Graf
2013-05-10 14:11     ` Caraman Mihai Claudiu-B02008
2013-05-10 14:13       ` Alexander Graf
2013-05-10 16:50         ` Caraman Mihai Claudiu-B02008
2013-05-10 16:50           ` Alexander Graf
2013-05-10 18:03             ` Caraman Mihai Claudiu-B02008
2013-05-10 18:06               ` Scott Wood
2013-05-10 18:22                 ` Alexander Graf
2013-05-10 18:51                   ` Caraman Mihai Claudiu-B02008
2013-05-10 18:59                     ` Alexander Graf
2013-05-10 18:39                 ` Caraman Mihai Claudiu-B02008
2013-05-10 17:42       ` Scott Wood
2013-05-10 18:20         ` Caraman Mihai Claudiu-B02008
2013-05-10 18:23           ` Scott Wood
2013-05-10 19:06             ` Caraman Mihai Claudiu-B02008
2013-05-10 19:15               ` Scott Wood
2013-05-30 21:52                 ` Scott Wood
2013-05-31  6:11                   ` Caraman Mihai Claudiu-B02008
2013-05-10 17:37   ` Scott Wood [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=1368207437.19683.1@snotra \
    --to=scottwood@freescale.com \
    --cc=B02008@freescale.com \
    --cc=B07421@freescale.com \
    --cc=agraf@suse.de \
    --cc=kvm-ppc@vger.kernel.org \
    --cc=kvm@vger.kernel.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