On 07/01/2013 03:07 PM, Luca Barbato wrote:
> Hopefully I will carve some time next weekend to play the restricted
> bisect game.
Release 3.10 apparently doesn't show the problem, I guess problem solved
for me =)
lu
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
On Thu, 04 Jul 2013 10:36:53 +0530, Viresh Kumar wrote:
> Hi Lukasz,
>
> Sorry for being late. Actually I didn't had an answer to your mail
> and wanted to go through it with some fresh mind. This is my
> first mail this morning, lets see if I can bring something good
> into the discussion.
>
>
As title, when we change the commit interval from default value, i.e., 5sec, to
other large value, for example, 100 sec., etc.
Does it really make the performance higher?
Since I change this value to some large value, running some benchmark(postmark,
iozone, bonnie++) to observe it, I didn't
Nearly all the other goldfish peripherals (mtd, keyboard, etc)
have a dependency on the main platform's GOLDFISH Kconfig item,
but this one got skipped. It was suggested to add it earlier[1],
but that never got responded to or picked up -- presumably because
some developers desired the extra
I only just noticed the existence of CONFIG_COMPILE_TEST (now in
mainline as of merge fc76a258d41 ("Merge tag 'driver-core-3.11-rc1' of
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core")
I like this; it parallels a discussion I had with Andrew a while ago:
Nearly all the other goldfish peripherals (mtd, keyboard, etc)
have a dependency on the main platform's GOLDFISH Kconfig item,
but this one got skipped. Even with consistency as a
justification, there was initial resistance[1] from some people
to adding it however, as they wanted the extra
commit 57f6ce072e35770a63be0c5d5e82f90d8da7d665 ("usb: phy:
add a new driver for usb3 phy") added the new Kconfig option
OMAP_USB3, but it had no dependencies whatsoever, and hence
became available across all arch/platforms.
Which presumably caused this to show up in x86 randconfig:
warning:
The option CONFIG_COMPILE_TEST, added in commit 4bb1667255a
("build some drivers only when compile-testing") is meant to
give a middle ground[1] between those who want the widest compile
coverage possible (e.g. building sparc drivers for mips) and
those who want dependencies to represent real
commit 5d33b883aed81c6fbcd09c6f7c3619eee850a7e2
clocksource: Always verify highres capability
This commit will reject a clock to be system clocksource if it has no
CLOCK_SOURCE_VALID_FOR_HRES flags. Then the tsc to be rejected as
clocksource, because this flag for tsc is set in
We find some benchmarks drop a lot on tip/sched/core on many Intel boxes,
like oltp, tbench, hackbench etc. and bisected the commit 5d33b883ae
cause this regression. Due to this commit, the clocksource was changed
to hpet from tsc even tsc will be set CLOCK_SOURCE_VALID_FOR_HRES later
in
After clocksource_find_best() introduced, it is impossible to get into
some code path. so clean them up.
Signed-off-by: Alex Shi
---
kernel/time/clocksource.c | 16 +---
1 file changed, 1 insertion(+), 15 deletions(-)
diff --git a/kernel/time/clocksource.c
Shrink the mutex region. And save a clocksource_select action if set
clocksource is same as current clocksource.
Signed-off-by: Alex Shi
---
kernel/time/clocksource.c | 12 +++-
1 file changed, 7 insertions(+), 5 deletions(-)
diff --git a/kernel/time/clocksource.c
Hi Steve,
On Wed, 03 Jul 2013 10:22:30 -0400, Steven Rostedt wrote:
> On Wed, 2013-07-03 at 21:35 +0900, Namhyung Kim wrote:
>> Hello,
>>
>> This patchset implements memory (address), stack[N], deference,
>> bitfield and retval (it needs uretprobe tho) fetch methods for
>> uprobes. It's based
On Wed, Jul 3, 2013 at 11:30 PM, Mark Brown wrote:
> On Mon, Jun 24, 2013 at 04:50:58PM +0530, Yadwinder Singh Brar wrote:
>
>> +static void s2mps11_pmic_parse_dt(struct of_regulator_match *rdata,
>> + struct s2mps11_info *s2mps11)
>> +{
>> + if
Hi Lukasz,
Sorry for being late. Actually I didn't had an answer to your mail
and wanted to go through it with some fresh mind. This is my
first mail this morning, lets see if I can bring something good
into the discussion.
On 1 July 2013 13:45, Lukasz Majewski wrote:
> Does anybody have any
On Wed, Jul 3, 2013 at 11:35 PM, Mark Brown wrote:
> On Mon, Jun 24, 2013 at 04:50:57PM +0530, Yadwinder Singh Brar wrote:
>
>> + regulator-ramp-delay for BUCKs = [6250/12500/25000(default)/5] uV/us
>
>> + Optional property for BUCK[2/3/4/6] only:
>> + regulator-ramp-disable: boolean,
Hi guys!
I encountered that a file cannot be opened even if the process has a valid
access authority for the file on linux-3.10.
This problem is caused since the group list which getgroups() returns includes
wrong ID as the group ID after setgid(). These groups include egid of the
process
On Wed, Jul 03, 2013 at 08:50:07PM -0700, Linus Torvalds wrote:
> On Wed, Jul 3, 2013 at 8:33 PM, Waiman Long wrote:
> > Because of the d_count name change made in dcache.h, all references
> > to d_count have to be changed to d_refcount. There is no change in
> > logic and everything should just
Hi all,
Building Linus' tree, today's linux-next build (x86_64 allmodconfig)
produced this warning (these have been around for a while):
drivers/infiniband/hw/nes/nes_hw.c:81:23: warning: 'nes_iwarp_state_str'
defined but not used [-Wunused-variable]
static unsigned char *nes_iwarp_state_str[]
From: Peter Zijlstra
Smart wake-affine is using node-size as the factor, but the overhead of
mask operation is high.
Thus, this patch introduce the 'sd_llc_size', which will record the highest
cache-share domain size, and make it to be the new factor, in order to
reduce the overhead and make
wake-affine stuff is always trying to pull wakee close to waker, by theory,
this will bring benefit if waker's cpu cached hot data for wakee, or the
extreme ping-pong case.
And testing show it could benefit hackbench 15% at most.
However, the whole stuff is somewhat blindly and time-consuming,
Since v2:
Add patch [PATCH 2/2] sched: reduce the overhead of obtain factor
for optimization. (Thanks to PeterZ)
This patch-set will implement a smart wake-affine, in order to regain the
lost performance of the workload like pgbench, meanwhile reserve the gained
benefit of the
On Wed, Jul 03, 2013 at 10:09:32AM -0600, Bjorn Helgaas wrote:
> On Wed, Jul 3, 2013 at 9:16 AM, Haicheng Li
> wrote:
> > With more and more SOCs having pci device integrated into chip (e.g. Intel
> > Atom series), it's useful to add an interface to cleanly hide pci devices
> > from
> > pci
On 07/04/2013 12:08 PM, Greg KH wrote:
> On Thu, Jul 04, 2013 at 11:26:53AM +0800, Chen Gang F T wrote:
>> > Please see the related comment in "init/Kconfig" of next-* tree.
> This is now in Linus's tree for 3.11.
>
OK, thanks (at least for me, it is a good news).
>> > config COMPILE_TEST
>> >
On 7/3/2013 7:33 PM, Luciano Coelho wrote:
> The platform_quirk element in the platform data was used to change the
> way the IRQ is triggered. When set, the EDGE_IRQ quirk would change
> the irqflags used and treat edge trigger differently from the rest.
>
> Instead of hiding this irq flag
Hi,
On Wednesday 03 July 2013 10:47 PM, Florian Fainelli wrote:
Hello,
2013/7/3 Sourav Poddar:
From: Mona Anonuevo
This patch adds support for a generic spinand framework(spinand_mtd.c).
This frameowrk can be used for other spi based flash devices. The idea
is to have a common model under
I'll look harder at the backtrace tomorrow, but my guess is that the cpu has
just gotten a scheduling interrupt (time quantum expired.)
Linus Torvalds wrote:
>On Wed, Jul 3, 2013 at 6:55 PM, Dave Jones wrote:
>> This is a pretty context free trace. What the hell happened here?
>
>That lack of
On Wed, Jul 03, 2013 at 04:22:17PM -0400, Waiman Long wrote:
> diff --git a/security/selinux/selinuxfs.c b/security/selinux/selinuxfs.c
> index ff42773..c83a201 100644
> --- a/security/selinux/selinuxfs.c
> +++ b/security/selinux/selinuxfs.c
> @@ -1187,28 +1187,28 @@ static void
On Thu, 4 Jul 2013 14:33:53 +1000 Stephen Rothwell
wrote:
> Hi Andrew,
>
> Today's linux-next merge of the akpm tree got conflicts in
> tools/include/tools/be_byteshift.h and tools/include/tools/le_byteshift.h
> between commit b35310627f39 ("tools/include: use stdint types for
> user-space
Hi Andrew,
Today's linux-next merge of the akpm tree got conflicts in
tools/include/tools/be_byteshift.h and tools/include/tools/le_byteshift.h
between commit b35310627f39 ("tools/include: use stdint types for
user-space byteshift headers") from the kbuild tree and commit
"scripts/sortextable.c:
On Wed, Jul 03, 2013 at 03:57:45PM +, Christoph Lameter wrote:
> On Wed, 3 Jul 2013, Joonsoo Kim wrote:
>
> > @@ -298,13 +298,15 @@ static inline void arch_alloc_page(struct page *page,
> > int order) { }
> >
> > struct page *
> > __alloc_pages_nodemask(gfp_t gfp_mask, unsigned int order,
On Thu, Jul 04, 2013 at 12:01:43AM +0800, Zhang Yanfei wrote:
> On 07/03/2013 11:51 PM, Zhang Yanfei wrote:
> > On 07/03/2013 11:28 PM, Michal Hocko wrote:
> >> On Wed 03-07-13 17:34:15, Joonsoo Kim wrote:
> >> [...]
> >>> For one page allocation at once, this patchset makes allocator slower than
(2013/07/04 6:02), Steven Rostedt wrote:
> On Wed, 2013-07-03 at 21:17 +0200, Oleg Nesterov wrote:
>
>> diff --git a/fs/debugfs/inode.c b/fs/debugfs/inode.c
>> index 4888cb3..c23d41e 100644
>> --- a/fs/debugfs/inode.c
>> +++ b/fs/debugfs/inode.c
>> @@ -475,6 +475,7 @@ static int
(2013/07/04 12:33), Steven Rostedt wrote:
> diff --git a/kernel/trace/trace_events.c b/kernel/trace/trace_events.c
> index 7d85429..90cf243 100644
> --- a/kernel/trace/trace_events.c
> +++ b/kernel/trace/trace_events.c
> @@ -391,6 +391,28 @@ static void __get_system_dir(struct ftrace_subsystem_dir
On Wed, Jul 03, 2013 at 04:25:32PM -0400, Waiman Long wrote:
> There is no change in logic and everything should just work.
> - spin_lock(>f_path.dentry->d_lock);
> + d_lock(file->f_path.dentry);
> if (!d_unhashed(file->f_path.dentry))
>
On Thu, Jul 04, 2013 at 11:26:53AM +0800, Chen Gang F T wrote:
> Please see the related comment in "init/Kconfig" of next-* tree.
This is now in Linus's tree for 3.11.
> config COMPILE_TEST
>bool "Compile also drivers which will not load"
>default n
This has _nothing_ to do with
acpi_device_list is not used by acpi code anymore, could be removed.
Signed-off-by: Haicheng Li
---
drivers/acpi/scan.c |1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/acpi/scan.c b/drivers/acpi/scan.c
index 27da630..fcc0cdc 100644
--- a/drivers/acpi/scan.c
+++
(2013/07/04 12:33), Steven Rostedt wrote:
> Currently there exists a race with deleting a kprobe or uprobe and
> a user opening the probe event file or using perf events.
>
> The problem stems from not being able to take the probe_lock from the
> unregister code because we may have the
On Wed, Jul 3, 2013 at 8:33 PM, Waiman Long wrote:
> Because of the d_count name change made in dcache.h, all references
> to d_count have to be changed to d_refcount. There is no change in
> logic and everything should just work.
These filesystem patches need to be just joined into the same
I am using a laptop with Intel Ivy bridge core i7 3610QM. I updated my
kernel to 3.10 and started to use intel_pstate as scaling driver:
#cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_driver
intel_pstate
However I find that one of my four cores is always in C0 state even when
there is no
From: Oleg Nesterov
Change trace_remove_event_call(call) to return the error if this
call is active. This is what the callers assume but can't verify
outside of the tracing locks. Both trace_kprobe.c/trace_uprobe.c
need the additional changes, unregister_trace_probe() should abort
if
Currently there exists a race with deleting a kprobe or uprobe and
a user opening the probe event file or using perf events.
The problem stems from not being able to take the probe_lock from the
unregister code because we may have the event_mutex at the time, and
the event mutex may be taken
From: "Steven Rostedt (Red Hat)"
When one of the event files is opened, we need to prevent them from
being removed. Modules do with with the module owner set (automated
from the VFS layer). The ftrace buffer instances have a ref count added
to the trace_array when the enabled file is opened
From: "Steven Rostedt (Red Hat)"
When one of the event files is opened, we need to prevent them from
being removed. Modules do with with the module owner set (automated
from the VFS layer). The ftrace buffer instances have a ref count added
to the trace_array when the enabled file is opened
From: "Steven Rostedt (Red Hat)"
When one of the event files is opened, we need to prevent them from
being removed. Modules do with with the module owner set (automated
from the VFS layer). The ftrace buffer instances have a ref count added
to the trace_array when the enabled file is opened
There are two steps to enable each architecture to do lockless
reference count update:
1. Define the ARCH_SPINLOCK_REFCOUNT config parameter in its Kconfig
file.
2. Add a architecture specific header file.
This is done for the x86 architecture to use the generic version
available.
This patch introduces a new set of spinlock_refcount.h header files to
be included by kernel codes that want to do a faster lockless update
of reference count protected by a spinlock.
The new lockref structure consists of just the spinlock and the
reference count data. Helper functions are
The current code takes the dentry's d_lock lock whenever the
d_refcount is being updated. In reality, nothing big really happens
until d_refcount goes to 0 in dput(). So it is not necessary to take
the lock if the reference count won't go to 0. On the other hand,
there are cases where refcount
Because of the d_count name change made in dcache.h, all references
to d_count have to be changed to d_refcount. There is no change in
logic and everything should just work.
Signed-off-by: Waiman Long
---
fs/nilfs2/super.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git
Because of the d_count name change made in dcache.h, all references
to d_count have to be changed to d_refcount. There is no change in
logic and everything should just work.
Signed-off-by: Waiman Long
---
fs/configfs/dir.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git
Because of the d_count name change made in dcache.h, all references
to d_count have to be changed to d_refcount. There is no change in
logic and everything should just work.
Signed-off-by: Waiman Long
---
fs/ecryptfs/inode.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff
Because of the d_count name change made in dcache.h, all references
to d_count have to be changed to d_refcount. There is no change in
logic and everything should just work.
Signed-off-by: Waiman Long
---
fs/locks.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git
Because of the d_count name change made in dcache.h, all references
to d_count have to be changed to d_refcount. There is no change in
logic and everything should just work.
Signed-off-by: Waiman Long
---
fs/nfs/dir.c|8
fs/nfs/unlink.c |2 +-
2 files changed, 5
Because of the d_count name change made in dcache.h, all references
to d_count have to be changed to d_refcount. There is no change in
logic and everything should just work.
Signed-off-by: Waiman Long
---
fs/ceph/inode.c |4 ++--
fs/ceph/mds_client.c |2 +-
2 files changed, 3
Because of the d_count name change made in dcache.h, all references
to d_count have to be changed to d_refcount. There is no change in
logic and everything should just work.
Signed-off-by: Waiman Long
---
fs/coda/dir.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git
Before converting the d_lock and d_count field of the dentry data
structure to the new lockref structure, we need to consider the
implication of such a change. All current references of d_count and
d_lock have to be changed accordingly.
One way to minimize the changes is to redefine the original
v3->v4:
- Replace helper function access to d_lock and d_count by using
macros to redefine the old d_lock name to the spinlock and new
d_refcount name to the reference count. This greatly reduces the
size of this patchset from 25 to 12 and make it easier to review.
v2->v3:
- Completely
Because of the d_count name change made in dcache.h, all references
to d_count have to be changed to d_refcount. There is no change in
logic and everything should just work.
Signed-off-by: Waiman Long
---
fs/autofs4/expire.c |8
fs/autofs4/root.c |2 +-
2 files changed, 5
Hi Soren,
On Wed, Jul 03, 2013 at 02:50:16PM -0700, Soren Brinkmann wrote:
> Reuse the TTC clocksource timer as sched clock, too. Since only a single
> sched clock is supported in Linux, this feature optional and can be
> selected through Kconfig.
>
> Signed-off-by: Soren Brinkmann
> ---
[...]
On 07/04/2013 11:06 AM, Steven Rostedt wrote:
> On Thu, 2013-07-04 at 10:42 +0800, Chen Gang F T wrote:
>
>> > Hmm..., I think maybe also has another way: get rid of 'COMPILE_TEST'
>> > (regress the related patch, which is only existent in next-* tree).
> I'm not working on linux-next at the
On 06/21/2013 11:48 AM, Gao feng wrote:
> On 06/20/2013 09:02 PM, Eric Paris wrote:
>> On Thu, 2013-06-20 at 11:02 +0800, Gao feng wrote:
>>> On 06/20/2013 04:51 AM, Eric Paris wrote:
On Wed, 2013-06-19 at 16:49 -0400, Aristeu Rozanski wrote:
> On Wed, Jun 19, 2013 at 09:53:32AM +0800,
On Wed, 3 Jul 2013, Vince Weaver wrote:
>
> Add some documentation for the perf_event related
> /sys/bus/event_source/bus/devices/
> files, since in theory it's a stable interface and the only
> current documentation is some lex and yacc files in the
> perf tools directory.
OK, don't I feel
On Thu, 2013-07-04 at 10:42 +0800, Chen Gang F T wrote:
> Hmm..., I think maybe also has another way: get rid of 'COMPILE_TEST'
> (regress the related patch, which is only existent in next-* tree).
I'm not working on linux-next at the moment. Hmm, I'm not even working
on mainline at the moment,
On Fri, 2013-06-28 at 14:27 -0500, Sherry Hurwitz wrote:
> For AMD Families 10h ~ 14h Processors
> file: amd-ucode/microcode_amd.bin
> md5sum: 55ae79b82cbfddcf7142058be3c9ec2d
>
> For AMD Family 15h Processors
> file: amd-ucode/microcode_amd_fam15h.bin
> md5sum:
On Wed, Jul 3, 2013 at 6:55 PM, Dave Jones wrote:
> This is a pretty context free trace. What the hell happened here?
That lack of call trace looks like it happened at the final stage of
an interrupt or page fault or other trap that is about to return to
user space.
My guess would be that the
On 07/04/2013 10:29 AM, Steven Rostedt wrote:
> On Thu, 2013-07-04 at 10:10 +0800, Chen Gang F T wrote:
>
>> > Select "COMPILE_TEST=y" with allmodconfig, but can not pass compiling in
>> > many architectures, one of the most reasons is "HW does not support".
>> >
>> > 'asm-generic' is really
On Wed, Jul 03, 2013 at 12:44:01PM -0400, Don Zickus wrote:
> On Fri, Jun 28, 2013 at 05:37:39PM -0300, Marcelo Tosatti wrote:
> > On Fri, Jun 28, 2013 at 10:12:15AM -0400, Don Zickus wrote:
> > > On Thu, Jun 27, 2013 at 11:57:23PM -0300, Marcelo Tosatti wrote:
> > > >
> > > > One possibility for
On Wed, Jul 03, 2013 at 12:44:01PM -0400, Don Zickus wrote:
> > And why overcommitment is not a valid reason to generate a softlockup in
> > the first place ?
>
> For the guest I don't believe it is. It isn't the guest's fault it
> couldn't run processes. A warning should be scheduled on the
On Thu, 2013-07-04 at 10:10 +0800, Chen Gang F T wrote:
> Select "COMPILE_TEST=y" with allmodconfig, but can not pass compiling in
> many architectures, one of the most reasons is "HW does not support".
>
> 'asm-generic' is really existent for a long time, and make an important
> role for both
On Wed, Jul 03, 2013 at 11:24:03PM +0200, Rafael J. Wysocki wrote:
> On Wednesday, July 03, 2013 11:16:18 PM Haicheng Li wrote:
> > Cc: Len Brown
> > Cc: "Rafael J. Wysocki"
> > Cc: linux-a...@vger.kernel.org
> > Signed-off-by: Haicheng Li
>
> -ENOCHANGELOG
Ah, just thought the patch is so
Jason Wang writes:
> Commit 55257d72bd1c51f25106350f4983ec19f62ed1fa (virtio-net: fill only rx
> queues
> which are being used) tries to refill on demand when changing the number of
> channels by call try_refill_recv() directly, this may race:
>
> - the refill work who may do the refill in the
On Wed, Jul 03, 2013 at 10:00:41AM -0600, Bjorn Helgaas wrote:
> On Wed, Jul 3, 2013 at 9:16 AM, Haicheng Li
> wrote:
> > Cc: Rob Landley
> > Cc: linux-...@vger.kernel.org
> > Cc: linux-...@vger.kernel.org
> > Signed-off-by: Haicheng Li
> > ---
> > Documentation/kernel-parameters.txt |2
On 07/04/2013 09:23 AM, Steven Rostedt wrote:
> On Wed, 2013-07-03 at 18:12 -0700, Greg KH wrote:
>
>> > confused,
> Good. I thought I was the only one. Confusion loves company, that way we
> can follow each other around in endless circles.
If you think, this mail has already make noises to many
On 07/04/2013 10:03 AM, Steven Rostedt wrote:
> On Thu, 2013-07-04 at 09:49 +0800, Chen Gang wrote:
>
>> > Hmm... at least, it is neither architectures issue nor modules issue.
>> >
>> > So we have to look for who have duty for it, since it is a 'generic'
>> > issue for many architectures and
Hi Jiaxing,
Please refer to inline comment.:)
On 07/02/2013 08:43 AM, Jiaxing Wang wrote:
> On 07/01/2013 08:41 PM, fangdong wrote:
>> On 06/29/2013 05:11 AM, Jiaxing Wang wrote:
>>> After pread(), file->f_pos and m->read_pos get different,
>>> and lseek() to m->read_pos did not update
On Thu, 2013-07-04 at 09:49 +0800, Chen Gang wrote:
> Hmm... at least, it is neither architectures issue nor modules issue.
>
> So we have to look for who have duty for it, since it is a 'generic'
> issue for many architectures and modules, we have to find it in
> 'generic' area (e.g.
This is a pretty context free trace. What the hell happened here?
BUG: scheduling while atomic: trinity-child0/13280/0xefff
INFO: lockdep is turned off.
Modules linked in: dlci dccp_ipv6 dccp_ipv4 dccp sctp bridge 8021q garp stp
snd_seq_dummy tun fuse hidp rfcomm bnep can_raw can_bcm
The following functions in the fs/dcache.c file are changed to use
the blocking reader seqlock as none of the dentries are being changed
by those functions. This will allow other non-blocking readers to
proceed when the blocking readers have taken the lock.
1. __d_path
2. d_absolute_path
3.
For the use cases where there are much more blocking readers than
writers, it will be beneficial performance-wise to use read/write lock
instead of a spinlock. However, read/write lock is non-deterministic
and can be problematic in some situations. So a complete conversion
of the underlying lock
This patch converts the underlying lock in rename_lock from spinlock
to a read/write lock. This allows multiple blocking readers to proceed
concurrently which is not possible with a spinlock implementation.
As contention of the rename_lock in the d_path() function is a
bottleneck when the perf
The sequence lock (seqlock) was originally designed for the cases
where the readers do not need to block the writers by making the
readers retry the read operation when the data change.
Since then, the use cases have been expanded to include situations
where a thread does not need to change the
On 07/04/2013 09:12 AM, Greg KH wrote:
> On Thu, Jul 04, 2013 at 08:57:34AM +0800, Chen Gang wrote:
>> > 'COMPILE_TEST=y' will let 'asm-generic' provide self checking sevices to
>> > both modules and architectures (especially with allmodconfig and
>> > "EXTRA_CFLAGS=-W")
> No it doesn't.
>
"If
During some perf-record sessions of the kernel running the high_systime
workload of the AIM7 benchmark, it was found that quite a large portion
of the spinlock contention was due to the perf_event_mmap_event()
function itself. This perf kernel function calls d_path() which,
in turn, call
>From 8b278828cb439b3b9b723a1de28ae10ce3e0cc44 Mon Sep 17 00:00:00 2001
From: Henrik Nordstrom
Date: Thu, 4 Jul 2013 03:24:41 +0200
Subject: [PATCH] tty/8250_early: Don't truncate last character of options
the 3,9 change to use strlcpy to save options uncovered a bug in the
options argument
> >
> > this bug caused by commit
> >f5fb976520a53f45f8bbf2e851f16b3b5558d485
> > ---
>
> You forgot to sign off this patch, can I add
>
> Signed-off-by: 张忠山
>
> like you did in the previous versions? Otherwise, the patch looks OK.
>
> Michal
Of course, you can.
--
Best Regards,
zzs
--
> -Original Message-
> From: Stefano Stabellini [mailto:stefano.stabell...@eu.citrix.com]
> Sent: Thursday, July 04, 2013 1:00 AM
> To: Jaeyong Yoo
> Cc: xen-de...@lists.xen.org; linux-arm-ker...@lists.infradead.org; linux-
> ker...@vger.kernel.org; Will Deacon; Arnd Bergmann; Olof
On Wed, 2013-07-03 at 18:12 -0700, Greg KH wrote:
> confused,
Good. I thought I was the only one. Confusion loves company, that way we
can follow each other around in endless circles.
-- Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message
On 07/04/2013 05:57 AM, Rafael J. Wysocki wrote:
> On Tuesday, July 02, 2013 10:01:27 PM Aaron Lu wrote:
>> Drivers may need to make policy decisions based on the OS that the firmware
>> believes it's interacting with. ACPI firmware will make a series of _OSI
>> calls, starting from the oldest OS
On Wed, Jul 03, 2013 at 08:59:39PM +0200, Laurent Pinchart wrote:
> Hi Magnus,
>
> Thank you for the patch.
>
> On Wednesday 03 July 2013 13:14:32 Magnus Damm wrote:
> > From: Magnus Damm
> >
> > Register the GPIO pin range, and request and free GPIO pins using the
> > pinctrl API. The
Hi Richard,
On 7/3/2013 23:51, Richard Genoud wrote:
>but there's a violent hang (kernel stops, no trace) when I try the record :
>arecord -v -V stereo -Dplug:default -f cd -t wav -c 2 /tmp/toto.wav
>last thing I see is :
>dma dma0chan3: atc_control (3)
I don't meet this issue. Playback and
On Thu, Jun 20, 2013 at 04:17:13PM -0400, Matthew Wilcox wrote:
>
> A paper at FAST2012
> (http://static.usenix.org/events/fast12/tech/full_papers/Yang.pdf) pointed
> out the performance overhead of taking interrupts for low-latency block
> I/Os. The solution the author investigated was to spin
On Thu, Jul 04, 2013 at 08:57:34AM +0800, Chen Gang wrote:
> 'asm-generic' neither belongs to architectures nor belongs to modules,
> it provides public services to both modules and architectures.
That sentence does not make any sense to me.
> 'COMPILE_TEST=y' will let 'asm-generic' provide self
'asm-generic' neither belongs to architectures nor belongs to modules,
it provides public services to both modules and architectures.
'COMPILE_TEST=y' will let 'asm-generic' provide self checking sevices to
both modules and architectures (especially with allmodconfig and
"EXTRA_CFLAGS=-W")
For
On Wed, Jul 03, 2013 at 08:15:52PM +0800, Jason Wang wrote:
> Commit 55257d72bd1c51f25106350f4983ec19f62ed1fa (virtio-net: fill only rx
> queues
> which are being used) tries to refill on demand when changing the number of
> channels by call try_refill_recv() directly, this may race:
>
> - the
This patch remove unused nr_partials variable.
Acked-by: Christoph Lameter
Signed-off-by: Wanpeng Li
---
mm/slub.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/mm/slub.c b/mm/slub.c
index 4649ff0..84b84f4 100644
--- a/mm/slub.c
+++ b/mm/slub.c
@@ -5269,7 +5269,6 @@
Slab have some tunables like limit, batchcount, and sharedfactor can be
tuned through function slabinfo_write. Commit (b7454ad3: mm/sl[au]b: Move
slabinfo processing to slab_common.c) uncorrectly change /proc/slabinfo
unwriteable for slab, this patch fix it by revert to original mode.
Acked-by:
Use existing interface node_nr_slabs and node_nr_objs to get
nr_slabs and nr_objs.
Acked-by: Christoph Lameter
Signed-off-by: Wanpeng Li
---
mm/slub.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/mm/slub.c b/mm/slub.c
index 84b84f4..d9135a8 100644
--- a/mm/slub.c
+++
This patch shares s_next and s_stop between slab and slub.
Acked-by: Christoph Lameter
Signed-off-by: Wanpeng Li
---
mm/slab.c| 10 --
mm/slab.h| 3 +++
mm/slab_common.c | 4 ++--
3 files changed, 5 insertions(+), 12 deletions(-)
diff --git a/mm/slab.c b/mm/slab.c
Changelog:
v1 -> v2:
* Fix the callers that pass # of objects. Make sure they pass # of slabs.
v2 -> v3:
* introduce helper function slabs_tofree
The drain_freelist is called to drain slabs_free lists for cache reap,
cache shrink, memory hotplug callback etc. The tofree parameter should
be
* Dave Chinner (da...@fromorbit.com) wrote:
> On Wed, Jul 03, 2013 at 10:53:08AM -0400, Jeff Moyer wrote:
> > Mel Gorman writes:
> >
> > >> > I just tried replacing my sync_file_range()+fadvise() calls and instead
> > >> > pass the O_DIRECT flag to open(). Unfortunately, I must be doing
> > >> >
1 - 100 of 1436 matches
Mail list logo