On 03/28/2013 08:52 PM, Steven Rostedt wrote:
From: Steven Rostedt (Red Hat) rost...@goodmis.org
The function tracing control loop used by perf spits out a warning
if the called function is not a control function. This is because
the control function references a per cpu allocated data
On Thu, Mar 28, 2013 at 07:24:02PM +0100, Maxime Ripard wrote:
Hi Simon,
Le 28/03/2013 13:42, Simon Horman a écrit :
On Thu, Mar 28, 2013 at 10:41:44AM +0100, Maxime Ripard wrote:
Now that the arm core code calls irqchip_init, we can remove it from all
the machines that were using it.
On Thu, Mar 28, 2013 at 10:08:23PM -0400, Paul Gortmaker wrote:
[Re: [PATCH 2/4] nohz: Print final full dynticks CPUs range on boot] On
28/03/2013 (Thu 19:00) Paul E. McKenney wrote:
On Fri, Mar 29, 2013 at 01:39:04AM +0100, Frederic Weisbecker wrote:
2013/3/29 Paul Gortmaker
Hi, simon
I forgot to add your email in the CC, could you please help
reviewing this patch since I will send the kexec-tools patch
if this patch is accepted.
Thanks
Zhang
于 2013年03月28日 16:15, Zhang Yanfei 写道:
For percpu notes, we are exporting only address and not size. So
the userspace tool
On Fri, Mar 29, 2013 at 11:50:35AM +0800, Zhang Yanfei wrote:
Hi, simon
I forgot to add your email in the CC, could you please help
reviewing this patch since I will send the kexec-tools patch
if this patch is accepted.
Thanks
Zhang
于 2013年03月28日 16:15, Zhang Yanfei 写道:
For percpu
On Thu, Mar 28, 2013 at 04:16:45PM +0800, Zhang Yanfei wrote:
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 gre...@linuxfoundation.org
Cc: Eric W. Biederman ebied...@xmission.com
Cc: Vivek Goyal
On Thu, Mar 28, 2013 at 04:58:30PM -0700, Sukadev Bhattiprolu wrote:
Roberto Vitillo [raviti...@lbl.gov] wrote:
| The proposed patch adds the convert tool to perf which allows to convert a
| perf.data file to a set of callgrind data files which can subsequently be
| displayed with kcachegrind.
On 03/28/2013 06:42:47 AM, Arnd Bergmann wrote:
On Thursday 28 March 2013, Ley Foon Tan wrote:
On Thu, 2013-03-28 at 10:40 +, Arnd Bergmann wrote:
On Thursday 28 March 2013, Ley Foon Tan wrote:
We will working on generic ABI for kernel and Glibc. This might
take
some times.
On Thu, Mar 28, 2013 at 9:18 PM, Namhyung Kim namhy...@kernel.org wrote:
On Thu, Mar 28, 2013 at 04:58:30PM -0700, Sukadev Bhattiprolu wrote:
Roberto Vitillo [raviti...@lbl.gov] wrote:
| The proposed patch adds the convert tool to perf which allows to convert a
| perf.data file to a set of
On 03/28/2013 09:41 PM, Rob Landley wrote:
You don't need a new glibc port, you need a new klibc or musl port.
http://www.openwall.com/lists/musl/2012/07/08/1
Way less work than getting glibc working for your basic smoketest...
Good point. Average time to port klibc to a new
Linus,
I tried to send the mail to 'Ben Dooks b...@simtec.co.uk' but the address
is dead now.
I assume you've tested it in practice?
Yes, I'm running the modified code both in bootloader and Linux kernel on
my board.
Thanks,
Max
Signed-off-by: Max Nekludov max.neklu...@us.elster.com
---
Michal Hocko mho...@suse.cz writes:
On Tue 26-03-13 16:59:40, Aneesh Kumar K.V wrote:
Naoya Horiguchi n-horigu...@ah.jp.nec.com writes:
[...]
diff --git v3.9-rc3.orig/mm/memory-failure.c v3.9-rc3/mm/memory-failure.c
index df0694c..4e01082 100644
--- v3.9-rc3.orig/mm/memory-failure.c
Naoya Horiguchi wrote:
On Thu, Mar 28, 2013 at 09:03:16PM +0400, Konstantin Khlebnikov wrote:
Naoya Horiguchi wrote:
Currently we fail to include any data on hugepages into coredump,
because VM_DONTDUMP is set on hugetlbfs's vma. This behavior was recently
introduced by commit 314e51b98 mm:
Dear RT Folks,
I'm pleased to announce the 3.4.37-rt51 stable release.
This release is just an update to the new stable 3.4.37 version
and no RT specific changes have been made.
You can get this release via the git tree at:
commit 84a9a8cd9d0aa93c17e5815ab8a9cc4c0a765c63 changed the sense key
used for returning task registers, but HDIO_DRIVE_CMD ioctl was
not changed accordingly.
Tested: check that SMART ENABLE sent using HDIO_DRIVE_CMD returns 0
instead of EIO.
Signed-off-by: Gwendal Grignou gwen...@google.com
---
Please ignore this patchset. It's not based on the right kernel
version..
On 2013/3/28 12:11, Li Zefan wrote:
- This patchset splits cpuacct out of core scheduler code.
- Plus two small optimizations.
0001-sched-Split-cpuacct-code-out-of-core.c.patch
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 gang.c...@asianux.com
---
include/linux/filter.h |3 +++
1 files changed, 3 insertions(+),
On Wednesday 27 March 2013 06:30 PM, Linus Walleij wrote:
On Thu, Mar 21, 2013 at 3:30 PM, Laxman Dewangan ldewan...@nvidia.com wrote:
+#ifdef CONFIG_OF
+static struct of_device_id of_palmas_gpio_match[] = {
+ { .compatible = ti,palmas-gpio},
+ { },
+};
+MODULE_DEVICE_TABLE(of,
On Wed, Mar 27, 2013 at 10:52 PM, Rajagopal Venkat
rajagopal.ven...@linaro.org wrote:
Fix compiler warnings generated when devfreq is not enabled
(CONFIG_PM_DEVFREQ is not set).
Signed-off-by: Rajagopal Venkat rajagopal.ven...@linaro.org
Thanks!
Acked-by: MyungJoo Ham
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 ldewan...@nvidia.com wrote:
#ifdef CONFIG_OF_GPIO
- palmas_gpio-gpio_chip.of_node = palmas-dev-of_node;
+
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
This patch adds pinctrl nodes to the VIA VT8500 and Wondermedia SoC dtsi
files to support the pinctrl driver.
Signed-off-by: Tony Prisk li...@prisktech.co.nz
---
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 li...@prisktech.co.nz
---
arch/arm/boot/dts/vt8500.dtsi |7 ---
arch/arm/boot/dts/wm8505.dtsi |7 ---
arch/arm/boot/dts/wm8650.dtsi
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 li...@prisktech.co.nz
---
drivers/of/base.c | 33 +
include/linux/of.h |9
With the move to a combined pinctrl/gpio driver, the arch-vt8500
gpio driver is no longer required.
Signed-off-by: Tony Prisk li...@prisktech.co.nz
---
.../devicetree/bindings/gpio/gpio-vt8500.txt | 24 --
drivers/gpio/Kconfig |6 -
drivers/gpio/Makefile
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 li...@prisktech.co.nz
---
arch/arm/Kconfig |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git
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 lkund...@v3.sk
Tested-by: Stephen Warren swar...@wwwdotorg.org
Cc: Stephen Warren swar...@wwwdotorg.org
Cc:
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 pebo...@tiscali.nl
---
0) I
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 lkund...@v3.sk
A commit description would be useful.
arch/arm/boot/dts/bcm2835.dtsi |5 +
arch/arm/configs/bcm2835_defconfig |3 +-
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 swar...@wwwdotorg.org
---
Note: This depends on the proposed patch of: Add support for reading
a u32 from a multi-value
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 axel@ingics.com
---
drivers/iommu/exynos-iommu.c |2 +-
1 file changed, 1
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 popcorn...@gmail.com
Signed-off-by: Lubomir Rintel lkund...@v3.sk
Tested-by: Stephen Warren swar...@wwwdotorg.org
Cc: Herbert Xu
Instead of using legacy suspend/resume methods, using newer dev_pm_ops
structure allows better control over power management.
Signed-off-by: Jingoo Han jg1@samsung.com
---
drivers/video/backlight/omap1_bl.c | 22 ++
1 files changed, 10 insertions(+), 12 deletions(-)
Instead of using legacy suspend/resume methods, using newer dev_pm_ops
structure allows better control over power management.
Signed-off-by: Jingoo Han jg1@samsung.com
---
drivers/video/backlight/tosa_bl.c | 18 --
drivers/video/backlight/tosa_lcd.c | 18
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 jg1@samsung.com
---
drivers/video/backlight/ili9320.c | 24
From b2277a4e655c0858da7d85b99f0925abeedc3b6c Mon Sep 17 00:00:00 2001
From: Tejun Heo t...@kernel.org
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
From b37c3e3a74346749f0278c349dc0857107cb4370 Mon Sep 17 00:00:00 2001
From: Tejun Heo t...@kernel.org
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
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 majordomo
Doug Anderson diand...@chromium.org wrote:
Hi,
On Wed, Mar 27, 2013 at 11:40 AM, Lars-Peter Clausen l...@metafoo.de
wrote:
On 03/27/2013 07:35 PM, Naveen Krishna Ch wrote:
On 13 March 2013 13:39, Doug Anderson diand...@chromium.org wrote:
The exynos ADC won't work without a regulator called
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:
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¨
Hi Chanwoo,
On 28 March 2013 04:51, Chanwoo Choi cw00.c...@samsung.com 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
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
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 t...@kernel.org
---
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 us
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
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 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
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, 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
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, 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
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:
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.
On Wed, Mar 27, 2013 at 9:02 PM, Paolo Pisati
paolo.pis...@canonical.com 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]
On Mon, Feb 25, 2013 at 10:52 PM, Guennadi Liakhovetski
g.liakhovet...@gmx.de 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
Use kmemdup instead of kzalloc and memcpy.
Signed-off-by: Alexandru Gheorghiu gheorghiuan...@gmail.com
---
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
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
This is a preparation, so later we can initialize cpuacct earlier.
Signed-off-by: Li Zefan lize...@huawei.com
---
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 lize...@huawei.com
---
kernel/sched/core.c| 2 --
kernel/sched/cpuacct.c | 11 ---
kernel/sched/cpuacct.h | 5 -
3 files changed, 4 insertions(+), 14
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 mho...@suse.cz 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 lize...@huawei.com
---
kernel/sched/cpuacct.c | 6 --
1 file changed, 6 deletions(-)
diff --git
The only user was cpuacct.
Signed-off-by: Li Zefan lize...@huawei.com
---
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
+++
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 lize...@huawei.com
---
kernel/sched/cpuacct.c | 11 ++-
1 file changed, 6 insertions(+), 5 deletions(-)
diff
2013/3/28, Alexandru Gheorghiu gheorghiuan...@gmail.com:
Use kmemdup instead of kzalloc and memcpy.
Signed-off-by: Alexandru Gheorghiu gheorghiuan...@gmail.com
Looks good to me.
Acked-by: Namjae Jeon namjae.j...@samsung.com
Thanks~
--
To unsubscribe from this list: send the line unsubscribe
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 mugunthan...@ti.com
---
Changes from Initial version
* Updated
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
On 28 March 2013 04:07, Jacob Shin jacob.s...@amd.com 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 dmitry.torok...@gmail.com
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
* Frederic Weisbecker fweis...@gmail.com 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.,
* Frederic Weisbecker fweis...@gmail.com 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
On Wed, Mar 27, 2013 at 3:56 PM, Bjorn Helgaas bhelg...@google.com 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
On 28 March 2013 04:16, Jacob Shin jacob.s...@amd.com wrote:
diff --git a/drivers/cpufreq/amd_freq_sensitivity.c
b/drivers/cpufreq/amd_freq_sensitivity.c
+#include linux/module.h
+
+#include cpufreq_governor.h
These two are enough for you?
+#define PROC_FEEDBACK_INTERFACE_SHIFT
Hi Andrew,
2013/3/27 Andrew Morton a...@linux-foundation.org:
On Wed, 20 Mar 2013 11:52:45 +0100 Philipp Zabel p.za...@pengutronix.de
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
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 future?
* Frederic Weisbecker fweis...@gmail.com 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
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.
---
From
- Original Message -
From: Dave Jones da...@redhat.com
To: CAI Qian caiq...@redhat.com
Cc: Christoph Lameter c...@linux.com, David Rientjes
rient...@google.com, linux-mm linux...@kvack.org,
linux-kernel@vger.kernel.org, Oleg Nesterov o...@redhat.com
Sent: Wednesday, March 27, 2013
Remove one division operation in find_buiest_queue().
Signed-off-by: Joonsoo Kim iamjoonsoo@lge.com
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
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
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.
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
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
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
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:
The OPP library support is needed for exynos5440 cpu frequency
dynamic scaling driver.
Signed-off-by: Amit Daniel Kachhap amit.dan...@samsung.com
---
arch/arm/mach-exynos/Kconfig |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/arch/arm/mach-exynos/Kconfig
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
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
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 amit.dan...@samsung.com
---
On Thu, Mar 28, 2013 at 08:36:52AM +0100, Sebastien Royen wrote:
Hi Dmitry
2013/3/28 Dmitry Torokhov dmitry.torok...@gmail.com
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
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 gre...@linuxfoundation.org
Cc: Eric W. Biederman ebied...@xmission.com
Cc: Vivek Goyal vgo...@redhat.com
Signed-off-by: Zhang Yanfei
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
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
2013/3/27 Fabio Coatti fabio.coa...@gmail.com:
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.
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 users to
On 28 March 2013 13:35, Amit Daniel Kachhap amit.dan...@samsung.com 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
801 - 900 of 1168 matches
Mail list logo
