From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: Vineet Gupta <Vineet.Gupta1@synopsys.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-snps-arc@lists.infradead.org"
<linux-snps-arc@lists.infradead.org>
Subject: Re: [PATCH] ARC: Add a knob to control usage of dual-issue
Date: Thu, 18 Jan 2018 19:11:01 +0000 [thread overview]
Message-ID: <1516302661.8324.32.camel@synopsys.com> (raw)
In-Reply-To: <7d97edc0-d0ee-326b-bcd2-c6731aa953b2@synopsys.com>
Hi Vineet,
On Thu, 2018-01-18 at 10:54 -0800, Vineet Gupta wrote:
> 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 ?
I think there's some sense in a global variable.
1. Not sure if OpenOCD/GDB pair for ARC allows to read/write random AUX regs.
Probably allows but I guess we'll need a new .xml description which lists EXEC_CTRL
AUX reg. Correct me if I'm wrong here.
2. If somebody wants to disable dual-issue persistently (here I mean building an image
which had dual-issue disabled and there's no need to alter anything after image loading)
then it's possible just to change a simple and very obvious line in arch/arc/kernel/setup.c
other than trying to guess what could be good place in sources to stick that AUX reg write.
Note we don't explicitly do reads of AUX_EXEC_CTRL instead we just use READ_BCR macro so
for newcomers it might not be immediately obvious what to do and where.
Add the fact that logic of the flag is reversed...
-Alexey
next prev parent reply other threads:[~2018-01-18 19:11 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
2018-01-18 19:11 ` Alexey Brodkin [this message]
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=1516302661.8324.32.camel@synopsys.com \
--to=alexey.brodkin@synopsys.com \
--cc=Vineet.Gupta1@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