public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman•id.au>
To: Jack Miller <jack@codezen•org>, linuxppc-dev@lists•ozlabs.org
Cc: michael.neuling@au1•ibm.com
Subject: Re: [1/3] powerpc: Complete FSCR context switch
Date: Wed, 13 Apr 2016 09:42:20 +1000 (AEST)	[thread overview]
Message-ID: <3ql3Pm4TZ5z9t4B@ozlabs.org> (raw)
In-Reply-To: <1460401065-10540-2-git-send-email-jack@codezen.org>

On Mon, 2016-11-04 at 18:57:43 UTC, Jack Miller wrote:
> Previously we just saved the FSCR, but only restored it in some
> settings, and never copied it thread to thread. This patch always
> restores the FSCR and formalizes new threads inheriting its setting so
> that later we can manipulate FSCR bits in start_thread.

This seems like it's a bug in the current code?

cheers

  reply	other threads:[~2016-04-12 23:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-11 18:57 [RFC] P9 ldmx support Jack Miller
2016-04-11 18:57 ` [PATCH 1/3] powerpc: Complete FSCR context switch Jack Miller
2016-04-12 23:42   ` Michael Ellerman [this message]
2016-04-13 10:51   ` Anton Blanchard
2016-04-13 17:52     ` Jack Miller
2016-04-13 23:49       ` Michael Neuling
2016-04-14 18:39         ` Jack Miller
2016-04-14 23:11           ` Michael Neuling
2016-04-11 18:57 ` [PATCH 2/3] powerpc: Load Monitor Register Support Jack Miller
2016-04-12  5:40   ` Segher Boessenkool
2016-04-13 17:39     ` Jack Miller
2016-04-11 18:57 ` [PATCH 3/3] powerpc: Load Monitor Register Tests Jack Miller
2016-04-15 10:34   ` Madhavan Srinivasan
2016-04-12  1:05 ` [RFC] P9 ldmx support Michael Neuling

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=3ql3Pm4TZ5z9t4B@ozlabs.org \
    --to=mpe@ellerman$(echo .)id.au \
    --cc=jack@codezen$(echo .)org \
    --cc=linuxppc-dev@lists$(echo .)ozlabs.org \
    --cc=michael.neuling@au1$(echo .)ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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