From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: Alexey Brodkin <Alexey.Brodkin@synopsys.com>,
"linux-snps-arc@lists.infradead.org"
<linux-snps-arc@lists.infradead.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ARC: Add a knob to control usage of dual-issue
Date: Thu, 18 Jan 2018 10:54:56 -0800 [thread overview]
Message-ID: <7d97edc0-d0ee-326b-bcd2-c6731aa953b2@synopsys.com> (raw)
In-Reply-To: <20180118134831.41489-1-abrodkin@synopsys.com>
On 01/18/2018 05:48 AM, Alexey Brodkin wrote:
> HS48 core starts with dual-issue enabled but in some cases like
> debugging as well as benchmarking it might be useful to disable
> dual-issue for a particular run.
>
> Note:
> 1. To disable dual-issue user has to change a value of a global variable
> in target's memory right before start of Linu kernel execution
> (most probably via JTAG)
>
> 2. Disabling happens very early on boot and to get it back enabled it's
> required to restart Linux kernel. I.e. with this change we don't allow
> toggling dual-issue state in random moments of run-time
But we need access to a debugger anyways to change this global variable.
If you already have that won't it be better to change the aux register itself from
the debugger itself.
I don't really see how the global variable way of toggle adds any value here ?
>
> Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com>
> ---
> arch/arc/kernel/setup.c | 13 +++++++++++++
> 1 file changed, 13 insertions(+)
>
> diff --git a/arch/arc/kernel/setup.c b/arch/arc/kernel/setup.c
> index 9d27331fe69a..cf97f7d88934 100644
> --- a/arch/arc/kernel/setup.c
> +++ b/arch/arc/kernel/setup.c
> @@ -31,6 +31,8 @@
>
> #define FIX_PTR(x) __asm__ __volatile__(";" : "+r"(x))
>
> +int dual_issue_enable = 1;
> +
> unsigned int intr_to_DE_cnt;
>
> /* Part of U-boot ABI: see head.S */
> @@ -198,6 +200,17 @@ static void read_arc_build_cfg_regs(void)
> if (cpu->core.family >= 0x54) {
> unsigned int exec_ctrl;
>
> + if (!dual_issue_enable) {
> + /*
> + * Note:
> + * 1) Reset value in AUX_EXEC_CTRL is 0
> + * 2) Reverse logic is used,
> + * i.e. by default (AUX_EXEC_CTRL=0)
> + * dual-issue is enabled.
> + */
> + write_aux_reg(AUX_EXEC_CTRL, 1);
> + }
> +
> READ_BCR(AUX_EXEC_CTRL, exec_ctrl);
> cpu->extn.dual_enb = !(exec_ctrl & 1);
>
next prev parent reply other threads:[~2018-01-18 18:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-18 13:48 Alexey Brodkin
2018-01-18 18:54 ` Vineet Gupta [this message]
2018-01-18 19:11 ` Alexey Brodkin
2018-01-18 22:50 ` Vineet Gupta
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=7d97edc0-d0ee-326b-bcd2-c6731aa953b2@synopsys.com \
--to=vineet.gupta1@synopsys.com \
--cc=Alexey.Brodkin@synopsys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.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
Powered by JetHome