On Thu, 17 Jan 2013 14:52:52 -0800
Cody P Schafer wrote:
> Summaries:
> 1 - avoid repeating checks for section in page flags by adding a define.
> 2 - add & switch to zone_end_pfn() and zone_spans_pfn()
> 3 - adds zone_is_initialized() & zone_is_empty()
> 4 - adds a VM_BUG using zone_is_initializ
On Sat, Feb 02, 2013 at 04:07:59AM +0400, Sergei Shtylyov wrote:
> Hello.
>
> On 02-02-2013 1:30, Russell King - ARM Linux wrote:
>
>>> On Fri, Feb 01, 2013 at 11:49:11PM +0300, Sergei Shtylyov wrote:
> good point, do you wanna send some patches ?
>
I have already sent them countless t
On Fri, Feb 1, 2013 at 4:44 PM, Darrick J. Wong wrote:
> This is a patch to migrate STEC's enhanceio driver out of their github
> repository and into the staging tree. From their README:
>
> "EnhanceIO driver is based on EnhanceIO SSD caching software product developed
> by STEC Inc. EnhanceIO wa
On Sat, Nov 03, 2012 at 11:58:30AM +0100, Julia Lawall wrote:
> From: Julia Lawall
>
> Use WARN rather than printk followed by WARN_ON(1), for conciseness.
>
> A simplified version of the semantic patch that makes this transformation
> is as follows: (http://coccinelle.lip6.fr/)
>
> //
> @@
>
On Fri, Feb 1, 2013 at 4:57 PM, Michel Lespinasse wrote:
> On Fri, Feb 1, 2013 at 4:44 PM, Darrick J. Wong
> wrote:
>> This is a patch to migrate STEC's enhanceio driver out of their github
>> repository and into the staging tree. From their README:
>>
>> "EnhanceIO driver is based on EnhanceIO
Also, where's the end user documentation?
On Fri, Feb 1, 2013 at 5:23 PM, Kent Overstreet wrote:
> On Fri, Feb 1, 2013 at 4:57 PM, Michel Lespinasse wrote:
>> On Fri, Feb 1, 2013 at 4:44 PM, Darrick J. Wong
>> wrote:
>>> This is a patch to migrate STEC's enhanceio driver out of their github
>>
> And there's a patchset [1] from Jiri to support some kind of formula -
> yeah, now I've written the correct spelling. :) - that might fit to this
> purpose if you provide suitable formula file IMHO. So I guess we don't
> need to have another command and can reuse perf stat, no?
Yes with a prope
On Fri, Feb 01, 2013 at 05:25:29PM -0800, Kent Overstreet wrote:
> Also, where's the end user documentation?
I was trying not to explode this patch's size, since the doc can go straight
into Documentation/ without as much fuss as, say, the ~1600 checkpatch
warnings and all the other comments we'll
From: Andi Kleen
This avoids some problems with spurious PMIs on Haswell.
Haswell seems to behave more like P4 in this regard. Do
the same thing as the P4 perf handler by unmasking
the NMI only at the end. Shouldn't make any difference
for earlier non P4 cores.
Signed-off-by: Andi Kleen
---
ar
This is based on v7 of the full Haswell PMU support, but
ported to the latest perf/core and stripped down to the
extreme "perf for dummies" edition as requested.
I removed some more patches, these will come soon later.
I moved parts of an later patch (counter constraints for qualifiers)
into a
From: Andi Kleen
Add basic Haswell PMU support.
Similar to SandyBridge, but has a few new events and two
new counter bits.
There are some new counter flags that need to be prevented
from being set on fixed counters, and allowed to be set
for generic counters.
Also we add support for the counte
From: Andi Kleen
Add basic PEBS support for Haswell.
The constraints are similar to SandyBridge with a few new events.
v2: Readd missing pebs_aliases
v3: Readd missing hunk. Fix some constraints.
v4: Fix typo in PEBS event table (Stephane Eranian)
Reviewed-by: Stephane Eranian
Signed-off-by: An
From: Andi Kleen
Recent Intel CPUs have a new alternative MSR range for perfctrs that allows
writing the full counter width. Enable this range if the hardware reports it
using a new capability bit. This lowers overhead of perf stat slightly because
it has to do less interrupts to accumulate the c
From: Andi Kleen
Add support for the v2 PEBS format. It has a superset of the v1 PEBS
fields, but has a longer record so we need to adjust the code paths.
The main advantage is the new "EventingRip" support which directly
gives the instruction, not off-by-one instruction. So with precise == 2
we
Hi,
After merging the nfsd tree, today's linux-next build (x86_64
allmodconfig) failed like this:
fs/nfs/dns_resolve.c: In function 'nfs_dns_resolver_cache_init':
fs/nfs/dns_resolve.c:375:4: error: 'struct cache_detail' has no member named
'cache_upcall'
fs/nfs/dns_resolve.c:375:35: warning: lef
Hello.
On 02-02-2013 4:44, Russell King - ARM Linux wrote:
On Fri, Feb 01, 2013 at 11:49:11PM +0300, Sergei Shtylyov wrote:
good point, do you wanna send some patches ?
I have already sent them countless times and even stuck CPPI 4.1 support
(in
arch/arm/common/cppi41.c) in Russell's
>> intel_idle already uses a driver-specific flag:
>>
>> #define CPUIDLE_FLAG_TLB_FLUSHED0x1
>>
>> This patch just uses 4 more bits along with that one.
>
> Ok. In this case it would make sense to move this flag out of the
> generic core code to the intel_idle.c file ?
This flag is a
On 2013/2/2 7:06, Bjorn Helgaas wrote:
> On Wed, Jan 30, 2013 at 9:10 AM, Jiang Liu wrote:
>> From: Jiang Liu
>>
>> With commit 4f535093cf8f6da8c "PCI: Put pci_dev in device tree as
>> early as possible", companion ACPI devices should be created before
>> creating correspoding PCI devices, otherw
End user documentation is on our github. I think it should go with the user
level utilities, rather than the kernel driver.
-Amit
> -Original Message-
> From: Kent Overstreet [mailto:koverstr...@google.com]
> Sent: Friday, February 01, 2013 5:25 PM
> To: Michel Lespinasse
> Cc: Darrick J.
On Sat, Feb 2, 2013 at 12:19 AM, wrote:
> diff --git a/drivers/cpufreq/cpufreq.c b/drivers/cpufreq/cpufreq.c
> @@ -1219,6 +1219,9 @@ unsigned int cpufreq_quick_get(unsigned int cpu)
> struct cpufreq_policy *policy = cpufreq_cpu_get(cpu);
> unsigned int ret_freq = 0;
>
> + i
On Sat, 2013-01-26 at 17:24 +0100, Frederic Weisbecker wrote:
> 2012/11/3 anish kumar :
> > From: anish kumar
> >
> > As no one is using the return value of irq_work_queue function
> > it is better to just make it void.
> >
> > Acked-by: Steven Rostedt
> > Signed-off-by: anish kumar
> > ---
> >
On Fri, 2013-02-01 at 09:59 -0500, Don Zickus wrote:
> On Fri, Feb 01, 2013 at 07:19:07PM +0530, anish kumar wrote:
> > From: anish kumar
> >
> > This watchdog_disabled flag is bit of cryptic.Howerver it's usefullnes is
> > multifold.
> > Uses are:
> > 1. Check if smpboot_register_percpu_thread
Hi all,
Today's linux-next merge of the net-next tree got a conflict in
drivers/net/vmxnet3/vmxnet3_drv.c between commit 6cdd20c380eb ("vmxnet3:
set carrier state properly on probe") from the net tree and commit
204a6e659439 ("vmxnet3: use netdev_ printk wrappers") from the net-next
tree.
I fixed
Hi all,
Today's linux-next merge of the net-next tree got a conflict in
net/ipv6/route.c between commit bd30e947207e ("ipv6: do not create
neighbor entries for local delivery") from the net tree and commit
c440f1609b65 ("ipv6: Do not depend on rt->n in ip6_pol_route()") from the
net-next tree.
I
On Sat, Feb 2, 2013 at 12:15 AM, wrote:
> From: Dirk Brandewie
>
> Scaling drivers that implement cpufreq_driver.setpolicy() have
> internal governors and may/will change the current operating frequency
> very frequently this will cause cpufreq_out_of_sync() to be called
> every time. Only call
On Sat, Feb 2, 2013 at 12:15 AM, wrote:
> From: Dirk Brandewie
>
> Scaling drivers that implement internal governors do not have governor
> structures assocaited with them. Only track the name of the governor
> associated with the CPU if the driver does not implement
> cpufreq_driver.setpolicy(
On Sat, Dec 01, 2012 at 11:33:41PM +, Cong Ding wrote:
> it is unnecessary to check i<4 after the loop. just do it before the break.
>
> Signed-off-by: Cong Ding
Thanks, applied.
- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux
Hi Artem,
After merging the l2-mtd tree, today's linux-next build (x86_64
allmodconfig) produced these warnings:
In file included from drivers/mtd/chips/cfi_cmdset_0002.c:36:0:
include/linux/of_platform.h:107:13: warning: 'struct of_device_id' declared
inside parameter list [enabled by default]
2013/2/2 anish kumar :
> On Sat, 2013-01-26 at 17:24 +0100, Frederic Weisbecker wrote:
>> 2012/11/3 anish kumar :
>> > From: anish kumar
>> >
>> > As no one is using the return value of irq_work_queue function
>> > it is better to just make it void.
>> >
>> > Acked-by: Steven Rostedt
>> > Signed-
Shaohua,
In next-20130128, commit 174f064 "swap: make each swap partition have
one address_space" (from the mm/akpm tree) appears causes a hang/RCU
stall for me when hot-unplugging a CPU.
I'm running on a quad-core ARM system, and hot-unplugging a CPU using:
echo 0 > /sys/devices/system/cpu/cpu2
The return statement after BUG() is invalid, move BUG() to the default choice
of the switch.
Signed-off-by: Jie Liu
---
kernel/res_counter.c |5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/kernel/res_counter.c b/kernel/res_counter.c
index ff55247..748a3bc 100644
---
Hi all,
After merging the tip tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
arch/powerpc/perf/power7-pmu.c:397:2: error: initialization from incompatible
pointer type [-Werror]
arch/powerpc/perf/power7-pmu.c:397:2: error: (near initialization for
'power7_events_attr
On Sat, Feb 2, 2013 at 12:15 AM, wrote:
> From: Dirk Brandewie
>
> Scaling drivers that implement internal governors do not have governor
> sturctures associated with them. Do not create/remove statisitcs
> entries for polices that do not have governors associated with them.
>
> Signed-off-by:
On Sat, Feb 2, 2013 at 12:15 AM, wrote:
> From: Dirk Brandewie
>
> There is an additional reference added to the driver in
> cpufreq_add_dev_policy() that is removed in__cpufreq_governor() if the
> driver implements target(). Remove the last reference when the driver
> implements setpolicy()
>
Hi all,
After merging the tip tree, today's linux-next build (x86_64 allmodconfig)
produced this warning:
arch/x86/kernel/kvm.c: In function 'kvm_register_steal_time':
arch/x86/kernel/kvm.c:302:3: warning: format '%lx' expects argument of type
'long unsigned int', but argument 3 has type 'phys_a
Hi all,
Today's linux-next merge of the kvm tree got a conflict in
arch/x86/include/asm/vmx.h between commit af170c5061dd ("UAPI: (Scripted)
Disintegrate arch/x86/include/asm") from Linus' tree and commits
83d4c286931c ("x86, apicv: add APICv register virtualization support")
and c7c9c56ca26f ("x8
On 2 February 2013 11:14, Dirk Brandewie wrote:
> Hi viresh,
>
> This is based on 3.8-rc5. I think this should work against bleeding_edge
> but I have not tested against bleeding_edge
Rafael wouldn't be able to apply these patches. There are a lot of core patches
present in bleeding_edge.
--
To
Hi all,
After merging the tip tree, today's linux-next build (x86_64 allmodconfig)
produced this warning:
arch/x86/kernel/kvm.c: At top level:
arch/x86/kernel/kvm.c:509:2: warning: initialization from incompatible pointer
type [enabled by default]
arch/x86/kernel/kvm.c:509:2: warning: (near init
Hi all,
After merging the tip tree, today's linux-next build (x86_64 allmodconfig)
produced this warning:
arch/x86/mm/numa.c: In function 'setup_node_data':
arch/x86/mm/numa.c:222:3: warning: passing argument 1 of '__phys_addr_nodebug'
makes integer from pointer without a cast [enabled by defaul
On Fri, Feb 1, 2013 at 10:51 PM, Joerg Roedel wrote:
> Cho,
>
> On Wed, Jan 02, 2013 at 02:53:49PM +0900, KyongHo Cho wrote:
>> On Tuesday, January 1, 2013, Sylwester Nawrocki
>>
>
>> > Cc: devicetree-disc...@lists.ozlabs.org
>
> Since patch 7 of this set is already merged, do you mind to re-pos
Hi. Jan.
Sorry for interrupt.
Have you taken this patch to your tree ? I can not find it..
or Is there any issue regarding this patch ?
Thanks!
2013/1/22, Namjae Jeon :
> 2013/1/22, Jan Kara :
>> On Tue 22-01-13 09:45:09, Namjae Jeon wrote:
>>> 2013/1/21, Jan Kara :
>>> > @@ -,6 +2219,8 @@ i
When an eventfd is closed, a wakeup with POLLHUP will be issued,
but cgroup wants to issue wakeup explicitly, so when a cgroup is
removed userspace can be notified.
Signed-off-by: Li Zefan
---
fs/eventfd.c| 11 +++
include/linux/eventfd.h | 5 +
2 files changed, 16 inser
commit 205a872bd6f9a9a09ef035ef1e90185a8245cc58 ("cgroup: fix lockdep
warning for event_control") sovled a deadlock by introducing a new
bug.
We can't access @event without event_list_lock, otherwise we'll race
with cgroup_event_wake() called when closing the eventfd, and then
both threads will tr
There're three bugs.
- If thread A is removing a cgroup, while thread B is closing an eventfd, the
two threads might free the same cgroup event and thus crash the kernel.
This is fixed by patch #1 and patch #2.
- If there're multiple threads are blocking in read() on the same eventfd,
and someon
Currently when a cgroup is removed, it calls eventfd_signal() for
each registered cgroup event, so userspace can be notified and blocked
reads can be unblocked.
The problem is, if we have multiple threads blocked on the same eventfd,
only one of them will be unlocked.
This patch makes sure all op
If read() returns with errno == EIDRM, we know the cgroup has been
removed.
Signed-off-by: Li Zefan
---
tools/cgroup/cgroup_event_listener.c | 12 +---
1 file changed, 5 insertions(+), 7 deletions(-)
diff --git a/tools/cgroup/cgroup_event_listener.c
b/tools/cgroup/cgroup_event_listener
(forgot to cc Kirill A. Shutemov , added)
On 2013/2/2 14:50, Li Zefan wrote:
> There're three bugs.
>
> - If thread A is removing a cgroup, while thread B is closing an eventfd, the
> two threads might free the same cgroup event and thus crash the kernel.
>
> This is fixed by patch #1 and patch
On Saturday 02 February 2013 02:31 AM, Matt Porter wrote:
Convert dmaengine channel requests to use
dma_request_slave_channel_compat(). This supports platforms booting
with or without DT populated.
Signed-off-by: Matt Porter
Acked-by: Tony Lindgren
---
Acked-by: Santosh Shilimkar
--
To unsub
On Saturday 02 February 2013 02:31 AM, Matt Porter wrote:
The binding definition is based on the generic DMA request binding.
Signed-off-by: Matt Porter
Acked-by: Tony Lindgren
---
Acked-by: Santosh Shilimkar
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the
2013/2/2 Michael Kerrisk (man-pages) :
>
> On Jan 30, 2013 8:05 AM, "Andrey Vagin" wrote:
>>
>> If signalfd is created with the flag SFD_PEEK, it reads siginfo-s
>> without dequeuing signals.
>>
>> For reading not first siginfo pread(fd, buf, size, pos) can be used,
>> where ppos / sizeof(signalfd
601 - 650 of 650 matches
Mail list logo
