From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Matt Brown <matthew.brown.dev@gmail.com>, linuxppc-dev@lists.ozlabs.org
Cc: anton@samba.org
Subject: Re: powerpc/lib: Split xor_vmx file to guarantee instruction ordering
Date: Mon, 5 Jun 2017 20:21:51 +1000 (AEST) [thread overview]
Message-ID: <3wh9pl4vtXz9sN5@ozlabs.org> (raw)
In-Reply-To: <20170523234559.28080-1-matthew.brown.dev@gmail.com>
On Tue, 2017-05-23 at 23:45:59 UTC, Matt Brown wrote:
> The xor_vmx.c file is used for the RAID5 xor operations. In these functions
> altivec is enabled to run the operation and then disabled. However due to
> compiler instruction reordering, altivec instructions are being run before
> enable_altivec() and after disable_altivec().
>
> This patch splits the non-altivec code into xor_vmx_glue.c which calls the
> altivec functions in xor_vmx.c. By compiling xor_vmx_glue.c without
> -maltivec we can guarantee that altivec instruction will not be reordered
> outside of the enable/disable block.
>
> Signed-off-by: Matt Brown <matthew.brown.dev@gmail.com>
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/f718d426d7e42eec6e5d2932f52a51
cheers
prev parent reply other threads:[~2017-06-05 10:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-23 23:45 [PATCH] powerpc/lib: Split xor_vmx file to guarantee instruction ordering Matt Brown
2017-05-24 13:36 ` Paul Clarke
2017-05-25 4:56 ` Matt Brown
2017-05-25 13:25 ` Paul Clarke
2017-05-26 4:12 ` Michael Ellerman
2017-06-05 10:21 ` Michael Ellerman [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=3wh9pl4vtXz9sN5@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=anton@samba.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=matthew.brown.dev@gmail.com \
/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.