All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Caraman Mihai Claudiu-B02008 <B02008@freescale.com>
Cc: Alexander Graf <agraf@suse.de>,
	Wood Scott-B07421 <B07421@freescale.com>,
	"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 18:06:25 +0000	[thread overview]
Message-ID: <1368209185.19683.4@snotra> (raw)
In-Reply-To: <300B73AA675FCE4A93EB4FC1D42459FF408017@039-SN2MPN1-013.039d.mgd.msft.net> (from B02008@freescale.com on Fri May 10 13:03:27 2013)

On 05/10/2013 01:03:27 PM, Caraman Mihai Claudiu-B02008 wrote:
> > -----Original Message-----
> > From: kvm-ppc-owner@vger.kernel.org [mailto:kvm-ppc-
> > owner@vger.kernel.org] On Behalf Of Alexander Graf
> > Sent: Friday, May 10, 2013 7:51 PM
> > To: Caraman Mihai Claudiu-B02008
> > Cc: Wood Scott-B07421; kvm-ppc@vger.kernel.org; kvm@vger.kernel.org
> > Subject: Re: [PATCH] kvm/ppc/booke64: fix build breakage from  
> Altivec,
> > and disable e6500
> >
> >
> > On 10.05.2013, at 18:50, Caraman Mihai Claudiu-B02008 wrote:
> >
> > >>> Do we really need to remove e6500 all together for this?
> > >>
> > >> No, just send real Altivec support quickly. We can add it to 3.10
> > through
> > >> stable if it's too later, but I'd prefer to have it in within  
> the rc
> > >> phase.
> > >
> > > I should have it by Monday, the smoke tests passed.
> >
> > Please make sure it also works on 32bit :)
> 
> I can make sure that it doesn't break 32-bit. Altivec is not present  
> in
> e500v2/e500mc/e5500 cores and e6500 is supported only by 64-bit host.  
> Are
> you looking for G4 support?

Just because Altivec isn't present on 32-bit doesn't mean that a  
particular patch can't break things there.  Just as a patch to deal  
with lazy ee issues can break 32-bit, even though 32-bit doesn't have  
lazy ee. :-)

-Scott

WARNING: multiple messages have this Message-ID (diff)
From: Scott Wood <scottwood@freescale.com>
To: Caraman Mihai Claudiu-B02008 <B02008@freescale.com>
Cc: Alexander Graf <agraf@suse.de>,
	Wood Scott-B07421 <B07421@freescale.com>,
	"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 13:06:25 -0500	[thread overview]
Message-ID: <1368209185.19683.4@snotra> (raw)
In-Reply-To: <300B73AA675FCE4A93EB4FC1D42459FF408017@039-SN2MPN1-013.039d.mgd.msft.net> (from B02008@freescale.com on Fri May 10 13:03:27 2013)

On 05/10/2013 01:03:27 PM, Caraman Mihai Claudiu-B02008 wrote:
> > -----Original Message-----
> > From: kvm-ppc-owner@vger.kernel.org [mailto:kvm-ppc-
> > owner@vger.kernel.org] On Behalf Of Alexander Graf
> > Sent: Friday, May 10, 2013 7:51 PM
> > To: Caraman Mihai Claudiu-B02008
> > Cc: Wood Scott-B07421; kvm-ppc@vger.kernel.org; kvm@vger.kernel.org
> > Subject: Re: [PATCH] kvm/ppc/booke64: fix build breakage from  
> Altivec,
> > and disable e6500
> >
> >
> > On 10.05.2013, at 18:50, Caraman Mihai Claudiu-B02008 wrote:
> >
> > >>> Do we really need to remove e6500 all together for this?
> > >>
> > >> No, just send real Altivec support quickly. We can add it to 3.10
> > through
> > >> stable if it's too later, but I'd prefer to have it in within  
> the rc
> > >> phase.
> > >
> > > I should have it by Monday, the smoke tests passed.
> >
> > Please make sure it also works on 32bit :)
> 
> I can make sure that it doesn't break 32-bit. Altivec is not present  
> in
> e500v2/e500mc/e5500 cores and e6500 is supported only by 64-bit host.  
> Are
> you looking for G4 support?

Just because Altivec isn't present on 32-bit doesn't mean that a  
particular patch can't break things there.  Just as a patch to deal  
with lazy ee issues can break 32-bit, even though 32-bit doesn't have  
lazy ee. :-)

-Scott

  reply	other threads:[~2013-05-10 18:06 UTC|newest]

Thread overview: 35+ 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  3:14 ` Scott Wood
2013-05-10  9:40 ` Caraman Mihai Claudiu-B02008
2013-05-10  9:40   ` Caraman Mihai Claudiu-B02008
2013-05-10 13:15   ` Alexander Graf
2013-05-10 13:15     ` Alexander Graf
2013-05-10 14:11     ` Caraman Mihai Claudiu-B02008
2013-05-10 14:11       ` Caraman Mihai Claudiu-B02008
2013-05-10 14:13       ` Alexander Graf
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 16:50             ` Alexander Graf
2013-05-10 18:03             ` Caraman Mihai Claudiu-B02008
2013-05-10 18:06               ` Scott Wood [this message]
2013-05-10 18:06                 ` Scott Wood
2013-05-10 18:22                 ` Alexander Graf
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:59                       ` Alexander Graf
2013-05-10 18:39                 ` Caraman Mihai Claudiu-B02008
2013-05-10 17:42       ` Scott Wood
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 18:23             ` Scott Wood
2013-05-10 19:06             ` Caraman Mihai Claudiu-B02008
2013-05-10 19:15               ` Scott Wood
2013-05-10 19:15                 ` Scott Wood
2013-05-30 21:52                 ` 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
2013-05-10 17:37     ` Scott Wood

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=1368209185.19683.4@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 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.