From: Marek Szyprowski
Print warning if FIFOs are configured in such a way that they don't fit
into the SPRAM available on the s3c hsotg module.
Signed-off-by: Marek Szyprowski
Signed-off-by: Robert Baldyga
---
drivers/usb/dwc2/core.h | 1 +
drivers/usb/dwc2/gadget.c | 15 ++-
(2014/06/20 11:48), Steven Rostedt wrote:
> On Tue, 17 Jun 2014 11:04:49 +
> Masami Hiramatsu wrote:
>
>> Introduce FTRACE_OPS_FL_IPMODIFY to avoid conflict among
>> ftrace users who may modify regs->ip to change the execution
>> path. This also adds the flag to kprobe_ftrace_ops, since
>>
From: Simon Que
The function machine__get_kernel_start_addr() was taking the first symbol
of kallsyms as the start address. This is incorrect in certain cases
where the first symbol is something at 0, while the actual kernel
functions begin at a later point (e.g. 0x8020).
This patch fixes
When device is stopped or suspended clock is not needed so we
can disable it for this time.
Signed-off-by: Robert Baldyga
---
drivers/usb/dwc2/gadget.c | 9 +
1 file changed, 9 insertions(+)
diff --git a/drivers/usb/dwc2/gadget.c b/drivers/usb/dwc2/gadget.c
index 2a7c014..0523bc3
hi Ingo,
please consider pulling
thanks,
jirka
The following changes since commit cf230918cda19532e4a5cc4f0d5c82fa7e5e94f6:
Merge branch 'perf/core' into perf/urgent, to pick up the latest fixes
(2014-06-14 14:10:08 +0200)
are available in the git repository at:
From: Marek Szyprowski
This patch fixes kernel panic/interrupt storm/etc issues if bootloader
left s3c-hsotg module in enabled state. Now interrupt handler is enabled
only after proper configuration of hardware registers.
Signed-off-by: Marek Szyprowski
Signed-off-by: Robert Baldyga
---
Because we have not enough memory to have each TX FIFO of size at least 3072
bytes (the maximum single packet size), we create four FIFOs of lenght 1024,
and four of length 3072 bytes, and assing them to endpoints dynamically
according to maxpacket size value of given endpoint.
Signed-off-by:
From: Marek Szyprowski
This leads to potential spinlock recursion in composite framework, other
udc drivers also don't call it directly from pullup method.
Signed-off-by: Marek Szyprowski
Signed-off-by: Robert Baldyga
---
drivers/usb/dwc2/gadget.c | 1 -
1 file changed, 1 deletion(-)
diff
From: Marek Szyprowski
This patch fixes possible freeze caused by infinite loop in interrupt
context.
Signed-off-by: Marek Szyprowski
Signed-off-by: Robert Baldyga
---
drivers/usb/dwc2/gadget.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/usb/dwc2/gadget.c
When cumulative callchain mode is on, we could get samples with
with no actual hits. This breaks the assumption of the annotation
code, that each sample has annotation counts allocated and leads
to segfault.
Fixing this by additional checks for annotation stats.
Acked-by: Namhyung Kim
Acked-by:
Acked-by: David Howells (fscache, keys)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
On 06/22/2014 11:49 PM, Andreas Färber wrote:
It's 1.6 GHz for the Cortex-A15.
Avoids warnings like "/cpus/cpu@0 missing clock-frequency property".
Signed-off-by: Andreas Färber
---
arch/arm/boot/dts/exynos5410.dtsi | 4
1 file changed, 4 insertions(+)
diff --git
From: Marek Szyprowski
Some DWC2/s3c-hsotg debug messages are really useless for typical user,
so hide them behind dev_dbg().
Signed-off-by: Marek Szyprowski
Signed-off-by: Robert Baldyga
---
drivers/usb/dwc2/gadget.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
From: Andrzej Pietrasiewicz
Adjust the debug text to the name of the printed variable.
Signed-off-by: Andrzej Pietrasiewicz
Signed-off-by: Robert Baldyga
---
drivers/usb/dwc2/gadget.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/dwc2/gadget.c
From: Kamil Debski
In the Generic PHY Framework a NULL phy is considered to be a valid phy
thus the "if (hsotg->phy)" check does not give us the information whether
the Generic PHY Framework is used.
In addition to the above this patch also removes phy_init from probe and
phy_exit from remove.
From: Kamil Debski
This patch moves the part of code that initializes the PHY bus width.
This results in simpler code and removes the need to check whether
the Generic PHY Framework is used.
Signed-off-by: Kamil Debski
Signed-off-by: Marek Szyprowski
Signed-off-by: Robert Baldyga
---
Hello,
This patchset contains fixes for dwc2 gadget driver. It touches PHY,
FIFO configuration, initialization sequence and adds many other small fixes.
Best regards
Robert Baldyga
Samsung R Institute Poland
Andrzej Pietrasiewicz (1):
usb: dwc2/gadget: Fix comment text
Kamil Debski (3):
From: Kamil Debski
When the driver is removed s3c_hsotg_phy_disable is called three times
instead of once. This results in decreasing of the phy reference counter
below zero and thus consecutive inserts of the module fails.
This patch removes calls to s3c_hsotg_phy_disable from s3c_hsotg_remove
On Fri 20-06-14 12:33:47, Johannes Weiner wrote:
> shrink_zones() has a special branch to skip the all_unreclaimable()
> check during hibernation, because a frozen kswapd can't mark a zone
> unreclaimable.
>
> But ever since 6e543d5780e3 ("mm: vmscan: fix do_try_to_free_pages()
> livelock"),
On Sun, Jun 22, 2014 at 07:50:07AM -0400, Theodore Ts'o wrote:
> On Sun, Jun 22, 2014 at 02:00:32AM +0100, Al Viro wrote:
> >
> > PS: I agree that it's worth careful commenting, obviously, but
> > before sending it to Linus (*with* comments) I want to get a
> > confirmation that this one-liner
On Thu, Jun 19, 2014 at 01:40:41PM -0700, Andi Kleen wrote:
> On Thu, Jun 19, 2014 at 10:31:29PM +0200, Stephane Eranian wrote:
> > On Thu, Jun 19, 2014 at 10:18 PM, Andi Kleen wrote:
> > >> I don't quite understand that.
> > >> You need to know which events support PEBS. You need a table
> > >
>
Two small but important fixes to SHIELD's pinmux configuration.
The use of invalid properties caused the pinmux to not be applied
at all. Also the setting for sdmmc clock lines resulted in random
errors or even the impossibility to probe attached devices.
Alexandre Courbot (2):
ARM: tegra:
The pinmux subsystem complained that the nvidia,low-power-mode property
is not supported by the sdio1, sdio3 and gma drive groups. In addition
gma also does not support nvidia,drive-type. Remove these properties so
the pinmux configuration can properly be applied.
Signed-off-by: Alexandre Courbot
Input had been disabled by mistake on these pins, leading to issues with
SDIO devices like the Wifi module not being probed or random errors
occuring on the SD card.
Signed-off-by: Alexandre Courbot
---
arch/arm/boot/dts/tegra114-roth.dts | 6 +++---
1 file changed, 3 insertions(+), 3
On Fri 20-06-14 16:24:49, Johannes Weiner wrote:
[...]
> From cd48b73fdca9e23aa21f65e9af1f850dbac5ab8e Mon Sep 17 00:00:00 2001
> From: Johannes Weiner
> Date: Wed, 11 Jun 2014 12:53:59 -0400
> Subject: [patch] mm: vmscan: rework compaction-ready signaling in direct
> reclaim
>
> Page reclaim
Hi Jason,
On Saturday 21 June 2014 08:27 AM, Jason Cooper wrote:
> On Mon, Jun 16, 2014 at 04:53:16PM +0530, Sricharan R wrote:
>> From: Nishanth Menon
>>
>> On certain platforms such as DRA7, SPIs 0, 1, 2, 3, 5, 6, 10, 131,
>> 132, 133 are direct wired to hardware blocks bypassing crossbar.
>>
On Saturday 21 June 2014 08:03 AM, Jason Cooper wrote:
> Sricharan,
>
> Your subject line seems truncated:
>
> "irqchip: crossbar: introduce ti,irqs-skip to skip"
>
> maybe "... Introduce DT property to skip hardwired irqs" ?
>
> Also note that you need to correct the subject line for
>>> On 20.06.14 at 23:29, wrote:
> --- a/drivers/firmware/efi/efi.c
> +++ b/drivers/firmware/efi/efi.c
> @@ -298,7 +298,7 @@ int __init efi_config_init(efi_config_table_type_t
> *arch_tables)
> if (table64 >> 32) {
> pr_cont("\n");
>
On Thu, Jun 19, 2014 at 11:00:28AM -0700, Andi Kleen wrote:
> However these days I'm actually thinking of just getting
> rid of the detailed table except for PREC_DIST. All the PEBS
> controls should be noops if the event does not support PEBS
I had something like the below stuck on the 'look
Hi Peter,
On Monday 23 June 2014 12:24 PM, Peter Zijlstra wrote:
> On Fri, Jun 20, 2014 at 11:21:13AM -0700, Davidlohr Bueso wrote:
>> diff --git a/arch/arc/include/asm/processor.h
>> b/arch/arc/include/asm/processor.h
>> index d99f9b3..8e1bf6b 100644
>> --- a/arch/arc/include/asm/processor.h
>>
This patch superseeds and replaces the initial fix submitted with [1].
After careful analysis of the code, the anticipated NULL pointer
deference is caught in drbg_ctr_update which only invokes drbg_ctr_df
when addtl is not NULL.
This patch is tested with CAVS testing and the test set provided in
On Thu, Jun 19, 2014 at 05:58:28PM +0200, Stephane Eranian wrote:
> + INTEL_EVENT_CONSTRAINT(0xd1, 0xf), /* MEM_LOAD_UOPS_RETIRED.* */
> + /* MEM_LOAD_UOPS_LLC_HIT_RETIRED.* */
> + INTEL_EVENT_CONSTRAINT(0xd2, 0xf),
> + /* MEM_LOAD_UOPS_LLC_MISS_RETIRED.* */
> +
As reported by a static code analyzer, the code for the ordering of
the linked list can be simplified.
Reported-by: kbuild test robot
Signed-off-by: Stephan Mueller
---
crypto/drbg.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/crypto/drbg.c b/crypto/drbg.c
On Sat, Jun 21, 2014 at 12:52:22AM +, Elliott, Robert (Server Storage)
wrote:
> Some of those context switches might be from scsi_end_request(),
> which always schedules the scsi_requeue_run_queue() function via the
> requeue_work workqueue for scsi-mq. That causes lots of context
>
On Sat, Jun 21, 2014 at 10:10:14PM +, Elliott, Robert (Server Storage)
wrote:
> > not_ready:
> > /*
> > * lock q, handle tag, requeue req, and decrement device_busy. We
>
> There's an extra & in that if statement.
Indeed, this crept in during a rebase and a later patch fixes it.
On Fri, Jun 20, 2014 at 03:22:46PM -0400, Waiman Long wrote:
> v2->v3:
> - Add a new read mode (3) for rwlock (used in
>lock_acquire_shared_cond_recursive()) to avoid conflict with other
>use cases of lock_acquire_shared_recursive().
>
> v1->v2:
> - Use less conditional & make it easier
On Fri, Jun 20, 2014 at 11:21:13AM -0700, Davidlohr Bueso wrote:
> From: Davidlohr Bueso
>
> The arch_mutex_cpu_relax() function, introduced by 34b133f, is
> hacky and ugly. It was added a few years ago to address the fact
> that common cpu_relax() calls include yielding on s390, and thus
>
On 06/20/2014 11:49 PM, Vlastimil Babka wrote:
> isolate_migratepages_range() is the main function of the compaction scanner,
> called either on a single pageblock by isolate_migratepages() during regular
> compaction, or on an arbitrary range by CMA's __alloc_contig_migrate_range().
> It
For platforms with virtualization enabled
1. The job ring registers can be written to only is the job ring has been
started i.e STARTR bit in JRSTART register is 1
2. For DECO's under direct software control, with virtualization enabled
PL, BMT, ICID and SDID values need to
On Fri, Jun 20, 2014 at 11:21:13AM -0700, Davidlohr Bueso wrote:
> diff --git a/arch/arc/include/asm/processor.h
> b/arch/arc/include/asm/processor.h
> index d99f9b3..8e1bf6b 100644
> --- a/arch/arc/include/asm/processor.h
> +++ b/arch/arc/include/asm/processor.h
> @@ -62,6 +62,8 @@ unsigned long
On Fri, Jun 20, 2014 at 12:33:50PM -0400, Johannes Weiner wrote:
> Swappiness is determined for each scanned memcg individually in
> shrink_zone() and is not a parameter that applies throughout the
> reclaim scan. Move it out of struct scan_control to prevent
> accidental use of a stale value.
>
On Fri, Jun 20, 2014 at 12:33:49PM -0400, Johannes Weiner wrote:
> Direct reclaim currently calls shrink_zones() to reclaim all members
> of a zonelist, and if that wasn't successful it does another pass
> through the same zonelist to check overall reclaimability.
>
> Just check reclaimability in
On Fri, Jun 20, 2014 at 03:21:20PM -0700, Ben Segall wrote:
> distribute_cfs_runtime intentionally only hands out enough runtime to
> bring each cfs_rq to 1 ns of runtime, expecting the cfs_rqs to then take
> the runtime they need only once they actually get to run. However, if
> they get to run
On Mon, Jun 23, 2014 at 01:42:51PM +1000, Dave Chinner wrote:
> On Sun, Jun 22, 2014 at 01:24:48PM +0300, Michael S. Tsirkin wrote:
> > On Fri, Jun 20, 2014 at 11:29:40PM +0800, Ming Lei wrote:
> > > @@ -24,8 +26,8 @@ static struct workqueue_struct *virtblk_wq;
> > > struct virtio_blk
> > > {
>
On Fri, Jun 20, 2014 at 12:33:48PM -0400, Johannes Weiner wrote:
> Page reclaim for a higher-order page runs until compaction is ready,
> then aborts and signals this situation through the return value of
> shrink_zones(). This is an oddly specific signal to encode in the
> return value of
On Monday 16 June 2014 19:55:04, Oliver Hartkopp wrote:
> Hello Tyler,
>
> On 16.06.2014 04:23, Tyler Hall wrote:
> > Use schedule_work() to avoid potentially taking the spinlock in
> > interrupt context.
> >
> (..)
>
> >
> > To deal with these issues, don't grab the lock in the wakeup
On Mon, 2014-06-23 at 08:23 +0200, Mathias Krause wrote:
> On 23 June 2014 00:56, Joe Perches wrote:
> > On Mon, 2014-06-23 at 00:46 +0200, Mathias Krause wrote:
> >> [...] patch 2 adds some syntactical sugar for the most popular use
> >> case, by providing pr_ alike macros, namely pi_ for __init
On 23 June 2014 03:30, Joe Perches wrote:
> On Mon, 2014-06-23 at 00:46 +0200, Mathias Krause wrote:
>> This RFC series tries to address the problem of dangling strings of
>> __init functions after initialization, as well as __exit strings for
>> code not even included in the final kernel image.
On Fri, Jun 20, 2014 at 07:59:58PM -0700, Paul E. McKenney wrote:
> Commit ac1bea85781e (Make cond_resched() report RCU quiescent states)
> fixed a problem where a CPU looping in the kernel with but one runnable
> task would give RCU CPU stall warnings, even if the in-kernel loop
> contained
On 06/20/2014 11:49 PM, Vlastimil Babka wrote:
> When direct sync compaction is often unsuccessful, it may become deferred for
> some time to avoid further useless attempts, both sync and async. Successful
> high-order allocations un-defer compaction, while further unsuccessful
> compaction
On 23 June 2014 00:56, Joe Perches wrote:
> On Mon, 2014-06-23 at 00:46 +0200, Mathias Krause wrote:
>> [...] patch 2 adds some syntactical sugar for the most popular use
>> case, by providing pr_ alike macros, namely pi_ for __init
>> code and pe_ for __exit code. This hides the use of the
On 06/21/2014 02:02 AM, Doug Anderson wrote:
> Tushar,
>
> On Fri, Jun 20, 2014 at 1:03 AM, Tushar Behera wrote:
>> From: Wonjoon Lee
>>
>> The MAX98091 CODEC is the same as MAX98090 CODEC, but with an extra
>> microphone. Existing driver for MAX98090 CODEC already has support
>> for MAX98091
On 06/17/2014 04:54 PM, Marek Szyprowski wrote:
> Hello,
>
> On 2014-06-17 13:08, Tushar Behera wrote:
>> 'err' is uninitialized, rather print the error code directly.
>>
>> This also fixes following warning.
>> drivers/usb/misc/usb3503.c: In function ‘usb3503_probe’:
>>
operated on. Worse,
> uncharge has to happen from a context that is still type-specific,
> rather than at the end of the page's lifetime with exclusive access,
> and so requires a lot of synchronization.
> ...
this patch made it into next-20140623 as 5e49555277df (mm: memcontrol: r
On Fri, Jun 20, 2014 at 12:33:47PM -0400, Johannes Weiner wrote:
> shrink_zones() has a special branch to skip the all_unreclaimable()
> check during hibernation, because a frozen kswapd can't mark a zone
> unreclaimable.
>
> But ever since 6e543d5780e3 ("mm: vmscan: fix do_try_to_free_pages()
>
> We probably should just the cpu_has_mp macro entirely. All it is used
> for is printing a warning in amd_k7_smp_check().
>
> Andi, Borislav -- as far as I can tell, we have *never* enforced this on
> the 64-bit kernel, although we have enforced it on 64-bit processors
> running the 32-bit
On Mon, Jun 23, 2014 at 11:32 AM, Tushar Behera wrote:
> probe_err label only returns the error code. This label can be removed
> and the error code can be returned directly.
>
> Signed-off-by: Tushar Behera
> ---
> drivers/tty/serial/samsung.c |5 +
> 1 file changed, 1 insertion(+), 4
On 06/19/2014 05:08 PM, Felipe Balbi wrote:
> On Mon, Jun 16, 2014 at 10:20:36AM +0200, Robert Baldyga wrote:
>> This field allows to mark ep as claimed in more clear way. Claiming
>> endpoint by setting driver_data to non-null value is leaky solution
>> and makes code unreadable.
>
> how come ?
probe_err label only returns the error code. This label can be removed
and the error code can be returned directly.
Signed-off-by: Tushar Behera
---
drivers/tty/serial/samsung.c |5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/drivers/tty/serial/samsung.c
The patches are based next-20140620 and they have only been build
tested.
Tushar Behera (2):
serial: amba-pl011: Simplify goto statements
serial: amba-pl010: Use devres APIs
drivers/tty/serial/amba-pl010.c | 46 ++-
drivers/tty/serial/amba-pl011.c |
Migrating to use devres managed APIs devm_kzalloc, devm_ioremap and
devm_clk_get.
Signed-off-by: Tushar Behera
---
drivers/tty/serial/amba-pl010.c | 46 ++-
1 file changed, 16 insertions(+), 30 deletions(-)
diff --git a/drivers/tty/serial/amba-pl010.c
The label 'out' is only used to return the error code. We can return the
error code directly and remove 'out' label.
Signed-off-by: Tushar Behera
---
drivers/tty/serial/amba-pl011.c | 30 ++
1 file changed, 10 insertions(+), 20 deletions(-)
diff --git
3.11.10.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: =?UTF-8?q?J=C3=A9r=C3=B4me=20Glisse?= jgli...@redhat.com
commit 24f47acc78b0ab5e2201f859fe1f693ae90c7c83 upstream.
When accel is not working on device with virtual address space radeon
3.11.10.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: J. Bruce Fields bfie...@redhat.com
commit 27b11428b7de097c42f205beabb1764f4365443b upstream.
The current code assumes a one-to-one lockowner-lock stateid
correspondance.
On Mon, Jun 23, 2014 at 9:02 AM, Pavel Machek pa...@ucw.cz wrote:
On Sun 2014-06-22 22:12:14, Ilia Mirkin wrote:
On Sat, Jun 21, 2014 at 3:45 PM, Greg KH g...@kroah.com wrote:
On Sat, Jun 21, 2014 at 02:22:59PM -0400, Ilia Mirkin wrote:
On Sat, Jun 21, 2014 at 2:02 PM, Pavel Machek
Kgr wants to test whether ftrace is OK with patching. If not, we just
bail out and will not initialize at all.
Signed-off-by: Jiri Slaby jsl...@suse.cz
Cc: Steven Rostedt rost...@goodmis.org
Cc: Frederic Weisbecker fweis...@gmail.com
Cc: Ingo Molnar mi...@redhat.com
---
include/linux/ftrace.h |
Sometimes we want to patch a function which is in a module that is not
currently loaded. In that case, patching would fail completely. So let
the user decide whether it is fatal when the function to be patched is
not found. If it is not, it is just skipped. Other functions in the
patch (if any)
From: Jiri Kosina jkos...@suse.cz
The only reliable way for function redirection through ftrace_ops (when
modifying pt_regs-rip in the handler) is fentry.
The alternative -- mcount -- is problematic in several ways. Namely the
caller's function prologue (that has already been executed by the
This is a text provided by Udo and polished.
Signed-off-by: Jiri Slaby jsl...@suse.cz
Cc: Udo Seidel udosei...@gmx.de
---
Documentation/kgraft.txt | 44
1 file changed, 44 insertions(+)
create mode 100644 Documentation/kgraft.txt
diff --git
From: Jiri Kosina jkos...@suse.cz
Provide initial implementation. We are now able to do ftrace-based
runtime patching of the kernel code.
In addition to that, we will provide a kgr_patcher module in the next
patch to test the functionality.
Note that the per-process flag dismisses in later
Introduce a per-cpu flag to check whether we should use the old or new
function in the slow stub. The new function starts being used on a
processor only after a scheduled function sets the flag via
schedule_on_each_cpu. Presumably this happens in the process context,
no irq is running. And protect
Before we enable a kthread support in kGraft, we must make sure all
kthreads mark themselves as kGraft-safe at some point explicitly.
We do this by injecting kgr_task_safe to the freezer test. There, we
assume that kthreads are in some predefined state and can expect
something bad to happen.
From: Jiri Kosina jkos...@suse.cz
Processes which are running in userspace at the time of patching can
be immediately marked as migrated to the new universe, as they are
provably outside the kernel and would have their 'in_progress' flag
cleared upon (eventual) kernel entry anyway.
This
Quoting chenhanx...@cn.fujitsu.com (chenhanx...@cn.fujitsu.com):
Hi
-Original Message-
From: Richard Weinberger [mailto:rich...@nod.at]
Sent: Friday, June 20, 2014 7:02 PM
To: Chen, Hanxiao/陈 晗霄; contain...@lists.linux-foundation.org;
linux-kernel@vger.kernel.org
Cc: Eric W.
This is based on Udo's text which was augmented in this patch.
Signed-off-by: Jiri Slaby jsl...@suse.cz
Cc: Udo Seidel udosei...@gmx.de
Cc: Vojtech Pavlik vojt...@suse.cz
---
kernel/Kconfig.kgraft | 3 +++
samples/Kconfig | 4
2 files changed, 7 insertions(+)
diff --git
In 10 seconds, not 30. This speeds up the whole process in most
scenarios.
Signed-off-by: Jiri Slaby jsl...@suse.cz
Cc: Steven Rostedt rost...@goodmis.org
Cc: Frederic Weisbecker fweis...@gmail.com
Cc: Ingo Molnar mi...@redhat.com
---
kernel/kgraft.c | 2 +-
1 file changed, 1 insertion(+), 1
While we are patching, we set up a stub which refers to
kgr_in_progress of a process. The stub can be called immediately when
set up, but we set the flag even after done with patching in
kgr_handle_processes. This is obviously too late, so set the flag
before we start patching, but after we check
This is needed for kGraft to find a fentry location to be ftraced.
We use this to find a place where to jump to a new/old code location.
Note that we use a O(n) algorithm to assert correctness (and
simplicity). This algorithm can be further optimized to be O(log(n))
using binary search, but care
On Fri, Jun 20, 2014 at 12:33:49PM -0400, Johannes Weiner wrote:
Direct reclaim currently calls shrink_zones() to reclaim all members
of a zonelist, and if that wasn't successful it does another pass
through the same zonelist to check overall reclaimability.
Just check reclaimability in
To be used from some kthreads.
Signed-off-by: Jiri Slaby jsl...@suse.cz
Cc: Steven Rostedt rost...@goodmis.org
Cc: Frederic Weisbecker fweis...@gmail.com
Cc: Ingo Molnar mi...@redhat.com
---
include/linux/sched.h | 9 +
1 file changed, 9 insertions(+)
diff --git a/include/linux/sched.h
Wake up kthreads so that they cycle through kgr_task_safe either
by an explicit call to it or implicitly via try_to_freeze. This
ensures nobody should use the old version of the code and kgraft core
can push everybody to use the new version by switching to the fast
path.
Signed-off-by: Jiri Slaby
This is to test the newly added functionality: non-fatal patching of
yet unknown functions.
Signed-off-by: Jiri Slaby jsl...@suse.cz
---
samples/kgraft/kgraft_patcher.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/samples/kgraft/kgraft_patcher.c b/samples/kgraft/kgraft_patcher.c
From: Jiri Kosina jkos...@suse.cz
Instead of flooding dmesg with data about tasks which haven't yet been
migrated to the new universe, create a 'kgr_in_progress' in
/proc/pid/ so that it's possible to easily script the checks/actions
in userspace.
js: use the kgr helper
Signed-off-by: Jiri
Signed-off-by: Jiri Slaby jsl...@suse.cz
Cc: Jiri Kosina jkos...@suse.cz
Cc: Vojtech Pavlik vojt...@suse.cz
---
MAINTAINERS | 9 +
1 file changed, 9 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 3f2e171047b9..73733eb50bb3 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -5239,6
From: Jiri Kosina jkos...@suse.cz
Having the per-task 'kgr_in_progress' flag stored as long is a waste
of space. And manipulating it is likely slower than just performing
single bit operations. Convert the flag to a thread info flag.
Additionally, making the KGR TI_flag part of _TIF_ALLWORK_MASK
From: Jiri Kosina jkos...@suse.cz
In addition to having a per-process flag that shows which processess have
already been migrated, it's useful to have a global-wide flag that will
show whether the patching operation is currently undergoing without having
to traverse all /proc entries.
js: handle
3.11.10.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Alex Deucher alexdeuc...@gmail.com
commit 4955bb073f1be6dd884b5d10041ba4bade6495bf upstream.
Probably a copy paste typo.
Signed-off-by: Alex Deucher alexander.deuc...@amd.com
This is intended to be a presentation of the kGraft engine, so it is
placed into samples/ directory.
It patches two chosen functions sys_iopl() and sys_capable() to print
a message in addition to the original functionality.
js: fix filename in Makefile (thanks mmarek)
Signed-off-by: Jiri Kosina
From: Libor Pechacek lpecha...@suse.cz
kGraft not succeeding on the first attempt can hardly be called a
failure. kGraft is merely waiting for sleeping processes to wake up
and get out of the way.
Signed-off-by: Libor Pechacek lpecha...@suse.cz
Signed-off-by: Jiri Slaby jsl...@suse.cz
---
3.11.10.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Alex Deucher alexdeuc...@gmail.com
commit d8ade3526b2aa0505132c404c05a38b73ea15490 upstream.
Newer PX systems have non-VGA pci class dGPUs. Update
the ATRM fetch method to handle
3.11.10.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Ben Skeggs bske...@redhat.com
commit 0f1d360b2ee3a2a0f510d3f1bcd3f5ebe5d41265 upstream.
Fixes a LVDS bleed issue on Lenovo W530 that can occur under a
number of circumstances.
3.11.10.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Ursula Braun ursula.br...@de.ibm.com
commit f5738e2ef88070ef1372e6e718124d88e9abe4ac upstream.
When sending data through IUCV a MESSAGE COMPLETE interrupt
signals that sent data memory
3.11.10.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Peter Zijlstra pet...@infradead.org
commit 0819b2e30ccb93edf04876237b6205eef84ec8d2 upstream.
Vince reported that using a large sample_period (one with bit 63 set)
results in wreckage
3.11.10.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Heiko Carstens heiko.carst...@de.ibm.com
commit e84d2f8d2ae33c8215429824e1ecf24cbca9645e upstream.
This is the s390 variant of Alexei's JIT bug fix.
(patch description below stolen
3.11.10.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Johan Hovold jhov...@gmail.com
commit 6954cc1f238199e971ec905c5cc87120806ac981 upstream.
Fix null-pointer dereference at probe when the mdio platform device is
missing (e.g. when it
3.11.10.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Johannes Berg johannes.b...@intel.com
commit b4b177a5556a686909e643f1e9b6434c10de079f upstream.
Jouni reported that if a remain-on-channel was active on the
same channel as the current
3.11.10.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Eliad Peller el...@wizery.com
commit c1fbb258846dfc425507a093922d2d001e54c3ea upstream.
cfg80211 is notified about connection failures by
__cfg80211_connect_result() call. However,
3.11.10.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Steven Rostedt (Red Hat) rost...@goodmis.org
commit 6227cb00cc120f9a43ce8313bb0475ddabcb7d01 upstream.
The check at the beginning of cpupri_find() makes sure that the task_pri
variable
This patch fix some coding style problems.
Signed-off-by: Raphaël Poggi poggi.r...@gmail.com
---
drivers/staging/media/lirc/lirc_imon.c | 13 +
1 file changed, 5 insertions(+), 8 deletions(-)
diff --git a/drivers/staging/media/lirc/lirc_imon.c
The Berlin SATA PHY drives the PHY related to the SATA interface. Add
the corresponding documentation.
Signed-off-by: Antoine Ténart antoine.ten...@free-electrons.com
---
.../devicetree/bindings/phy/berlin-sata-phy.txt | 16
1 file changed, 16 insertions(+)
create mode
901 - 1000 of 1924 matches
Mail list logo
