From: Michael Ellerman <mpe@ellerman.id.au>
To: Cyril Bur <cyrilbur@gmail.com>, linuxppc-dev@ozlabs.org
Subject: Re: [1/9] selftests/powerpc: Test the preservation of FPU and VMX regs across syscall
Date: Thu, 3 Mar 2016 21:58:52 +1100 (AEDT) [thread overview]
Message-ID: <20160303105852.A3A60140C3B@ozlabs.org> (raw)
In-Reply-To: <1456728831-31862-2-git-send-email-cyrilbur@gmail.com>
On Mon, 2016-29-02 at 06:53:43 UTC, Cyril Bur wrote:
> Test that the non volatile floating point and Altivec registers get
> correctly preserved across the fork() syscall.
>
> fork() works nicely for this purpose, the registers should be the same for
> both parent and child
>
> Signed-off-by: Cyril Bur <cyrilbur@gmail.com>
Series applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/01127f1ead4cef75e2b9b309e0
cheers
next prev parent reply other threads:[~2016-03-03 10:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-29 6:53 [PATCH 0/9] FP/VEC/VSX switching optimisations Cyril Bur
2016-02-29 6:53 ` [PATCH 1/9] selftests/powerpc: Test the preservation of FPU and VMX regs across syscall Cyril Bur
2016-03-03 10:58 ` Michael Ellerman [this message]
2016-02-29 6:53 ` [PATCH 2/9] selftests/powerpc: Test preservation of FPU and VMX regs across preemption Cyril Bur
2016-02-29 6:53 ` [PATCH 3/9] selftests/powerpc: Test FPU and VMX regs in signal ucontext Cyril Bur
2016-02-29 6:53 ` [PATCH 4/9] powerpc: Explicitly disable math features when copying thread Cyril Bur
2016-02-29 6:53 ` [PATCH 5/9] powerpc: Restore FPU/VEC/VSX if previously used Cyril Bur
2016-02-29 6:53 ` [PATCH 6/9] powerpc: Prepare for splitting giveup_{fpu, altivec, vsx} in two Cyril Bur
2016-02-29 6:53 ` [PATCH 7/9] powerpc: Add the ability to save FPU without giving it up Cyril Bur
2016-02-29 6:53 ` [PATCH 8/9] powerpc: Add the ability to save Altivec " Cyril Bur
2016-02-29 6:53 ` [PATCH 9/9] powerpc: Add the ability to save VSX " Cyril Bur
2016-02-29 23:02 ` [PATCH 0/9] FP/VEC/VSX switching optimisations Cyril Bur
2016-05-05 12:02 ` Naveen N. Rao
2016-05-06 10:48 ` Naveen N. Rao
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=20160303105852.A3A60140C3B@ozlabs.org \
--to=mpe@ellerman.id.au \
--cc=cyrilbur@gmail.com \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).