From: Michael Ellerman <mpe@ellerman.id.au>
To: Marc Dietrich <marvin24@gmx.de>, linuxppc-dev@lists.ozlabs.org
Cc: linuxppc-dev@ozlabs.org, Anton Blanchard <anton@samba.org>
Subject: Re: [PATCH] powerpc: Enable VMX copy on PPC970 (G5)
Date: Thu, 21 Jan 2016 21:23:44 +1100 [thread overview]
Message-ID: <1453371824.28627.0.camel@ellerman.id.au> (raw)
In-Reply-To: <7901441.McfCmZyUcA@fb07-iapwap2>
On Thu, 2016-01-21 at 10:51 +0100, Marc Dietrich wrote:
> Am Donnerstag, 21. Januar 2016, 11:25:27 schrieb Michael Ellerman:
> > There's no reason I'm aware of that the VMX copy loop shouldn't work on
> > PPC970. And in fact it seems to boot and generally be happy.
>
> does the same also hold for Cell? Maybe there are even more optimizations
> which can be copied from PPC970.
Yeah in theory the PPE has VMX, I'll try it.
cheers
next prev parent reply other threads:[~2016-01-21 10:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-21 0:25 [PATCH] powerpc: Enable VMX copy on PPC970 (G5) Michael Ellerman
2016-01-21 9:51 ` Marc Dietrich
2016-01-21 10:23 ` Michael Ellerman [this message]
2016-01-22 8:08 ` Segher Boessenkool
2016-01-22 8:37 ` Michael Ellerman
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=1453371824.28627.0.camel@ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=anton@samba.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=marvin24@gmx.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;
as well as URLs for NNTP newsgroup(s).