linux-kernel - Re: [PATCH 0/4] devfreq: exynos: generalize PPMU code

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-id: <14716616.146541395914888684.JavaMail.weblogic@epml10>
Date:	Thu, 27 Mar 2014 10:08:10 +0000 (GMT)
From:	함명주 <myungjoo.ham@...sung.com>
To:	Bartlomiej Zolnierkiewicz <b.zolnierkie@...sung.com>,
	최찬우 <cw00.choi@...sung.com>
Cc:	박경민 <kyungmin.park@...sung.com>,
	"rafael.j.wysocki@...el.com" <rafael.j.wysocki@...el.com>,
	Tomasz Figa <t.figa@...sung.com>,
	"linux-samsung-soc@...r.kernel.org" 
	<linux-samsung-soc@...r.kernel.org>,
	"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/4] devfreq: exynos: generalize PPMU code



On Sat, Mar 22, 2014 at 2:31 AM, Bartlomiej Zolnierkiewicz <b.zolnierkie@...sung.com> wrote:
> Hi,
>
> This patch series generalizes PPMU support for Exynos devfreq
> drivers.
>
> It is based on top of "devfreq: exynos: Fix minor issue and code
> clean to remove legacy method" patch series from Chanwoo Choi
> (https://lkml.org/lkml/2014/3/19/713).
>
> Please note that the patches were only compile tested because
> Exynos devfreq drivers don't work yet in the upstream kernels
> (FWIW these changes were briefly tested with the internal tree
> which has working devfreq drivers).

Hi Blartlomiej,


Thank you.

I'll merge this into devfreq's for-next.


Anyway, days ago, I had a short discussion with Chanwoo about
providing some common interface for PPMU-like devices
(sort of sub device of devfreq device) that provide usage statistics. 

At this stage, I roughly guess that such a device driver (or whatever
entity it is) may be simply a helper for filling out the "get_dev_status" callback.
It is because devfreq's PPMU usage is limited to getting get_dev_status().
As you had done something on PPMU, I guess you may have some
idea on this.

Cheers,
MyungJoo.
>
> Best regards,
> --
> Bartlomiej Zolnierkiewicz
> Samsung R&D Institute Poland
> Samsung Electronics
>
>
> Bartlomiej Zolnierkiewicz (3):
>   devfreq: exynos4: introduce struct busfreq_ppmu_data
>   devfreq: exynos5: introduce struct busfreq_ppmu_data
>   devfreq: exynos: make more PPMU code common
>
> Chanwoo Choi (1):
>   devfreq: exynos4: use common PPMU code
>
>  drivers/devfreq/exynos/Makefile      |   2 +-
>  drivers/devfreq/exynos/exynos4_bus.c | 176 +++++++++--------------------------
>  drivers/devfreq/exynos/exynos5_bus.c |  94 +++++--------------
>  drivers/devfreq/exynos/exynos_ppmu.c |  60 ++++++++++++
>  drivers/devfreq/exynos/exynos_ppmu.h |   8 ++
>  5 files changed, 135 insertions(+), 205 deletions(-)
>
> --
> 1.8.2.3
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pm" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html



-- 
MyungJoo Ham, Ph.D.
System S/W Lab, S/W Center, Samsung Electronics