From: Segher Boessenkool <segher@kernel.crashing.org>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: linuxppc-dev@ozlabs.org, Anton Blanchard <anton@samba.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: Re: [PATCH] powerpc: Enable VMX copy on PPC970 (G5)
Date: Fri, 22 Jan 2016 02:08:57 -0600 [thread overview]
Message-ID: <20160122080857.GA11095@gate.crashing.org> (raw)
In-Reply-To: <1453335927-17419-1-git-send-email-mpe@ellerman.id.au>
On Thu, Jan 21, 2016 at 11:25:27AM +1100, Michael Ellerman wrote:
> 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.
But is it faster?
Segher
next prev parent reply other threads:[~2016-01-22 8:12 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
2016-01-22 8:08 ` Segher Boessenkool [this message]
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=20160122080857.GA11095@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=anton@samba.org \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mpe@ellerman.id.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 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).