On 28 March 2013 13:35, Amit Daniel Kachhap wrote:
> Submitting the V5 version of exynos5440 cpufreq driver. This patchset
> addresses
> all the coding and design concerns raised especially by Viresh.
>
> Changes in V5:
> * Removed the unnecessary DT look up entry from mach-exynos5-dt.c.
> *
On Thu, 2013-03-28 at 07:44 +, Arnd Bergmann wrote:
> Yes, absolutely. What a couple of the previous architectures have done is
> to keep out of tree patches for their old ABI for a while, and to submit
> only code that follows the generic ABI upstream. Usually it doesn't take
> long for
2013/3/27 Fabio Coatti :
> Hi all,
> we are experiencing crashes on some servers, right now running 3.7.10;
> I've been able to get only screenshots from dying server that I
> attached below. Probably we can exclude hardware issues, as it
> happened on two different servers.
Further information:
Hi Linus:
This push removes IPsec ESN support from the talitos/caam drivers
since they were implemented incorrectly, causing interoperability
problems if ESN is used with them.
Please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git
or
For percpu notes, we are exporting only address and not size. So
the userspace tool kexec-tools is putting an upper limit of 1024
and putting the value in p_memsz and p_filesz fields. So the patch
add the new sysfile crash_notes_size to export the exact percpu
note size and let the kexec-tools
Add an Documentation/ABI entry for /sys/devices/system/cpu/cpu0/crash_notes
and /sys/devices/system/cpu/cpu0/crash_notes_size.
Cc: Greg KH
Cc: "Eric W. Biederman"
Cc: Vivek Goyal
Signed-off-by: Zhang Yanfei
---
Documentation/ABI/testing/sysfs-devices-system-cpu | 12
1 files
On Thu, Mar 28, 2013 at 08:36:52AM +0100, Sebastien Royen wrote:
> Hi Dmitry
>
> 2013/3/28 Dmitry Torokhov
> >
> > Hi Seb,
> >
> > On Wed, Mar 27, 2013 at 09:17:43AM +0100, seb wrote:
> > > Event value is wrong. Should be in range -2048 to 2047, but is in range 0
> > > to 4095.
> > > Use int8_t
This patch helps to have single binary for exynos5440 and previous
exynos soc's. This change is needed for adding exynos5440 cpufreq driver
which does not uses exynos-cpufreq common file and adds it own driver.
Signed-off-by: Amit Daniel Kachhap
---
drivers/cpufreq/exynos-cpufreq.c |2 +-
1
This patch adds dvfs support for exynos5440 SOC. This soc has 4 cores and
they scale at same frequency. The nature of exynos5440 clock controller is
different from previous exynos controllers so not using the common exynos
cpufreq framework. The major difference being interrupt notification for
Add cpufreq controller device node for Exynos5440 SoC for passing
parameters like controller base address, interrupt and cpufreq
table. This node is added outside cpu0 as this driver is now a platform
driver and a new device structure is needed.
Signed-off-by: Amit Daniel Kachhap
---
The OPP library support is needed for exynos5440 cpu frequency
dynamic scaling driver.
Signed-off-by: Amit Daniel Kachhap
---
arch/arm/mach-exynos/Kconfig |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/arch/arm/mach-exynos/Kconfig b/arch/arm/mach-exynos/Kconfig
index
Submitting the V5 version of exynos5440 cpufreq driver. This patchset addresses
all the coding and design concerns raised especially by Viresh.
Changes in V5:
* Removed the unnecessary DT look up entry from mach-exynos5-dt.c.
* Fixed all coding and comments issue raised by Viresh.
Changes in V4:
There is no unified subject for this patchset.
Patch 1 is for removing one division operation with multiplication.
Patch 2,3 is for clean-up related to load_balance(), there is improvement
in terms of code size and IMO, readability may be also improved.
Patch 4,5 is for correctness about
Now checking that this cpu is appropriate to balance is embedded into
update_sg_lb_stats() and this checking has no direct relationship to this
function.
There is not enough reason to place this checking at update_sg_lb_stats(),
except saving one iteration for sched_group_cpus. But with this
sched_slice() compute ideal runtime slice. If there are many tasks
in cfs_rq, period for this cfs_rq is extended to guarantee that each task
has time slice at least, sched_min_granularity. And then each task get
a portion of this period for it. If there is a task which have much larger
load weight
There is no reason to maintain separate variables for this_group
and busiest_group in sd_lb_stat, except saving some space.
But this structure is always allocated in stack, so this saving
isn't really benificial.
This patch unify these variables, so IMO, readability may be improved.
Remove one division operation in find_buiest_queue().
Signed-off-by: Joonsoo Kim
diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
index 6f238d2..1d8774f 100644
--- a/kernel/sched/fair.c
+++ b/kernel/sched/fair.c
@@ -4911,7 +4911,7 @@ static struct rq *find_busiest_queue(struct lb_env
Following-up upper se in sched_slice() should not be done,
because sched_slice() is used for checking that resched is needed
whithin *this* cfs_rq and there is one problem related to this
in current implementation.
The problem is that if we follow-up upper se in sched_slice(), it is
possible that
- Original Message -
> From: "Dave Jones"
> To: "CAI Qian"
> Cc: "Christoph Lameter" , "David Rientjes"
> , "linux-mm" ,
> linux-kernel@vger.kernel.org, "Oleg Nesterov"
> Sent: Wednesday, March 27, 2013 3:53:44 AM
> Subject: Re: BUG at kmem_cache_alloc
>
> On Tue, Mar 26, 2013 at
On Wed 27-03-13 18:32:23, Michal Hocko wrote:
[...]
> Removed WARN_ON_ONCE as suggested by Johannes and kept kmalloc with
> PATH_MAX used instead of PAGE_SIZE. I've kept Glauber's acked-by but I
> can remove it.
And hopefully the last version. I forgot to s/PAGE_SIZE/MAX_PATH/ in
snprintf.
---
* Frederic Weisbecker wrote:
> +config NO_HZ_EXTENDED_ALL
> + bool "Full dynticks system on all CPUs"
> + depends on NO_HZ_EXTENDED
> + help
> + Force all CPUs to be full dynticks. The range specified in the
> + nohz_extended boot option will then be ignored.
> +
> +
On Thursday 28 March 2013, H. Peter Anvin wrote:
> On 03/27/2013 08:09 PM, Ley Foon Tan wrote:
> > The question is, is it a requirement for new arch to support generic
> > syscall ABI when upstreaming? Can we upstream a non-generic syscall ABI
> > first and migrate to generic syscall ABI in
Hi Andrew,
2013/3/27 Andrew Morton :
> On Wed, 20 Mar 2013 11:52:45 +0100 Philipp Zabel
> wrote:
>
>> This driver requests and remaps a memory region as configured in the
>> device tree. It serves memory from this region via the genalloc API.
>> It optionally enables the SRAM clock.
>>
>> Other
On Wed, Mar 27, 2013 at 3:56 PM, Bjorn Helgaas wrote:
>
> Why can't we set all the ASPM flags *first*, before calling
> pci_acpi_scan_root()? That way we could just do the correct ASPM
> setup as we discover devices during enumeration, rather than trying to
> fix things up afterwards. I suspect
On 28 March 2013 04:16, Jacob Shin wrote:
> diff --git a/drivers/cpufreq/amd_freq_sensitivity.c
> b/drivers/cpufreq/amd_freq_sensitivity.c
> +#include
> +
> +#include "cpufreq_governor.h"
These two are enough for you?
> +#define PROC_FEEDBACK_INTERFACE_SHIFT 11
> +#define
* Frederic Weisbecker wrote:
> + cpulist_scnprintf(nohz_ext_buf, sizeof(nohz_ext_buf),
> nohz_extended_mask);
> + pr_info("NO_HZ: Experimental full dynticks CPUs: %s.\n", nohz_ext_buf);
I'd suggest removing the 'experimental' word. We are not sending anything
experimental to Linus:
* Frederic Weisbecker wrote:
> The timekeeping job must be able to run early on boot
> because there may be some pre-SMP (and thus pre-initcalls )
> components that rely on it. The IO-APIC is one such users
> as it tests the timer health by watching jiffies progression.
Btw., while I agree
On 28 March 2013 04:07, Jacob Shin wrote:
> diff --git a/drivers/cpufreq/cpufreq_ondemand.c
> b/drivers/cpufreq/cpufreq_ondemand.c
> +void od_register_ops(struct od_ops *ops)
> +{
> + if (ops->powersave_bias_init_cpu)
> + od_ops.powersave_bias_init_cpu =
Hi Dmitry
2013/3/28 Dmitry Torokhov
>
> Hi Seb,
>
> On Wed, Mar 27, 2013 at 09:17:43AM +0100, seb wrote:
> > Event value is wrong. Should be in range -2048 to 2047, but is in range 0
> > to 4095.
> > Use int8_t to int conversion and remove 0xfff mask.
> >
> > Signed-off-by: seb
> > ---
> >
if we pull some commits from other git repo
which bring in a few CONFIG_* options, then
we have to build all again, but we do assure
these options are not interesting for us,
so the long waiting build will be offending.
this change help us to avoid all-build.
Signed-off-by: liguang
---
Makefile
As people started using Suggested-by as standard signature, adding
"Suggested-by" to the standard signature so that checkpatch won't
generate warning when Suggested-by is used in patch signature
Signed-off-by: Mugunthan V N
---
Changes from Initial version
* Updated
2013/3/28, Alexandru Gheorghiu :
> Use kmemdup instead of kzalloc and memcpy.
>
> Signed-off-by: Alexandru Gheorghiu
Looks good to me.
Acked-by: Namjae Jeon
Thanks~
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
Initialize cpuacct before the scheduler is functioning, so when
cpuacct_charge() and cpuacct_account_field() are called, task_ca()
won't return NULL.
Signed-off-by: Li Zefan
---
kernel/sched/cpuacct.c | 11 ++-
1 file changed, 6 insertions(+), 5 deletions(-)
diff --git
The only user was cpuacct.
Signed-off-by: Li Zefan
---
include/linux/cgroup.h | 1 -
kernel/cgroup.c| 3 ---
2 files changed, 4 deletions(-)
diff --git a/include/linux/cgroup.h b/include/linux/cgroup.h
index 7d73905..a236a5b 100644
--- a/include/linux/cgroup.h
+++
On 03/27/2013 08:27 PM, Michal Hocko wrote:
> On Wed 27-03-13 09:21:02, Tejun Heo wrote:
>> On Wed, Mar 27, 2013 at 9:19 AM, Michal Hocko wrote:
Maybe the name could signify it's part of memcg?
>>>
>>> kmem_ prefix is used for all CONFIG_MEMCG_KMEM functions. I understand
>>> it clashes with
Now we're guaranteed when cpuacct_charge() and cpuacct_account_field()
are called, cpuacct has already been properly initialized, so we no
longer need those checks.
Signed-off-by: Li Zefan
---
kernel/sched/cpuacct.c | 6 --
1 file changed, 6 deletions(-)
diff --git a/kernel/sched/cpuacct.c
This is a preparation, so later we can initialize cpuacct earlier.
Signed-off-by: Li Zefan
---
kernel/sched/cpuacct.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/kernel/sched/cpuacct.c b/kernel/sched/cpuacct.c
index 9305fd2..a691c4d 100644
---
Now we don't need cpuacct_init(), and instead we just initialize
root_cpuacct when it's defined.
Signed-off-by: Li Zefan
---
kernel/sched/core.c| 2 --
kernel/sched/cpuacct.c | 11 ---
kernel/sched/cpuacct.h | 5 -
3 files changed, 4 insertions(+), 14 deletions(-)
diff --git
cpuacct is the only user of cgroup_subsys.active flag.
The flag is needed because cpuacct_charge() and cpuacct_account_field() can
be called when cpuacct hasn't been initialized during system bootup.
This patch initializes cpuacct earlier, and the result is we don't have
to check the flag in
Use kmemdup instead of kzalloc and memcpy.
Signed-off-by: Alexandru Gheorghiu
---
fs/f2fs/node.c| 12 +---
fs/f2fs/segment.c |3 +--
2 files changed, 6 insertions(+), 9 deletions(-)
diff --git a/fs/f2fs/node.c b/fs/f2fs/node.c
index e275218..9f5eca4 100644
---
On Mon, Feb 25, 2013 at 10:52 PM, Guennadi Liakhovetski
wrote:
> clk_set_rate() isn't supposed to accept approximate frequencies, instead
> a supported frequency should be obtained from clk_round_rate() and then
> used to set the clock.
>
> Signed-off-by: Guennadi Liakhovetski
> ---
>
> Applies
On Wed, Mar 27, 2013 at 9:02 PM, Paolo Pisati
wrote:
> check for '/cpus' presence before blindly dereferencing it:
>
> [4.181793] Unable to handle kernel NULL pointer dereference at virtual
> address 001c
> [4.181793] pgd = c0004000
> [4.181823] [001c] *pgd=
> [
Unbound workqueues are going to be NUMA-affine. Add wq_numa_tbl_len
and wq_numa_possible_cpumask[] in preparation. The former is the
highest NUMA node ID + 1 and the latter is masks of possibles CPUs for
each NUMA node.
This patch only introduces these. Future patches will make use of
them.
Factor out lock pool, put_pwq(), unlock sequence into
put_pwq_unlocked(). The two existing places are converted and there
will be more with NUMA affinity support.
This is to prepare for NUMA affinity support for unbound workqueues
and doesn't introduce any functional difference.
Signed-off-by:
Currently, when exposing attrs of an unbound workqueue via sysfs, the
workqueue_attrs of first_pwq() is used as that should equal the
current state of the workqueue.
The planned NUMA affinity support will make unbound workqueues make
use of multiple pool_workqueues for different NUMA nodes and
When worker tasks are created using kthread_create_on_node(),
currently only per-cpu ones have the matching NUMA node specified.
All unbound workers are always created with NUMA_NO_NODE.
Now that an unbound worker pool may have an arbitrary cpumask
associated with it, this isn't optimal. Add
Currently, all workqueue workers which have negative nice value has
'H' postfixed to their names. This is necessary for per-cpu workers
as they use the CPU number instead of pool->id to identify the pool
and the 'H' postfix is the only thing distinguishing normal and
highpri workers.
As workers
Unbound workqueues are now NUMA aware. Let's add some control knobs
and update sysfs interface accordingly.
* Add kernel param workqueue.numa_disable which disables NUMA affinity
globally.
* Replace sysfs file "pool_id" with "pool_ids" which contain
node:pool_id pairs. This change is
Currently, an unbound workqueue has single current, or first, pwq
(pool_workqueue) to which all new work items are queued. This often
isn't optimal on NUMA machines as workers may jump around across node
boundaries and work items get assigned to workers without any regard
to NUMA affinity.
This
Use kmem_cache_alloc_node() with @pool->node instead of
kmem_cache_zalloc() when allocating a pool_workqueue so that it's
allocated on the same node as the associated worker_pool. As there's
no no kmem_cache_zalloc_node(), move zeroing to init_pwq().
This was suggested by Lai Jiangshan.
Factor out pool_workqueue linking and installation into numa_pwq_tbl[]
from apply_workqueue_attrs() into numa_pwq_tbl_install(). link_pwq()
is made safe to call multiple times. numa_pwq_tbl_install() links the
pwq, installs it into numa_pwq_tbl[] at the specified node and returns
the old entry.
Currently, an unbound workqueue has only one "current" pool_workqueue
associated with it. It may have multple pool_workqueues but only the
first pool_workqueue servies new work items. For NUMA affinity, we
want to change this so that there are multiple current pool_workqueues
serving different
Break init_and_link_pwq() into init_pwq() and link_pwq() and move
unbound-workqueue specific handling into apply_workqueue_attrs().
Also, factor out unbound pool and pool_workqueue allocation into
alloc_unbound_pwq().
This reorganization is to prepare for NUMA affinity and doesn't
introduce any
Currently workqueue->name[] is of flexible length. We want to use the
flexible field for something more useful and there isn't much benefit
in allowing arbitrary name length anyway. Make it fixed len capping
at 24 bytes.
Signed-off-by: Tejun Heo
---
kernel/workqueue.c | 19 ---
Move wq->flags and ->cpu_pwqs to the end of workqueue_struct and align
them to the cacheline. These two fields are used in the work item
issue path and thus hot. The scheduled NUMA affinity support will add
dispatch table at the end of workqueue_struct and relocating these two
fields will allow
Hello,
Changes from the last take[L] are
* Lai pointed out that the previous implementation was broken in that
if a workqueue spans over multiple nodes and some of the nodes don't
have any desired online CPUs, work items queued on those nodes would
be spread across all CPUs violating the
The scheduled NUMA affinity support for unbound workqueues would need
to walk workqueues list and pool related operations on each workqueue.
Move wq_pool_mutex locking out of get/put_unbound_pool() to their
callers so that pool operations can be performed while walking the
workqueues list, which
Hi Chanwoo,
On 28 March 2013 04:51, Chanwoo Choi wrote:
> On 03/27/2013 08:23 PM, Sachin Kamat wrote:
>> Return the value obtained from the function instead of hardcoding.
>> Silences the following warning:
>> drivers/extcon/extcon-max77693.c:297 max77693_muic_set_path()
>> info: why not
System hung when running xfstests-dev 013 test case on an s390x guest. Never saw
this on 3.9-rc3 before but need to double-check. Any idea?
CAI Qian
Ý 1113.795759¨ Ý cut here ¨
Ý 1113.795771¨ kernel BUG at fs/ext4/inode.c:1591!
Ý 1113.795845¨ illegal operation: 0001 Ý#1¨
Return the value obtained from the function instead of hardcoding.
Silences the following warnings:
drivers/extcon/extcon-max77693.c:297 max77693_muic_set_path()
info: why not propagate 'ret' from max77693_update_reg() instead of (-11)?
drivers/extcon/extcon-max77693.c:310 max77693_muic_set_path()
Return the value obtained from the function instead of hardcoding.
Fixes the following warnings:
drivers/extcon/extcon-max8997.c:235 max8997_muic_set_path() info:
why not propagate 'ret' from max8997_update_reg() instead of (-11)?
drivers/extcon/extcon-max8997.c:248 max8997_muic_set_path() info:
Doug Anderson wrote:
>Hi,
>
>On Wed, Mar 27, 2013 at 11:40 AM, Lars-Peter Clausen
>wrote:
>> On 03/27/2013 07:35 PM, Naveen Krishna Ch wrote:
>>> On 13 March 2013 13:39, Doug Anderson wrote:
The exynos ADC won't work without a regulator called "vdd" and a
>clock
called "adc".
Oops, forgot something.
Both patches are against wq/for-3.10 and fix problems introduced in
this devel cycle, so no need to be alarmed.
Thanks.
--
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More
>From b37c3e3a74346749f0278c349dc0857107cb4370 Mon Sep 17 00:00:00 2001
From: Tejun Heo
Date: Wed, 27 Mar 2013 23:27:41 -0700
29c91e9912b ("workqueue: implement attribute-based unbound worker_pool
management") implemented attrs based worker_pool matching. It tried
to avoid false negative when
>From b2277a4e655c0858da7d85b99f0925abeedc3b6c Mon Sep 17 00:00:00 2001
From: Tejun Heo
Date: Wed, 27 Mar 2013 23:27:41 -0700
8864b4e59 ("workqueue: implement get/put_pwq()") implemented pwq
(pool_workqueue) refcnting which frees workqueue when the last pwq
goes away. It determined whether it
Instead of using legacy suspend/resume methods, using newer dev_pm_ops
structure allows better control over power management. Also, use of
pm_message_t is deprecated. Thus, it is removed.
Signed-off-by: Jingoo Han
---
drivers/video/backlight/ili9320.c | 24 +---
Instead of using legacy suspend/resume methods, using newer dev_pm_ops
structure allows better control over power management.
Signed-off-by: Jingoo Han
---
drivers/video/backlight/tosa_bl.c | 18 --
drivers/video/backlight/tosa_lcd.c | 18 --
2 files
Instead of using legacy suspend/resume methods, using newer dev_pm_ops
structure allows better control over power management.
Signed-off-by: Jingoo Han
---
drivers/video/backlight/omap1_bl.c | 22 ++
1 files changed, 10 insertions(+), 12 deletions(-)
diff --git
This adds a driver for random number generator present on Broadcom BCM2835 SoC,
used in Raspberry Pi and Roku 2 devices.
Signed-off-by: Dom Cobley
Signed-off-by: Lubomir Rintel
Tested-by: Stephen Warren
Cc: Herbert Xu
Cc: Stephen Warren
Cc: Matt Mackall
Cc:
In the case of no-match in "for (i = 0; i < (pdev->num_resources / 2); i++)",
i is "pdev->num_resources / 2". Fix the boundary checking to avoid the out of
bound array access for data->sfrbases[i].
Signed-off-by: Axel Lin
---
drivers/iommu/exynos-iommu.c |2 +-
1 file changed, 1
On Wed, 2013-03-27 at 23:09 -0600, Stephen Warren wrote:
> Use the new standard API of_property_read_u32_index() instead of open-
> coding it.
>
> Signed-off-by: Stephen Warren
> ---
> Note: This depends on the proposed patch "of: Add support for reading
> a u32 from a multi-value property" by
On Fri, 2013-03-22 at 20:44 -0600, Stephen Warren wrote:
> On 03/22/2013 06:55 AM, Lubomir Rintel wrote:
> > Signed-off-by: Lubomir Rintel
>
> A commit description would be useful.
>
> > arch/arm/boot/dts/bcm2835.dtsi |5 +
> > arch/arm/configs/bcm2835_defconfig |3 +-
> >
On 03/27/2013 03:30:22 AM, Paul Bolle wrote:
CONFIG_SND_HDA_POWER_SAVE was removed in v3.6.7, see commit
83012a7ccbb90dee33c97a004b3e374f988612af ("ALSA: hda - Clean up
CONFIG_SND_HDA_POWER_SAVE"). Clean up hda's documentation to reflect
that.
Signed-off-by: Paul Bolle
---
0) I send this to
This adds a device tree binding for random number generator present on Broadcom
BCM2835 SoC, used in Raspberry Pi and Roku 2 devices.
Signed-off-by: Lubomir Rintel
Tested-by: Stephen Warren
Cc: Stephen Warren
Cc: linux-rpi-ker...@lists.infradead.org
Cc: devicetree-disc...@lists.ozlabs.org
Cc:
With the inclusion of the pin control driver, more GPIO pins have been
identified on the arch-vt8500 SoCs requiring an increase in the available
GPIOs.
Signed-off-by: Tony Prisk
---
arch/arm/Kconfig |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/arch/arm/Kconfig
This patch adds an of_property_read_u32_index() function to allow
reading a single indexed u32 value from a property containing multiple
u32 values.
Signed-off-by: Tony Prisk
---
drivers/of/base.c | 33 +
include/linux/of.h |9 +
2 files changed,
With the move to a combined pinctrl/gpio driver, the arch-vt8500
gpio driver is no longer required.
Signed-off-by: Tony Prisk
---
.../devicetree/bindings/gpio/gpio-vt8500.txt | 24 --
drivers/gpio/Kconfig |6 -
drivers/gpio/Makefile
This patch adds pinctrl nodes to the VIA VT8500 and Wondermedia SoC dtsi
files to support the pinctrl driver.
Signed-off-by: Tony Prisk
---
arch/arm/boot/dts/vt8500.dtsi |9 +
arch/arm/boot/dts/wm8505.dtsi |9 +
arch/arm/boot/dts/wm8650.dtsi |9 +
Remove the gpio related devicetree nodes as these are no longer required
with the move to a combined pinctrl/gpio driver.
Signed-off-by: Tony Prisk
---
arch/arm/boot/dts/vt8500.dtsi |7 ---
arch/arm/boot/dts/wm8505.dtsi |7 ---
arch/arm/boot/dts/wm8650.dtsi |7 ---
v3 changes:
Rebased onto v3.9-rc4
Added the missing interrupt-controller info to the relevant dtsi files.
Removed the gpio-vt8500.txt binding along with the gpio driver.
Changes made as requested by Linux Walleij:
Removed the wm,pinmux property which has caused too much confusion, and left the
On Wednesday 27 March 2013 09:27 PM, Stephen Warren wrote:
On 03/27/2013 07:00 AM, Linus Walleij wrote:
On Thu, Mar 21, 2013 at 3:30 PM, Laxman Dewangan wrote:
#ifdef CONFIG_OF_GPIO
- palmas_gpio->gpio_chip.of_node = palmas->dev->of_node;
+ palmas_gpio->gpio_chip.of_node =
On Wed, Mar 27, 2013 at 10:52 PM, Rajagopal Venkat
wrote:
> Fix compiler warnings generated when devfreq is not enabled
> (CONFIG_PM_DEVFREQ is not set).
>
> Signed-off-by: Rajagopal Venkat
Thanks!
Acked-by: MyungJoo Ham
> ---
> include/linux/devfreq.h | 16
> 1 file
On Wednesday 27 March 2013 06:30 PM, Linus Walleij wrote:
On Thu, Mar 21, 2013 at 3:30 PM, Laxman Dewangan wrote:
+#ifdef CONFIG_OF
+static struct of_device_id of_palmas_gpio_match[] = {
+ { .compatible = "ti,palmas-gpio"},
+ { },
+};
+MODULE_DEVICE_TABLE(of,
for make V=1 EXTRA_CFLAGS=-W ARCH=arm allmodconfig
printk is need when CONFIG_BPF_JIT is defined
or it will report pr_err and print_hex_dump are implicit declaration
Signed-off-by: Chen Gang
---
include/linux/filter.h |3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff
From: Stephane Eranian eran...@google.com
Make the PEBS Load Latency threshold register layout
and encoding visible to user level tools.
Signed-off-by: Stephane Eranian eran...@google.com
Cc: pet...@infradead.org
Cc: a...@linux.intel.com
Cc: a...@redhat.com
Cc: jo...@redhat.com
Cc:
From: Andi Kleen a...@linux.intel.com
perf record has a new option -W that enables weightened sampling.
Add sorting support in top/report for the average weight per sample and the
total weight sum. This allows to both compare relative cost per event
and the total cost over the measurement
From: Stephane Eranian eran...@google.com
This patch adds the --mem-mode option to perf report.
This mode requires a perf.data file created with memory access samples.
Signed-off-by: Stephane Eranian eran...@google.com
Cc: Andi Kleen a...@linux.intel.com
Cc: Ingo Molnar mi...@elte.hu
Cc: Jiri
From: Stephane Eranian eran...@google.com
This new command is a wrapper on top of perf record and perf report to
make it easier to configure for memory access profiling.
To record loads:
$ perf mem -t load rec .
To record stores:
$ perf mem -t store rec .
To get the report:
$ perf mem
From: Stephane Eranian eran...@gmail.com
This patch adds the --per-core option to perf stat.
This option is used to aggregate system-wide counts
on a per physical core basis. On processors with
hyperthreading, this means counts of all HT threads
running on a physical core are aggregated.
This
On Sat, Mar 23, 2013 at 04:06:51PM +0100, Sebastian Hesselbarth wrote:
The CPU used in Marvell Dove SoCs is a PJ4 Sheeva core. Using
CONFIG_CPU_PJ4 instead of CONFIG_CPU_V7 will also allow to enable
iWMMXt extensions on Dove.
Signed-off-by: Sebastian Hesselbarth
From: Stephane Eranian eran...@google.com
This patch adds a flags field to each event constraint.
It can be used to store event specific features which can
then later be used by scheduling code or low-level x86 code.
The flags are propagated into event-hw.flags during the
get_event_constraint()
From: Stephane Eranian eran...@google.com
This patch adds support for PEBS Precise Store
which is available on Intel Sandy Bridge and
Ivy Bridge processors.
To use Precise store, the proper PEBS event
must be used: mem_trans_retired:precise_stores.
For the perf tool, the generic mem-stores event
From: Arnaldo Carvalho de Melo a...@redhat.com
Now that the map browser shares the input routine with the hists
browser, there is no need for using any libnewt routine, so remove all
traces except for honouring NO_NEWT=1 on the makefile command line as an
indication that TUI support is not
From: Arnaldo Carvalho de Melo a...@redhat.com
This reverts commit 0439539f72ea222fbfe511b47318b9c1815a7108.
This caused this segfault:
[root@sandy linux]# perf sched rec
^C[ perf record: Woken up 1 times to write data ]
[ perf record: Captured and wrote 1.306 MB perf.data (~57062 samples) ]
From: Stephane Eranian eran...@google.com
Leverages the PERF_RECORD_MISC_MMAP_DATA bit in the RECORD_MMAP record
header. When the bit is set then the mapping type is set to
MAP__VARIABLE.
Signed-off-by: Stephane Eranian eran...@google.com
Cc: Andi Kleen a...@linux.intel.com
Cc: Ingo Molnar
From: Stephane Eranian eran...@google.com
To make it more obvious what this option does as suggested by Andi on
LKML.
Signed-off-by: Stephane Eranian eran...@google.com
Cc: Andi Kleen a...@linux.intel.com
Cc: Ingo Molnar mi...@elte.hu
Cc: Jiri Olsa jo...@redhat.com
Cc: Namhyung Kim
From: Namhyung Kim namhyung@lge.com
Check return value of malloc and fail if NULL.
Signed-off-by: Namhyung Kim namhy...@kernel.org
Cc: Frederic Weisbecker fweis...@gmail.com
Cc: Ingo Molnar mi...@kernel.org
Cc: Paul Mackerras pau...@samba.org
Cc: Peter Zijlstra a.p.zijls...@chello.nl
Cc:
From: Namhyung Kim namhyung@lge.com
Convert them to pr_debug() and propagate error code.
Signed-off-by: Namhyung Kim namhy...@kernel.org
Cc: Frederic Weisbecker fweis...@gmail.com
Cc: Ingo Molnar mi...@kernel.org
Cc: Paul Mackerras pau...@samba.org
Cc: Peter Zijlstra a.p.zijls...@chello.nl
From: Stephane Eranian eran...@google.com
This patch adds support for memory profiling using the
PEBS Load Latency facility.
Load accesses are sampled by HW and the instruction
address, data address, load latency, data source, tlb,
locked information can be saved in the sampling buffer
if using
From: Stephane Eranian eran...@google.com
Type of mapping was lost and made it hard for a tool
to distinguish code vs. data mmaps. Perf has the ability
to distinguish the two.
Use a bit in the header-misc bitmask to keep track of
the mmap type. If PERF_RECORD_MISC_MMAP_DATA is set then
the
501 - 600 of 1168 matches
Mail list logo
