Message-ID: <53862142.8080006@codeaurora.org>
Date:	Wed, 28 May 2014 10:47:46 -0700
From:	Saravana Kannan <skannan@...eaurora.org>
To:	Peter De Schrijver <pdeschrijver@...dia.com>
CC:	"linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org>,
	Mike Turquette <mturquette@...aro.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [RFC PATCH] clk: flatten clk tree in debugfs

On 05/26/2014 04:14 AM, Peter De Schrijver wrote:
> On Sat, May 24, 2014 at 12:24:32AM +0200, Saravana Kannan wrote:
>> On 05/23/2014 03:59 AM, Peter De Schrijver wrote:
>>> This patch flattens the clk tree in CCF debugfs. Instead of representing the
>>> clocks and their hierarchy as a directory structure under
>>> /sys/kernel/debug/clk, each clock gets a single directory directly under
>>> /sys/kernel/debug/clk.
>>>
>>> While this may seem strange, here's way I think this is the right thing to do:
>>>
>>> 1) a directory structure cannot be 'snapshotted' atomically, therefore it's
>>>      not in general possible to get a consistent view of the clocktree, because
>>>      clocks can be reparented at any time. This was solved by adding clk_dump
>>>      and clk_summary, which do guarantee an atomic snapshot of the tree.
>>>      Therefore I think the directory structure doesn't add any value.
>>>
>>> 2) When writing userspace programs which use the files in the clock
>>>      directories (eg. for testing purposes), it's impossible to know for sure
>>>      where a certain clock will be, because it might have been reparented by the
>>>      time you figured out the path from clk_dump. This makes writing such
>>>      programs more difficult than it should be.
>>>
>>> So because the directory structure doesn't give any information we don't
>>> already provide by other means and it makes certain usecases more difficult
>>> than the should be, I think we should move to a flat directory containing
>>> one subdir per clock.
>>
>> Completely agree and a huge ACK to this idea.
>>
>
> Thanks.
>
>>>
>>> Signed-off-by: Peter De Schrijver <pdeschrijver@...dia.com>
>>> ---
>>>    drivers/clk/clk.c |   54 +++-------------------------------------------------
>>>    1 files changed, 4 insertions(+), 50 deletions(-)
>>>
>>> diff --git a/drivers/clk/clk.c b/drivers/clk/clk.c
>>> index dff0373..53c6b4f 100644
>>> --- a/drivers/clk/clk.c
>>> +++ b/drivers/clk/clk.c
>>> @@ -306,7 +306,7 @@ static int clk_debug_create_subtree(struct clk *clk, struct dentry *pdentry)
>>>    		goto out;
>>>
>>>    	hlist_for_each_entry(child, &clk->children, child_node)
>>> -		clk_debug_create_subtree(child, clk->dentry);
>>> +		clk_debug_create_subtree(child, pdentry);
>>>
>>>    	ret = 0;
>>>    out:
>>> @@ -326,29 +326,20 @@ out:
>>>     */
>>>    static int clk_debug_register(struct clk *clk)
>>>    {
>>> -	struct clk *parent;
>>>    	struct dentry *pdentry;
>>>    	int ret = 0;
>>>
>>>    	if (!inited)
>>>    		goto out;
>>>
>>> -	parent = clk->parent;
>>> -
>>>    	/*
>>>    	 * Check to see if a clk is a root clk.  Also check that it is
>>>    	 * safe to add this clk to debugfs
>>>    	 */
>>> -	if (!parent)
>>> -		if (clk->flags & CLK_IS_ROOT)
>>> -			pdentry = rootdir;
>>> -		else
>>> -			pdentry = orphandir;
>>> +	if (clk->flags & CLK_IS_ROOT)
>>> +		pdentry = rootdir;
>>>    	else
>>> -		if (parent->dentry)
>>> -			pdentry = parent->dentry;
>>> -		else
>>> -			goto out;
>>> +		pdentry = orphandir;
>>
>> I'm confused by this code. Shouldn't pdentry always be the same? Do we
>> need a dir for orphans? Also, I'm not sure the code is actually right?
>
> Indeed. This code is most likely wrong... I don't have a strong opinion
> if we need an orphan dir or if we can just have a file to list orphaned
> clocks.
I don't have a strong opinion either. A file is probably safer in case 
we add debug files that allow changes to the clock. In which case, we 
don't want orphan clocks to be modifiable.

> I would still like to be able to see if there are orphaned clocks.
Agree

> You could argue that the same race exists for the orphan dir. It is possible
> for the parent to be registered while you're traversing the orphan dir and
> cause a clock to move around. In practice this seems rather unlikely to happen
> to me?
I think you read too much into my comment. I wasn't in any way against 
knowing orphaned clocks from debugfs. I was just referring to that 
specific point in code, the clock might always need to pick the same 
dentry. I might be wrong about the code too (I just looked at the diff).


>> Looks like you are putting everything but the root into orphandir?
>>
>
> Yes...

Now I'm confused. Does some other code path unorphan and move them into 
the clock debug "root" dir later on?

Mike, others,

Any objections to this idea? If there's not much opposition, then maybe 
Peter can actually spend time fixing and testing this patch?

-Saravana

-- 
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
hosted by The Linux Foundation
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists