From: Simon Guo <wei.guo.simon@gmail.com>
To: linuxppc-dev@lists.ozlabs.org
Cc: Simon Guo <simonguo@linux.vnet.ibm.com>,
Laurent Dufour <ldufour@linux.vnet.ibm.com>,
Michael Ellerman <mpe@ellerman.id.au>
Subject: Re: [RESEND][PATCH v2] powerpc: Export thread_struct.used_vr/used_vsr to user space
Date: Wed, 22 Jun 2016 10:40:39 +0800 [thread overview]
Message-ID: <20160622024039.GA4313@simonLocalRHEL7.x64> (raw)
In-Reply-To: <20160621063006.GA6367@simonLocalRHEL7.x64>
On Tue, Jun 21, 2016 at 02:30:06PM +0800, Simon Guo wrote:
> Hi Michael,
> On Wed, Apr 06, 2016 at 03:00:12PM +0800, Simon Guo wrote:
> > These 2 fields track whether user process has used Altivec/VSX
> > registers or not. They are used by kernel to setup signal frame
> > on user stack correctly regarding vector part.
> >
> > CRIU(Checkpoint and Restore In User space) builds signal frame
> > for restored process. It will need this export information to
> > setup signal frame correctly. And CRIU will need to restore these
> > 2 fields for the restored process.
> >
> > Signed-off-by: Simon Guo <wei.guo.simon@gmail.com>
> > Reviewed-by: Laurent Dufour <ldufour@linux.vnet.ibm.com>
> > ---
>
> Just a kind reminder per our previous discussion.
> If possible, please help pull this in during 4.8 merge window. Some CRIU work items are pending for it.
>
> Have a nice day.
>
> Thanks,
> - Simon
+ linuxppc-dev list
Thanks,
- Simon (IBM LTC)
next prev parent reply other threads:[~2016-06-22 2:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-06 7:00 [RESEND][PATCH v2] powerpc: Export thread_struct.used_vr/used_vsr to user space Simon Guo
2016-04-12 2:58 ` Simon Guo
[not found] ` <20160621063006.GA6367@simonLocalRHEL7.x64>
2016-06-22 2:40 ` Simon Guo [this message]
2016-07-05 5:40 ` [RESEND, " Michael Ellerman
2016-07-04 21:08 ` Simon Guo
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=20160622024039.GA4313@simonLocalRHEL7.x64 \
--to=wei.guo.simon@gmail.com \
--cc=ldufour@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=simonguo@linux.vnet.ibm.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 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).