From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Jiaxun Yang <jiaxun.yang@flygoat.com>
Cc: jiaqingtong97@163.com, mark.tomlinson@alliedtelesis.co.nz,
paulburton@kernel.org, linux-mips@vger.kernel.org
Subject: Re: [PATCH] MIPS: OCTEON: Add OCTEON II build and configuration option
Date: Sat, 19 Dec 2020 16:39:57 +0100 [thread overview]
Message-ID: <20201219153957.GB5012@alpha.franken.de> (raw)
In-Reply-To: <c749749f-0d9b-461d-0f9b-f8ac828a7681@flygoat.com>
On Sat, Dec 19, 2020 at 02:08:49PM +0800, Jiaxun Yang wrote:
>
>
> 在 2020/12/19 上午12:28, jiaqingtong97@163.com 写道:
> > From: Jia Qingtong <jiaqingtong97@163.com>
> >
> > If building for OCTEON II only,we can select compiler options that
> > give better code, but will not run on earlier chips.
>
>
> I'd rather add a workaround Kconfig option and default y for it.
> In case no other optimization can be enabled for OCTANE2, like
>
> WORKAROUND_OCTANE_BARRIER
please start them with WAR_ like the other workarounds I've converted
to Kconfig. Something like
WAR_OCTEON_BARRIER
But the description talks about different compiler options, which I don't
see in the patch ?
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
next prev parent reply other threads:[~2020-12-19 15:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-18 16:28 [PATCH] MIPS: OCTEON: Add OCTEON II build and configuration option jiaqingtong97
2020-12-19 6:08 ` Jiaxun Yang
2020-12-19 15:39 ` Thomas Bogendoerfer [this message]
2020-12-27 14:56 ` [PATCH v2] MIPS: OCTEON: Add WAR_OCTEON_BARRIER workaround config jiaqingtong97
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=20201219153957.GB5012@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=jiaqingtong97@163.com \
--cc=jiaxun.yang@flygoat.com \
--cc=linux-mips@vger.kernel.org \
--cc=mark.tomlinson@alliedtelesis.co.nz \
--cc=paulburton@kernel.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 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.