(2013/01/07 23:02), Steven Rostedt wrote:
> From: Steven Rostedt
>
> If some other kernel subsystem has a module notifier, and adds a kprobe
> to a ftrace mcount point (now that kprobes work on ftrace points),
> when the ftrace notifier runs it will fail and disable ftrace, as well
> as kprobes
On Thu, Dec 20, 2012 at 10:43 PM, wrote:
> From: Zhi Yong Wu
>
> HI, guys,
>
> This patchset has been done scalability or performance tests
> by fs_mark, ffsb and compilebench.
> I have done the perf testing on Linux 3.7.0-rc8+ with Intel(R) Core(TM)
> i7-3770 CPU @ 3.40GHz with 8 CPUs, 16G
Switch cgroup to use the new hashtable implementation. No functional changes.
Signed-off-by: Li Zefan
---
kernel/cgroup.c | 92 -
1 file changed, 39 insertions(+), 53 deletions(-)
diff --git a/kernel/cgroup.c b/kernel/cgroup.c
index
With 749fefe677 in v3.7 ("block: lift the initial queue bypass mode
on blk_register_queue() instead of blk_init_allocated_queue()"),
the following warning appears when multipath is used with CONFIG_PREEMPT=y.
This patch moves blk_queue_bypass_start() before radix_tree_preload()
to avoid the
On Mon, Jan 07, 2013 at 05:51:46PM +0900, Kamezawa Hiroyuki wrote:
[...]
> I'm just curious..
Thanks for taking a look! :)
[...]
> > +/*
> > + * The window size is the number of scanned pages before we try to analyze
> > + * the scanned/reclaimed ratio (or difference).
> > + *
> > + * It is used
On 01/08/2013 01:21 AM, Alan Stern wrote:
> On Sun, 6 Jan 2013, Aaron Lu wrote:
>
>> From: Lin Ming
>>
>> When a request is added:
>> If device is suspended or is suspending and the request is not a
>> PM request, resume the device.
>>
>> When the last request finishes:
>> Call
From: Pritesh Raithatha
NVIDIA's Tegra114 added two more configuration parameter in pinmux i.e.
rcv-sel and drive type.
rcv-sel: Select between High and Normal VIL/VIH receivers.
RCVR_SEL=1: High VIL/VIH
RCVR_SEL=0: Normal VIL/VIH
drv_type: Ouptput drive type:
33-50 ohm
On 01/08/2013 01:11 AM, Alan Stern wrote:
> On Sun, 6 Jan 2013, Aaron Lu wrote:
>
>> In August 2010, Jens and Alan discussed about "Runtime PM and the block
>> layer". http://marc.info/?t=12825910841=1=2
>> And then Alan has given a detailed implementation guide:
>>
Signed-off-by: Alexandre Courbot
---
Documentation/gpio.txt | 94 --
1 file changed, 92 insertions(+), 2 deletions(-)
diff --git a/Documentation/gpio.txt b/Documentation/gpio.txt
index 77a1d11..871ccda 100644
--- a/Documentation/gpio.txt
+++
With the current API, GPIOs are represented by a unique integer. This
causes problems in terms of security (GPIO numbers can be arbitrarily
forged and used without proper allocation) and flexibility (the maximum
number of GPIOs that the system can handle is fixed at compilation time
and a static
Adds new GPIO allocation functions that work with the opaque descriptor
interface.
Signed-off-by: Alexandre Courbot
---
drivers/gpio/gpiolib.c| 164 ++
include/linux/gpio/consumer.h | 8 +++
include/linux/gpio/driver.h | 21 ++
3 files
Convert gpiolib-of.c's internals to rely on descriptors instead of
integers and add the gpiod_ counterparts of existing OF functions.
Signed-off-by: Alexandre Courbot
---
drivers/gpio/gpiolib-of.c | 26 +--
include/linux/gpio/consumer.h | 56 +
This series introduce a first take at implementing the RFC for the new GPIO API
that I submitted last month. It proposes a new, opaque descriptor-based GPIO API
that becomes available when GPIOlib is compiled, and provides a safer, more
abstract alternative to the current integer-based interface.
On Thu, Dec 20, 2012 at 10:12:56AM +0100, Boris BREZILLON wrote:
> Hi,
>
> Sorry for resend. The previous version still has alignment issues on
> atmel_tcb_pwm_set_polarity, atmel_tcb_pwm_request and
> atmel_tcb_pwm_config function parameters.
>
> This patch adds a PWM driver based on Atmel
On Wed, Dec 19, 2012 at 05:00:09PM +, Grant Likely wrote:
> On Sat, 10 Nov 2012 18:07:42 +0100, Thierry Reding
> wrote:
> > On Fri, Nov 09, 2012 at 10:28:38AM -0700, Stephen Warren wrote:
> > > On 11/09/2012 10:10 AM, Mark Brown wrote:
> > > > On Fri, Nov 09, 2012 at 10:04:56AM -0700,
On 01/08/2013 12:09 AM, H. Peter Anvin wrote:
On 01/07/2013 09:08 PM, Rik van Riel wrote:
On 01/08/2013 12:03 AM, H. Peter Anvin wrote:
On 01/07/2013 08:55 PM, Shaohua Li wrote:
I searched a little bit, the change (doing TLB flush to clear access
bit) is
made between 2.6.7 - 2.6.8, I can't
On 01/05/2013 04:06 PM, Russell King - ARM Linux wrote:
> On Thu, Jan 03, 2013 at 06:58:38PM -0800, Srivatsa Vaddagiri wrote:
>> I also think that the
>> wait_for_completion() based wait in ARM's __cpu_die() can be replaced with a
>> busy-loop based one, as the wait there in general should be
Hello,
On 1/6/2013 6:29 PM, Federico Vaga wrote:
This is useful when you need to specify specific GFP flags during memory
allocation (e.g. GFP_DMA).
Signed-off-by: Federico Vaga
---
drivers/media/v4l2-core/videobuf2-dma-contig.c | 7 ++-
include/media/videobuf2-dma-contig.h |
>
>>>>>> ERROR: "trace_clock_local" [kernel/rcutorture.ko] undefined!
>>>>>
>>>>> Hello, Randy,
>>>>>
>>>>> Did your build include the following, also pushed to -next in that same
>>>>> batch from
On 1/7/2013 9:15 PM, Mauro Carvalho Chehab wrote:
Em Mon, 7 Jan 2013 12:40:50 -0700
Jonathan Corbet escreveu:
> On Mon, 7 Jan 2013 00:09:47 +0100
> Alessandro Rubini wrote:
>
> > I don't expect you'll see serious performance differences on the PC. I
> > think ARM users will have better
On Mon, Jan 07, 2013 at 20:02 -0800, Casey Schaufler wrote:
> On 1/7/2013 7:01 PM, Stephen Rothwell wrote:
> > Let me ask Andrew's question: Why do you want to do this (what is the
> > use case)? What does this gain us?
>
> There has been an amazing amount of development in system security
>
Instead of devfreq device driver explicitly calling devfreq suspend
and resume apis perhaps from runtime-pm suspend and resume callbacks,
let devfreq core handle it automatically.
Attach devfreq core to runtime-pm framework so that, devfreq device
driver pm_runtime_suspend() will automatically
On Mon, Jan 07, 2013 at 20:11 -0800, Casey Schaufler wrote:
> On 1/7/2013 7:59 PM, Stephen Rothwell wrote:
> > You probably also want to think a bit harder about the order of the
> > patches - you should introduce new APIs before you use them and remove
> > calls to functions before you remove the
The current reexecute_instruction can not well detect the failed instruction
emulation. It allows guest to retry all the instructions except it accesses
on error pfn
For example, some cases are nested-write-protect - if the page we want to
write is used as PDE but it chains to itself. Under this
Currently, reexecute_instruction refused to retry all instructions if
tdp is enabled. If nested npt is used, the emulation may be caused by
shadow page, it can be fixed by dropping the shadow page. And the only
condition that tdp can not retry the instruction is the access fault
on error pfn
Little cleanup for reexecute_instruction, also use gpa_to_gfn in
retry_instruction
Signed-off-by: Xiao Guangrong
---
arch/x86/kvm/x86.c | 13 ++---
1 files changed, 6 insertions(+), 7 deletions(-)
diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
index 1c9c834..08cacd9 100644
---
We have two issues in current code:
- if target gfn is used as its page table, guest will refault then kvm will use
small page size to map it. We need two #PF to fix its shadow page table
- sometimes, say a exception is triggered during vm-exit caused by #PF
(see handle_exception() in vmx.c),
If the write-fault access is from supervisor and CR0.WP is not set on the
vcpu, kvm will fix it by adjusting pte access - it sets the W bit on pte
and clears U bit. This is the chance that kvm can change pte access from
readonly to writable
Unfortunately, the pte access is the access of 'direct'
LM355x family devices provide flash, torch and indicator functions.
This patch support LED trigger feature.
Using LED trigger APIs(), other driver simply turn on/off the flash, torch
and indicator.
Platform data
the name of LED trigger is configurable.
Documentation
example and
> cgroups: fix cgroup_event_listener error handling
>
> The error handling in cgroup_event_listener.c did not correctly deal
> with either an error opening either or
> cgroup.event_control. Due to an uninitialized variable the program
> exit code was undefined if either of these opens failed.
>
>From aaea3405944d844f53679b295d4082584f33d9a3 Mon Sep 17 00:00:00 2001
From: ZhangYi
Date: Tue, 8 Jan 2013 13:50:09 +0800
Subject: [PATCH] mmc: correct the EXCEPTION_EVENTS_STATUS vaule comment
The right value is 54 according to eMMC 4.5 specification.
Signed-off-by: ZhangYi
---
On 01/07/2013 09:18 PM, Vincent Guittot wrote:
> On 2 January 2013 05:22, Preeti U Murthy wrote:
>> Hi everyone,
>> I have been looking at how different workloads react when the per entity
>> load tracking metric is integrated into the load balancer and what are
>> the possible reasons for it.
>>
SDMA uses firmware to expand some features for modules.
add SDMA firmware for i.mx6 series,
Signed-off-by: Gary Zhang
---
firmware/Makefile |1 +
firmware/imx/sdma/sdma-imx6q-to1.bin.ihex | 116 +
2 files changed, 117 insertions(+), 0
devfreq stats is not taking device suspend and resume into
account. Fix it.
Signed-off-by: Rajagopal Venkat
---
drivers/devfreq/devfreq.c | 15 ---
1 file changed, 12 insertions(+), 3 deletions(-)
diff --git a/drivers/devfreq/devfreq.c b/drivers/devfreq/devfreq.c
index
Mark the stats start time stamp when actual load monitoring is
started for accuracy.
Signed-off-by: Rajagopal Venkat
---
drivers/devfreq/devfreq.c |6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/drivers/devfreq/devfreq.c b/drivers/devfreq/devfreq.c
index
Set devfreq device min and max frequency limits when device
is added to devfreq, provided frequency table is supplied.
This helps governors to suggest target frequency with in
limits.
Signed-off-by: Rajagopal Venkat
---
drivers/devfreq/devfreq.c | 24
1 file changed,
On Tue, Jan 08, 2013 at 01:49:00PM +0800, Harvey Yang wrote:
> This patchset refines some spinlocks which maybe not used properly.
>
> [PATCH 1/2]: The function 'usbip_event_add()' may be called in interrupt
> context on the stub side:
>
On Wed, 2012-12-12 at 10:18 -0800, Joe Perches wrote:
> Remove the somewhat awkward uses of print_symbol and convert all the
> existing uses to a new vsprintf pointer type of %pSR.
Jiri? Are you going to do anything with this?
--
To unsubscribe from this list: send the line "unsubscribe
On Tue, Jan 08, 2013 at 01:49:01PM +0800, Harvey Yang wrote:
>
> Signed-off-by: Harvey Yang
You need to describe _why_ you did this, not just what you did. Why is
this needed? What are you fixing by doing this? Is this something that
older kernels need? Is it something that others are
Signed-off-by: Harvey Yang
---
drivers/staging/usbip/vhci_hcd.c | 76 --
drivers/staging/usbip/vhci_rx.c | 10 ++---
drivers/staging/usbip/vhci_tx.c | 14 +++
3 files changed, 42 insertions(+), 58 deletions(-)
diff --git
Signed-off-by: Harvey Yang
---
drivers/staging/usbip/stub_dev.c| 34 +-
drivers/staging/usbip/stub_rx.c |4 ++--
drivers/staging/usbip/usbip_event.c |6 --
3 files changed, 23 insertions(+), 21 deletions(-)
diff --git
This patchset refines some spinlocks which maybe not used properly.
[PATCH 1/2]: The function 'usbip_event_add()' may be called in interrupt
context on the stub side:
'stub_complete'->'stub_enqueue_ret_unlink'->'usbip_event_add'.
In this function it tries to get the lock 'ud->lock', so we
On 01/08/2013 02:50 AM, H Hartley Sweeten wrote:
On Monday, January 07, 2013 3:40 PM, Greg KH wrote:
On Sat, Jan 05, 2013 at 06:12:55PM +0400, Lijo Antony wrote:
Reduced line lengths to 80 chars by removing extra spaces.
Signed-off-by: Lijo Antony
---
On 01/07/2013 09:08 PM, Rik van Riel wrote:
> On 01/08/2013 12:03 AM, H. Peter Anvin wrote:
>> On 01/07/2013 08:55 PM, Shaohua Li wrote:
>>>
>>> I searched a little bit, the change (doing TLB flush to clear access
>>> bit) is
>>> made between 2.6.7 - 2.6.8, I can't find the changelog, but I found
On 01/08/2013 12:03 AM, H. Peter Anvin wrote:
On 01/07/2013 08:55 PM, Shaohua Li wrote:
I searched a little bit, the change (doing TLB flush to clear access bit) is
made between 2.6.7 - 2.6.8, I can't find the changelog, but I found a patch:
On 01/07/2013 08:55 PM, Shaohua Li wrote:
>
> I searched a little bit, the change (doing TLB flush to clear access bit) is
> made between 2.6.7 - 2.6.8, I can't find the changelog, but I found a patch:
>
On Mon, Jan 07, 2013 at 02:31:21PM -0800, H. Peter Anvin wrote:
> On 01/07/2013 07:14 AM, Rik van Riel wrote:
> > On 01/07/2013 03:12 AM, Shaohua Li wrote:
> >>
> >> We use access bit to age a page at page reclaim. When clearing pte
> >> access bit,
> >> we could skip tlb flush for the virtual
The caller of sched_sliced() should pass se.cfs_rq and se as the arguments,
however in sched_rr_get_interval() we gave it rq.cfs_rq and se, which made
the following compution obviously wrong.
The change was introduced by commit 77034937, while it had been correct
'cfs_rq_of'
before the commit.
Hi all,
Changes since 20130107:
The slave-dma tree lost its build failure.
The staging tree gained a build failure for which I applied a merge fix.
The drop-experimental tree gained conflicts against the net-next and Linus'
trees
On Tue, Jan 8, 2013 at 4:05 AM, Stephen Rothwell wrote:
> In commit 548860697046 ("dmaengine: dw_dmac: Enhance device tree
> support") (which was changed since yesterday :-(), an instance of
> __devinit has been added. We are in the process of making CONFIG_HOTPLUG
> always true, and since
On Tue, Jan 08, 2013 at 01:23:52PM +1100, Stephen Rothwell wrote:
> Hi Greg,
>
> After merging the staging tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/staging/comedi/comedi_fops.c: In function 'comedi_unlocked_ioctl':
>
Hi Greg,
On Mon, 7 Jan 2013 20:27:30 -0800 Greg KH wrote:
>
> On Tue, Jan 08, 2013 at 01:23:52PM +1100, Stephen Rothwell wrote:
> > Hi Greg,
> >
> > After merging the staging tree, today's linux-next build (x86_64
> > allmodconfig) failed like this:
> >
> >
On Mon, Jan 7, 2013 at 8:35 PM, Andrew Morton wrote:
> On Tue, 08 Jan 2013 10:25:35 +0900 Jingoo Han wrote:
>
>> On Tuesday, January 08, 2013 9:02 AM, Andrew Morton wrote
>> > On Fri, 04 Jan 2013 17:29:11 +0900
>> > Jingoo Han wrote:
>> >
>> > > NULL deference of name is checked when device is
* Russell King - ARM Linux [2013-01-05 10:36:27]:
> On Thu, Jan 03, 2013 at 06:58:38PM -0800, Srivatsa Vaddagiri wrote:
> > I also think that the
> > wait_for_completion() based wait in ARM's __cpu_die() can be replaced with a
> > busy-loop based one, as the wait there in general should be
On Mon, Jan 07, 2013 at 02:19:15PM -0800, Paul E. McKenney wrote:
> On Mon, Jan 07, 2013 at 09:56:06AM -0800, Josh Triplett wrote:
> > On Mon, Jan 07, 2013 at 08:57:48AM -0800, Paul E. McKenney wrote:
> > > On Mon, Jan 07, 2013 at 07:58:10AM -0800, Josh Triplett wrote:
> > > > This patch seems
On 1/7/2013 7:59 PM, Stephen Rothwell wrote:
> Hi Casey,
>
> On Tue, 8 Jan 2013 14:01:59 +1100 Stephen Rothwell
> wrote:
>> Let me ask Andrew's question: Why do you want to do this (what is the
>> use case)? What does this gain us?
>>
>> Also, you should use unique subjects for each of the
On Tue, Jan 08, 2013 at 03:08:26AM +0100, Frederic Weisbecker wrote:
> If we are interrupting userspace, we don't need to keep
> the tick for RCU: quiescent states don't need to be reported
> because we soon run in userspace and local callbacks are handled
> by the nocb threads.
>
> CHECKME: Do
Hi Steven,
On 8 January 2013 03:59, Steven Rostedt wrote:
> On Mon, 2013-01-07 at 23:29 +0530, Viresh Kumar wrote:
>
>> > By default, I would suggest for cache locality,
>> > that we try to keep it on the same CPU. But if there's a better CPU to
>> > run on, it runs there.
>>
>> That would break
On 1/7/2013 7:01 PM, Stephen Rothwell wrote:
> Hi Casey,
>
> On Mon, 07 Jan 2013 17:54:24 -0800 Casey Schaufler
> wrote:
>> Subject: [PATCH v12 0/9] LSM: Multiple concurrent LSMs
>>
>> Change the infrastructure for Linux Security Modules (LSM)s
>> from a single vector of hook handlers to a list
Hi Casey,
On Tue, 8 Jan 2013 14:01:59 +1100 Stephen Rothwell
wrote:
>
> Let me ask Andrew's question: Why do you want to do this (what is the
> use case)? What does this gain us?
>
> Also, you should use unique subjects for each of the patches in the
> series.
You probably also want to
al" [kernel/rcutorture.ko] undefined!
> > > >
> > > > Hello, Randy,
> > > >
> > > > Did your build include the following, also pushed to -next in that same
> > > > batch from -rcu? Including Steven Rostedt on CC for his take.
> > >
On Mon, Jan 7, 2013 at 7:13 PM, Eric W. Biederman wrote:
> I meant we should detect failure to allocate bounce buffers in in
> swiotlb_init() instead of panicing.
>
> I meant swiotlb_map_single() should either panic or simply fail.
>
> If I have read lib/swiotlb.c correctly the only place we
On Mon, Jan 07, 2013 at 02:18:38PM -0500, Vivien Didelot wrote:
> This patch renames the supply_uV* variables to supply_uv* to avoid
> CamelCase as warned by the checkpatch.pl script.
>
> Signed-off-by: Vivien Didelot
Applied to -next.
Thanks,
Guenter
--
To unsubscribe from this list: send the
From: Joe Perches
Date: Sun, 06 Jan 2013 15:34:49 -0800
> Use more current logging styles.
>
> Convert printks to pr_ and
> printks with ("%s: ...", dev->name to netdev_(dev, "...
>
> Add pr_fmt #defines where appropriate.
> Coalesce formats.
> Use pr__once where appropriate.
>
>
Fix incorrect bit test that originally showed up in
4ee823b83bc9851743fab756c76b27d6a1e2472b: use '&' instead of '&&'.
Signed-off-by: Nickolai Zeldovich
---
drivers/usb/host/xhci-ring.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/host/xhci-ring.c
On Mon, Jan 7, 2013 at 6:44 PM, Mika Westerberg
wrote:
> In addition fix following warnings seen when compiling 64-bit:
>
> drivers/spi/spi-pxa2xx.c: In function ‘map_dma_buffers’:
> drivers/spi/spi-pxa2xx.c:384:7: warning: cast from pointer to integer of
> different size
Hi Kees,
Today's linux-next merge of the drop-experimental tree got a conflict in
drivers/net/ethernet/intel/Kconfig between commit c56283034ce2 ("pps,
ptp: Remove dependencies on EXPERIMENTAL") from Linus' tree, commit
483f777266f5 ("drivers/net: remove orphaned references to micro channel")
On Mon, 7 Jan 2013, Andrew Morton wrote:
> ---
> a/mm/compaction.c~mm-compaction-fix-echo-1-compact_memory-return-error-issue-fix
> +++ a/mm/compaction.c
> @@ -1150,7 +1150,7 @@ unsigned long try_to_compact_pages(struc
>
>
> /* Compact all zones within a node */
> -static int
Hi Kees,
Today's linux-next merge of the drop-experimental tree got conflicts in
drivers/net/ethernet/8390/Kconfig and drivers/net/ethernet/i825xx/Kconfig
between commits 483f777266f5 ("drivers/net: remove orphaned references to
micro channel") from the net-next tree and commits 16f5471ff2da
On Sun, 6 Jan 2013, Jason Liu wrote:
> when run the folloing command under shell, it will return error
> sh/$ echo 1 > /proc/sys/vm/compact_memory
> sh/$ sh: write error: Bad address
>
> After strace, I found the following log:
> ...
> write(1, "1\n", 2) = 3
> write(1, "",
Hi Shaohua,
On Mon, 2013-01-07 at 16:12 +0800, Shaohua Li wrote:
> We use access bit to age a page at page reclaim. When clearing pte access bit,
Who sets this flag to pte? mmu? tlb?
> we could skip tlb flush for the virtual address. The side effect is if the pte
> is in tlb and pte access bit
Yinghai Lu writes:
> On Mon, Jan 7, 2013 at 6:22 PM, Eric W. Biederman
> wrote:
>> Yinghai I sat down and read your patch and the approach you are taking
>> is totally wrong.
>
> Thanks for check the patch, did you check v3?
I looked at the version of the patch you had as an attachment. I
On Mon, Jan 7, 2013 at 4:42 PM, Thomas Renninger wrote:
> memmap=256M$3584M
may need to change to:
memmap=256M\$\$3584M
Thanks
Yinghai
--
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
Paolo Bonzini writes:
> Il 07/01/2013 01:02, Rusty Russell ha scritto:
>> Paolo Bonzini writes:
>>> Il 02/01/2013 06:03, Rusty Russell ha scritto:
Paolo Bonzini writes:
> The virtqueue_add_buf function has two limitations:
>
> 1) it requires the caller to provide all the
Konrad Rzeszutek Wilk writes:
> On Mon, Jan 07, 2013 at 06:22:51PM -0800, Eric W. Biederman wrote:
>> Shuah Khan writes:
>>
>> > On Mon, Jan 7, 2013 at 8:26 AM, Konrad Rzeszutek Wilk
>> > wrote:
>> >> On Fri, Jan 04, 2013 at 02:10:25PM -0800, Yinghai Lu wrote:
>> >>> On Fri, Jan 4, 2013 at
Hi Casey,
On Mon, 07 Jan 2013 17:54:24 -0800 Casey Schaufler
wrote:
>
> Subject: [PATCH v12 0/9] LSM: Multiple concurrent LSMs
>
> Change the infrastructure for Linux Security Modules (LSM)s
> from a single vector of hook handlers to a list based method
> for handling multiple concurrent
On Mon, Jan 7, 2013 at 6:22 PM, Eric W. Biederman wrote:
> Yinghai I sat down and read your patch and the approach you are taking
> is totally wrong.
Thanks for check the patch, did you check v3?
>
> The problem is that swiotlb_init() in lib/swiotlb.c does not know how to
> fail without
On Mon, Jan 07, 2013 at 06:22:51PM -0800, Eric W. Biederman wrote:
> Shuah Khan writes:
>
> > On Mon, Jan 7, 2013 at 8:26 AM, Konrad Rzeszutek Wilk
> > wrote:
> >> On Fri, Jan 04, 2013 at 02:10:25PM -0800, Yinghai Lu wrote:
> >>> On Fri, Jan 4, 2013 at 1:02 PM, Shuah Khan wrote:
> >>> >
On Mon, 7 Jan 2013, Simon Jeons wrote:
> On Thu, 2013-01-03 at 13:24 +0100, Petr Holasek wrote:
> > Hi Simon,
> >
> > On Mon, 31 Dec 2012, Simon Jeons wrote:
> > > On Fri, 2012-12-28 at 02:32 +0100, Petr Holasek wrote:
> > > >
> > > > v7: - added sysfs ABI documentation for KSM
> > >
> > >
If kzalloc returns NULL, do not dereference the said NULL pointer as the
first argument to dev_err(); use >dev instead. Similarly, before
sisusb->sisusb_dev has been initialized to dev, use dev_err(>dev)
instead.
Signed-off-by: Nickolai Zeldovich
---
drivers/usb/misc/sisusbvga/sisusb.c |4
On 1/7/13 5:36 PM, Steven Rostedt wrote:
> This patch is obsoleted by:
>
> https://lkml.org/lkml/2012/12/13/710
>
> Which I just got the automated reply, and it's in Greg's staging tree
> now.
>
> When I get time, I do want to try to get this driver (and device)
> working on my ppc64 box.
Ok,
Change several memcpy() to memmove() in cases when the regions are
definitely overlapping; memcpy() of overlapping regions is undefined
behavior in C and can produce different results depending on the compiler,
the memcpy implementation, etc.
Signed-off-by: Nickolai Zeldovich
---
[CC avr32 maintainers]
On Mon, Jan 07, 2013 at 12:20:52PM -0800, Andrew Morton wrote:
> On Mon, 07 Jan 2013 12:45:36 +0800
> kbuild test robot wrote:
>
> > tree: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> > akpm
> > head: e862d51dae9808e394a118ca1692f09bf0751aba
>
Hi Greg,
After merging the staging tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/staging/comedi/comedi_fops.c: In function 'comedi_unlocked_ioctl':
drivers/staging/comedi/comedi_fops.c:1665:4: error: 'dev_file_info' undeclared
(first use in this function)
Shuah Khan writes:
> On Mon, Jan 7, 2013 at 8:26 AM, Konrad Rzeszutek Wilk
> wrote:
>> On Fri, Jan 04, 2013 at 02:10:25PM -0800, Yinghai Lu wrote:
>>> On Fri, Jan 4, 2013 at 1:02 PM, Shuah Khan wrote:
>>> > Pani'cing the system doesn't sound like a good option to me in this
>>> > case. This
Subject: [PATCH v12 1/9] LSM: Multiple concurrent LSMs
Change the infrastructure for Linux Security Modules (LSM)s
from a single vector of hook handlers to a list based method
for handling multiple concurrent modules.
Changes for AppArmor. Abstract access to security blobs.
Remove commoncap
This is in preparation for the full dynticks feature. While
remotely reading the cputime of a task running in a full
dynticks CPU, we'll need to do some extra-computation. This
way we can account the time it spent tickless in userspace
since its last cputime snapshot.
Signed-off-by: Frederic
Subject: [PATCH v12 2/9] LSM: Multiple concurrent LSMs
Change the infrastructure for Linux Security Modules (LSM)s
from a single vector of hook handlers to a list based method
for handling multiple concurrent modules.
Remove security/capability.c as there is no longer need
of a "default" LSM.
Not for merge. This may become a real tracepoint.
Signed-off-by: Frederic Weisbecker
Cc: Alessio Igor Bogani
Cc: Andrew Morton
Cc: Chris Metcalf
Cc: Christoph Lameter
Cc: Geoff Levand
Cc: Gilad Ben Yossef
Cc: Hakan Akkan
Cc: Ingo Molnar
Cc: Li Zhong
Cc: Namhyung Kim
Cc: Paul E.
Wake up a CPU when a timer list timer is enqueued there and
the CPU is in full dynticks mode. Sending an IPI to it makes
it reconsidering the next timer to program on top of recent
updates.
Signed-off-by: Frederic Weisbecker
Cc: Alessio Igor Bogani
Cc: Andrew Morton
Cc: Chris Metcalf
Cc:
When a CPU in full dynticks mode doesn't respond to complete
a grace period, issue it a specific IPI so that it restarts
the tick and chases a quiescent state.
Signed-off-by: Frederic Weisbecker
Cc: Alessio Igor Bogani
Cc: Andrew Morton
Cc: Chris Metcalf
Cc: Christoph Lameter
Cc: Geoff
This way the full nohz CPUs can safely run with the tick
stopped with a guarantee that somebody else is taking
care of the jiffies and gtod progression.
NOTE: this doesn't handle CPU hotplug. Also we could use something
more elaborated wrt. powersaving if we have more than one non full-nohz
CPU
Start with a very simple interface to define full dynticks CPU:
use a boot time option defined cpumask through the "full_nohz="
kernel parameter.
Make sure you keep at least one CPU outside this range to handle
the timekeeping.
Also full_nohz= must match rcu_nocb= value.
Suggested-by: Paul E.
Allow to dynamically switch between tick and virtual based cputime accounting.
This way we can provide a kind of "on-demand" virtual based cputime
accounting. In this mode, the kernel will rely on the user hooks
subsystem to dynamically hook on kernel boundaries.
This is in preparation for being
Just to avoid confusion.
Signed-off-by: Frederic Weisbecker
Cc: Alessio Igor Bogani
Cc: Andrew Morton
Cc: Chris Metcalf
Cc: Christoph Lameter
Cc: Geoff Levand
Cc: Gilad Ben Yossef
Cc: Hakan Akkan
Cc: Ingo Molnar
Cc: Li Zhong
Cc: Namhyung Kim
Cc: Paul E. McKenney
Cc: Paul Gortmaker
Hi,
Here is a new version of the full dynticks patchset based on 3.8-rc2.
It addresses most feedbacks I got on the previous release (see the list of
changes
below).
Thanks you for your reviews, they are really useful!
This version is pullable at:
Because the sched_class::put_prev_task() callback of rt and fair
classes are referring to the rq clock to update their runtime
statistics. A CPU running in tickless mode may carry a stale value.
We need to update it there.
Signed-off-by: Frederic Weisbecker
Cc: Alessio Igor Bogani
Cc: Andrew
Subject: [PATCH v12 4/9] LSM: Multiple concurrent LSMs
Change the infrastructure for Linux Security Modules (LSM)s
from a single vector of hook handlers to a list based method
for handling multiple concurrent modules.
Configuration changes.
Headers files. Add securityfs files to report the
Subject: [PATCH v12 6/9] LSM: Multiple concurrent LSMs
Change the infrastructure for Linux Security Modules (LSM)s
from a single vector of hook handlers to a list based method
for handling multiple concurrent modules.
Changes for SELinux. Abstract access to security blobs.
Add the now required
In this function we are making use of rq->clock right before the
update of the rq clock, let's just call update_rq_clock() just
before that to avoid using a stale rq clock value.
Signed-off-by: Frederic Weisbecker
Cc: Alessio Igor Bogani
Cc: Andrew Morton
Cc: Chris Metcalf
Cc: Christoph
1 - 100 of 1154 matches
Mail list logo
