On Mon, 2015-11-16 at 20:27 +1100, Michael Ellerman wrote:
> On Fri, 2015-11-13 at 15:57 +1100, Michael Neuling wrote:
>
> > Print the MSR TM bits in oops messages. This appends them to the
> > end
> > like this:
> > MSR: 800502823031
> >
> > You get the TM[] only if at least one TM MSR bi
Hi,
> > +{
> > + if (val & (MSR_TM | MSR_TS_S | MSR_TS_T)) {
> > + printk(",TM[");
> > + printbits(val, msr_tm_bits, "");
> > + printk("]");
>
> I suspect all these individual printks are going to behave badly if
> we have multiple cpus crashing simultaneously. But
On Fri, 2015-11-13 at 15:57 +1100, Michael Neuling wrote:
> Print the MSR TM bits in oops messages. This appends them to the end
> like this:
> MSR: 800502823031
>
> 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 (bi
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: 800502823031
>
> 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
Print the MSR TM bits in oops messages. This appends them to the end
like this:
MSR: 800502823031
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
