linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Balbir Singh <bsingharora@gmail.com>
To: Chris Smart <chris@distroguy.com>, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] powerpc: Add support for userspace P9 copy paste
Date: Tue, 26 Apr 2016 17:45:41 +1000	[thread overview]
Message-ID: <571F1CA5.9020208@gmail.com> (raw)
In-Reply-To: <20160426002844.GA9198@x1.distroguy.com>

> /*
>  * System calls.
> @@ -508,6 +509,14 @@ BEGIN_FTR_SECTION
>     ldarx    r6,0,r1
> END_FTR_SECTION_IFSET(CPU_FTR_STCX_CHECKS_ADDRESS)
> 
> +BEGIN_FTR_SECTION
> +/*
> + * A cp_abort (copy paste abort) here ensures that when context switching, a
> + * copy from one process can't leak into the paste of another.
> + */
> +        PPC_CP_ABORT

I think the alignment issue has been called out, but it is not clear from the changelog that
we do this during syscall_exit/syscalls.

And also, do we need to care about preemptions, etc by the scheduler?

> +END_FTR_SECTION_IFSET(CPU_FTR_ARCH_300)
> +
> #ifdef CONFIG_PPC_BOOK3S
> /* Cancel all explict user streams as they will have no use after context
>  * switch and will stop the HW from creating streams itself

  parent reply	other threads:[~2016-04-26  7:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-26  0:28 [PATCH] powerpc: Add support for userspace P9 copy paste Chris Smart
2016-04-26  6:42 ` Cyril Bur
2016-04-26  6:49   ` Chris Smart
2016-04-26  7:45 ` Balbir Singh [this message]
2016-04-27  2:05   ` Michael Neuling
2016-04-27 15:25 ` David Laight
2016-04-27 23:51   ` Chris Smart
2016-04-28 14:48     ` David Laight
2016-04-28 14:22 ` 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=571F1CA5.9020208@gmail.com \
    --to=bsingharora@gmail.com \
    --cc=chris@distroguy.com \
    --cc=linuxppc-dev@lists.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).