linaro-kernel

linaro-kernel@lists.linaro.org

10094 discussions

[PATCH] cpufreq: stats: Remove CONFIG_CPU_FREQ_STAT_DETAILS

by Viresh Kumar

Current cpufreq stats has got three parts: time_in_state, total_trans and trans_table. trans_table was present under a separate macro's from others: CONFIG_CPU_FREQ_STAT_DETAILS The reason quoted for that was: - trans_table goes against the traditional /sysfs rule of one value per interface. It provides a whole bunch of value in a 2 dimensional matrix form. I don't understand how necessary it is to keep trans_table inside a separate macro. These are all cpufreq sysfs stats, probably it doesn't matter if its one dimensional or two. Lets remove CONFIG_CPU_FREQ_STAT_DETAILS and use CONFIG_CPU_FREQ_STAT only to make code more cleaner (i.e. remove unnecessary macros). Signed-off-by: Viresh Kumar <viresh.kumar(a)linaro.org> --- Documentation/cpu-freq/cpufreq-stats.txt | 18 ++++-------------- arch/mips/configs/lemote2f_defconfig | 1 - arch/powerpc/configs/ppc6xx_defconfig | 1 - arch/sh/configs/sh7785lcr_32bit_defconfig | 1 - drivers/cpufreq/Kconfig | 9 --------- drivers/cpufreq/cpufreq_stats.c | 12 ------------ 6 files changed, 4 insertions(+), 38 deletions(-) diff --git a/Documentation/cpu-freq/cpufreq-stats.txt b/Documentation/cpu-freq/cpufreq-stats.txt index fc64749..838f990 100644 --- a/Documentation/cpu-freq/cpufreq-stats.txt +++ b/Documentation/cpu-freq/cpufreq-stats.txt @@ -111,18 +111,8 @@ Config Main Menu cpufreq-stats. "CPU frequency translation statistics" (CONFIG_CPU_FREQ_STAT) provides the -basic statistics which includes time_in_state and total_trans. - -"CPU frequency translation statistics details" (CONFIG_CPU_FREQ_STAT_DETAILS) -provides fine grained cpufreq stats by trans_table. The reason for having a -separate config option for trans_table is: -- trans_table goes against the traditional /sysfs rule of one value per - interface. It provides a whole bunch of value in a 2 dimensional matrix - form. - -Once these two options are enabled and your CPU supports cpufrequency, you -will be able to see the CPU frequency statistics in /sysfs. - - - +statistics which includes time_in_state, total_trans and fine grained cpufreq +stats by trans_table. +Once this option is enabled and your CPU supports cpufrequency, you will be able +to see the CPU frequency statistics in /sysfs. diff --git a/arch/mips/configs/lemote2f_defconfig b/arch/mips/configs/lemote2f_defconfig index 343bebc..f9229e9 100644 --- a/arch/mips/configs/lemote2f_defconfig +++ b/arch/mips/configs/lemote2f_defconfig @@ -41,7 +41,6 @@ CONFIG_PM_RUNTIME=y CONFIG_CPU_FREQ=y CONFIG_CPU_FREQ_DEBUG=y CONFIG_CPU_FREQ_STAT=m -CONFIG_CPU_FREQ_STAT_DETAILS=y CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y CONFIG_CPU_FREQ_GOV_POWERSAVE=m CONFIG_CPU_FREQ_GOV_USERSPACE=m diff --git a/arch/powerpc/configs/ppc6xx_defconfig b/arch/powerpc/configs/ppc6xx_defconfig index be1cb6e..bb7664c 100644 --- a/arch/powerpc/configs/ppc6xx_defconfig +++ b/arch/powerpc/configs/ppc6xx_defconfig @@ -58,7 +58,6 @@ CONFIG_GEF_SBC610=y CONFIG_CPU_FREQ=y CONFIG_CPU_FREQ_DEBUG=y CONFIG_CPU_FREQ_STAT=m -CONFIG_CPU_FREQ_STAT_DETAILS=y CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE=y CONFIG_CPU_FREQ_GOV_PERFORMANCE=y CONFIG_CPU_FREQ_GOV_POWERSAVE=m diff --git a/arch/sh/configs/sh7785lcr_32bit_defconfig b/arch/sh/configs/sh7785lcr_32bit_defconfig index 9bdcf72..7ce136d 100644 --- a/arch/sh/configs/sh7785lcr_32bit_defconfig +++ b/arch/sh/configs/sh7785lcr_32bit_defconfig @@ -25,7 +25,6 @@ CONFIG_SH_SH7785LCR=y CONFIG_NO_HZ=y CONFIG_HIGH_RES_TIMERS=y CONFIG_CPU_FREQ=y -CONFIG_CPU_FREQ_STAT_DETAILS=y CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y CONFIG_SH_CPU_FREQ=y CONFIG_HEARTBEAT=y diff --git a/drivers/cpufreq/Kconfig b/drivers/cpufreq/Kconfig index 534fcb8..f64ed8a 100644 --- a/drivers/cpufreq/Kconfig +++ b/drivers/cpufreq/Kconfig @@ -36,15 +36,6 @@ config CPU_FREQ_STAT If in doubt, say N. -config CPU_FREQ_STAT_DETAILS - bool "CPU frequency translation statistics details" - depends on CPU_FREQ_STAT - help - This will show detail CPU frequency translation table in sysfs file - system. - - If in doubt, say N. - choice prompt "Default CPUFreq governor" default CPU_FREQ_DEFAULT_GOV_USERSPACE if ARM_SA1100_CPUFREQ || ARM_SA1110_CPUFREQ diff --git a/drivers/cpufreq/cpufreq_stats.c b/drivers/cpufreq/cpufreq_stats.c index fb65dec..c774005 100644 --- a/drivers/cpufreq/cpufreq_stats.c +++ b/drivers/cpufreq/cpufreq_stats.c @@ -33,9 +33,7 @@ struct cpufreq_stats { unsigned int last_index; u64 *time_in_state; unsigned int *freq_table; -#ifdef CONFIG_CPU_FREQ_STAT_DETAILS unsigned int *trans_table; -#endif }; static DEFINE_PER_CPU(struct cpufreq_stats *, cpufreq_stats_table); @@ -86,7 +84,6 @@ static ssize_t show_time_in_state(struct cpufreq_policy *policy, char *buf) return len; } -#ifdef CONFIG_CPU_FREQ_STAT_DETAILS static ssize_t show_trans_table(struct cpufreq_policy *policy, char *buf) { ssize_t len = 0; @@ -131,7 +128,6 @@ static ssize_t show_trans_table(struct cpufreq_policy *policy, char *buf) return len; } cpufreq_freq_attr_ro(trans_table); -#endif cpufreq_freq_attr_ro(total_trans); cpufreq_freq_attr_ro(time_in_state); @@ -139,9 +135,7 @@ cpufreq_freq_attr_ro(time_in_state); static struct attribute *default_attrs[] = { &total_trans.attr, &time_in_state.attr, -#ifdef CONFIG_CPU_FREQ_STAT_DETAILS &trans_table.attr, -#endif NULL }; static struct attribute_group stats_attr_group = { @@ -231,9 +225,7 @@ static int cpufreq_stats_create_table(struct cpufreq_policy *policy, alloc_size = count * sizeof(int) + count * sizeof(u64); -#ifdef CONFIG_CPU_FREQ_STAT_DETAILS alloc_size += count * count * sizeof(int); -#endif stat->max_state = count; stat->time_in_state = kzalloc(alloc_size, GFP_KERNEL); if (!stat->time_in_state) { @@ -242,9 +234,7 @@ static int cpufreq_stats_create_table(struct cpufreq_policy *policy, } stat->freq_table = (unsigned int *)(stat->time_in_state + count); -#ifdef CONFIG_CPU_FREQ_STAT_DETAILS stat->trans_table = stat->freq_table + count; -#endif j = 0; for (i = 0; table[i].frequency != CPUFREQ_TABLE_END; i++) { unsigned int freq = table[i].frequency; @@ -333,9 +323,7 @@ static int cpufreq_stat_notifier_trans(struct notifier_block *nb, spin_lock(&cpufreq_stats_lock); stat->last_index = new_index; -#ifdef CONFIG_CPU_FREQ_STAT_DETAILS stat->trans_table[old_index * stat->max_state + new_index]++; -#endif stat->total_trans++; spin_unlock(&cpufreq_stats_lock); return 0; -- 1.7.12.rc2.18.g61b472e

11 years, 11 months

[PATCH v2 00/14] perf, persistent: Kernel updates for perf tool integration

by Robert Richter

This patch set implements out of the box support of perf tools for persistent events. For this the kernel must provide necessary information about existing persistent events via sysfs to userland. Persistent events are provided by the kernel with readonly event buffers. To allow the independent usage of the event buffers by any process without limiting other processes, multiple users of a single event must be handled too. The basic concept is to use a pmu as an event container for persistent events. The pmu registers events in sysfs and provides format and event information for the userland. The persistent event framework requires to add events to the pmu dynamically. With the information in sysfs userland knows about how to setup the perf_event attribute of a persistent event. Since a persistent event always has the persistent flag set, a way is needed to express this in sysfs. A new syntax is used for this. With 'attr<num>:<mask>' any bit in the attribute structure may be set in a similar way as using 'config<num>', but <num> is an index that points to the u64 value to change within the attribute. For persistent events the persistent flag (bit 23 of flag field in struct perf_event_attr) needs to be set which is expressed in sysfs with "attr5:23". E.g. the mce_record event is described in sysfs as follows: /sys/bus/event_source/devices/persistent/events/mce_record:persistent,config=106 /sys/bus/event_source/devices/persistent/format/persistent:attr5:23 Note that perf tools need to support the 'attr<num>' syntax that is added in a separate patch set. With it we are able to run perf tool commands to read persistent events, e.g.: # perf record -e persistent/mce_record/ sleep 10 # perf top -e persistent/mce_record/ In general the new syntax is flexible to describe with sysfs any event to be setup by perf tools. First patches contain also fixes and reworks made after reviewing code. Could be applied separately. Patches base on Boris' patches which I have rebased to latest tip/perf/core. All patches can be found here: git://git.kernel.org/pub/scm/linux/kernel/git/rric/oprofile.git persistent-v2 I wonder if this patch set could be applied to a tip/perf topic branch? This would avoid reposting already reviewed patches. Note: The perf tools patch set do not need to be reposted. -Robert Changes for V2: * Merged minor changes into Boris' patches * Included Boris' patches for review * Document attr<index> syntax in sysfs ABI * Adding cpu check to perf_get_persistent_event_fd() * Rebased to latest tip/perf/core Borislav Petkov (4): perf, ring_buffer: Use same prefix perf: Add persistent events perf: Add persistent event facilities MCE: Enable persistent event Robert Richter (10): perf, persistent: Rework struct pers_event_desc perf, persistent: Remove rb_put() perf, persistent: Introduce get_persistent_event() perf, persistent: Reworking perf_get_persistent_event_fd() perf, persistent: Protect event lists with mutex perf, persistent: Avoid adding identical events perf, persistent: Implementing a persistent pmu perf, persistent: Name each persistent event perf, persistent: Exposing persistent events using sysfs perf, persistent: Allow multiple users for an event .../testing/sysfs-bus-event_source-devices-format | 43 ++- arch/x86/kernel/cpu/mcheck/mce.c | 19 ++ include/linux/perf_event.h | 9 +- include/uapi/linux/perf_event.h | 3 +- kernel/events/Makefile | 2 +- kernel/events/core.c | 56 ++-- kernel/events/internal.h | 3 + kernel/events/persistent.c | 320 +++++++++++++++++++++ kernel/events/ring_buffer.c | 7 +- 9 files changed, 419 insertions(+), 43 deletions(-) create mode 100644 kernel/events/persistent.c -- 1.8.1.1

11 years, 11 months

[PATCH] cpuidle: arm_big_little: pass target residency to mcpm

by Sebastian Capella

also cc linaro kernel Hi, This patch will forward target residency information from the arm_big_little driver to mcpm. If multiple powerdown states are used, the vendor specific code will need a way to distinguish the intended c-state information. I do not have TC2 hardware to verify this. Would someone be able to help verify this change on TC2? Thanks! Sebastian Sebastian Capella (1): cpuidle: arm_big_little: route target residency to mcpm drivers/cpuidle/arm_big_little.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) -- 1.7.9.5

11 years, 11 months

Re: [RESEND][PATCH] cpufreq: stats: Add 'load_table' sysfs file to show accumulated data of CPU

by Viresh Kumar

Hi Chanwoo, On 5 June 2013 13:41, Chanwoo Choi <cw00.choi(a)samsung.com> wrote: > This patch add new sysfs file to show previous accumulated data of CPU load Please mention we are only accumulating latest 20 values. > as following path. This sysfs file is used to judge the correct system state > or determine suitable system resource on user-space. Please write it as: load_table will be used to judge how many cpus would be sufficient for managing current load. > - /sys/devices/system/cpu/cpu0/cpufreq/stats/load_table > > This sysfs file include following data: > - Measurement point of time > - CPU frequency > - Per-CPU load > > Signed-off-by: Chanwoo Choi <cw00.choi(a)samsung.com> > Signed-off-by: Myungjoo Ham <myungjoo.ham(a)samsung.com> > Signed-off-by: Kyungmin Park <kyungmin.park(a)samsung.com> > --- > > Additionally, I explain an example using 'load_table' sysfs entry. > > Exynos4412 series has Quad-core and all cores share the power-line. > I cann't set diffent voltage/frequency to each CPU. To reduce power- > consumption, I certainly have to turn on/off CPU online state > according to CPU load on runtime. As a result, I peridically need to > monitor current cpu state to determine a proper amount of system > resource(necessary number of online cpu) and to delete wasted power. > So, I need 'load_table' sysfs file to monitor current cpu state. > > I add a table which show power consumption of target based on > Exynos4412 SoC. This table indicate the difference power-consumption > according to a number of online core and with same number of running task. > > [Environment of power estimation] > - cpufreq governor used performance mode to estimate power-consumption on each frequency step. > - Use infinite-loop test program which execute while statement infinitely. > - Always measure the power consumption under same temperature during 1 minutes. > - Unit is mA. > ------------------------------------------------------------------------------------------------------------------------------------ > A number of Online core | Core 1 | Core 2 | Core 3 | Core 4 > A number of nr_running | 0 1 | 0 1 2 | 0 1 2 3 | 0 1 2 3 4 > ------------------------------------------------------------------------------------------------------------------------------------ > CPU Frequency | > 800 MHz | 293 330 | 295 338 379 | 300 339 386 433 | 303 341 390 412 482 > 1000 MHz | 312 371 | 316 377 435 | 318 383 454 522 | 322 391 462 526 596 > 1200 MHz | 323 404 | 328 418 504 | 336 423 521 615 | 343 433 499 639 748 > 1600 MHz | 380 525 | 388 556 771 | 399 575 771 1011 | 412 597 822 1172 1684 > ------------------------------------------------------------------------------------------------------------------------------------ > > For example, > The case A/B/C have the same condition except for a number of online core. > - case A: Online core is 2, 1000MHz and nr_running is 1 : 377mA > - case B: Online core is 3, 1000MHz and nr_running is 1 : 383mA > - case C: Online core is 4, 1000Mz and nr_running is 1 : 391mA > > If system has only one running task, cpu hotplug policy, by monitoring > cpu state through 'load_table' sysfs file on user-space, > will determine 'case A' state for reducing power-consumption. > > Show the result of reading 'load_table sysfs file as following: > - cpufreq governor is ondemand_org governor. > > $ cat /sys/devices/system/cpu/cpu0/cpufreq/stats/load_table > Time Frequency cpu0 cpu1 cpu2 cpu3 > 1300500043122 1600000 32 6 0 26 > 1300600079080 800000 63 10 2 45 > 1300700065288 800000 51 9 1 42 > 1300800228747 800000 51 9 1 43 > 1300900182997 800000 78 11 3 47 > 1301000106163 800000 96 26 6 48 > 1301100056247 1600000 45 7 1 27 > 1301200071373 1000000 55 9 1 37 > 1301300096082 800000 54 10 0 45 > 1301400132832 800000 70 11 2 46 > 1301500082290 800000 61 11 1 43 > 1301600236415 800000 61 9 2 43 > 1301700071498 800000 59 10 2 43 > 1301800159290 800000 55 9 1 42 > 1301900076332 800000 66 10 2 43 > 1302000102165 800000 47 9 0 43 > 1302100086623 800000 75 11 2 50 > 1302200101082 800000 66 10 4 46 > 1302300108873 800000 53 10 1 44 > 1302400373373 600000 63 12 1 54 How are you getting loads different for all your cpus? I believe you are just recording these values for policy->cpu and all cpus share same policy on your platform. > Please let me know some opinion about this patch. > > Best regards and Thanks, > Chanwoo Choi > > --- > drivers/cpufreq/cpufreq.c | 4 +++ > drivers/cpufreq/cpufreq_governor.c | 21 ++++++++++-- > drivers/cpufreq/cpufreq_stats.c | 70 ++++++++++++++++++++++++++++++++++++++ > include/linux/cpufreq.h | 6 ++++ > 4 files changed, 99 insertions(+), 2 deletions(-) > > diff --git a/drivers/cpufreq/cpufreq.c b/drivers/cpufreq/cpufreq.c > index 2d53f47..cbaaff0 100644 > --- a/drivers/cpufreq/cpufreq.c > +++ b/drivers/cpufreq/cpufreq.c > @@ -292,6 +292,10 @@ void __cpufreq_notify_transition(struct cpufreq_policy *policy, > if (likely(policy) && likely(policy->cpu == freqs->cpu)) > policy->cur = freqs->new; > break; > + case CPUFREQ_LOADCHECK: > + srcu_notifier_call_chain(&cpufreq_transition_notifier_list, > + CPUFREQ_LOADCHECK, freqs); > + break; > } > } > /** > diff --git a/drivers/cpufreq/cpufreq_governor.c b/drivers/cpufreq/cpufreq_governor.c > index 5af40ad..bc50624 100644 > --- a/drivers/cpufreq/cpufreq_governor.c > +++ b/drivers/cpufreq/cpufreq_governor.c > @@ -23,12 +23,17 @@ > #include <linux/kernel_stat.h> > #include <linux/mutex.h> > #include <linux/slab.h> > +#include <linux/sched.h> > #include <linux/tick.h> > #include <linux/types.h> > #include <linux/workqueue.h> > > #include "cpufreq_governor.h" > > +#ifdef CONFIG_CPU_FREQ_STAT_DETAILS > + struct cpufreq_freqs freqs; > +#endif Why do you need this to be global? > static struct kobject *get_governor_parent_kobj(struct cpufreq_policy *policy) > { > if (have_governor_per_policy()) > @@ -143,11 +148,17 @@ void dbs_check_cpu(struct dbs_data *dbs_data, int cpu) > idle_time += jiffies_to_usecs(cur_nice_jiffies); > } > > - if (unlikely(!wall_time || wall_time < idle_time)) > + if (unlikely(!wall_time || wall_time < idle_time)) { > +#ifdef CONFIG_CPU_FREQ_STAT_DETAILS > + freqs.load[j] = 0; > +#endif > continue; > + } > > load = 100 * (wall_time - idle_time) / wall_time; > - > +#ifdef CONFIG_CPU_FREQ_STAT_DETAILS > + freqs.load[j] = load; > +#endif > if (dbs_data->cdata->governor == GOV_ONDEMAND) { > int freq_avg = __cpufreq_driver_getavg(policy, j); > if (freq_avg <= 0) > @@ -160,6 +171,12 @@ void dbs_check_cpu(struct dbs_data *dbs_data, int cpu) > max_load = load; > } > > +#ifdef CONFIG_CPU_FREQ_STAT_DETAILS > + freqs.time = ktime_to_ns(ktime_get()); > + freqs.old = freqs.new = policy->cur; > + > + cpufreq_notify_transition(policy, &freqs, CPUFREQ_LOADCHECK); > +#endif > dbs_data->cdata->gov_check_cpu(cpu, max_load); > } > EXPORT_SYMBOL_GPL(dbs_check_cpu); > diff --git a/drivers/cpufreq/cpufreq_stats.c b/drivers/cpufreq/cpufreq_stats.c > index fb65dec..2379b1d 100644 > --- a/drivers/cpufreq/cpufreq_stats.c > +++ b/drivers/cpufreq/cpufreq_stats.c > @@ -22,6 +22,8 @@ > #include <linux/notifier.h> > #include <asm/cputime.h> > > +#define CPUFREQ_LOAD_TABLE_MAX 20 > + > static spinlock_t cpufreq_stats_lock; > > struct cpufreq_stats { > @@ -35,6 +37,10 @@ struct cpufreq_stats { > unsigned int *freq_table; > #ifdef CONFIG_CPU_FREQ_STAT_DETAILS > unsigned int *trans_table; > + > + struct cpufreq_freqs *load_table; > + unsigned int load_last_index; > + unsigned int load_max_index; > #endif > }; > > @@ -131,6 +137,38 @@ static ssize_t show_trans_table(struct cpufreq_policy *policy, char *buf) > return len; > } > cpufreq_freq_attr_ro(trans_table); > + > +static ssize_t show_load_table(struct cpufreq_policy *policy, char *buf) > +{ > + struct cpufreq_stats *stat = per_cpu(cpufreq_stats_table, policy->cpu); > + struct cpufreq_freqs *load_table = stat->load_table; > + ssize_t len = 0; > + int i; > + int j; merge above two lines. > + > + len += sprintf(buf + len, "%11s %10s", "Time", "Frequency"); > + for (j = 0; j < NR_CPUS; j++) > + len += sprintf(buf + len, " %3s%d", "cpu", j); > + len += sprintf(buf + len, "\n"); > + > + i = stat->load_last_index; > + do { > + len += sprintf(buf + len, "%lld %9d", > + load_table[i].time, > + load_table[i].old); > + > + for (j = 0; j < NR_CPUS; j++) > + len += sprintf(buf + len, " %4d", > + load_table[i].load[j]); > + len += sprintf(buf + len, "\n"); > + > + if (++i == stat->load_max_index) > + i = 0; > + } while (i != stat->load_last_index); You want/need some locking to protect addition to this list while we are reading from it? > + return len; > +} > +cpufreq_freq_attr_ro(load_table); > #endif > > cpufreq_freq_attr_ro(total_trans); > @@ -141,6 +179,7 @@ static struct attribute *default_attrs[] = { > &time_in_state.attr, > #ifdef CONFIG_CPU_FREQ_STAT_DETAILS > &trans_table.attr, > + &load_table.attr, > #endif > NULL > }; > @@ -167,6 +206,9 @@ static void cpufreq_stats_free_table(unsigned int cpu) > > if (stat) { > pr_debug("%s: Free stat table\n", __func__); > +#ifdef CONFIG_CPU_FREQ_STAT_DETAILS > + kfree(stat->load_table); > +#endif > kfree(stat->time_in_state); > kfree(stat); > per_cpu(cpufreq_stats_table, cpu) = NULL; > @@ -244,6 +286,16 @@ static int cpufreq_stats_create_table(struct cpufreq_policy *policy, > > #ifdef CONFIG_CPU_FREQ_STAT_DETAILS > stat->trans_table = stat->freq_table + count; > + > + stat->load_max_index = CPUFREQ_LOAD_TABLE_MAX; > + stat->load_last_index = 0; > + > + alloc_size = sizeof(struct cpufreq_freqs) * stat->load_max_index; We aren't using this variable multiple times so get rid of it and also you need to do: sizeof(*stat->load_table). > + stat->load_table = kzalloc(alloc_size, GFP_KERNEL); > + if (!stat->load_table) { > + ret = -ENOMEM; > + goto error_out; > + } > #endif > j = 0; > for (i = 0; table[i].frequency != CPUFREQ_TABLE_END; i++) { > @@ -312,13 +364,31 @@ static int cpufreq_stat_notifier_trans(struct notifier_block *nb, > struct cpufreq_stats *stat; > int old_index, new_index; > > +#ifdef CONFIG_CPU_FREQ_STAT_DETAILS > + if (val != CPUFREQ_POSTCHANGE && val != CPUFREQ_LOADCHECK) > +#else > if (val != CPUFREQ_POSTCHANGE) > +#endif > return 0; > > stat = per_cpu(cpufreq_stats_table, freq->cpu); > if (!stat) > return 0; > > +#ifdef CONFIG_CPU_FREQ_STAT_DETAILS > + if (val == CPUFREQ_LOADCHECK) { > + struct cpufreq_freqs *dest_freq; > + > + dest_freq = &stat->load_table[stat->load_last_index]; > + memcpy(dest_freq, freq, sizeof(struct cpufreq_freqs)); again sizeof()... You don't need to copy full structure probably. > + > + if (++stat->load_last_index == stat->load_max_index) > + stat->load_last_index = 0; > + > + return 0; > + } > +#endif > + > old_index = stat->last_index; > new_index = freq_table_get_index(stat, freq->new); > > diff --git a/include/linux/cpufreq.h b/include/linux/cpufreq.h > index 037d36a..f780645 100644 > --- a/include/linux/cpufreq.h > +++ b/include/linux/cpufreq.h > @@ -140,12 +140,18 @@ static inline bool policy_is_shared(struct cpufreq_policy *policy) > #define CPUFREQ_POSTCHANGE (1) > #define CPUFREQ_RESUMECHANGE (8) > #define CPUFREQ_SUSPENDCHANGE (9) > +#define CPUFREQ_LOADCHECK (10) > > struct cpufreq_freqs { > unsigned int cpu; /* cpu nr */ > unsigned int old; > unsigned int new; > u8 flags; /* flags of cpufreq_driver, see below. */ > + > +#ifdef CONFIG_CPU_FREQ_STAT_DETAILS > + int64_t time; > + unsigned int load[NR_CPUS]; > +#endif > }; Other wise it looks good mostly. PS: I have cc'd you for a patch of mine which will get rid of most of the CONFIG_*** you used in your code.. But wait for it to be applied to change your code accordingly..

11 years, 11 months

A15 errata implementation

by Mark Hambleton

Hi, Does anyone know if there is a patch available for errata 801819? Thanks, Mark

11 years, 11 months

[PATCH] arm/dt: Don't add disabled CPUs to system topology

by James King

If CPUs are marked as disabled in the devicetree, make sure they do not exist in the system CPU information and CPU topology information. In this case these CPUs will not be able to be added to the system later using hot-plug. This allows a single chip with many CPUs to be easily used in a variety of hardware devices where they may have different actual processing requirements (eg for thermal/cost reasons). - Change devicetree.c to ignore any cpu nodes marked as disabled, this effectively limits the number of active cpu cores so no need for the max_cpus=x in the chosen node. - Change topology.c to ignore any cpu nodes marked as disabled, this is where the scheduler would learn about big/LITTLE cores so this effectively keeps the scheduler in sync. Signed-off-by: James King <james.king(a)linaro.org> --- Documentation/devicetree/bindings/arm/cpus.txt | 5 +++++ arch/arm/kernel/devtree.c | 6 ++++++ arch/arm/kernel/topology.c | 4 ++++ 3 files changed, 15 insertions(+) diff --git a/Documentation/devicetree/bindings/arm/cpus.txt b/Documentation/devicetree/bindings/arm/cpus.txt index f32494d..9fbcbc5 100644 --- a/Documentation/devicetree/bindings/arm/cpus.txt +++ b/Documentation/devicetree/bindings/arm/cpus.txt @@ -45,6 +45,10 @@ For the ARM architecture every CPU node must contain the following properties: "marvell,xsc3" "marvell,xscale" +And optionally set the following properties: + +- status: can be set to "disabled" to remove that CPU from the system CPU topology + Example: cpus { @@ -73,5 +77,6 @@ Example: device_type = "cpu"; compatible = "arm,cortex-a7"; reg = <0x101>; + status = "disabled"; }; }; diff --git a/arch/arm/kernel/devtree.c b/arch/arm/kernel/devtree.c index 5af04f6..f4ba8ee 100644 --- a/arch/arm/kernel/devtree.c +++ b/arch/arm/kernel/devtree.c @@ -112,6 +112,12 @@ void __init arm_dt_init_cpu_maps(void) return; /* + * Check if the cpu is marked as "disabled", if so ignore. + */ + if (!of_device_is_available(cpu)) + continue; + + /* * Duplicate MPIDRs are a recipe for disaster. * Scan all initialized entries and check for * duplicates. If any is found just bail out. diff --git a/arch/arm/kernel/topology.c b/arch/arm/kernel/topology.c index f10316b..90f8fb3 100644 --- a/arch/arm/kernel/topology.c +++ b/arch/arm/kernel/topology.c @@ -116,6 +116,10 @@ static void __init parse_dt_topology(void) if (cpu_eff->compatible == NULL) continue; + /* Check if the cpu is marked as "disabled", if so ignore. */ + if (!of_device_is_available(cn)) + continue; + rate = of_get_property(cn, "clock-frequency", &len); if (!rate || len != 4) { pr_err("%s missing clock-frequency property\n", -- 1.8.1.2

11 years, 11 months

[PATCH] cpuidle: fix ARCH_NEEDS_CPU_IDLE_COUPLED dependency warning

by Daniel Lezcano

Before the commit d6f346f2d2bf511c2c59176121a6e42ce60173a0, the ARCH_NEEDS_CPU_IDLE_COUPLED option was wrongly not depending on the CPU_IDLE and the Kconfig for OMAP / TEGRA was not checking this dependency when setting the option. With this patch, the ARCH_NEEDS_CPU_IDLE_COUPLED has been moved under the CPU_IDLE option. The dependency has been fixed in the relevant arch's Kconfig. Signed-off-by: Daniel Lezcano <daniel.lezcano(a)linaro.org> --- arch/arm/mach-omap2/Kconfig | 2 +- arch/arm/mach-tegra/Kconfig | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/arch/arm/mach-omap2/Kconfig b/arch/arm/mach-omap2/Kconfig index f49cd51..831e89e 100644 --- a/arch/arm/mach-omap2/Kconfig +++ b/arch/arm/mach-omap2/Kconfig @@ -83,7 +83,7 @@ config ARCH_OMAP4 depends on ARCH_OMAP2PLUS depends on ARCH_MULTI_V7 select ARCH_HAS_OPP - select ARCH_NEEDS_CPU_IDLE_COUPLED if SMP + select ARCH_NEEDS_CPU_IDLE_COUPLED if (SMP && CPU_IDLE) select ARM_CPU_SUSPEND if PM select ARM_ERRATA_720789 select ARM_GIC diff --git a/arch/arm/mach-tegra/Kconfig b/arch/arm/mach-tegra/Kconfig index 84d72fc..04c6221 100644 --- a/arch/arm/mach-tegra/Kconfig +++ b/arch/arm/mach-tegra/Kconfig @@ -23,7 +23,7 @@ menu "NVIDIA Tegra options" config ARCH_TEGRA_2x_SOC bool "Enable support for Tegra20 family" - select ARCH_NEEDS_CPU_IDLE_COUPLED if SMP + select ARCH_NEEDS_CPU_IDLE_COUPLED if (SMP && CPU_IDLE) select ARM_ERRATA_720789 select ARM_ERRATA_754327 if SMP select ARM_ERRATA_764369 if SMP -- 1.7.9.5

11 years, 11 months

[RFC PATCH] arm64: add support for NEON in kernel mode

by Ard Biesheuvel

Add <asm/neon.h> containing kernel_neon_begin/kernel_neon_end function declarations and corresponding definitions in fpsimd.c These are needed to wrap uses of NEON in kernel mode. The names are identical to the ones used in arm/ so code using intrinsics or vectorized by GCC can be shared between arm and arm64. Signed-off-by: Ard Biesheuvel <ard.biesheuvel(a)linaro.org> --- arch/arm64/Kconfig | 3 +++ arch/arm64/include/asm/neon.h | 14 ++++++++++++++ arch/arm64/kernel/fpsimd.c | 29 ++++++++++++++++++++++++++++- 3 files changed, 45 insertions(+), 1 deletion(-) create mode 100644 arch/arm64/include/asm/neon.h diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig index 56b3f6d..46ba680 100644 --- a/arch/arm64/Kconfig +++ b/arch/arm64/Kconfig @@ -95,6 +95,9 @@ config SWIOTLB config IOMMU_HELPER def_bool SWIOTLB +config KERNEL_MODE_NEON + def_bool y + source "init/Kconfig" source "kernel/Kconfig.freezer" diff --git a/arch/arm64/include/asm/neon.h b/arch/arm64/include/asm/neon.h new file mode 100644 index 0000000..b0cc58a9 --- /dev/null +++ b/arch/arm64/include/asm/neon.h @@ -0,0 +1,14 @@ +/* + * linux/arch/arm64/include/asm/neon.h + * + * Copyright (C) 2013 Linaro Ltd <ard.biesheuvel(a)linaro.org> + * + * This program is free software; you can redistribute it and/or modify + * it under the terms of the GNU General Public License version 2 as + * published by the Free Software Foundation. + */ + +#define cpu_has_neon() (1) + +void kernel_neon_begin(void); +void kernel_neon_end(void); diff --git a/arch/arm64/kernel/fpsimd.c b/arch/arm64/kernel/fpsimd.c index e8b8357..68d6caa 100644 --- a/arch/arm64/kernel/fpsimd.c +++ b/arch/arm64/kernel/fpsimd.c @@ -83,6 +83,33 @@ void fpsimd_flush_thread(void) fpsimd_load_state(&current->thread.fpsimd_state); } +#ifdef CONFIG_KERNEL_MODE_NEON + +/* + * Kernel-side NEON support functions + */ +void kernel_neon_begin(void) +{ + /* Avoid using the NEON in interrupt context */ + might_sleep(); + preempt_disable(); + + if (current->mm) + fpsimd_save_state(&current->thread.fpsimd_state); +} +EXPORT_SYMBOL(kernel_neon_begin); + +void kernel_neon_end(void) +{ + if (current->mm) + fpsimd_load_state(&current->thread.fpsimd_state); + + preempt_enable(); +} +EXPORT_SYMBOL(kernel_neon_end); + +#endif /* CONFIG_KERNEL_MODE_NEON */ + /* * FP/SIMD support code initialisation. */ @@ -103,4 +130,4 @@ static int __init fpsimd_init(void) return 0; } -late_initcall(fpsimd_init); +core_initcall(fpsimd_init); -- 1.8.1.2

11 years, 11 months

[PATCH v2 0/5] Add generic set_rate clk_ops for PLL35xx and PLL36xx for samsung SoCs

by Vikas Sajjan

This patch series does the following: 1) Factors out possible common code, unifies the clk strutures used for PLL35xx & PLL36xx and usues clk->base instead of clk->con0 2) Defines a common rate_table which will contain recommended p, m, s and k values for supported rates that needs to be changed for changing corresponding PLL's rate 3) Adds set_rate() and round_rate() clk_ops for PLL35xx and PLL36xx changes since v1: - removed sorting and bsearch - modified the definition of struct "samsung_pll_rate_table" - added generic round_rate() - rectified the ops assignment for "rate table passed as NULL" during PLL registration Is rebased on branch kgene's "for-next" https://git.kernel.org/cgit/linux/kernel/git/kgene/linux-samsung.git/log/?h… And tested these patch on chromebook for EPLL settings for Audio on our chrome tree. Vikas Sajjan (2): clk: samsung: Add set_rate() clk_ops for PLL36xx clk: samsung: Add EPLL and VPLL freq table for exynos5250 SoC Yadwinder Singh Brar (3): clk: samsung: Use clk->base instead of directly using clk->con0 for PLL3xxx clk: samsung: Add support to register rate_table for PLL3xxx clk: samsung: Add set_rate() clk_ops for PLL35xx drivers/clk/samsung/clk-exynos4.c | 10 +- drivers/clk/samsung/clk-exynos5250.c | 30 +++-- drivers/clk/samsung/clk-pll.c | 226 ++++++++++++++++++++++++++++++---- drivers/clk/samsung/clk-pll.h | 33 ++++- 4 files changed, 260 insertions(+), 39 deletions(-) -- 1.7.9.5

11 years, 11 months

[ACTIVITY] (John Stultz) June 3 - 7

by John Stultz

=== Highlights === * Sent my 3.11 queue to Thomas * Reviewed/Looked at queueing generic sched_clock logic from arch/arm * Strange 3.9.4 regression from last week ended up being a gcc issue * Reviewed blueprints and sent out weekly android upstreaming mail * Dhaval G. (Mozilla) is interested in helping with Volatile Ranges, so spent some time bringing him up to speed on volatile range work * Continued some older discussions with Minchan on volatile ranges * Started re-factoring volatile ranges patch to make shared volatility the default and private an optimization * Worked with Zoran on some new tasks (pushing wakeup_source driver enablement upstream) * Synced with AntonV on memcg pressure levels and userland low-memory killer. * Sent mail to Android devs to get their thoughts on userland low-memory killer * Pinged maintainers on KDB kiosk mode === Plans === * Continued volatile range work * Send out refactored ION patches and comments to Google devs * Finish queuing items for 3.11 * LSK / upstream review & mentoring discussions === Issues === * N/A

11 years, 11 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

linaro-kernel