From: Ralf Baechle <ralf@linux-mips.org>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Markos Chandras <markos.chandras@imgtec.com>, linux-mips@linux-mips.org
Subject: Re: [PATCH] MIPS: Kconfig: microMIPS and SmartMIPS are mutually exclusive
Date: Tue, 3 Jun 2014 14:24:51 +0200 [thread overview]
Message-ID: <20140603122451.GS17197@linux-mips.org> (raw)
In-Reply-To: <alpine.LFD.2.11.1406031214390.18344@eddie.linux-mips.org>
On Tue, Jun 03, 2014 at 12:18:43PM +0100, Maciej W. Rozycki wrote:
> Do we need this CPU_HAS_SMARTMIPS setting at all? Can't we just
> save/restore this SmartMIPS ACX register on context switches where
> available (straightforward to detect at the run time) and have the
> relevant pieces of code excluded (#ifdef-ed out or suchlike) on
> non-supported configurations such as microMIPS or MIPS64?
SmartMIPS has new instructions which are hardcoded in various assembler
fragments, where something like if (cpu_has_smartmips) won't work.
So until a more complex solution is implemented CPU_HAS_SMARTMIPS is
what there is.
Ralf
next prev parent reply other threads:[~2014-06-03 12:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-03 8:46 [PATCH] MIPS: Kconfig: microMIPS and SmartMIPS are mutually exclusive Markos Chandras
2014-06-03 8:46 ` Markos Chandras
2014-06-03 9:34 ` Ralf Baechle
2014-06-03 9:34 ` Ralf Baechle
2014-06-03 9:45 ` Markos Chandras
2014-06-03 9:45 ` Markos Chandras
2014-06-03 11:18 ` Maciej W. Rozycki
2014-06-03 12:24 ` Ralf Baechle [this message]
2014-06-03 13:56 ` Maciej W. Rozycki
2014-07-21 7:46 ` [PATCH v2] MIPS: Kconfig: Add choice symbol to select microMIPS or SmartMIPS Markos Chandras
2014-07-21 7:46 ` Markos Chandras
2014-10-08 13:28 ` Markos Chandras
2014-10-08 13:28 ` 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=20140603122451.GS17197@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=macro@linux-mips.org \
--cc=markos.chandras@imgtec.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox