From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Gustavo Romero <gromero@linux.vnet.ibm.com>,
linuxppc-dev@lists.ozlabs.org
Cc: cyrilbur@gmail.com, Gustavo Romero <gromero@linux.vnet.ibm.com>
Subject: Re: powerpc/tm: fix TM SPRs in code dump file
Date: Mon, 31 Jul 2017 16:31:40 +1000 (AEST) [thread overview]
Message-ID: <3xLV3J3Yrjz9tW3@ozlabs.org> (raw)
In-Reply-To: <1500443053-1264-1-git-send-email-gromero@linux.vnet.ibm.com>
On Wed, 2017-07-19 at 05:44:13 UTC, Gustavo Romero wrote:
> Currently flush_tmregs_to_thread() does not update accordingly the thread
> structures from live state before a core dump rendering wrong values of
> THFAR, TFIAR, and TEXASR in core dump files.
>
> That commit fixes it by copying from live state to the appropriate thread
> structures when it's necessary.
>
> Signed-off-by: Gustavo Romero <gromero@linux.vnet.ibm.com>
> Reviewed-by: Cyril Bur <cyrilbur@gmail.com>
Applied to powerpc fixes, thanks.
https://git.kernel.org/powerpc/c/cd63f3cf1d59b7ad8419eba1cac8f9
cheers
prev parent reply other threads:[~2017-07-31 6:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-19 5:44 [PATCH] powerpc/tm: fix TM SPRs in code dump file Gustavo Romero
2017-07-24 1:36 ` Cyril Bur
2017-07-31 6:31 ` Michael Ellerman [this message]
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=3xLV3J3Yrjz9tW3@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=cyrilbur@gmail.com \
--cc=gromero@linux.vnet.ibm.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).