public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Sudeep Holla <sudeep.holla@arm.com>
To: Timur Tabi <timur@codeaurora.org>
Cc: Sudeep Holla <sudeep.holla@arm.com>,
	Prashanth Prakash <pprakash@codeaurora.org>,
	ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
	Len Brown <lenb@kernel.org>
Subject: Re: [PATCH v3] ACPI / Processor: add sysfs support for low power idle
Date: Wed, 15 Nov 2017 18:14:05 +0000	[thread overview]
Message-ID: <f45c6d49-a22d-9ef2-fa2a-b8dc1009549d@arm.com> (raw)
In-Reply-To: <CAOZdJXXK62Sx75F8Ef62hjS-NBNh9Am_RBXjOzLbjvoQPGMUJg@mail.gmail.com>



On 15/11/17 15:33, Timur Tabi wrote:
> On Wed, Nov 8, 2017 at 8:18 AM, Sudeep Holla <sudeep.holla@arm.com> wrote:
>> I still prefer this as debugfs and not as sysfs ABI. We already have
>> issues with multiple interfaces for the same thing. E.g. cpufreq on x86.
>> I don't want this to end up in the same way after few years. CPUIdle
>> sysfs should be only sysfs ABI for these, adding an alternative is
>> inviting troubles for future especially if some user-space starts using
>> it and we will be stuck with that. Moreover with more h/w controlled
>> idle we may not provide accurate data sooner.
>>
>> Sorry for the noise, I will shup up now ;). Since this may be last
>> chance to make some noise, I am trying it. I completely understand that
>> this is just my opinion and am fine if others thinks it's good to make
>> this sysfs ABI.
> 
> Unfortunately, I think Prashanth really needs a specific requirement
> rather than opinions. 

I completely understand that. So for I haven't got a solid reason as
why debugfs is not sufficient? If it becomes so popular in future, we
can discuss and then make it sysfs ABI with more thoughts/discussions.

> This patch has been languishing for over a month, and we still have
> no idea whether it will make 4.15 or if Prashanth is *required* to
> make any more changes.
> 

It's sysfs ABI which we need to support for very long time(not in months
but in years), so waiting/discussing for couple of months is much safer
than spending more time to keep it the sysfs ABI unbroken.

Also I assume(was explicitly mentioned IIRC) that it's purely used
for debug and tuning purposes and hence I see *no need* to be part of
*sysfs ABI*. Let me know if the circumstances have changed.

-- 
Regards,
Sudeep

  parent reply	other threads:[~2017-11-15 18:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-19 18:19 [PATCH v3] ACPI / Processor: add sysfs support for low power idle Prashanth Prakash
2017-11-06 21:49 ` Prakash, Prashanth
2017-11-08 14:18 ` Sudeep Holla
2017-11-15 15:33   ` Timur Tabi
2017-11-15 17:22     ` Rafael J. Wysocki
2017-11-15 17:24       ` Rafael J. Wysocki
2017-11-15 18:14     ` Sudeep Holla [this message]
2017-11-15 18:37       ` Rafael J. Wysocki
2017-11-15 20:21         ` Prakash, Prashanth
2017-11-16 14:52         ` Sudeep Holla
2017-11-16 17:50           ` Prakash, Prashanth
2017-11-16 23:34             ` Rafael J. Wysocki

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=f45c6d49-a22d-9ef2-fa2a-b8dc1009549d@arm.com \
    --to=sudeep.holla@arm.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=pprakash@codeaurora.org \
    --cc=rjw@rjwysocki.net \
    --cc=timur@codeaurora.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