On Fri, May 27, 2016 at 02:04:47PM +0100, Catalin Marinas wrote:
> On Fri, May 27, 2016 at 12:49:11PM +0200, Arnd Bergmann wrote:
> > On Friday, May 27, 2016 10:30:52 AM CEST Catalin Marinas wrote:
> > > On Fri, May 27, 2016 at 10:42:59AM +0200, Arnd Bergmann wrote:
> > > > On Friday, May 27, 2016
On Fri, 27 May 2016 09:45:49 -0700
Brian Norris wrote:
> It seems like in the process of refactoring pwm_config() to utilize the
> newly-introduced pwm_apply_state() API, some args/bounds checking was
> dropped.
>
> In particular, I noted that we are now allowing invalid period
> selections. e.g
On 2016-05-19 14:21:48 [+0200], Peter Zijlstra wrote:
> > +static void futex_populate_hash(unsigned int hash_bits)
> > +{
…
> > + raw_spin_lock(&mm->futex_hash.lock);
> > + /* We might have raced with another task allocating the hash. */
> > + if (!mm->futex_hash.hash) {
> > + mm->f
On Fri, May 27, 2016 at 09:39:43AM -0700, Brian Norris wrote:
> On Fri, May 27, 2016 at 06:38:14PM +0200, Boris Brezillon wrote:
> > On Fri, 27 May 2016 09:35:33 -0700
> > Brian Norris wrote:
> > > On Fri, May 27, 2016 at 09:34:39AM +0200, Boris Brezillon wrote:
> > > Now that you mention it, I th
On Thu, May 26, 2016 at 02:40:13PM +0200, Michal Hocko wrote:
> From: Michal Hocko
>
> vforked tasks are not really sitting on memory so it doesn't matter much
> to kill them. Parents are waiting for vforked task killable so it is
> better to chose parent which is the real mm owner. Teach oom_bad
It seems like in the process of refactoring pwm_config() to utilize the
newly-introduced pwm_apply_state() API, some args/bounds checking was
dropped.
In particular, I noted that we are now allowing invalid period
selections. e.g.:
# echo 1 > /sys/class/pwm/pwmchip0/export
# cat /sys/class/pw
On Thu, May 26, 2016 at 11:04:18PM +0200, Christer Weinigel wrote:
> My point is that I don't think it would be doable to get every
> devicetree file out there into the mainline kernel; it's not even
> desirable. devicetree files for custom platforms are a lot like
> userspace applications, the d
Hi Boris,
On Fri, May 27, 2016 at 09:34:39AM +0200, Boris Brezillon wrote:
> On Thu, 26 May 2016 14:05:30 -0700
> Brian Norris wrote:
>
> > It doesn't make sense to allow the duty cycle to be larger than the
> > period. I can see this behavior by, e.g.:
> >
> > # echo 1 > /sys/class/pwm/pwmch
Hi Ashwin,
Yes, I saw kernel crash.
As cpc_desc_ptr is not NULL, cppc_cpufreq_init() still can pass then
crash during cppc_get_perf_caps() access CPPC shared memory.
It's not only "PCC channel request fail" can create this issue but
"acpi_get_psd() fail" also creates it
Thanks
Hoan
On Fri, May
On Tue, 2016-05-03 at 14:01 -0700, Tim Chen wrote:
> This patch prepares the code for being able to batch the anonymous
> pages
> to be swapped out. It reorganizes shrink_page_list function with
> 2 new functions: handle_pgout and pg_finish.
>
> The paging operation in shrink_page_list is consoli
On Fri, 27 May 2016 18:38:14 +0200
Boris Brezillon wrote:
> On Fri, 27 May 2016 09:35:33 -0700
> Brian Norris wrote:
>
> > Hi Boris,
> >
> > On Fri, May 27, 2016 at 09:34:39AM +0200, Boris Brezillon wrote:
> > > On Thu, 26 May 2016 14:05:30 -0700
> > > Brian Norris wrote:
> > >
> > > >
On Fri, May 27, 2016 at 06:38:14PM +0200, Boris Brezillon wrote:
> On Fri, 27 May 2016 09:35:33 -0700
> Brian Norris wrote:
> > On Fri, May 27, 2016 at 09:34:39AM +0200, Boris Brezillon wrote:
> > Now that you mention it, I think you've also dropped some signed
> > (negative value) checking in pwm
On Fri, 27 May 2016 09:35:33 -0700
Brian Norris wrote:
> Hi Boris,
>
> On Fri, May 27, 2016 at 09:34:39AM +0200, Boris Brezillon wrote:
> > On Thu, 26 May 2016 14:05:30 -0700
> > Brian Norris wrote:
> >
> > > It doesn't make sense to allow the duty cycle to be larger than the
> > > period. I
* Peter Ujfalusi [160525 07:24]:
> Add clock properties to the McBSP nodes. McBSP2 and 3 need to have ick also
> since the Sidetone block of these modules are operating using the McBSP
> interface clock.
Sorry replied to the earlier thread putting this patch as the first
patch when committing aga
On 2016-05-07 10:44:39 [+0200], Thomas Gleixner wrote:
> On Fri, 6 May 2016, Darren Hart wrote:
> > On Thu, May 05, 2016 at 08:44:04PM -, Thomas Gleixner wrote:
> Sure, we need to serialize attempts to populate the hash. Especially in the
> non preallocated case. The thing with raw vs. non raw
* Peter Ujfalusi [160525 07:20]:
> Add clock properties to the McBSP nodes. McBSP2 and 3 need to have ick also
> since the Sidetone block of these modules are operating using the McBSP
> interface clock.
Can you please apply this dts patch as the first patch in the
series? That way I can merge it
On 5/27/2016 4:02 AM, Andrey Ryabinin wrote:
On 05/26/2016 09:43 PM, Yang Shi wrote:
The upstream commit 1771c6e1a567ea0ba20a4ffe68a1419fd8ef
("x86/kasan: instrument user memory access API") added KASAN instrument to
x86 user memory access API, so added such instrument to ARM64 too.
Teste
Hi Jeffrey,
On Tue, May 24, 2016 at 05:31:41PM +0800, jeffrey.lin wrote:
> Hi Dmitry:
> >
> > BUILD_BUG_ON((RM_FW_PAGE_SIZE % RM_BL_WRT_PKG_SIZE) != 0);
> >
> > for (i = 0; i < RM_FW_PAGE_SIZE / RM_BL_WRT_PKG_SIZE; i++) {
> > buf[BL_HEADER] = RM_CMD_BOOT_PAGE_WRT;
> >
On Fri, May 27, 2016 at 12:08:22PM -0400, Tejun Heo wrote:
> Hello,
>
> On Fri, May 27, 2016 at 12:01:14PM -0400, Konrad Rzeszutek Wilk wrote:
> > On Fri, May 27, 2016 at 09:24:11PM +0530, Bhaktipriya Shridhar wrote:
> > > With concurrency managed workqueues, use of dedicated workqueues can be
> >
Remove commas from unit addresses as suggested by Rob Herring upon me
posting initial Apalis TK1 support:
http://article.gmane.org/gmane.linux.ports.tegra/26608
Signed-off-by: Marcel Ziswiler
---
arch/arm/boot/dts/tegra124-jetson-tk1-emc.dtsi | 6 +-
arch/arm/boot/dts/tegra124-jetson-tk1.dt
On 05/26/2016 08:36 PM, Leizhen (ThunderTown) wrote:
[...] continue;
Hi, everybody:
If some "memory" node contains "numa-node-id", but some others missed. Can
we simply ignored it?
I think we should break out too, and faking to only have node0.
I think if some "memory" nodes co
On Fri, May 27, 2016 at 01:18:03PM +0200, Michal Hocko wrote:
...
> @@ -1087,7 +1105,25 @@ static int __set_oom_adj(struct file *file, int
> oom_adj, bool legacy)
> unlock_task_sighand(task, &flags);
> err_put_task:
> put_task_struct(task);
> +
> + if (mm) {
> + struct
* Steven Rostedt | 2016-05-27 11:06:58 [-0400]:
>You probably didn't remove it. It may have been removed a while ago
>when Thomas did his big rewrite to get things working again.
okay. As long as I don't lose patches :)
>> about adding such a flag… I remember you had something in your tree to
>>
Remove the dbg macro and debug module parameter and use
the generic kernel facility.
Trivially reduces defconfig object size on x86-64
$ size drivers/acpi/pci_slot.o*
textdata bss dec hex filename
880 752 41636 664 drivers/acpi/pci_slot.o.new
935 7
Hi Patrice,
On Fri, 27 May 2016, Patrice Chotard wrote:
> >+struct rproc *xp70_rproc_alloc(struct platform_device *pdev, char *fw_name);
> >+void xp70_rproc_put(struct st_xp70_rproc *xp70_rproc);
> >+
> >+#endif
>
> Hi Peter
>
> Applying this series on top of v4.6 kernel leads to the following
On Fri, May 27, 2016 at 05:20:45PM +0300, Alexander Popov wrote:
> Hello,
>
> Excuse me for disturbing, could I have a feedback?
Nope, it's the middle of the merge window, I can't do anything with new
patches until after 4.7-rc1 comes out. And even then, give me a week or
so to catch up...
than
On 25 May 2016 at 15:09, Hoan Tran wrote:
> When CPPC fails to request PCC channel, the CPC data is freed
> and cpc_desc_ptr points to the invalid data. This change prevents
> this issue by moving cpc_desc_ptr assignment after PCC channel
> request.
>
> Signed-off-by: Hoan Tran
> ---
> drivers/a
Hello,
On Fri, May 27, 2016 at 12:01:14PM -0400, Konrad Rzeszutek Wilk wrote:
> On Fri, May 27, 2016 at 09:24:11PM +0530, Bhaktipriya Shridhar wrote:
> > With concurrency managed workqueues, use of dedicated workqueues can be
> > replaced by using system_wq. Drop host->intr_wq by using
On 27/05/2016 17:40, Andy Lutomirski wrote:
> On Thu, May 26, 2016 at 11:17 PM, Minfei Huang wrote:
>> There is a generic function __pvclock_read_cycles to be used to get both
>> flags and cycles. For function pvclock_read_flags, it's useless to get
>> cycles value. To make this function be more
This patch fixes erroneous z3fold header access in a HEADLESS page
in reclaim function, and changes one remaining direct
handle-to-buddy conversion to use the appropriate helper.
Signed-off-by: Vitaly Wool
---
mm/z3fold.c | 24 ++--
1 file changed, 14 insertions(+), 10 delet
On Fri, May 27, 2016 at 09:24:11PM +0530, Bhaktipriya Shridhar wrote:
> With concurrency managed workqueues, use of dedicated workqueues can be
> replaced by using system_wq. Drop host->intr_wq by using
> system_wq.
>
> Since there is only a single work item, increase of concurrency level by
> swi
JFYI, I plan to repost the series early next week after I review all the
pieces again properly with a clean head. If some parts are not sound or
completely unacceptable in principle then let me know of course.
--
Michal Hocko
SUSE Labs
Use generic pr_ functions with pr_fmt for info and err.
This also reduces object size a trivial bit:
$ size drivers/acpi/pci_slot.o*
textdata bss dec hex filename
935 752 51692 69c drivers/acpi/pci_slot.o.new
1027 752 51784 6f8 drivers
From: Wang Nan
If kptr_restrict is set to 2, even root is not allowed to see pointers.
This patch checks kptr_restrict even if euid == 0. For root, report
error if kptr_restrict is 2.
Signed-off-by: Wang Nan
Tested-by: Arnaldo Carvalho de Melo
Cc: Zefan Li
Cc: pi3or...@163.com
Link:
http://l
/git/acme/linux.git
tags/perf-urgent-for-mingo-20160527
for you to fetch changes up to 5ea5888b2fbf5b230da62b2a21c8247bebb6c9cf:
perf ctf: Convert invalid chars in a string before set value (2016-05-27
12:08:40 -0300)
perf
From: Wang Nan
We observed some crazy apps on Android set their comm to unprintable
string. For example:
# cat /proc/10607/task/*/comm
tencent.qqmusic
...
Binder_2
日志输出线 <-- Chinese word 'log output thread'
WifiManager
...
'perf data convert' fails to convert perf.data with such
From: Wang Nan
Before this patch, a simple 'perf record' could fail if kptr_restrict is
set to 1 (for normal user) or 2 (for root):
# perf record ls
WARNING: Kernel address maps (/proc/{kallsyms,modules}) are restricted,
check /proc/sys/kernel/kptr_restrict.
Samples in kernel functions
With concurrency managed workqueues, use of dedicated workqueues can be
replaced by using system_wq. Drop host->intr_wq by using
system_wq.
Since there is only a single work item, increase of concurrency level by
switching to system_wq should not break anything.
cancel_work_sync() has been used i
Em Fri, May 27, 2016 at 11:35:51AM +, Wang Nan escreveu:
> We observed some crazy apps on Android set their comm to unprintable
> string. For example:
>
> # cat /proc/10607/task/*/comm
> tencent.qqmusic
> ...
> Binder_2
> 日志输出线 <-- Chinese word 'log output thread'
> WifiManager
>
On 25/05/16 16:01, Vincent Guittot wrote:
> The cfs_rq->avg.last_update_time is initialize to 0 with the main effect
> that the 1st sched_entity that will be attached, will keep its
> last_update_time set to 0 and will attached once again during the
> enqueue.
> Initialize cfs_rq->avg.last_update_t
On Wed, May 25, 2016 at 05:06:44PM +0100, Peter Griffin wrote:
> uniperiph-id, version and mode are ST specific bindings and
> need the 'st,' prefix. Update the examples, as otherwise copying
> them yields a runtime error parsing the DT node.
>
> Signed-off-by: Peter Griffin
> Cc: arnaud.pouliq..
On Wed, May 25, 2016 at 05:06:38PM +0100, Peter Griffin wrote:
> This patch adds the DT binding documentation for the FDMA constroller
> found on STi based chipsets from STMicroelectronics.
>
> Signed-off-by: Ludovic Barre
> Signed-off-by: Peter Griffin
> ---
> Documentation/devicetree/bindings
On Fri, May 27, 2016 at 09:23:20AM +0200, loic pallardy wrote:
>
>
> On 05/26/2016 03:20 PM, Rob Herring wrote:
> >On Thu, May 26, 2016 at 8:05 AM, loic pallardy wrote:
> >>
> >>
> >>On 05/26/2016 02:46 PM, Rob Herring wrote:
> >>>
> >>>On Thu, May 26, 2016 at 4:49 AM, Gabriel Fernandez
> >>> wr
On Thu, May 26, 2016 at 11:17 PM, Minfei Huang wrote:
> There is a generic function __pvclock_read_cycles to be used to get both
> flags and cycles. For function pvclock_read_flags, it's useless to get
> cycles value. To make this function be more effective, add a new wrapper
> function to only ge
On Thu, May 26, 2016 at 11:17 PM, Minfei Huang wrote:
> Function __pvclock_read_cycles is short enough, so there is no need to
> have another function pvclock_get_nsec_offset to calculate tsc delta.
> It's better to combine it into function __pvclock_read_cycles.
>
> Remove useless variables in fu
On Thu, May 26, 2016 at 11:17 PM, Minfei Huang wrote:
> Protocol for the "version" fields is: hypervisor raises it (making it
> uneven) before it starts updating the fields and raises it again (making
> it even) when it is done. Thus the guest can make sure the time values
> it got are consistent
2016-05-27 17:22+0200, Radim Krčmář:
> (I wonder why MacOS X doesn't read IA32_PERF_STATUS, though.)
Oh, it maybe does ... we already emulate status and return 0x1000 in its
bottom 16 bits. I have no idea what is that supposed to mean, but I
think we should return 0x1000 in IA32_PERF_CTL then.
(
I am announcing the release of the Linux 4.2.8-ckt11 kernel.
The updated 4.2.y-ckt tree can be found at:
git://git.launchpad.net/~canonical-kernel/linux/+git/linux-stable-ckt
linux-4.2.y
and can be browsed at:
https://git.launchpad.net/~canonical-kernel/linux/+git/linux-stable-ckt/log/?
diff --git a/Makefile b/Makefile
index 9e3086c..daa93e8 100644
--- a/Makefile
+++ b/Makefile
@@ -1,7 +1,7 @@
VERSION = 4
PATCHLEVEL = 2
SUBLEVEL = 8
-EXTRAVERSION = -ckt10
+EXTRAVERSION = -ckt11
NAME = Hare's hurried rump
# *DOCUMENTATION*
diff --git a/arch/arm64/net/bpf_jit_comp.c b/arch/ar
This helps in reducing code in .remove callbacks and sometimes
dropping .remove callbacks entirely.
Changes since v1 at
http://lkml.kernel.org/r/1464251510-15554-1-git-send-email-narmstr...@baylibre.com
:
- Fix brackets in devm_watchdog_register_device()
Signed-off-by: Neil Armstrong
---
Docu
On Thu, May 26, 2016 at 05:17:45PM +0530, Venkat Reddy Talla wrote:
> Add the support for Device tree bindings of extcon-gpio driver.
> The extcon-gpio device tree node must include the both 'extcon-id' and
> 'gpios' property.
I think extcon bindings are a mess in general...
> For example:
>
2016-05-26 10:32+0300, km...@yandex-team.ru:
> From: Dmitry Bilunov
>
> Intel CPUs having Turbo Boost feature implement an MSR to provide a
> control interface via rdmsr/wrmsr instructions. One could detect the
> presence of this feature by issuing one of these instructions and
> handling the #GP
On Wed, May 18, 2016 at 04:11:28PM -0400, Javier Martinez Canillas wrote:
> The IS_ENABLED() macro checks if a Kconfig symbol has been enabled either
> built-in or as a module, use that macro instead of open coding the same.
>
> Signed-off-by: Javier Martinez Canillas
Applied to libata/for-4.8.
With concurrency managed workqueues, use of dedicated workqueues can be
replaced by using system_wq. Drop host->intr_wq by using
system_wq.
Since there is only a single work item, increase of concurrency level by
switching to system_wq should not break anything.
cancel_work_sync() is used to ensu
This tracepoint allows to keep track of all priority changes made by all
sites that can change this value. The impacted system calls are
sched_setscheduler, sched_setattr, sched_process_fork and set_user_nice.
The priority inheritance mechanism from rt_mutex gets also instrumented
with this tracepo
On Sun, May 22, 2016 at 11:06:01AM +0200, Geert Uytterhoeven wrote:
> Submitters of device tree binding documentation may forget to CC
> the subsystem maintainer if this is missing.
>
> Signed-off-by: Geert Uytterhoeven
> Cc: Tejun Heo
> Cc: linux-...@vger.kernel.org
Applied to libata/for-4.8.
Currently, the priority of tasks is modified directly in the scheduling
functions. Encapsulate priority updates to enable instrumentation of
priority changes. This will enable analysis of real-time scheduling
delays per thread priority, which cannot be performed accurately if we
only trace the prio
While building m32r allmodconfig the build is failing with the error:
ERROR: "bad_dma_ops" [drivers/fpga/zynq-fpga.ko] undefined!
Xilinx Zynq FPGA is using DMA but there was no dependency while
building.
Signed-off-by: Sudip Mukherjee
---
drivers/fpga/Kconfig | 1 +
1 file changed, 1 insertion(
On 05/27/2016 03:48 PM, Guenter Roeck wrote:
> On 05/27/2016 01:25 AM, Neil Armstrong wrote:
> [ ... ]
+data->wdt_dev.max_hw_heartbeat_ms = GXBB_WDT_TCNT_SETUP_MASK;
+data->wdt_dev.min_hw_heartbeat_ms = 1;
>>>
>>> Does the device require a minimum time between heartbeats ?
>>> Jus
On Mon, May 16, 2016 at 12:35:03PM +0100, Colin King wrote:
> From: Colin Ian King
>
> Remove extraneous space on if statement and on the following line,
> trivial fix, no functional change
>
> Signed-off-by: Colin Ian King
Applied to libata/for-4.8.
Thanks.
--
tejun
2016-05-27 09:49+0300, km...@yandex-team.ru:
> 26.05.2016, 23:44, "Gabriel L. Somlo" :
>> On Thu, May 26, 2016 at 10:39:31PM +0200, Radim Krčmář wrote:
>>> 2016-05-26 10:32+0300, km...@yandex-team.ru:
>>> > This patch implements a dummy handler for MSR_IA32_PERF_CTL to avoid the
>>> > crashes. M
The latest mainline kernel (commit 3f59de0) shows a regression. The symptom is
that as soon as the kernel is started, the display is blanked, and it is never
turned on again. This problem was bisected to commit
f21a21983ef13a031250c4c3f6018e29a549d0f1
("drm/i915: Splitting intel_dp_detect"). The
On 05/27/2016 10:17 AM, Neil Armstrong wrote:
> Hi,
> On 05/26/2016 06:29 PM, Sudeep Holla wrote:
>> Hi Neil,
>>> To keep the spirit of the SCPI interface, add a thin "register" layer to get
>>> the ops from the parent node and switch the drivers using the ops to use
>>> the new of_scpi_ops_get() c
On Fri, May 27, 2016 at 08:09:09PM +0900, Seung-Woo Kim wrote:
> After commit, "b968091 security_d_instantiate(): move to the point prior to
> attaching dentry to inode", booting on system with
> systemd and security smack, following kernel panic occurs.
/*
This will improve the performance of hash_32() and hash_64(), but due
to complete lack of multi-bit shift instructions on H8, performance will
still be bad in surrounding code.
Designing H8-specific hash algorithms to work around that is a separate
project. (But if the maintainers would like to g
gcc-6 on x86 started warning about wl3501_get_encode when building
with -O2:
drivers/net/wireless/wl3501_cs.c: In function ‘wl3501_get_encode’:
drivers/net/wireless/wl3501_cs.c:1769:5: warning: ‘implemented’ may be used
uninitialized in this function
drivers/net/wireless/wl3501_cs.c:1686:19: warn
Microblaze is an FPGA soft core that can be configured various ways.
If it is configured without a multiplier, the standard __hash_32()
will require a call to __mulsi3, which is a slow software loop.
Instead, use a shift-and-add sequence for the constant multiply.
GCC knows how to do this, but it
On Fri, 27 May 2016 16:56:01 +0200
Sebastian Andrzej Siewior wrote:
> >We use to have a patch where a console could flag itself as atomic.
> >That is, that it doesn't call any sleeping locks. What happened to that.
> >
> >IIRC, the video console was one such console. Otherwise, we lose out on
> >
This provides a multiply by constant GOLDEN_RATIO_32 = 0x61C88647
for the original mc68000, which lacks a 32x32-bit multiply instruction.
Yes, the amount of optimization effort put in is excessive. :-)
Shift-add chain found by Yevgen Voronenko's Hcub algorithm at
http://spiral.ece.cmu.edu/mcm/gen
This is just the infrastructure; there are no users yet.
This is modelled on CONFIG_ARCH_RANDOM; a CONFIG_ symbol declares
the existence of .
That file may define its own versions of various functions, and define
HAVE_* symbols (no CONFIG_ prefix!) to suppress the generic ones.
Included is a sel
On Thu, May 26, 2016 at 07:15:49AM -0700, Eric Dumazet wrote:
> On Thu, 2016-05-26 at 16:59 +0300, Vladimir Davydov wrote:
> > On Thu, May 26, 2016 at 04:04:55PM +0900, Minchan Kim wrote:
> > > On Wed, May 25, 2016 at 01:30:11PM +0300, Vladimir Davydov wrote:
> > > > On Tue, May 24, 2016 at 01:04:3
This is just the arch-specific part, updated as per requests.
* Fix the stupidly overcomplex m68k conditionals (per Geert Uytterhoeven)
* Renamed the arch file to (per Geert Uytterhoeven)
* Improved the comments on the progress of shift-and-add (Philippe De Muyter)
* Added a self-test (per Michal
* Steven Rostedt | 2016-05-27 10:12:51 [-0400]:
>On Fri, 27 May 2016 15:58:12 +0200
>Sebastian Andrzej Siewior wrote:
>
>> On -RT we try to acquire sleeping locks which might lead to warnings
>> from lockdep or a warn_on() from spin_try_lock() (which is a rtmutex on
>> RT).
>> We don't print in g
On Fri 27-05-16 17:45:49, Vladimir Davydov wrote:
> On Fri, May 27, 2016 at 04:26:26PM +0200, Michal Hocko wrote:
[...]
> > I am doing quite large changes in this area and this would cause many
> > conflicts. Do you think you can postpone this after my patchset [1] gets
> > sorted out please?
>
>
On Fri, May 27, 2016 at 04:26:26PM +0200, Michal Hocko wrote:
> On Fri 27-05-16 17:17:42, Vladimir Davydov wrote:
> > When selecting an oom victim, we use the same heuristic for both memory
> > cgroup and global oom. The only difference is the scope of tasks to
> > select the victim from. So we cou
Hi Frank,
> On May 27, 2016, at 00:15 , Frank Rowand wrote:
>
> On 5/16/2016 1:18 PM, Pantelis Antoniou wrote:
>> This patchset implements two new target methods.
>>
>> A target index method which allows selecting different
>> targets according to an argument using an extended API and
>> a targ
Em Fri, May 27, 2016 at 07:01:14PM +0900, Taeung Song escreveu:
> Commit 1b700c9975008615ad470cf79acc8455ce60a695 ("perf tools: Build
> syscall table .c header from kernel's syscall_64.tbl") that automatically
> generate per-arch syscall table arrays e.g.
>
> arch/x86/include/generated/asm/sys
On 27.05.2016 15:46, Jon Hunter wrote:
On 26/05/16 18:01, Dmitry Osipenko wrote:
On 26.05.2016 18:27, Jon Hunter wrote:
On 26/05/16 15:57, Dmitry Osipenko wrote:
...
That's how I see it:
+--+
|CPU 0 |
+---
On Fri 27-05-16 17:17:41, Vladimir Davydov wrote:
> It's a part of oom context just like allocation order and nodemask, so
> let's move it to oom_control instead of passing it in the argument list.
Don't remember why we haven't done that when the structure was adde.
> Signed-off-by: Vladimir Davy
On Fri 27-05-16 17:17:42, Vladimir Davydov wrote:
> When selecting an oom victim, we use the same heuristic for both memory
> cgroup and global oom. The only difference is the scope of tasks to
> select the victim from. So we could just export an iterator over all
> memcg tasks and keep all oom rel
On 05/20/2016 04:23 PM, Minchan Kim wrote:
We have allowed migration for only LRU pages until now and it was
enough to make high-order pages. But recently, embedded system(e.g.,
webOS, android) uses lots of non-movable pages(e.g., zram, GPU memory)
so we have seen several reports about troubles o
Hello,
Excuse me for disturbing, could I have a feedback?
On 20.05.2016 12:37, Alexander Popov wrote:
> stub_disconnect() calls stub_device_reset() during usb_unbind_device() when
> usb device is locked. So usb_lock_device_for_reset() in stub_device_reset()
> in that case polls for one second and
The Documentation/devicetree/bindings/net/wireless/marvell-sd8xxx.txt DT
binding document say that the "interrupts" property in the child node is
optional. So the property being missed shouldn't be treated as an error.
Signed-off-by: Javier Martinez Canillas
---
drivers/net/wireless/marvell/mwi
Hello,
While booting a system with a mwifiex WiFi card, I noticed the following
missleading error message:
[ 12.480042] mwifiex_sdio mmc2:0001:1: sdio platform data not available
This error only applies to platforms that define a child node for the SDIO
device, but it's currently shown even in
SDIO is an auto enumerable bus so the SDIO devices are matched using the
sdio_device_id table and not using compatible strings from a OF id table.
However, commit ce4f6f0c353b ("mwifiex: add platform specific wakeup
interrupt support") allowed to match nodes defined as child of the SDIO
host contr
The function can fail so the returned value should be checked
and the error propagated to the caller in case of a failure.
Signed-off-by: Javier Martinez Canillas
---
drivers/net/wireless/marvell/mwifiex/sdio.c | 9 +++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/drivers
Instead of duplicating part of the cleanups needed in case of an error
in .probe callback, have a single error path and use goto labels as is
common practice in the kernel.
This also has the nice side effect that the cleanup operations are made
in the inverse order of their counterparts, which was
The Documentation/devicetree/bindings/net/wireless/marvell-sd8xxx.txt DT
binding document lists the possible compatible strings that a SDIO child
node can have, so the driver checks if the defined in the node matches.
But the error message when that's not the case is misleading, so change
for one
There's only a check if mwifiex_add_card() returned a nonzero value, but
the actual error code is neither stored nor propagated to the caller. So
instead of always returning -1 (which is -EPERM and not a suitable errno
code in this case), propagate the value returned by mwifiex_add_card().
Patch a
It's better to have the device name prefixed in the error message.
Signed-off-by: Javier Martinez Canillas
---
drivers/net/wireless/marvell/mwifiex/sdio.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/net/wireless/marvell/mwifiex/sdio.c
b/drivers/net/wireless/
If the sdio_enable_func() function fails on .probe, the -EIO errno code
is always returned but that could make more difficult to debug and find
the cause of why the function actually failed.
Since the driver/device core prints the value returned by .probe in its
error message propagate what was re
When selecting an oom victim, we use the same heuristic for both memory
cgroup and global oom. The only difference is the scope of tasks to
select the victim from. So we could just export an iterator over all
memcg tasks and keep all oom related logic in oom_kill.c, but instead we
duplicate pieces
It's a part of oom context just like allocation order and nodemask, so
let's move it to oom_control instead of passing it in the argument list.
Signed-off-by: Vladimir Davydov
---
drivers/tty/sysrq.c | 1 +
include/linux/oom.h | 8 +---
mm/memcontrol.c | 5 +++--
mm/oom_kill.c |
On Fri, May 27, 2016 at 12:22:19PM +0300, Michael Rapoport wrote:
> I've run two guests without any CPU pinning and without any actual
> interaction with cgroups
> Here's the results (in MBits/sec):
>
> size | 64 | 256 | 1024 | 4096 | 16384
> -+---+-+-+--
On Fri 27-05-16 17:08:13, Vladimir Davydov wrote:
> Not used since oom_lock was instroduced.
>
> Signed-off-by: Vladimir Davydov
Acked-by: Michal Hocko
> ---
> include/linux/mmzone.h | 1 -
> mm/oom_kill.c | 4 ++--
> 2 files changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a
On Fri, 27 May 2016 15:58:12 +0200
Sebastian Andrzej Siewior wrote:
> On -RT we try to acquire sleeping locks which might lead to warnings
> from lockdep or a warn_on() from spin_try_lock() (which is a rtmutex on
> RT).
> We don't print in general from a IRQ off region so we should not try
> this
Not used since oom_lock was instroduced.
Signed-off-by: Vladimir Davydov
---
include/linux/mmzone.h | 1 -
mm/oom_kill.c | 4 ++--
2 files changed, 2 insertions(+), 3 deletions(-)
diff --git a/include/linux/mmzone.h b/include/linux/mmzone.h
index 02069c23486d..3388ccbab7d6 100644
--- a
On 05/27/2016 12:55 AM, Heikki Krogerus wrote:
Hi,
[ ... ]
---
This patch applies on top of '[RFC PATCHv2] usb: USB Type-C Connector Class'
from Heikki Krogerus. It provided the changes I made to get the code
operational.
drivers/usb/type-c/typec.c | 134 ++
On -RT we try to acquire sleeping locks which might lead to warnings
from lockdep or a warn_on() from spin_try_lock() (which is a rtmutex on
RT).
We don't print in general from a IRQ off region so we should not try
this via console_unblank() / bust_spinlocks() as well.
Signed-off-by: Sebastian And
On 05/27/2016 01:25 AM, Neil Armstrong wrote:
[ ... ]
+data->wdt_dev.max_hw_heartbeat_ms = GXBB_WDT_TCNT_SETUP_MASK;
+data->wdt_dev.min_hw_heartbeat_ms = 1;
Does the device require a minimum time between heartbeats ?
Just asking, because you violate it yourself below.
If you want to se
201 - 300 of 537 matches
Mail list logo
