From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: David Daney <ddaney.cavm@gmail.com>
Cc: "Steven J. Hill" <Steven.Hill@imgtec.com>,
linux-mips@linux-mips.org, Ralf Baechle <ralf@linux-mips.org>
Subject: Re: [PATCH v4] MIPS: micromips: Fix improper definition of ISA exception bit.
Date: Wed, 5 Jun 2013 20:26:57 +0100 (BST) [thread overview]
Message-ID: <alpine.LFD.2.03.1306052016120.15274@linux-mips.org> (raw)
In-Reply-To: <51AF8DAE.30206@gmail.com>
On Wed, 5 Jun 2013, David Daney wrote:
> > Shouldn't this be in a generic place such as trap_init instead?
> >
>
> I think it is fine here. If it spreads to more systems, then factoring them
> out into trap_init might make sense. For now it doesn't seem like we should
> clutter up trap_init when there aren't many microMIPS systems in existence.
I disagree. I don't think a generic processor feature should be handled
in board-specific files. A kernel built as a microMIPS binary has
microMIPS exception handlers so no matter what system it is for it'll need
the mode bit set correctly (unless someone implements support for a mixed
setup), so having to add this change to some board-specific file for every
system that gets support for a microMIPS-ISA-enabled processor looks like
no more than a maintenance burden to me. Especially as the !CPU_MICROMIPS
version of the function is empty and will be optimised away (although
actually it shouldn't be -- it should clear the ISAOnExc bit to avoid
surprises).
Maciej
prev parent reply other threads:[~2013-06-05 19:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-05 18:05 [PATCH v4] MIPS: micromips: Fix improper definition of ISA exception bit Steven J. Hill
2013-06-05 18:20 ` David Daney
2013-06-05 19:08 ` Maciej W. Rozycki
2013-06-05 19:12 ` David Daney
2013-06-05 19:26 ` Maciej W. Rozycki [this message]
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=alpine.LFD.2.03.1306052016120.15274@linux-mips.org \
--to=macro@linux-mips.org \
--cc=Steven.Hill@imgtec.com \
--cc=ddaney.cavm@gmail.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