From: Anshuman Khandual <khandual@linux.vnet.ibm.com>
To: Michael Neuling <mikey@neuling.org>,
mpe@ellerman.id.au, benh@kernel.crashing.org
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org, sam.bobroff@au1.ibm.com
Subject: Re: [PATCH 1/5] powerpc: Print MSR TM bits in oops message
Date: Mon, 16 Nov 2015 12:52:19 +0530 [thread overview]
Message-ID: <5649842B.9080107@linux.vnet.ibm.com> (raw)
In-Reply-To: <1447390652-28355-1-git-send-email-mikey@neuling.org>
On 11/13/2015 10:27 AM, Michael Neuling wrote:
> Print the 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.
>
Just a small nit, the above commit message can be formatted better.
next prev parent reply other threads:[~2015-11-16 7:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-13 4:57 [PATCH 1/5] powerpc: Print MSR TM bits in oops message Michael Neuling
2015-11-13 4:57 ` [PATCH 2/5] selftests/powerpc: Add TM signal return selftest Michael Neuling
2015-11-16 10:24 ` Michael Ellerman
2015-11-17 10:12 ` Michael Neuling
2015-11-13 4:57 ` [PATCH 3/5] powerpc/tm: Block signal return setting invalid MSR state Michael Neuling
2015-11-16 10:05 ` Michael Ellerman
2015-11-17 10:30 ` Michael Neuling
2015-11-13 4:57 ` [PATCH 4/5] powerpc/tm: Check for already reclaimed tasks Michael Neuling
2015-11-16 7:21 ` Anshuman Khandual
2015-11-16 9:23 ` Michael Neuling
2015-11-16 9:33 ` Michael Ellerman
2015-11-16 10:21 ` Michael Neuling
2015-11-13 4:57 ` [PATCH 5/5] powerpc/tm: Clarify get_tm_stackpointer() by renaming it Michael Neuling
2015-11-16 9:51 ` Michael Ellerman
2015-11-16 7:22 ` Anshuman Khandual [this message]
2015-11-16 9:27 ` [PATCH 1/5] powerpc: Print MSR TM bits in oops message Michael Ellerman
2015-11-16 22:07 ` Anton Blanchard
2015-11-17 10:01 ` 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=5649842B.9080107@linux.vnet.ibm.com \
--to=khandual@linux.vnet.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mikey@neuling.org \
--cc=mpe@ellerman.id.au \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.