From: Markos Chandras <Markos.Chandras@imgtec.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: <linux-mips@linux-mips.org>,
Leonid Yegoshin <Leonid.Yegoshin@imgtec.com>
Subject: Re: [PATCH] MIPS: Add printing of ES bit when cache error occurs.
Date: Tue, 8 Oct 2013 09:16:27 +0100 [thread overview]
Message-ID: <5253BF5B.40405@imgtec.com> (raw)
In-Reply-To: <20131008050633.GD1615@linux-mips.org>
On 10/08/13 06:06, Ralf Baechle wrote:
> On Mon, Oct 07, 2013 at 10:25:52AM +0100, Markos Chandras wrote:
>
>> From: Leonid Yegoshin <Leonid.Yegoshin@imgtec.com>
>>
>> Print out the source of request that caused the error (ES bit) when
>> a cache error exception occurs.
>
> The reason ES isn't being printed is that not all processors that support
> a cache error exception have an ES bit. The R4000 has it, R5000 doesn't,
> R10000 CacheErr looks rather different - and in fact MIPS32/64 make the
> entire register optional and its details implementation specific.
>
> Don't even ask me anymore which processor the implementation in the
> kernel is trying to support - probably something R7000ish, at least
> that's what guess from the 1385617929e09545f9858785ea3dc1068fedfde1
> commit log.
>
> Short of some fancy engineering, I'd suggest throwing in a switch
> statement and per processor type printks just as in parity_protection_init.
>
> Ralf
>
Hi Ralf,
hmm i see. ok i will do that instead.
WARNING: multiple messages have this Message-ID (diff)
From: Markos Chandras <Markos.Chandras@imgtec.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: linux-mips@linux-mips.org, Leonid Yegoshin <Leonid.Yegoshin@imgtec.com>
Subject: Re: [PATCH] MIPS: Add printing of ES bit when cache error occurs.
Date: Tue, 8 Oct 2013 09:16:27 +0100 [thread overview]
Message-ID: <5253BF5B.40405@imgtec.com> (raw)
Message-ID: <20131008081627.qB6fecw3a5I9rjwVw_5nwP-aWq06haYMVZb5cS72tTs@z> (raw)
In-Reply-To: <20131008050633.GD1615@linux-mips.org>
On 10/08/13 06:06, Ralf Baechle wrote:
> On Mon, Oct 07, 2013 at 10:25:52AM +0100, Markos Chandras wrote:
>
>> From: Leonid Yegoshin <Leonid.Yegoshin@imgtec.com>
>>
>> Print out the source of request that caused the error (ES bit) when
>> a cache error exception occurs.
>
> The reason ES isn't being printed is that not all processors that support
> a cache error exception have an ES bit. The R4000 has it, R5000 doesn't,
> R10000 CacheErr looks rather different - and in fact MIPS32/64 make the
> entire register optional and its details implementation specific.
>
> Don't even ask me anymore which processor the implementation in the
> kernel is trying to support - probably something R7000ish, at least
> that's what guess from the 1385617929e09545f9858785ea3dc1068fedfde1
> commit log.
>
> Short of some fancy engineering, I'd suggest throwing in a switch
> statement and per processor type printks just as in parity_protection_init.
>
> Ralf
>
Hi Ralf,
hmm i see. ok i will do that instead.
next prev parent reply other threads:[~2013-10-08 8:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-07 9:25 [PATCH] MIPS: Add printing of ES bit when cache error occurs Markos Chandras
2013-10-07 9:25 ` Markos Chandras
2013-10-08 5:06 ` Ralf Baechle
2013-10-08 8:16 ` Markos Chandras [this message]
2013-10-08 8:16 ` Markos Chandras
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=5253BF5B.40405@imgtec.com \
--to=markos.chandras@imgtec.com \
--cc=Leonid.Yegoshin@imgtec.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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