The job ring init function creates a platform device for each job ring.
While the job ring is shutdown, e.g. while caam module removal, its
platform device was not being removed. This leads to failure while
reinsertion and then removal of caam module second time.
The following kernel crash dump
On 2013年04月15日 10:05, Rusty Russell wrote:
Chen Gang gang.c...@asianux.com writes:
We don't export any symbols 128 characters, but if we did then
kallsyms_expand_symbol() would overflow the buffer handed to it.
So we need check destination buffer length when copying.
the
On Wed, Apr 10, 2013 at 7:37 PM, Jonghwan Choi jhbird.c...@samsung.com wrote:
hyp_hvc vector offset should be 0x14 and hyp_svc vector offset should be
0x8.
Signed-off-by: Jonghwan Choi jhbird.c...@samsung.com
---
arch/arm/kvm/interrupts.S |4 ++--
1 file changed, 2 insertions(+), 2
On Mon, 2013-04-15 at 05:22 +0100, Hin-Tak Leung wrote:
How is converting a few hundred lines of print nothing to
another few hundred lines of print nothing functional?
What does it achieve?
Standardization of output style when enabled.
Easier conversion to pr_debug/dynamic_debugging.
Emitting
We don't export any symbols 128 characters, but if we did then
kallsyms_expand_symbol() would overflow the buffer handed to it.
So we need check destination buffer length when copying.
the related test:
if we define an EXPORT function which name more than 128.
will panic when
(2013/04/13 7:17), Dave Hansen wrote:
On 04/12/2013 07:56 AM, H. Peter Anvin wrote:
On 04/12/2013 07:31 AM, Vivek Goyal wrote:
I also have to admit that I don't see the difference between /dev/mem
and /dev/oldmem, as the former allows access to memory ranges outside
the ones used by the
On Sat, Apr 13, 2013 at 11:36:20PM +0800, Jiang Liu wrote:
Commit 600cc5b7f6 mm: Kill NO_BOOTMEM version free_all_bootmem_node()
has kill free_all_bootmem_node() for NO_BOOTMEM.
Currently the usage pattern for free_all_bootmem_node() is like:
for_each_online_pgdat(pgdat)
Hi Mike,
After merging the clk tree, today's linux-next build (x86_64 allmodconfig)
failed like this:
ERROR: of_clk_add_provider [drivers/clk/clk-si5351.ko] undefined!
ERROR: of_clk_src_onecell_get [drivers/clk/clk-si5351.ko] undefined!
ERROR: __clk_get_flags [drivers/clk/clk-si5351.ko]
From: Namhyung Kim namhyung@lge.com
They're not used anywhere and same information is kept in a pevent
already. So let's get rid of them.
Signed-off-by: Namhyung Kim namhy...@kernel.org
---
tools/perf/util/trace-event-parse.c | 4
tools/perf/util/trace-event.h | 4
2 files
From: Namhyung Kim namhyung@lge.com
It's the only user of the variable, so move it.
Signed-off-by: Namhyung Kim namhy...@kernel.org
---
tools/perf/builtin-script.c | 1 +
tools/perf/util/trace-event-parse.c | 2 --
tools/perf/util/trace-event.h | 1 -
3 files changed, 1
From: Namhyung Kim namhyung@lge.com
It's confusing to have same name for two difference functions which
does something opposite way. Since what they do in this file is read
*AND* writing some of tracing metadata files, rename them to
record_*() looks better to me.
Signed-off-by: Namhyung
From: Namhyung Kim namhyung@lge.com
They're not used anywhere, just make them local variables.
Signed-off-by: Namhyung Kim namhy...@kernel.org
---
tools/perf/util/trace-event-read.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/tools/perf/util/trace-event-read.c
From: Namhyung Kim namhyung@lge.com
It's useless to call the read_trace_init() function at this time as we
don't need a returned pevent and it makes me confusing. :)
Signed-off-by: Namhyung Kim namhy...@kernel.org
---
tools/perf/util/trace-event-info.c | 2 --
1 file changed, 2 deletions(-)
From: Namhyung Kim namhyung@lge.com
They're internals of ftrace ring-buffer and not used in perf code
directly. As it now resides on libtraceevent/kbuffer.h, just get
rid of them.
Signed-off-by: Namhyung Kim namhy...@kernel.org
---
tools/perf/util/trace-event.h | 10 --
1 file
From: Namhyung Kim namhyung@lge.com
The header_page file describes the format of the ring buffer page
which is used by ftrace (not perf). And size of commit field (I
guess it's older name was 'size') represents the real size of long
type used for kernel. So update the pevent's long size.
From: Namhyung Kim namhyung@lge.com
It seems perf does not parse header_event file so we can skip it as we
do for header_page file.
Signed-off-by: Namhyung Kim namhy...@kernel.org
---
tools/perf/util/trace-event-read.c | 9 +
1 file changed, 1 insertion(+), 8 deletions(-)
diff
Hello,
It seems some code that handle tracepoint events left unchanged when
they were copied from the trace-cmd. This series tries to cleanup
them by removing unnecessary function calls and variables and filling
up some missing pieces.
It's based on my previous patchset on libtraceevent [1] and
From: Namhyung Kim namhyung@lge.com
Save size of long type of system to struct pevent. Since original
static variable was not used anywhere, just get rid of it.
Signed-off-by: Namhyung Kim namhy...@kernel.org
---
tools/perf/util/trace-event-read.c | 11 +++
1 file changed, 3
From: Namhyung Kim namhyung@lge.com
We now have page_size field in struct pevent, save the actual size of
the system.
Signed-off-by: Namhyung Kim namhy...@kernel.org
---
tools/perf/util/trace-event-read.c | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git
Add basic documentation for virtio-9p. I can expand more on device operation,
but I don't think there's anything significant enough for the spec to be
mentioned there. Please let me know if I'm wrong.
Signed-off-by: Sasha Levin sasha.le...@oracle.com
---
virtio-spec.lyx | 206
Hi Andrew,
Today's linux-next merge of the akpm tree got a conflict in
drivers/staging/zcache/ramster/ramster.c between commit df735543008f
(staging: ramster: Move debugfs code out of ramster.c file) from the
staging tree and commit staging: zcache: enable ramster to be
built/loaded as a module
Quoting Tejun Heo (t...@kernel.org):
Hello, Serge.
On Sun, Apr 14, 2013 at 08:13:36PM -0500, Serge Hallyn wrote:
If I do
cd /sys/fs/cgroup/memory
mkdir b
cd b
echo 1 memory.use_hierarchy
echo 5000 memory.limit_in_bytes
cat memory.limit_in_bytes
8192
From: Lad, Prabhakar prabhakar.cse...@gmail.com
As of now TI has no maintainer/supporter for davinci media
drivers, Until it has any I'll be maintaining it.
Signed-off-by: Lad, Prabhakar prabhakar.cse...@gmail.com
Cc: Sekhar Nori nsek...@ti.com
---
MAINTAINERS |5 ++---
1 files changed, 2
Hi,
one of our servers keeps spitting GPF messages:
(sorry for long message)
[34110.179005] general protection fault: [#1] PREEMPT SMP
[34110.185000] CPU 0
[34110.186872] Modules linked in: ipmi_devintf ipmi_si ipmi_msghandler
ip6table_filter ip6_tables ipt_MASQUERADE ipt_REJECT
The latest r1p5-revision of the ARM PL011 UART has 32-byte FIFOs,
while all earlier ones have 16-byte FIFOs. This patch suggests
a way to set the FIFO-size correctly flexibly by using a member
function named get_fifosize, rather than using the fifosize member
variable. The function takes the
On Sat, Apr 13, 2013 at 11:06:14PM -0700, Joe Perches wrote:
Hello Heiko.
Commit ea81531d (s390/uaccess: fix page table walk)
added this code. It looks like it should have break;
for each case.
Hi Joe,
no, the fallthrough is on purpose for each case statement.
static unsigned long
When hot removing a memory, a firmware_map_entry which has memory range
of the memory is released by release_firmware_map_entry(). If the entry
is allocated by bootmem, release_firmware_map_entry() adds the entry to
map_entires_bootmem list when firmware_map_find_entry() finds the entry
from
On Mon, 2013-04-15 at 07:48 +0200, Heiko Carstens wrote:
On Sat, Apr 13, 2013 at 11:06:14PM -0700, Joe Perches wrote:
Commit ea81531d (s390/uaccess: fix page table walk)
added this code. It looks like it should have break;
for each case.
no, the fallthrough is on purpose for each case
On Sun, Apr 14, 2013 at 11:28:40PM -0400, Zhouping Liu wrote:
Hi All,
I hit the below crashed when doing memory related tests[1] on s390x:
--- snip -
� 15929.351639¨ � 0021c0a6¨ shrink_inactive_list+0x1c6/0x56c
� 15929.351647¨ � 0021c69e¨
On 04/14/2013 09:52 PM, HATAYAMA Daisuke wrote:
This sounds like there's no such issue on x86 cache mechanism. Is it
correct? If so, what is the difference between ia64 and x86 cache
mechanisms?
I'm just going by the code comments:
drivers/char/mem.c
/*
* On
On Sun, Apr 14, 2013 at 10:53:27PM -0700, Joe Perches wrote:
On Mon, 2013-04-15 at 07:48 +0200, Heiko Carstens wrote:
On Sat, Apr 13, 2013 at 11:06:14PM -0700, Joe Perches wrote:
Commit ea81531d (s390/uaccess: fix page table walk)
added this code. It looks like it should have break;
On 2013年04月12日 22:29, Serge E. Hallyn wrote:
Quoting Chen Gang (gang.c...@asianux.com):
after kfree acct, also set ns-bacct to NULL.
Signed-off-by: Chen Gang gang.c...@asianux.com
Acked-by: Serge Hallyn serge.hal...@canonical.com
thanks.
--
Chen Gang
Flying Transformer
--
To
Hello Heiko.
Commit ea81531d (s390/uaccess: fix page table walk)
added this code. It looks like it should have break;
for each case.
static unsigned long follow_table(struct mm_struct *mm,
unsigned long address, int write)
{
unsigned long
On Sat, Apr 13, 2013 at 03:09:43PM -0700, Paul E. McKenney wrote:
On Sat, Apr 13, 2013 at 12:53:36PM -0700, Josh Triplett wrote:
On Sat, Apr 13, 2013 at 12:34:25PM -0700, Paul E. McKenney wrote:
On Sat, Apr 13, 2013 at 11:18:00AM -0700, Josh Triplett wrote:
On Fri, Apr 12, 2013 at
Dear All,
In the setting of an SSD and an HDD connected to a HighPoint RocketRAID
620, I am seeing quite a number of log messages such as:
Apr 14 06:02:30 jekaterina kernel: [ 952.460537] sd 8:0:1:0: [sde]
Unhandled error code
Apr 14 06:02:30 jekaterina kernel: [ 952.460542] sd 8:0:1:0: [sde]
On 04/06/2013 03:55:26 PM, Randy Dunlap wrote:
On 03/03/13 04:43, Borislav Petkov wrote:
From: Borislav Petkov b...@suse.de
Hold down some important points to pay attention to when preparing a
pull request to upper-level maintainers and/or Linus. Based on a
couple
of agitated mails from
Cleaning out look at this directory, I don't see this applied
upstream but it may already be in Jens' tree. (That's the tree it
should go in through...)
On 03/30/2013 09:55:04 PM, Namjae Jeon wrote:
From: Namjae Jeon namjae.j...@samsung.com
Add the documentation text for latency,
On Sat, Apr 13, 2013 at 06:10:40PM +0100, Chris Wilson wrote:
On Sat, Apr 13, 2013 at 05:41:46PM +0200, Krzysztof Mazur wrote:
Hi,
the drm_fb_helper_hotplug_event() locks all crtc-mutex locks by calling
drm_modeset_lock_all() and later calls
drm_fb_helper_probe_connector_modes(),
On Thu, Apr 11, 2013 at 04:18:13PM +0300, Kirill A. Shutemov wrote:
Minchan Kim wrote:
On Fri, Mar 29, 2013 at 09:04:16AM -0400, Sasha Levin wrote:
Hi all,
While fuzzing with trinity inside a KVM tools guest running latest -next
kernel,
I've stumbled on the following.
It
Hi Linus,
Please pull from 'master' branch of
git://www.linux-watchdog.org/linux-watchdog.git
It will fix compile errors for teh at91rm9200_wdt driver.
This will update the following files:
Kconfig |2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
with these Changes:
commit
Hi,
Il 14/04/2013 02:18, KOSAKI Motohiro ha scritto:
(4/13/13 5:14 AM), Marco Stornelli wrote:
Hi,
I was seeing the code of __mm_populate (in -next) and I've got a doubt
about the return value. The function __mlock_posix_error_return should
return a proper error for mlock, converting the
Hi KOSAKI,
On Thu, Apr 11, 2013 at 11:01:11AM -0400, KOSAKI Motohiro wrote:
and adding new syscall invokation is unwelcome.
Sure. But one more system call could be cheaper than page-granuarity
operation on purged range.
I don't think vrange(VOLATILE) cost is the related of this
On Sat, Apr 13 2013, Rob Landley wrote:
Cleaning out look at this directory, I don't see this applied upstream but
it may already be in Jens' tree. (That's the tree it should go in
through...)
It's already included, see:
On Fri, Apr 12 2013, Asai Thambi S P wrote:
Temporarily disabling TRIM support until TRIM related issues
are addressed in the firmware.
How serious is this? We do have released kernels out there with the
driver, you might want to consider a stable backport too.
Anyway, applied for 3.10.
--
On Fri, Apr 12 2013, Asai Thambi S P wrote:
Reported smatch warning:
drivers/block/mtip32xx/mtip32xx.c:4163 mtip_block_shutdown() warn: variable
dereferenced before check 'dd-disk' (see line 4159)
dd-disk-disk_name accessed before the check if dd-disk is NULL. Fixed this
and access of
Hi Linus
one fix for a hotplug locking regressions, and one fix for an oops if you
unplug the monitor at an inopportune moment on the udl device.
Dave.
The following changes since commit cfb63bafdb87bbcdc5d6dbbca623d3f69475f118:
Merge branch 'fixes' of
Hello,
On 4/12/13 9:19 PM, Borislav Petkov wrote:
so I'm currently experimenting with my randconfig build scripts and
thought that maybe it would be a cool thing to not only do the random
builds only but also boot-test them in kvm. Which reminded me that we
have that KVMTOOL_TEST_ENABLE config
Devices have various maintenance operations need to perform internally.
In order to reduce latencies during time critical operations like read
and write, it is better to execute maintenance operations in other
times - when the host is not being serviced. Such operations are called
Background
On Sun, Apr 14, 2013 at 12:31:12PM +0300, Pekka Enberg wrote:
I obviously support having something like this in mainline. I wonder
though if we could just call this default standalone KVM guest
config instead of emphasizing testing angle.
/me nods agreeingly...
And it should be unter
On Sun, Apr 14, 2013 at 09:17:03AM +0200, Wim Van Sebroeck wrote:
Hi Linus,
Please pull from 'master' branch of
git://www.linux-watchdog.org/linux-watchdog.git
It will fix compile errors for teh at91rm9200_wdt driver.
This will update the following files:
Kconfig |2 +-
1
On Thu, Apr 11, 2013 at 02:04:50AM +0200, Arnd Bergmann wrote:
No other file in the kernel besides i2c-s3c2410.c uses the current
plat/regs-iic.h, so we can simply move the header file to live in the
same directory as the driver, as a preparation to multiplatform builds.
What about putting
On 04/13/13 23:46, Rob Landley wrote:
On 04/06/2013 03:55:26 PM, Randy Dunlap wrote:
On 03/03/13 04:43, Borislav Petkov wrote:
From: Borislav Petkov b...@suse.de
Documentation/SubmittingPullRequests | 148
+++
1 file changed, 148 insertions(+)
Hi James,
I am a newbie to linux kernel device driver and would like to use this
client driver on my uClinux running on the NIOS2. Can you kindly point me to
the right direction, since I am using a device tree and believe this doesn't
support device tree, right? What do I need to add/modify so I
On Mon, Apr 08, 2013 at 12:54:01PM -0700, Bryan Freed wrote:
[...]
And as a more general question, why should we try not to put
configuration in the device tree? It seems like a great (and
portable) place to put this stuff.
It certainly seems better to have it there than hardwired in the
Linus,
Please pull the latest perf-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
perf-urgent-for-linus
HEAD: c481420248c6730246d2a1b1773d5d7007ae0835 perf: Fix error return code
Misc fixlets.
Thanks,
Ingo
--
Chen
Linus,
Please pull the latest sched-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
sched-urgent-for-linus
HEAD: e614b3332a4f3f264a26da28e5a1f4cc3aea3974 sched/cputime: Fix accounting
on multi-threaded processes
Misc fixlets.
Thanks,
Linus,
Please pull the latest x86-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
x86-urgent-for-linus
HEAD: 26564600c9e88c6572a5e6ef5ae9121907edfb7f x86/mm: Flush lazy MMU when
DEBUG_PAGEALLOC is set
Misc fixes.
Thanks,
Ingo
On Sun, Apr 14, 2013 at 09:28:50AM +0800, Alex Shi wrote:
Even some scenario the total energy cost more, at least the avg watts
dropped in that scenarios.
Ok, what's wrong with x = 32 then? So basically if you're looking at
avg watts, you don't want to have more than 16 threads, otherwise
Commit-ID: c481420248c6730246d2a1b1773d5d7007ae0835
Gitweb: http://git.kernel.org/tip/c481420248c6730246d2a1b1773d5d7007ae0835
Author: Wei Yongjun yongjun_...@trendmicro.com.cn
AuthorDate: Fri, 12 Apr 2013 11:05:54 +0800
Committer: Ingo Molnar mi...@kernel.org
CommitDate: Fri, 12 Apr
Commit-ID: 26564600c9e88c6572a5e6ef5ae9121907edfb7f
Gitweb: http://git.kernel.org/tip/26564600c9e88c6572a5e6ef5ae9121907edfb7f
Author: Boris Ostrovsky boris.ostrov...@oracle.com
AuthorDate: Thu, 11 Apr 2013 13:59:52 -0400
Committer: Ingo Molnar mi...@kernel.org
CommitDate: Fri, 12 Apr
Commit-ID: 18699739b60cb60230153ff5475b2ba92be185f9
Gitweb: http://git.kernel.org/tip/18699739b60cb60230153ff5475b2ba92be185f9
Author: Andrea Arcangeli aarca...@redhat.com
AuthorDate: Thu, 11 Apr 2013 15:36:09 +0200
Committer: Ingo Molnar mi...@kernel.org
CommitDate: Fri, 12 Apr 2013
This reverts commit 87dc669ba25777b67796d7262c569429e58b1ed4.
The patch was fine but we can no longer race with SIGKILL after
9899d11f ptrace: ensure arch_ptrace/ptrace_request can never race
with SIGKILL, the __TASK_TRACED tracee can't be woken up and
-ptrace_bps[] can't go away.
The patch only
This reverts commit bf0b8f4b55e591ba417c2dbaff42769e1fc773b0.
The patch was fine but we can no longer race with SIGKILL after
9899d11f ptrace: ensure arch_ptrace/ptrace_request can never race
with SIGKILL, the __TASK_TRACED tracee can't be woken up and
-ptrace_bps[] can't go away.
Signed-off-by:
This reverts commit e0ac8457d020c0289ea566917267da9e5e6d9865.
The patch was fine but we can no longer race with SIGKILL after
9899d11f ptrace: ensure arch_ptrace/ptrace_request can never race
with SIGKILL, the __TASK_TRACED tracee can't be woken up and
-ptrace_bps[] can't go away.
Signed-off-by:
This reverts commit bf26c018490c2fce7fe9b629083b96ce0e6ad019.
The patch was fine but we can no longer race with SIGKILL after
9899d11f ptrace: ensure arch_ptrace/ptrace_request can never race
with SIGKILL, the __TASK_TRACED tracee can't be woken up and
-ptrace_bps[] can't go away.
Now that
Hello.
Kill ptrace_{get,put}_breakpoints and task_struct-ptrace_bp_refcnt,
9899d11f ptrace: ensure arch_ptrace/ptrace_request can never race
with SIGKILL made this all unneeded.
Benjamin, Paul, arch_dup_task_struct()-flush_ptrace_hw_breakpoint(src)
on powerpc looks obviously wrong. Don't we need
Commit-ID: 9b89f6ba2ab56e4d9c00e7e591d6bc333137895e
Gitweb: http://git.kernel.org/tip/9b89f6ba2ab56e4d9c00e7e591d6bc333137895e
Author: Andrei Epure epure.and...@gmail.com
AuthorDate: Thu, 11 Apr 2013 20:30:29 +0300
Committer: Ingo Molnar mi...@kernel.org
CommitDate: Fri, 12 Apr 2013
This reverts commit 07fa7a0a8a586c01a8b416358c7012dcb9dc688d and
removes ptrace_get/put_breakpoints() added by other commits.
The patch was fine but we can no longer race with SIGKILL after
9899d11f ptrace: ensure arch_ptrace/ptrace_request can never race
with SIGKILL, the __TASK_TRACED tracee
Commit-ID: a7e6567585e513cb4e44387831cb75eb5b562cbb
Gitweb: http://git.kernel.org/tip/a7e6567585e513cb4e44387831cb75eb5b562cbb
Author: Paul Bolle pebo...@tiscali.nl
AuthorDate: Thu, 11 Apr 2013 18:49:42 +0200
Committer: Ingo Molnar mi...@kernel.org
CommitDate: Fri, 12 Apr 2013 07:21:18
When user requests encryption (or decryption) of block which
is not aligned to cipher block size through userspace crypto
interface, an OOps like this can happen:
[ 112.738285] BUG: unable to handle kernel paging request at e1c44840
[ 112.738407] IP: [c121f473] scatterwalk_done+0x53/0x70
...
[
On 04/14/2013 06:12 PM, Milan Broz wrote:
When user requests encryption (or decryption) of block which
is not aligned to cipher block size through userspace crypto
interface, an OOps like this can happen
And this is a reproducer for the problem above...
Milan
/*
* Check for unaligned
2013/4/12 Lee Jones lee.jo...@linaro.org:
So I need to devise another way, as this function cannot be called
here either. Using the dmaengine API, allocating a channel and
configuring it are to be completed using different calls. Using the
API correctly, there is no way the driver can setup
I found the early-increasing nr_running in wq_worker_waking_up() is useless
in many cases. it tries to avoid waking up idle workers for pending work item.
but delay increasing nr_running does not increase waking up idle workers.
so we delay increasing and remove wq_worker_waking_up() and ...
WARN_ON_ONCE(cpu != raw_smp_processor_id()) in
wq_worker_sleeping() in useless, the caller ensures
cpu == raw_smp_processor_id().
We should use WARN_ON_ONCE(pool-cpu != raw_smp_processor_id())
to do the expected test.
It results @cpu removed from wq_worker_sleeping()
Signed-off-by: Lai
After we allocated worker, we are free to access the worker without and
protection before it is visiable/published.
In old code, worker is published by start_worker(), and it is visiable only
after start_worker(), but in current code, it is visiable by
for_each_pool_worker() after
In process_one_work(), we can use worker-flags WORKER_CPU_INTENSIVE
instead cpu_intensive and because worker-flags is hot field
(accessed when process each work item). so this change will not cause
any performance down.
It prepare for also clearing WORKER_QUIT_CM in the same place.
When a work is waken up from sleeping, it makes very small sense if
we still consider this worker is RUNNING(in view of concurrency management)
o if the work goes to sleep again, it is not RUNNING again.
o if the work runs long without sleeping, the worker should be consider
as
When a worker is sleeping, its flags has WORKER_QUIT_CM, which means
worker-flags WORKER_NOT_RUNNING is always non-zero, and which means
wq_worker_waking_up() is disabled.
so we removed wq_worker_waking_up(). (the access to worker-flags
in wq_worker_waking_up() is not protected by LI. after
Now, nr_running is accessed only with local IRQ-disabled and only from local
cpu if the pool is assocated.(execpt read-access in insert_work()).
so we convert it to non-atomic to reduce the overhead of atomic.
It is protected by LI
Signed-off-by: Lai Jiangshan la...@cn.fujitsu.com
---
worker-flags is hot field(accessed when process each work item).
Move it up the the first 64 bytes(32 byte in 32bis) which are
hot fields.
And move colder field worker-task down to ensure worker-pool is
still in the first 64 bytes.
Signed-off-by: Lai Jiangshan la...@cn.fujitsu.com
---
nr_running is not a good name, the reviewers may think they are non-sleeping
busy workers. nr_running is actually a counter for concurrency managed
workers. renaming it to nr_cm_workers would be better.
s/nr_running/nr_cm_workers/
s/NOT_RUNNING/NOT_CM/
manually tune a little(indent and the
Am Sonntag, 14. April 2013, 14:20:35 schrieb Wolfram Sang:
On Thu, Apr 11, 2013 at 02:04:50AM +0200, Arnd Bergmann wrote:
No other file in the kernel besides i2c-s3c2410.c uses the current
plat/regs-iic.h, so we can simply move the header file to live in the
same directory as the driver, as
Hi Joe,
On Sat, 13 Apr 2013 22:55:45 -0700, Joe Perches j...@perches.com wrote:
commit 3401d54696f (KVM: ARM: Introduce KVM_ARM_SET_DEVICE_ADDR ioctl)
added the case, but omitted adding break;
[...]
Already reported here:
Cc: Linus Walleij linus.wall...@linaro.org
Cc: Jean Delvare jdelv...@suse.de
Cc: Samuel Ortiz sa...@linux.intel.com
Cc: Mark Brown broo...@opensource.wolfsonmicro.com
Cc: Guenter Roeck li...@roeck-us.net
Cc: linux-kernel linux-kernel@vger.kernel.org
Cc: Grant Likely grant.lik...@secretlab.ca
Now that hierarchy_id alloc / free are protected by the cgroup
mutexes, there's no need for this separate lock. Drop it.
Signed-off-by: Tejun Heo t...@kernel.org
---
kernel/cgroup.c | 23 +--
1 file changed, 17 insertions(+), 6 deletions(-)
diff --git a/kernel/cgroup.c
kdbus folks want a sane way to determine the cgroup path that a given
task belongs to on a given hierarchy, which is a reasonble thing to
expect from cgroup core.
Implement task_cgroup_path_from_hierarchy().
Signed-off-by: Tejun Heo t...@kernel.org
Cc: Kay Sievers k...@vrfy.org
Cc: Greg
We're planning to converting hierarchy_ida to an idr and use it to
look up hierarchy from its id. As we want the mapping to happen
atomically with cgroupfs_root registration, this patch refactors
hierarchy_id init / exit so that ida operations happen inside
cgroup_[root_]mutex.
*
We want to be able to lookup a hierarchy from its id and cyclic
allocation is a whole lot simpler with idr. Convert to idr and use
idr_alloc_cyclc().
Signed-off-by: Tejun Heo t...@kernel.org
---
kernel/cgroup.c | 28
1 file changed, 8 insertions(+), 20 deletions(-)
kdbus folks want a sane way to determine the cgroup path that a given
task belongs to on a given hierarchy, which is a reasonble thing to
expect from cgroup core.
This patchset make hierarchy_id allocation use idr instead of ida and
implement task_cgroup_path_from_hierarchy(). In the process,
Dear Marek Vasut,
Cc: Linus Walleij linus.wall...@linaro.org
Cc: Jean Delvare jdelv...@suse.de
Cc: Samuel Ortiz sa...@linux.intel.com
Cc: Mark Brown broo...@opensource.wolfsonmicro.com
Cc: Guenter Roeck li...@roeck-us.net
Cc: linux-kernel linux-kernel@vger.kernel.org
Cc: Grant Likely
ptrace_write_dr7() looks unnecessarily overcomplicated. We can
factor out ptrace_modify_breakpoint() and do not do continue
twice, just we need to pass the proper disabled argument to
ptrace_modify_breakpoint().
Signed-off-by: Oleg Nesterov o...@redhat.com
---
arch/x86/kernel/ptrace.c | 40
On Sun, Apr 14, 2013 at 11:36:59AM -0700, Tejun Heo wrote:
kdbus folks want a sane way to determine the cgroup path that a given
task belongs to on a given hierarchy, which is a reasonble thing to
expect from cgroup core.
Implement task_cgroup_path_from_hierarchy().
Signed-off-by: Tejun
ptrace_write_dr7() skips ptrace_modify_breakpoint(disabled = true)
unless second_pass, this buys nothing but complicates the code and
means that we always do the main loop twice even if disabled was
never true.
The comment says:
Don't unregister the breakpoints right-away,
unless
Hello.
On top of [PATCH 0/5] kill ptrace_{get,put}_breakpoints().
Cleanup and preparation for the potential fix, see below.
--
Now the question. Initially I was going to make more patches
and fix the regression
swap_pci_ref function is used by the IOMMU API code for swapping pci device
pointers, while determining the iommu group for the device.
Currently this function was being implemented for different IOMMU drivers.
This patch moves the function to pci.h so that the implementation can be
shared across
Added the following domain attributes for the FSL PAMU driver:
1. Added new iommu stash attribute, which allows setting of the
LIODN specific stash id parameter through IOMMU API.
2. Added an attribute for enabling/disabling DMA to a particular
memory window.
3. Added domain attribute to
On Sun, 14 Apr 2013 21:12:05 +0200, Oleg Nesterov wrote:
Jan, Frederic, et all. What do you think we should do?
1. Change ptrace_write_dr7() to do register_user_hw_breakpoint()
if necessary.
This is what I was going to do, but I am no longer sure
we want
Some filesystems try to optimize barrier flushes by maintaining
fs-specific generation counters, but if we introduce generic
flush generation counter for block device filesystems may use
it for fdatasync(2) optimization. Optimization should works if
userspace performs mutli-threaded IO with a lot
Track blkdev's flush generation counter on per-inode basis and update
inside end_io. If inode's flush generation counter is older than current
blkdev's flush counter inode's data was already flushed to stable media,
so we can skip explicit barrier. Optimization is safe only when inode's
end_io was
Callers may use this counter to optimize flushes
Signed-off-by: Dmitry Monakhov dmonak...@openvz.org
---
block/blk-core.c |1 +
block/blk-flush.c |3 ++-
include/linux/blkdev.h |1 +
3 files changed, 4 insertions(+), 1 deletions(-)
diff --git a/block/blk-core.c
101 - 200 of 444 matches
Mail list logo
