From: Michael Ellerman <mpe@ellerman.id.au>
To: Michael Neuling <mikey@neuling.org>, benh@kernel.crashing.org
Cc: linuxppc-dev@ozlabs.org, mikey@neuling.org, paulus@samba.org,
sam.bobroff@au1.ibm.com
Subject: Re: [v2,1/3] powerpc: Print MSR TM bits in oops messages
Date: Tue, 15 Dec 2015 22:27:05 +1100 (AEDT) [thread overview]
Message-ID: <20151215112706.0880B140323@ozlabs.org> (raw)
In-Reply-To: <1447992934-18905-2-git-send-email-mikey@neuling.org>
On Fri, 2015-20-11 at 04:15:32 UTC, Michael Neuling wrote:
> Print MSR TM bits in oops messages. This appends them to the end
> like this:
>
> MSR: 8000000502823031 <SF,VEC,VSX,FP,ME,IR,DR,LE,TM[TE]>
>
> You get the TM[] only if at least one TM MSR bit is set. Inside the
> TM[], E means Enabled (bit 32), S means Suspended (bit 33), and T
> means Transactional (bit 34)
>
> If no bits are set, you get no TM[] output.
>
> Include rework of printbits() to handle this case.
>
> Signed-off-by: Michael Neuling <mikey@neuling.org>
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/801c0b2c4db3a33d56b3e192
cheers
next prev parent reply other threads:[~2015-12-15 11:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-20 4:15 [PATCH v2 0/3] powerpc/tm: MSR oops printing and selftests Michael Neuling
2015-11-20 4:15 ` [PATCH v2 1/3] powerpc: Print MSR TM bits in oops messages Michael Neuling
2015-12-15 11:27 ` Michael Ellerman [this message]
2015-11-20 4:15 ` [PATCH v2 2/3] selftests/powerpc: Add TM signal return test Michael Neuling
2015-11-23 11:32 ` Anshuman Khandual
2015-12-15 11:27 ` [v2,2/3] " Michael Ellerman
2015-11-20 4:15 ` [PATCH v2 3/3] selftests/powerpc: Add TM signal with invalid stack test Michael Neuling
2015-11-23 11:32 ` Anshuman Khandual
2015-12-15 11:27 ` [v2, " 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=20151215112706.0880B140323@ozlabs.org \
--to=mpe@ellerman.id.au \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mikey@neuling.org \
--cc=paulus@samba.org \
--cc=sam.bobroff@au1.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).