[PATCH]smp: Fix send func call IPI to empty cpu mask

I get below warning every day with 3.7, one or two times per day. [ 2235.186027] WARNING: at /mnt/sda7/kernel/linux/arch/x86/kernel/apic/ipi.c:109 default_send_IPI_mask_logical+0x2f/0xb8() [ 2235.186030] Hardware name: Aspire 4741 [ 2235.186032] empty IPI mask [ 2235.186034] Modules linked in:

[patch] edac: test correct variable in ->store function

We're testing for ->show but calling ->store(). Signed-off-by: Dan Carpenter diff --git a/drivers/edac/edac_pci_sysfs.c b/drivers/edac/edac_pci_sysfs.c index 7684426..e8658e4 100644 --- a/drivers/edac/edac_pci_sysfs.c +++ b/drivers/edac/edac_pci_sysfs.c @@ -256,7 +256,7 @@ static ssize_t

Re: Bug#695182: [PATCH] Subtract min_free_kbytes from dirtyable memory

Hi Paul, Ben Hutchings wrote: > If you can identify where it was fixed then your patch for older > versions should go to stable with a reference to the upstream fix (see > Documentation/stable_kernel_rules.txt). How about this patch? It was applied in mainline during the 3.3 merge window, so

Re: [PATCH 1/2] spi: spi-gpio: Add checks for the dt properties

On Fri, Jan 25, 2013 at 09:39:34AM +0100, Maxime Ripard wrote: > The bindings assumed that the gpios properties were always there, which > made the NO_TX and NO_RX mode not usable from device tree. Add extra > checks to make sure that the driver can work if either MOSI or MISO is > not used.

Re: [PATCH] regulators/db8500: Fix compile failure for drivers/regulator/dbx500-prcmu.c

On Thu, Jan 24, 2013 at 10:29:26AM -0500, Steven Rostedt wrote: > Building for the snowball board, I ran into this compile failure: Applied, thanks. Please use subject lines appropriate for the subsystem (I see I let the original one through). signature.asc Description: Digital signature

Re: [PATCH v3 04/10] spi/pxa2xx: convert to the common clk framework

On Tue, Jan 22, 2013 at 12:26:27PM +0200, Mika Westerberg wrote: > Convert clk_enable() to clk_prepare_enable() and clk_disable() to > clk_disable_unprepare() respectively in order to support the common clk > framework. Otherwise we get warnings on the console as the clock is not > prepared before

Re: [PATCH v3 03/10] spi/pxa2xx: convert to the pump message infrastructure

On Tue, Jan 22, 2013 at 12:26:26PM +0200, Mika Westerberg wrote: > The SPI core provides infrastructure for standard message queueing so use > that instead of handling everything in the driver. This simplifies the > driver. Applied, thanks. signature.asc Description: Digital signature

Re: [PATCH v3 02/10] spi/pxa2xx: fix warnings when compiling a 64-bit kernel

On Tue, Jan 22, 2013 at 12:26:25PM +0200, Mika Westerberg wrote: > Fix following warnings seen when compiling 64-bit: Applied, thanks. signature.asc Description: Digital signature

Re: [PATCH v3 01/10] spi/pxa2xx: allow building on a 64-bit kernel

On Tue, Jan 22, 2013 at 12:26:24PM +0200, Mika Westerberg wrote: > We are going to use it on 64-bit kernel on Intel Lynxpoint so make sure we > can build it into such kernel. Applied, thanks. signature.asc Description: Digital signature

Re: [PATCH -v4 0/5] x86,smp: make ticket spinlock proportional backoff w/ auto tuning

On Fri, 2013-01-25 at 14:05 -0500, Rik van Riel wrote: > The performance issue observed with AIM7 is still a mystery. Hm. AIM7 mystery _may_ be the same crud I see on a 4 node 40 core box. Stock scheduler knobs are too preempt happy, produce unstable results. I twiddle them as below to

Re: [PATCH RESEND] ARM: dts: max77686: Add DTS file for max77686 PMIC

Hello Mark, Yes, this is not ARM-specific chip at all. Just wanted to be reviewed by you and others if the format is ok before integrating to my board file. I had sent similar one before, https://patchwork.kernel.org/patch/1287711, and you advised that was too board specific. And plan to

[RFC PATCH 2/4] lib: add support for LZ4-compressed kernels

This patch adds support for extracting LZ4-compressed kernel images, as well as LZ4-compressed ramdisk images in the kernel boot process. This depends on the patch below decompressors: add lz4 decompressor module Signed-off-by: Kyungsik Lee --- include/linux/decompress/unlz4.h | 10 ++

[RFC PATCH 3/4] arm: add support for LZ4-compressed kernels

This patch integrates the LZ4 decompression code to the arm pre-boot code. And it depends on two patchs below lib: add support for LZ4-compressed kernels decompressors: add lz4 decompressor module Signed-off-by: Kyungsik Lee --- arch/arm/Kconfig | 1 +

[RFC PATCH 1/4] decompressors: add lz4 decompressor module

This patch adds support for LZ4 decompression in the kernel. LZ4 Decompression APIs for kernel are based on LZ4 implementation by Yann Collet. LZ4 homepage : http://fastcompression.blogspot.com/p/lz4.html LZ4 source repository : http://code.google.com/p/lz4/ Signed-off-by: Kyungsik Lee ---

[RFC PATCH 4/4] x86: add support for LZ4-compressed kernels

This patch integrates the LZ4 decompression code to the x86 pre-boot code. And it depends on two patchs below lib: add support for LZ4-compressed kernels decompressors: add lz4 decompressor module Signed-off-by: Kyungsik Lee --- arch/x86/Kconfig | 1 +

Re: [PATCHv2] ARM: mxs: dt: Add Crystalfontz CFA-10037 device tree support

On Fri, Jan 25, 2013 at 10:00:35AM +0100, Maxime Ripard wrote: > The CFA-10037 is another expansion board for the CFA-10036 module, with > only a USB Host, a Ethernet device and a lot of gpios. > > Signed-off-by: Maxime Ripard Applied, thanks. -- To unsubscribe from this list: send the line

Re: [PATCH v2 1/3] pwm: Add pwm_cansleep() as exported API to users

On Fri, Jan 25, 2013 at 02:44:29PM +0100, Florian Vaussard wrote: > Calls to some external PWM chips can sleep. To help users, > add pwm_cansleep() API. > > Signed-off-by: Florian Vaussard > --- > drivers/pwm/core.c | 12 > include/linux/pwm.h | 10 ++ > 2 files

[PATCH] regulator: lp8755: Use LP8755_BUCK_MAX instead of magic number

Signed-off-by: Axel Lin --- drivers/regulator/lp8755.c |6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/regulator/lp8755.c b/drivers/regulator/lp8755.c index 8b1ce0f..f0f6ea0 100644 --- a/drivers/regulator/lp8755.c +++ b/drivers/regulator/lp8755.c @@ -373,7

[PATCH] mmc: fix to refer NULL pointer

Check whether host->sdio_irq_thread is NULL before wake_up_process() is called about host->sdio_irq_thread. Signed-off-by: Joonyoung Shim --- Currently the kernel panic to refer NULL pointer about host->sdio_irq_thread are occuring at the trats board using Samsung SDHCI driver.

Re: [PATCH 5/6] ARM: regulator: add tps6507x device tree data

On Fri, Jan 25, 2013 at 06:29:49AM +, Vishwanathrao Badarkhe, Manish wrote: > On Thu, Jan 24, 2013 at 17:30:51, Mark Brown wrote: > I too doubt that whether it should be in architecture specific folder, > My code is in reference to below patch: > arm/dts: regulator: Add tps65910 device tree

Re: [PATCH RESEND] ARM: dts: max77686: Add DTS file for max77686 PMIC

On Fri, Jan 25, 2013 at 03:46:08AM +0900, Dongjin Kim wrote: > --- > arch/arm/boot/dts/max77686.dtsi | 156 > +++ Why is this in arch/arm? This isn't an ARM-specific chip. signature.asc Description: Digital signature

[PATCH v2] mm: clean up soft_offline_page()

Currently soft_offline_page() is hard to maintain because it has many return points and goto statements. All of this mess come from get_any_page(). This function should only get page refcount as the name implies, but it does some page isolating actions like SetPageHWPoison() and dequeuing

Re: [PATCH 1/2] i2c-core: Add gpio based bus arbitration implementation

On Thu, Jan 24, 2013 at 12:39:48PM +0100, Wolfram Sang wrote: > On Thu, Jan 24, 2013 at 07:18:47PM +0800, Mark Brown wrote: > > A read is typically implemented as a write of the register address > > followed by a read of the value, usually with the ability to free the > > bus in between. If two

Re: [PATCH 11/19] regmap: avoid undefined return from regmap_read_debugfs

On Sat, Jan 26, 2013 at 12:42:26PM +0800, Mark Brown wrote: > On Fri, Jan 25, 2013 at 02:14:28PM +, Arnd Bergmann wrote: > > Gcc warns about the case where regmap_read_debugfs tries > Are you sure about that function name? > > to walk an empty map->debugfs_off_cache list, which results > >

Re: [PATCH 11/19] regmap: avoid undefined return from regmap_read_debugfs

On Fri, Jan 25, 2013 at 02:14:28PM +, Arnd Bergmann wrote: > Gcc warns about the case where regmap_read_debugfs tries Are you sure about that function name? > to walk an empty map->debugfs_off_cache list, which results > in uninitialized variable getting returned. > Setting this variable to

Re: [PATCH 1/2] media: add support for decoder subdevs along with sensor and others

Hi Sylwester, On Sat, Jan 26, 2013 at 1:24 AM, Sylwester Nawrocki wrote: > Hi Prahakar, > > > On 01/25/2013 08:01 AM, Prabhakar Lad wrote: >> >> From: Manjunath Hadli >> >> A lot of SOCs including Texas Instruments Davinci family mainly use >> video decoders as input devices. Here the initial

Re: [PATCH v5 7/8] fat (exportfs): rebuild directory-inode if fat_dget() fails

Namjae Jeon writes: > 2013/1/20, OGAWA Hirofumi : >> Namjae Jeon writes: >> >>> We rewrite patch as your suggestion using dummy inode. Would please >>> you review below patch code ? >> >> Looks like good as initial. Clean and shorter. >> >> Next is, we have to think about race. I.e. if real

Re: [PATCH] Negative (setpoint-dirty) in bdi_position_ratio()

Dear Fengguang (et al), > There are 260MB reclaimable slab pages in the normal zone, however we > somehow failed to reclaim them. ... Could the problem be that without CONFIG_NUMA, zone_reclaim_mode stays at zero and anyway zone_reclaim() does nothing in include/linux/swap.h ? Though... there

Re: [PATCH 1/2]linux-usb:Define a new macro for USB storage match rules

On Fri, Jan 25, 2013 at 07:10:29PM -0800, Matthew Dharm wrote: > I suggest one of two options: > > 1) Setup an alternative mail client. There are many to choose from > which will not damage your patches. I personally like 'mutt' (which > you should be able to install on your linux machine).

Re: Bug#695182: [PATCH] Subtract min_free_kbytes from dirtyable memory

On Sat, 2013-01-26 at 14:07 +1100, paul.sz...@sydney.edu.au wrote: > Dear Ben, > > > ... the mm maintainers are probably much better placed ... > > Exactly. Now I wonder: are you one of them? Hah, no. Ben. -- Ben Hutchings Any smoothly functioning technology is indistinguishable from a

Re: [PATCH 1/2]linux-usb:Define a new macro for USB storage match rules

On Fri, Jan 25, 2013 at 6:05 PM, Greg KH wrote: > On Sat, Jan 26, 2013 at 01:39:50AM +, Fangxiaozhi (Franko) wrote: >> >> >> > -Original Message- >> > From: Greg KH [mailto:g...@kroah.com] >> > Sent: Saturday, January 26, 2013 1:45 AM >> > To: Fangxiaozhi (Franko) >> > Cc: Sergei

Re: Bug#695182: [PATCH] Subtract min_free_kbytes from dirtyable memory

Dear Ben, > ... the mm maintainers are probably much better placed ... Exactly. Now I wonder: are you one of them? Thanks, Paul Paul Szabo p...@maths.usyd.edu.au http://www.maths.usyd.edu.au/u/psz/ School of Mathematics and Statistics University of SydneyAustralia -- To unsubscribe

Re: Bug#695182: [PATCH] Subtract min_free_kbytes from dirtyable memory

-- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

Re: [PATCH] extcon: arizona: Use regulated mode for microphone supply when detecting

On 01/25/2013 06:16 PM, Mark Brown wrote: When starting microphone detection some headsets should be exposed to the fully regulated microphone bias in order to ensure that they behave in an optimal fashion. Signed-off-by: Mark Brown --- drivers/extcon/Kconfig |2 +-

Re: [PATCH v2] userns: improve uid/gid map collision detection

Aristeu Rozanski writes: > On Thu, Jan 24, 2013 at 04:46:12PM -0800, Andrew Morton wrote: >> eek, a macro! Macros are always bad. >> >> This one is bad because >> >> a) it's a macro >> >> b) it evaluates its args multiple times and hence will cause nasty >>bugs if called with

[PATCH review 6/6] userns: Allow the userns root to mount tmpfs.

There is no backing store to tmpfs and file creation rules are the same as for any other filesystem so it is semantically safe to allow unprivileged users to mount it. ramfs is safe for the same reasons so allow either flavor of tmpfs to be mounted by a user namespace root user. The memory

[PATCH review 5/6] userns: Allow the userns root to mount ramfs.

There is no backing store to ramfs and file creation rules are the same as for any other filesystem so it is semantically safe to allow unprivileged users to mount it. The memory control group successfully limits how much memory ramfs can consume on any system that cares about a user namespace

[PATCH review 4/6] userns: Allow the userns root to mount of devpts

- The context in which devpts is mounted has no effect on the creation of ptys as the /dev/ptmx interface has been used by unprivileged users for many years. - Only support unprivileged mounts in combination with the newinstance option to ensure that mounting of /dev/pts in a user

[PATCH review 3/6] userns: Recommend use of memory control groups.

In the help text describing user namespaces recommend use of memory control groups. In many cases memory control groups are the only mechanism there is to limit how much memory a user who can create user namespaces can use. Signed-off-by: "Eric W. Biederman" ---

[PATCH review 2/6] userns: Allow any uid or gid mappings that don't overlap.

When I initially wrote the code for /proc//uid_map. I was lazy and avoided duplicate mappings by the simple expedient of ensuring the first number in a new extent was greater than any number in the previous extent. Unfortunately that precludes a number of valid mappings, and someone noticed and

[PATCH review 1/6] userns: Avoid recursion in put_user_ns

When freeing a deeply nested user namespace free_user_ns calls put_user_ns on it's parent which may in turn call free_user_ns again. When -fno-optimize-sibling-calls is passed to gcc one stack frame per user namespace is left on the stack, potentially overflowing the kernel stack.

[PATCH review 0/6] miscelaneous user namespace patches

Now that I have done my worst to infect user space with some basic tools for using user namespaces, this is my first round of patches aimed at the 3.9 merge window. This documents that if you care about limit resources you want to configure the memory control group when user namespaces are

[PATCH 11/11] ksm: stop hotremove lockdep warning

Complaints are rare, but lockdep still does not understand the way ksm_memory_callback(MEM_GOING_OFFLINE) takes ksm_thread_mutex, and holds it until the ksm_memory_callback(MEM_OFFLINE): that appears to be a problem because notifier callbacks are made under down_read of

[PATCH 10/11] mm: remove offlining arg to migrate_pages

No functional change, but the only purpose of the offlining argument to migrate_pages() etc, was to ensure that __unmap_and_move() could migrate a KSM page for memory hotremove (which took ksm_thread_mutex) but not for other callers. Now all cases are safe, remove the arg. Signed-off-by: Hugh

[PATCH 9/11] ksm: enable KSM page migration

Migration of KSM pages is now safe: remove the PageKsm restrictions from mempolicy.c and migrate.c. But keep PageKsm out of __unmap_and_move()'s anon_vma contortions, which are irrelevant to KSM: it looks as if that code was preventing hotremove migration of KSM pages, unless they happened to be

[PATCH 8/11] ksm: make !merge_across_nodes migration safe

The new KSM NUMA merge_across_nodes knob introduces a problem, when it's set to non-default 0: if a KSM page is migrated to a different NUMA node, how do we migrate its stable node to the right tree? And what if that collides with an existing stable node? ksm_migrate_page() can do no more than

Re: [PATCH 1/2]linux-usb:Define a new macro for USB storage match rules

On Sat, Jan 26, 2013 at 01:39:50AM +, Fangxiaozhi (Franko) wrote: > > > > -Original Message- > > From: Greg KH [mailto:g...@kroah.com] > > Sent: Saturday, January 26, 2013 1:45 AM > > To: Fangxiaozhi (Franko) > > Cc: Sergei Shtylyov; linux-...@vger.kernel.org; > >

[PATCH 7/11] ksm: make KSM page migration possible

KSM page migration is already supported in the case of memory hotremove, which takes the ksm_thread_mutex across all its migrations to keep life simple. But the new KSM NUMA merge_across_nodes knob introduces a problem, when it's set to non-default 0: if a KSM page is migrated to a different NUMA

[PATCH 6/11] ksm: remove old stable nodes more thoroughly

Switching merge_across_nodes after running KSM is liable to oops on stale nodes still left over from the previous stable tree. It's not something that people will often want to do, but it would be lame to demand a reboot when they're trying to determine which merge_across_nodes setting is best.

[PATCH 5/11] ksm: get_ksm_page locked

In some places where get_ksm_page() is used, we need the page to be locked. When KSM migration is fully enabled, we shall want that to make sure that the page just acquired cannot be migrated beneath us (raised page count is only effective when there is serialization to make sure migration

[PATCH 4/11] ksm: reorganize ksm_check_stable_tree

Memory hotremove's ksm_check_stable_tree() is pitifully inefficient (restarting whenever it finds a stale node to remove), but rearrange so that at least it does not needlessly restart from nid 0 each time. And add a couple of comments: here is why we keep pfn instead of page. Signed-off-by: Hugh

[PATCH 3/11] ksm: trivial tidyups

Add NUMA() and DO_NUMA() macros to minimize blight of #ifdef CONFIG_NUMAs (but indeed we don't want to expand struct rmap_item by nid when not NUMA). Add comment, remove "unsigned" from rmap_item->nid, as "int nid" elsewhere. Define ksm_merge_across_nodes 1U when #ifndef NUMA to help optimizing

[PATCH 2/11] ksm: add sysfs ABI Documentation

From: Petr Holasek This patch adds sysfs documentation for Kernel Samepage Merging (KSM) including new merge_across_nodes knob. Signed-off-by: Petr Holasek Signed-off-by: Hugh Dickins --- Documentation/ABI/testing/sysfs-kernel-mm-ksm | 52 1 file changed, 52 insertions(+)

[tip:x86/mm] x86, kvm: Fix kvm's use of __pa() on percpu areas

Commit-ID: 5dfd486c4750c9278c63fa96e6e85bdd2fb58e9d Gitweb: http://git.kernel.org/tip/5dfd486c4750c9278c63fa96e6e85bdd2fb58e9d Author: Dave Hansen AuthorDate: Tue, 22 Jan 2013 13:24:35 -0800 Committer: H. Peter Anvin CommitDate: Fri, 25 Jan 2013 16:34:55 -0800 x86, kvm: Fix kvm's use

[tip:x86/mm] x86, mm: Create slow_virt_to_phys()

Commit-ID: d765653445129b7c476758040e3079480775f80a Gitweb: http://git.kernel.org/tip/d765653445129b7c476758040e3079480775f80a Author: Dave Hansen AuthorDate: Tue, 22 Jan 2013 13:24:33 -0800 Committer: H. Peter Anvin CommitDate: Fri, 25 Jan 2013 16:33:23 -0800 x86, mm: Create

[PATCH 1/11] ksm: allow trees per NUMA node

From: Petr Holasek Introduces new sysfs boolean knob /sys/kernel/mm/ksm/merge_across_nodes which control merging pages across different numa nodes. When it is set to zero only pages from the same node are merged, otherwise pages from all nodes can be merged together (default behavior). Typical

[tip:x86/mm] x86, mm: Use new pagetable helpers in try_preserve_large_page()

Commit-ID: f3c4fbb68e93b10c781c0cc462a9d80770244da6 Gitweb: http://git.kernel.org/tip/f3c4fbb68e93b10c781c0cc462a9d80770244da6 Author: Dave Hansen AuthorDate: Tue, 22 Jan 2013 13:24:32 -0800 Committer: H. Peter Anvin CommitDate: Fri, 25 Jan 2013 16:33:23 -0800 x86, mm: Use new

[PATCH 0/11] ksm: NUMA trees and page migration

Here's a KSM series, based on mmotm 2013-01-23-17-04: starting with Petr's v7 "KSM: numa awareness sysfs knob"; then fixing the two issues we had with that, fully enabling KSM page migration on the way. (A different kind of KSM/NUMA issue which I've certainly not begun to address here: when KSM

[tip:x86/mm] x86, mm: Pagetable level size/shift/mask helpers

Commit-ID: 4cbeb51b860c57ba8b2ae50c4016ee7a41f5fbd5 Gitweb: http://git.kernel.org/tip/4cbeb51b860c57ba8b2ae50c4016ee7a41f5fbd5 Author: Dave Hansen AuthorDate: Tue, 22 Jan 2013 13:24:31 -0800 Committer: H. Peter Anvin CommitDate: Fri, 25 Jan 2013 16:33:22 -0800 x86, mm: Pagetable level

[PATCH 1/1] Drivers: scsi: storvsc: Initialize the sglist

Properly initialize scatterlist before using it. Signed-off-by: K. Y. Srinivasan Cc: sta...@vger.kernel.org --- drivers/scsi/storvsc_drv.c |1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/drivers/scsi/storvsc_drv.c b/drivers/scsi/storvsc_drv.c index 270b3cf..5ada1d0

[tip:x86/mm] x86, mm: Make DEBUG_VIRTUAL work earlier in boot

Commit-ID: a25b9316841c5afa226f8f70a457861b35276a92 Gitweb: http://git.kernel.org/tip/a25b9316841c5afa226f8f70a457861b35276a92 Author: Dave Hansen AuthorDate: Tue, 22 Jan 2013 13:24:30 -0800 Committer: H. Peter Anvin CommitDate: Fri, 25 Jan 2013 16:33:22 -0800 x86, mm: Make

[RFC patch v2 7/7] sched: consider runnable load average in effective_load

effective_load calculates the load change as seen from the root_task_group. It needs to engage the runnable average of changed task. Thanks for Morten Rasmussen's reminder of this. Signed-off-by: Alex Shi --- kernel/sched/fair.c | 27 --- 1 file changed, 20

[RFC patch v2 1/7] sched: give initial value for runnable avg of sched entities.

We need initialize the se.avg.{decay_count, load_avg_contrib} to zero after a new task forked. Otherwise random values of above variables cause mess when do new task enqueue: enqueue_task_fair enqueue_entity enqueue_entity_load_avg Signed-off-by: Alex Shi ---

[RFC patch v2 5/7] sched: compute runnable load avg in cpu_load and cpu_avg_load_per_task

They are the base values in load balance, update them with rq runnable load average, then the load balance will consider runnable load avg naturally. Signed-off-by: Alex Shi --- kernel/sched/core.c | 4 ++-- kernel/sched/fair.c | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff

[RFC patch v2 6/7] sched: consider runnable load average in move_tasks

Except using runnable load average in background, move_tasks is also the key functions in load balance. We need consider the runnable load average in it in order to the apple to apple load comparison. Signed-off-by: Alex Shi --- kernel/sched/fair.c | 11 ++- 1 file changed, 10

[RFC patch v2 2/7] sched: set initial load avg of new forked task

New task has no runnable sum at its first runnable time, so its runnable load is zero. That makes burst forking balancing just select few idle cpus to assign tasks if we engage runnable load in balancing. Set initial load avg of new forked task as its load weight to resolve this issue.

[RFC patch v2 3/7] Revert "sched: Introduce temporary FAIR_GROUP_SCHED dependency for load-tracking"

Remove CONFIG_FAIR_GROUP_SCHED that covers the runnable info, then we can use runnable load variables. Signed-off-by: Alex Shi --- include/linux/sched.h | 8 +--- kernel/sched/core.c | 7 +-- kernel/sched/fair.c | 13 ++--- kernel/sched/sched.h | 9 + 4 files

[RFC patch v2 4/7] sched: update cpu load after task_tick.

To get the latest runnable info, we need do this cpuload update after task_tick. Signed-off-by: Alex Shi --- kernel/sched/core.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/kernel/sched/core.c b/kernel/sched/core.c index dbab4b3..4f4714e 100644 --- a/kernel/sched/core.c

[RFC patch v2] sched: use runnable load avg in cfs balance instead of instant load

This patchset can be used, but causes burst waking benchmark aim9 drop 5~7% on my 2 sockets machine. The reason is too light runnable load in early stage of waked tasks causes imbalance in balancing. So, it is immature and just a reference for guys who want to go gurther. V2 change: 1, attached

Re: [RFC] ACPI scan handlers

On Friday, January 25, 2013 04:07:38 PM Toshi Kani wrote: > On Fri, 2013-01-25 at 23:11 +0100, Rafael J. Wysocki wrote: > > On Friday, January 25, 2013 09:52:21 AM Toshi Kani wrote: > > > On Thu, 2013-01-24 at 01:26 +0100, Rafael J. Wysocki wrote: > : > > > > > > > > I wonder if anyone is seeing

RE: [PATCH 1/2]linux-usb:Define a new macro for USB storage match rules

> -Original Message- > From: Greg KH [mailto:g...@kroah.com] > Sent: Saturday, January 26, 2013 1:45 AM > To: Fangxiaozhi (Franko) > Cc: Sergei Shtylyov; linux-...@vger.kernel.org; linux-kernel@vger.kernel.org; > Xueguiying (Zihan); Linlei (Lei Lin); Yili (Neil); Wangyuhua (Roger,

[PATCH 09/14] dlm: use idr_for_each_entry() in recover_idr_clear() error path

Convert recover_idr_clear() to use idr_for_each_entry() instead of idr_for_each(). It's somewhat less efficient this way but it shouldn't matter in an error path. This is to help with deprecation of idr_remove_all(). Only compile tested. Signed-off-by: Tejun Heo Cc: Christine Caulfield Cc:

[PATCH 10/14] dlm: don't use idr_remove_all()

idr_destroy() can destroy idr by itself and idr_remove_all() is being deprecated. The conversion isn't completely trivial for recover_idr_clear() as it's the only place in kernel which makes legitimate use of idr_remove_all() w/o idr_destroy(). Replace it with idr_remove() call inside

[PATCH 02/14] atm/nicstar: don't use idr_remove_all()

idr_destroy() can destroy idr by itself and idr_remove_all() is being deprecated. Drop its usage. Signed-off-by: Tejun Heo Cc: Chas Williams Cc: net...@vger.kernel.org --- This patch depends on an earlier idr patch and given the trivial nature of the patch, I think it would be best to route

[PATCHSET] idr: deprecate idr_remove_all()

Hello, (Andrew, I think this one is best routed through -mm. Please read on) idr is one of the areas with much higher concentration of bad interface and implementation decisions. This patchset removes one of those oddities - idr_remove_all(). idr needs two steps for destruction -

[PATCH 11/14] nfs: idr_destroy() no longer needs idr_remove_all()

idr_destroy() can destroy idr by itself and idr_remove_all() is being deprecated. Drop reference to idr_remove_all(). Note that the code wasn't completely correct before because idr_remove() on all entries doesn't necessarily release all idr_layers which could lead to memory leak.

[PATCH 13/14] cgroup: don't use idr_remove_all()

idr_destroy() can destroy idr by itself and idr_remove_all() is being deprecated. Drop its usage. Signed-off-by: Tejun Heo Cc: Li Zefan Cc: contain...@lists.linux-foundation.org Cc: cgro...@vger.kernel.org --- This patch depends on an earlier idr patch and given the trivial nature of the

[PATCH 14/14] idr: deprecate idr_remove_all()

There was only one legitimate use of idr_remove_all() and a lot more of incorrect uses (or lack of it). Now that idr_destroy() implies idr_remove_all() and all the in-kernel users updated not to use it, there's no reason to keep it around. Mark it deprecated so that we can later unexport it.

[PATCH 12/14] inotify: don't use idr_remove_all()

idr_destroy() can destroy idr by itself and idr_remove_all() is being deprecated. Drop its usage. Signed-off-by: Tejun Heo Cc: John McCutchan Cc: Robert Love Cc: Eric Paris --- This patch depends on an earlier idr patch and given the trivial nature of the patch, I think it would be best to

[PATCH 06/14] dm: don't use idr_remove_all()

idr_destroy() can destroy idr by itself and idr_remove_all() is being deprecated. Drop its usage. Signed-off-by: Tejun Heo Cc: Alasdair Kergon Cc: dm-de...@redhat.com --- This patch depends on an earlier idr patch and given the trivial nature of the patch, I think it would be best to route

[PATCH 08/14] rpmsg: don't use idr_remove_all()

idr_destroy() can destroy idr by itself and idr_remove_all() is being deprecated. Drop its usage. Signed-off-by: Tejun Heo Cc: Ohad Ben-Cohen --- This patch depends on an earlier idr patch and given the trivial nature of the patch, I think it would be best to route these together through -mm.

[PATCH 05/14] drm: don't use idr_remove_all()

idr_destroy() can destroy idr by itself and idr_remove_all() is being deprecated. Drop its usage. * drm_ctxbitmap_cleanup() was calling idr_remove_all() but forgetting idr_destroy() thus leaking all buffered free idr_layers. Replace it with idr_destroy(). Signed-off-by: Tejun Heo Cc:

[PATCH 03/14] block/loop: don't use idr_remove_all()

idr_destroy() can destroy idr by itself and idr_remove_all() is being deprecated. Drop its usage. Signed-off-by: Tejun Heo Cc: Jens Axboe --- This patch depends on an earlier idr patch and given the trivial nature of the patch, I think it would be best to route these together through -mm.

[PATCH 04/14] firewire: don't use idr_remove_all()

idr_destroy() can destroy idr by itself and idr_remove_all() is being deprecated. Drop its usage. Signed-off-by: Tejun Heo Cc: Stefan Richter Cc: linux1394-de...@lists.sourceforge.net --- This patch depends on an earlier idr patch and given the trivial nature of the patch, I think it would be

[PATCH 07/14] remoteproc: don't use idr_remove_all()

idr_destroy() can destroy idr by itself and idr_remove_all() is being deprecated. Drop its usage. Signed-off-by: Tejun Heo Cc: Ohad Ben-Cohen --- This patch depends on an earlier idr patch and given the trivial nature of the patch, I think it would be best to route these together through -mm.

[PATCH 01/14] idr: make idr_destroy() imply idr_remove_all()

idr is silly in quite a few ways, one of which is how it's supposed to be destroyed - idr_destroy() doesn't release IDs and doesn't even whine if the idr isn't empty. If the caller forgets idr_remove_all(), it simply leaks memory. Even ida gets this wrong and leaks memory on destruction. There

Re: [PATCH 3/3] acpi, memory-hotplug: Support getting hotplug info from SRAT.

On 01/25/2013 05:12 PM, Andrew Morton wrote: > On Fri, 25 Jan 2013 17:42:09 +0800 > Tang Chen wrote: > >> NOTE: Using this way will cause NUMA performance down because the whole node >> will be set as ZONE_MOVABLE, and kernel cannot use memory on it. >> If users don't want to lose

Re: [PATCH v10 00/11] PCI, ACPI: pci root bus hotplug support / pci match_driver

On 2013-1-26 8:04, Bjorn Helgaas wrote: > On Tue, Jan 22, 2013 at 3:19 PM, Yinghai Lu wrote: >> On Tue, Jan 22, 2013 at 2:09 PM, Rafael J. Wysocki wrote: >>> On Monday, January 21, 2013 01:20:41 PM Yinghai Lu wrote: It includes 1. preparing patches for pci root bus hotadd/hotremove

Re: [PATCH]cputime: make bool type for steal ticks

On Sat, 2013-01-26 at 01:45 +0100, Frederic Weisbecker wrote: > > diff --git a/kernel/sched/cputime.c b/kernel/sched/cputime.c [] > > @@ -282,7 +282,7 @@ static __always_inline bool > > steal_account_process_tick(void) [] > > - return st; > > + return !!st; > > I

[PATCH] checkpatch: Fix $Float creation of match variables

commit 74349bccedb ("checkpatch: add support for floating point constants") added an unnecessary match variable that caused tests that used a $Constant or $LvalOrFunc to have one too many matches. This causes problems with usleep_range, min/max and other extended tests. Avoid using match

Re: [PATCH 3/3] acpi, memory-hotplug: Support getting hotplug info from SRAT.

On Fri, 25 Jan 2013 17:42:09 +0800 Tang Chen wrote: > NOTE: Using this way will cause NUMA performance down because the whole node > will be set as ZONE_MOVABLE, and kernel cannot use memory on it. > If users don't want to lose NUMA performance, just don't use it. I agree with this,

Re: [PATCH v2 3/3] timekeeping: Add CONFIG_HAS_PERSISTENT_CLOCK option

On 01/22/2013 11:49 AM, John Stultz wrote: On 01/22/2013 11:44 AM, Jason Gunthorpe wrote: On Tue, Jan 15, 2013 at 11:50:18AM -0800, John Stultz wrote: On 01/15/2013 08:09 AM, Feng Tang wrote: Make the persistent clock check a kernel config option, so that some platform can explicitely select

Re: [tip:x86/asm] x86/xor: Make virtualization friendly

On 01/25/2013 02:15 PM, H. Peter Anvin wrote: On 01/25/2013 02:11 PM, H. Peter Anvin wrote: On 01/25/2013 02:43 AM, tip-bot for Jan Beulich wrote: Commit-ID: 05fbf4d6fc6a3c0c3e63b77979c9311596716d10 Gitweb: http://git.kernel.org/tip/05fbf4d6fc6a3c0c3e63b77979c9311596716d10 Author: Jan

[PATCH 1/2] PCI: introduce accessor to retrieve PCIe Capabilities Register

Provide an accessor to retrieve the PCI Express device's Capabilities Register. Signed-off-by: Myron Stowe --- include/linux/pci.h |9 + 1 files changed, 9 insertions(+), 0 deletions(-) diff --git a/include/linux/pci.h b/include/linux/pci.h index 15472d6..78581e1 100644 ---

[PATCH 2/2] PCI: Use PCI Express Capability accessors

Use PCI Express Capability access functions to simplify device Capabilities Register usages. Signed-off-by: Myron Stowe --- drivers/pci/access.c|4 ++-- drivers/pci/pcie/portdrv_core.c |2 +- include/linux/pci.h |2 +- 3 files changed, 4 insertions(+), 4

[PATCH 0/2] Extend interfaces to access PCIe capabilities registers

This series is a minor extension to Jiang Liu's recent efforts - [PATCH v3 00/32] provide interfaces to access PCIe capabilities registers - which adds an additional PCI Express accessor for obtaining a device's Capabilities Register. Reference: https://lkml.org/lkml/2012/8/1/253 --- Myron Stowe

Re: [PATCH 19/19] [INCOMPLETE] ARM: make return_address available for ARM_UNWIND

On Friday 25 January 2013, Dave Martin wrote: > On Fri, Jan 25, 2013 at 11:44:14AM -0500, Steven Rostedt wrote: > > [ I got an error with linux-arm-ker...@list.infradead.org and had to > > remove from CC ] > > Blame Arnd :) > Sorry about that, I now posted the entire series again with the right

Re: [PATCH]cputime: make bool type for steal ticks

2012/11/16 liguang : > Signed-off-by: liguang > --- > kernel/sched/cputime.c |2 +- > 1 files changed, 1 insertions(+), 1 deletions(-) > > diff --git a/kernel/sched/cputime.c b/kernel/sched/cputime.c > index 81b763b..d2c24c1 100644 > --- a/kernel/sched/cputime.c > +++

Re: [PATCH 3/3] acpi, memory-hotplug: Support getting hotplug info from SRAT.

On Fri, 25 Jan 2013 17:42:09 +0800 Tang Chen wrote: > We now provide an option for users who don't want to specify physical > memory address in kernel commandline. > > /* > * For movablemem_map=acpi: > * > * SRAT:|_| |_| |_|

Re: [PATCH 2/3] acpi, memory-hotplug: Extend movablemem_map ranges to the end of node.

On Fri, 25 Jan 2013 17:42:08 +0800 Tang Chen wrote: > When implementing movablemem_map boot option, we introduced an array > movablemem_map.map[] to store the memory ranges to be set as ZONE_MOVABLE. > > Since ZONE_MOVABLE is the latst zone of a node, if user didn't specify > the whole node

  1   2   3   4   5   6   7   8   9   10   >