From: Will Deacon <will.deacon@arm.com>
To: John Garry <john.garry@huawei.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
Shaokun Zhang <zhangshaokun@hisilicon.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, anurup.m@huawei.com,
tanxiaojun@huawei.com, xuwei5@hisilicon.com,
sanil.kumar@hisilicon.com, gabriele.paoloni@huawei.com,
shiju.jose@huawei.com, huangdaode@hisilicon.com,
linuxarm@huawei.com, dikshit.n@huawei.com, shyju.pv@huawei.com,
anurupvasu@gmail.com
Subject: Re: [PATCH v8 6/9] drivers: perf: hisi: Add support for Hisilicon Djtag driver
Date: Fri, 9 Jun 2017 15:30:50 +0100 [thread overview]
Message-ID: <20170609143050.GM13955@arm.com> (raw)
In-Reply-To: <8666a0fa-126d-e4a3-ac4b-7962f5d79942@huawei.com>
On Fri, Jun 09, 2017 at 03:18:39PM +0100, John Garry wrote:
> On 08/06/2017 17:35, Mark Rutland wrote:
> >Hi,
> >
> >On Mon, May 22, 2017 at 08:48:32PM +0800, Shaokun Zhang wrote:
> >>+/*
> >>+ * hisi_djtag_lock_v2: djtag lock to avoid djtag access conflict b/w kernel
> >>+ * and UEFI.
> >
> >The mention of UEFI here worries me somewhat, and I have a number of
> >questions specifically relating to how we interact with UEFI here.
> >
>
> Hi Mark,
>
> This djtag locking mechanism is an advisory software-only policy. The
> problem is the hardware designers made an interface which does not consider
> multiple agents in the system concurrently accessing the djtag registers.
>
> System wide, djtag is used as an interface to other HW modules, but we only
> use for perf HW in the kernel.
>
> >When precisely does UEFI need to touch the djtag hardware? e.g. does
> >this happen in runtime services? ... or completely asynchronously?
> >
>
> Actually it's trusted firmware which accesses for L3 cache management in CPU
> hotplug
>
> >What does UEFI do with djtag when it holds the lock?
> >
>
> As mentioned, cache management
>
> >Are there other software agents (e.g. secure firmware) which try to
> >take this lock?
> >
>
> No
>
> >Can you explain how the locking scheme works? e.g. is this an advisory
> >software-only policy, or does the hardware prohibit accesses from other
> >agents somehow?
> >
>
> The locking scheme is a software solution to spinlock. It's uses djtag
> module select register as the spinlock flag, to avoid using some shared
> memory.
>
> The tricky part is that there is no test-and-set hardware support, so we use
> this algorithm:
> - precondition: flag initially set unlocked
>
> a. agent reads flag
> - if not unlocked, continues to poll
> - otherwise, writes agent's unique lock value to flag
> b. agent waits defined amount of time *uninterrupted* and then checks the
> flag
How do you figure out this time period? Doesn't it need to be no shorter
than the longest critical section?
Will
next prev parent reply other threads:[~2017-06-09 14:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-22 12:48 [PATCH v8 6/9] drivers: perf: hisi: Add support for Hisilicon Djtag driver Shaokun Zhang
2017-06-08 16:35 ` Mark Rutland
2017-06-09 14:18 ` John Garry
2017-06-09 14:30 ` Will Deacon [this message]
2017-06-09 15:10 ` John Garry
2017-06-14 10:06 ` Will Deacon
2017-06-14 10:42 ` Mark Rutland
2017-06-14 10:50 ` Mark Rutland
2017-06-14 11:01 ` Will Deacon
2017-06-14 11:35 ` John Garry
2017-06-14 11:40 ` Will Deacon
2017-06-14 11:59 ` John Garry
2017-06-14 10:48 ` Russell King - ARM Linux
2017-06-14 11:06 ` Will Deacon
2017-06-09 15:44 ` Mark Rutland
2017-06-09 16:09 ` John Garry
2017-06-09 16:45 ` Mark Rutland
2017-06-14 8:11 ` Zhangshaokun
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=20170609143050.GM13955@arm.com \
--to=will.deacon@arm.com \
--cc=anurup.m@huawei.com \
--cc=anurupvasu@gmail.com \
--cc=dikshit.n@huawei.com \
--cc=gabriele.paoloni@huawei.com \
--cc=huangdaode@hisilicon.com \
--cc=john.garry@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mark.rutland@arm.com \
--cc=sanil.kumar@hisilicon.com \
--cc=shiju.jose@huawei.com \
--cc=shyju.pv@huawei.com \
--cc=tanxiaojun@huawei.com \
--cc=xuwei5@hisilicon.com \
--cc=zhangshaokun@hisilicon.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