From: Markos Chandras <Markos.Chandras@imgtec.com>
To: <thomas.langer@lantiq.com>, <linux-mips@linux-mips.org>
Cc: <Leonid.Yegoshin@imgtec.com>
Subject: Re: [PATCH] MIPS: Print correct PC in trace dump after NMI exception
Date: Tue, 8 Oct 2013 13:21:07 +0100 [thread overview]
Message-ID: <5253F8B3.3070700@imgtec.com> (raw)
In-Reply-To: <593AEF6C47F46446852B067021A273D6D990182F@MUCSE039.lantiq.com>
On 10/08/13 12:48, thomas.langer@lantiq.com wrote:
> Hello Markos,
>
> If this is a YAMON specific fix, why is it done in a common file?
>
Hi Thomas,
I can see how the commit message can be a bit misleading. However, it's
not YAMON specific. The NMI was just delivered by YAMON because we patch
the default NMI location in YAMON (see mti-malta/malta-init.c).
NMI, Reset and Cache Error exceptions use ErrorEPC instead of EPC so
this patch is platform independent.
WARNING: multiple messages have this Message-ID (diff)
From: Markos Chandras <Markos.Chandras@imgtec.com>
To: thomas.langer@lantiq.com, linux-mips@linux-mips.org
Cc: Leonid.Yegoshin@imgtec.com
Subject: Re: [PATCH] MIPS: Print correct PC in trace dump after NMI exception
Date: Tue, 8 Oct 2013 13:21:07 +0100 [thread overview]
Message-ID: <5253F8B3.3070700@imgtec.com> (raw)
Message-ID: <20131008122107.ydLMWLG83TtthI00Lrwh1nKFzGRVaOUrxQ2yKYjt36c@z> (raw)
In-Reply-To: <593AEF6C47F46446852B067021A273D6D990182F@MUCSE039.lantiq.com>
On 10/08/13 12:48, thomas.langer@lantiq.com wrote:
> Hello Markos,
>
> If this is a YAMON specific fix, why is it done in a common file?
>
Hi Thomas,
I can see how the commit message can be a bit misleading. However, it's
not YAMON specific. The NMI was just delivered by YAMON because we patch
the default NMI location in YAMON (see mti-malta/malta-init.c).
NMI, Reset and Cache Error exceptions use ErrorEPC instead of EPC so
this patch is platform independent.
next prev parent reply other threads:[~2013-10-08 12:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-08 11:39 [PATCH] MIPS: Print correct PC in trace dump after NMI exception Markos Chandras
2013-10-08 11:39 ` Markos Chandras
2013-10-08 11:48 ` thomas.langer
2013-10-08 11:48 ` thomas.langer
2013-10-08 12:21 ` Markos Chandras [this message]
2013-10-08 12:21 ` Markos Chandras
2013-10-08 12:29 ` Ralf Baechle
2013-10-08 12:57 ` thomas.langer
2013-10-08 12:57 ` thomas.langer
2013-10-08 12:15 ` Ralf Baechle
2013-10-08 12:31 ` Markos Chandras
2013-10-08 12:31 ` Markos Chandras
2013-10-08 12:38 ` Ralf Baechle
2013-10-08 12:43 ` Markos Chandras
2013-10-08 12:43 ` Markos Chandras
2013-10-08 12:55 ` Ralf Baechle
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=5253F8B3.3070700@imgtec.com \
--to=markos.chandras@imgtec.com \
--cc=Leonid.Yegoshin@imgtec.com \
--cc=linux-mips@linux-mips.org \
--cc=thomas.langer@lantiq.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.