linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Jack Miller <jack@codezen.org>
To: linuxppc-dev@lists.ozlabs.org
Cc: mpe@ellerman.id.au, mikey@neuling.org, anton@samba.org
Subject: [v2] P9 ldmx support
Date: Mon, 18 Apr 2016 14:07:59 -0500	[thread overview]
Message-ID: <1461006482-20595-1-git-send-email-jack@codezen.org> (raw)

Second spin of these patches:

https://lists.ozlabs.org/pipermail/linuxppc-dev/2016-April/141609.html

Differences from v1:

- As part of the FSCR context switch patch, remove extra FSCR manipulation in
  the DSCR case. If anything set FSCR.DSCR it should automatically be set
  correctly now. If I understand correctly, dscr_inherit is still required
  however and covers the < P8 case.

- Minor assembly readability clean up suggested by Segher (thanks!)

Any further comments or concerns welcome.

- Jack

             reply	other threads:[~2016-04-18 19:09 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-18 19:07 Jack Miller [this message]
2016-04-18 19:08 ` [PATCH 1/3] powerpc: Complete FSCR context switch Jack Miller
2016-04-18 19:08 ` [PATCH 2/3] powerpc: Load Monitor Register Support Jack Miller
2016-04-18 20:47   ` kbuild test robot
2016-04-18 21:08     ` [v3] P9 ldmx support Jack Miller
2016-04-18 21:08       ` [PATCH 1/3] powerpc: Complete FSCR context switch Jack Miller
2016-05-04 11:16         ` [PATCH v4] " Michael Neuling
2016-05-06  2:30           ` [PATCH v5 0/3] POWER9 Load Monitor Support Michael Neuling
2016-05-06  2:30             ` [PATCH v5 1/3] powerpc: Improve FSCR init and context switching Michael Neuling
2016-05-06  2:30             ` [PATCH v5 2/3] powerpc: Load Monitor Register Support Michael Neuling
2016-05-06  2:30             ` [PATCH v5 3/3] powerpc: Load Monitor Register Tests Michael Neuling
2016-06-08 10:38             ` [PATCH v6 0/3] POWER9 Load Monitor Support Michael Neuling
2016-06-08 10:38               ` [PATCH v6 1/3] powerpc: Improve FSCR init and context switching Michael Neuling
2016-06-08 10:38               ` [PATCH v6 2/3] powerpc: Load Monitor Register Support Michael Neuling
2016-06-08 10:38               ` [PATCH v6 3/3] powerpc: Load Monitor Register Tests Michael Neuling
2016-06-09  2:31               ` [PATCH v7 0/3] POWER9 Load Monitor Support Michael Neuling
2016-06-09  2:31                 ` [PATCH v7 1/3] powerpc: Improve FSCR init and context switching Michael Neuling
2016-06-21 12:27                   ` [v7,1/3] " Michael Ellerman
2016-06-09  2:31                 ` [PATCH v7 2/3] powerpc: Load Monitor Register Support Michael Neuling
2016-06-21 12:27                   ` [v7,2/3] " Michael Ellerman
2016-06-09  2:31                 ` [PATCH v7 3/3] powerpc: Load Monitor Register Tests Michael Neuling
2016-06-21 12:27                   ` [v7,3/3] " Michael Ellerman
2016-04-18 21:08       ` [PATCH 2/3] powerpc: Load Monitor Register Support Jack Miller
2016-04-18 21:08       ` [PATCH 3/3] powerpc: Load Monitor Register Tests Jack Miller
2016-05-04 10:43         ` Michael Neuling
2016-05-04 11:31           ` Michael Ellerman
2016-05-04 11:41             ` Michael Neuling
2016-04-18 19:08 ` Jack Miller

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=1461006482-20595-1-git-send-email-jack@codezen.org \
    --to=jack@codezen.org \
    --cc=anton@samba.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mikey@neuling.org \
    --cc=mpe@ellerman.id.au \
    /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).