On Tue, 30 Aug 2016, Lee Jones wrote:
> On Mon, 29 Aug 2016, Heikki Krogerus wrote:
>
> > Intel WhiskeyCove PMIC has also a USB Type-C PHY, so let's
> > create a device for it.
> >
> > Signed-off-by: Heikki Krogerus
> > Cc: Lee Jones
> > ---
> > drivers/mfd/intel_soc_pmic_bxtwc.c | 11 +++
Suppose you have a map array value that is somethihng like this
struct foo {
unsigned iter;
int array[SOME_CONSTANT];
};
You can easily insert this into an array, but you cannot modify the contents of
foo->array[] after the fact. This is because we have no way to verify we won't
On Fri, 19 Aug 2016 09:38:43 +0200
Boris Brezillon wrote:
> Hi,
>
> We recently faced some problems when using an BT uart chip interfaced
> through the H5 proto (rtk_h5). Here are the logs of the 2 different
> issues we had when closing the line discipline (actually, restoring
> the previous one
On 08/25/2016 08:04 AM, Thomas Gleixner wrote:
> On Mon, 22 Aug 2016, Tom Lendacky wrote:
>
>> Provide support for Secure Memory Encryption (SME). This initial support
>> defines the memory encryption mask as a variable for quick access and an
>> accessor for retrieving the number of physical addr
From: Michael Trimarchi
IMX6UL GEA M6UL modules are system on module solutions manufactured
by Engicam with following characteristics:
Processor Freescale i.MX 6UltraLite MCIMX6G2, 528 MHz
RAM 128MB, 16-bit DDR3
NAND SLC256MB
Power supplySingle 5V
MAX LCD RES up
In case that CONFIG_HOTPLUG_CPU and CONFIG_CFS_BANDWIDTH is turned on
and tasks in bandwidth controlled task group run on hotplug core,
the tasks are not controlled by cfs_b->quota when hotplug core is offline
and then online. The remaining tasks in task group consume all of
cfs_b->quota on other c
Hi,
On Tue, Aug 30, 2016 at 02:49:50PM +0300, Heikki Krogerus wrote:
> On Tue, Aug 30, 2016 at 01:16:46PM +0200, Oliver Neukum wrote:
> > Error reporting does not require a synchronous operation. Reporting
> > it in the next read() or write() and making it pollable is perfectly
> > viable. It just
In case that CONFIG_HOTPLUG_CPU and CONFIG_CFS_BANDWIDTH is turned on
and tasks in bandwidth controlled task group run on hotplug core,
the tasks are not controlled by cfs_b->quota when hotplug core is offline
and then online. The remaining tasks in task group consume all of
cfs_b->quota on other c
Texas Instrument's System Control Interface (TI-SCI) Message Protocol
is used in Texas Instrument's System on Chip (SoC) such as those
in keystone family K2G SoC to communicate between various compute
processors with a central system controller entity.
TI-SCI message protocol provides support for
Hello,
On Tue, 23 Aug 2016 08:26:48 +0200, Marcin Wojtas wrote:
> diff --git a/drivers/clk/mvebu/cp110-system-controller.c
> b/drivers/clk/mvebu/cp110-system-controller.c
> index 7fa42d6..0835e1d 100644
> --- a/drivers/clk/mvebu/cp110-system-controller.c
> +++ b/drivers/clk/mvebu/cp110-system-co
Texas Instrument's System Control Interface (TI-SCI) Message Protocol
is used in Texas Instrument's System on Chip (SoC) such as those
in keystone family K2G SoC to communicate between various compute
processors with a central system controller entity.
TI-SCI message protocol provides support for
On Mon, Aug 29, 2016 at 2:02 PM, Paolo Bonzini wrote:
>
> On 19/08/2016 02:16, Dmitry Vyukov wrote:
>> > > This seems non-exploitable due to mmap_min_addr, so I guess it should
>> > > be treated just as a regular bug
>> >
>> > Probably fixed by commit 4c5ea0a9cd02 ("locking/static_key: Fix
>> > co
Texas Instrument's System Control Interface (TI-SCI) Message Protocol
is used in Texas Instrument's System on Chip (SoC) such as those in
newer SoCs in the keystone processor family starting with K2G.
This message protocol is used to communicate between various compute
or processing entities (such
Since system controller now has control over SoC power management, it
needs to be explicitly requested to reboot the SoC. Add support for
it.
In some systems however, SoC needs to toggle a GPIO or send event to an
external entity (like a PMIC) for a system reboot to take place. To
facilitate that,
Hi,
Thanks for the reviews on the patches, here is v2 of the series.
Texas Instruments' Keystone generation System on Chips (SoC)
starting with 66AK2G02[1], now include a dedicated SoC System Control
entity called PMMC(Power Management Micro Controller) in line with
ARM architecture recommendatio
Texas Instrument's System Control Interface (TI-SCI) Message Protocol
is used in Texas Instrument's System on Chip (SoC) such as those
in keystone family K2G SoC to communicate between various compute
processors with a central system controller entity.
TI-SCI message protocol provides support for
On Tue, Aug 30, 2016 at 12:08:57PM +0200, Roland Singer wrote:
> Thanks for pointing it out.
>
> Yeah that's right. The system will hang randomly a few minutes later,
> because some certain actions in the graphical user session will trigger
> the freeze.
>
> I had a look at the function body of p
There are three usercopy warnings which are currently being silenced for
gcc 4.6 and newer:
1) "copy_from_user() buffer size is too small" compile warning/error
This is a static warning which happens when object size and copy size
are both const, and copy size > object size. I didn't see a
On 08/30, Peter Zijlstra wrote:
>
> /*
>* Ensure we load p->on_rq _after_ p->state, otherwise it would
>* be possible to, falsely, observe p->on_rq == 0 and get stuck
>* in smp_cond_load_acquire() below.
>*
>* sched_ttwu_pending() try_to
On 08/30, Balbir Singh wrote:
>
> The origin of the issue I've seen seems to be related to
> rwsem spin lock stealing. Basically I see the system deadlock'd in the
> following state
>
> I have a system with multiple threads and
>
> Most of the threads are stuck doing
>
> [67272.593915] --- inter
On Tue, Aug 30, 2016 at 11:41:28AM +0200, Jiri Kosina wrote:
> On Mon, 29 Aug 2016, Christopher Arges wrote:
>
> > Another example is CVE-2016-2117. Here we need to unset NETIF_F_SG on a
> > particular device. If the device is already loaded we need a way to
> > fixup hw_features on an already a
Hi,
On Tue, Aug 30, 2016 at 08:22:23PM +0800, Chen-Yu Tsai wrote:
> The KMS helpers (drm_atomic_helper_check_modeset/mode_fixup) pass
> encoder->bridge directly to drm_bridge_mode_fixup, which expects a
> valid pointer, or NULL (in which case it just returns).
>
> Clear encoder->bridge if a bridg
Hi,
On Tue, Aug 30, 2016 at 07:43:29PM +0800, Shawn Guo wrote:
> On Mon, Aug 29, 2016 at 11:06:44AM -0500, Zhi Li wrote:
> > On Wed, Aug 17, 2016 at 2:42 PM, Zhengyu Shen wrote:
> > > MMDC is a multi-mode DDR controller that supports DDR3/DDR3L x16/x32/x64
> > > and LPDDR2 two channel x16/x32 mem
Hi,
On Tue, Aug 30, 2016 at 04:55:00PM +1000, Jonathan Liu wrote:
> If the enable-gpios property of a simple panel in device tree is set,
> the GPIO is not toggled on/off because of missing calls to
> drm_panel_prepare and drm_panel_unprepare.
>
> Signed-off-by: Jonathan Liu
This was not applyi
On Tue, 30 Aug 2016 08:20:38 +0300
"Michael S. Tsirkin" wrote:
> On Mon, Aug 29, 2016 at 10:53:04PM -0600, Alex Williamson wrote:
> > On Mon, 29 Aug 2016 21:52:20 -0600
> > Alex Williamson wrote:
> >
> > > On Mon, 29 Aug 2016 21:23:25 -0600
> > > Alex Williamson wrote:
> > >
> > > > On Tu
"Aneesh Kumar K.V" writes:
>
>
>> static inline void check_highest_zone(enum zone_type k)
>> {
>> -if (k > policy_zone && k != ZONE_MOVABLE)
>> +if (k > policy_zone && k != ZONE_MOVABLE && !is_zone_cma_idx(k))
>> policy_zone = k;
>> }
>>
>
>
> Should we apply policy t
On Tuesday 30 August 2016, Baoyou Xie wrote:
> On 30 August 2016 at 00:01, Sean Paul wrote:
>
> > On Mon, Aug 29, 2016 at 9:02 AM, Baoyou Xie wrote:
> > > We get 1 warning when build kernel with W=1:
> > > drivers/gpu/drm/nouveau/nvkm/engine/gr/ctxgm107.c:937:1: warning: no
> > previous prototyp
On Fri, 26 Aug 2016, Peter Griffin wrote:
> slim core is used as a basis for many IPs in the STi
> chipsets such as fdma and demux. To avoid duplicating
> the elf loading code in each device driver a slim
> rproc driver has been created.
>
> This driver is designed to be used by other device driv
VPU driver add mdp support
Signed-off-by: Minghsiu Tsai
---
drivers/media/platform/mtk-vpu/mtk_vpu.h |5 +
1 file changed, 5 insertions(+)
diff --git a/drivers/media/platform/mtk-vpu/mtk_vpu.h
b/drivers/media/platform/mtk-vpu/mtk_vpu.h
index f457479..291ae46 100644
--- a/drivers/media/
Add V4L2_PIX_FMT_MT21C in format list.
Signed-off-by: Minghsiu Tsai
---
drivers/media/platform/mtk-mdp/mtk_mdp_m2m.c |8
drivers/media/platform/mtk-mdp/mtk_mdp_regs.c |4
2 files changed, 12 insertions(+)
diff --git a/drivers/media/platform/mtk-mdp/mtk_mdp_m2m.c
b/driver
Add a DT binding documentation of MDP for the MT8173 SoC
from Mediatek
Signed-off-by: Minghsiu Tsai
Acked-by: Rob Herring
---
.../devicetree/bindings/media/mediatek-mdp.txt | 109
1 file changed, 109 insertions(+)
create mode 100644 Documentation/devicetree/bindings/m
If cxt->pstore.buf allocated failed, no need to initialize
cxt->pstore.buf_lock. So this patch moves spin_lock_init() after the
error checking.
Signed-off-by: Geliang Tang
---
fs/pstore/ram.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/pstore/ram.c b/fs/pstore/ram.c
in
Changes in v5:
- Add ack in the comment of dts patch
- Fix s/g_selection()
- Separate format V4L2_PIX_FMT_MT21C into new patch
Changes in v4:
- Add "depends on HAS_DMA" in Kconfig.
- Fix s/g_selection()
- Replace struct v4l2_crop with u32 and struct v4l2_rect
- Remove VB2_USERPTR
- Move mutex l
On newer components compatible with the at91sam9x5, the Touchscreen
Switches Closure Time or TSSCTIM value of the Touchscreen Mode Register is
not filled at all.
On some hardware, having no time indicated for it may lead to incoherent
values and jitter.
We fix this time to 10us as it is usually dif
Add MDP driver for MT8173
Signed-off-by: Minghsiu Tsai
---
drivers/media/platform/Kconfig| 17 +
drivers/media/platform/Makefile |2 +
drivers/media/platform/mtk-mdp/Makefile |9 +
drivers/media/platform/mtk-mdp/mtk_mdp_comp.c | 159
drivers/me
Since buffer_size() and buffer_start() have been defined in ram_core.c,
use them instead of open-coding.
Signed-off-by: Geliang Tang
---
fs/pstore/ram_core.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/fs/pstore/ram_core.c b/fs/pstore/ram_core.c
index 76c3f80..
Add MDP node for MT8173
Signed-off-by: Minghsiu Tsai
---
arch/arm64/boot/dts/mediatek/mt8173.dtsi | 84 ++
1 file changed, 84 insertions(+)
diff --git a/arch/arm64/boot/dts/mediatek/mt8173.dtsi
b/arch/arm64/boot/dts/mediatek/mt8173.dtsi
index 10f638f..cd93228 1006
On Tue, Aug 30, 2016 at 02:43:31PM +0530, Jagan Teki wrote:
> +&lcdif {
> + display = <&display0>;
> + status = "okay";
> +
> + display0: display {
> + bits-per-pixel = <16>;
> + bus-width = <18>;
> +
> + display-timings {
> + n
The KMS helpers (drm_atomic_helper_check_modeset/mode_fixup) pass
encoder->bridge directly to drm_bridge_mode_fixup, which expects a
valid pointer, or NULL (in which case it just returns).
Clear encoder->bridge if a bridge is not found, instead of keeping
the ERR_PTR value.
Since other drm_bridge
Hi Marc,
On 08/30/2016 05:54 AM, Marc Zyngier wrote:
On 30/08/16 10:55, Christoffer Dall wrote:
On Mon, Aug 29, 2016 at 10:51:14PM -0500, Shanker Donthineni wrote:
We are doing an unnecessary stack push/pop operation when restoring
the guest registers x0-x18 in __guest_enter(). This patch sav
On Tue, Aug 30, 2016 at 06:49:37PM +1000, Balbir Singh wrote:
>
>
> The origin of the issue I've seen seems to be related to
> rwsem spin lock stealing. Basically I see the system deadlock'd in the
> following state
As Nick says (good to see you're back Nick!), this is unrelated to
rwsems.
This
Hi Bharat,
On 30/08/16 11:39, Bharat Kumar Gogada wrote:
> PCIe legacy interrupts start at 1, not at 0.
> When testing with multi function device "error: hwirq 0x4 is too large for
> dummy" error comes.
> So adding one addtional interrupt when creating irq domain.
>
> Signed-off-by: Bharat Kumar
Dear Greg,
On 2016년 08월 30일 21:08, Greg KH wrote:
> On Tue, Jul 05, 2016 at 08:04:08PM +0900, Chanwoo Choi wrote:
>> Dear Greg,
>>
>> This is extcon-next pull request for v4.8. I add detailed description of
>> this pull request on below. Please pull extcon with following updates.
>>
>> Best Regard
On Tue, Aug 30, 2016 at 7:10 AM, Michal Simek wrote:
> Hi Rob,
>
> On 30.8.2016 01:45, Rob Herring wrote:
>> Microblaze bus probing is partially broken because "xlnx,compound" is
>> missing from the default bus probe. Add it to the default and remove from
>> the Microblaze arch code.
>
> xlnx,comp
The current mask enables and allows only one MSI interrupt on each MSI line.
This change, enables all MSI interrupts, which will also support End Points
with multi MSI support.
Signed-off-by: Bharat Kumar Gogada
---
drivers/pci/host/pcie-xilinx-nwl.c | 4 ++--
1 file changed, 2 insertions(+), 2
On Fri, Aug 19, 2016 at 06:51:51PM +0530, Kishon Vijay Abraham I wrote:
> Hi Greg,
>
> Please find the pull request for this -rc cycle below.
> It has fixes to get host-only mode working in sun4i, fixes a compilation
> error (failed to catch this earlier because of missing COMPILE_TEST) and
> othe
Hi Rob,
On 30.8.2016 01:45, Rob Herring wrote:
> Microblaze bus probing is partially broken because "xlnx,compound" is
> missing from the default bus probe. Add it to the default and remove from
> the Microblaze arch code.
xlnx,compound is not used for ages. I see see dts files for MB in the
tree
On Tue, Jul 05, 2016 at 08:04:08PM +0900, Chanwoo Choi wrote:
> Dear Greg,
>
> This is extcon-next pull request for v4.8. I add detailed description of
> this pull request on below. Please pull extcon with following updates.
>
> Best Regards,
> Chanwoo Choi
>
> The following changes since commit
On Mon, Aug 29, 2016 at 03:08:44PM +0530, Srikar Dronamraju wrote:
> > Patch "mm: vmscan: Begin reclaiming pages on a per-node basis" started
> > thinking of reclaim in terms of nodes but kswapd is still zone-centric. This
> > patch gets rid of many of the node-based versus zone-based decisions.
>
On Fri, Aug 26, 2016 at 05:38:05PM +0200, Rafał Miłecki wrote:
> On 25 August 2016 at 14:49, Greg KH wrote:
> > On Thu, Aug 25, 2016 at 10:03:52AM +0200, Rafał Miłecki wrote:
> >> +static void usbport_trig_activate(struct led_classdev *led_cdev)
> >> +{
> >> + struct usbport_trig_data *usbport
Hi Mathias,
On 18 August 2016 at 15:17, Felipe Balbi wrote:
>
> Hi,
>
> Baolin Wang writes:
>> It will reset the xhci quirks in xhci_gen_setup() function when xhci try to
>> add one hcd, thus we need to move the XHCI_LPM_SUPPORT quirk checking after
>> adding hcd.
>>
>> Signed-off-by: Baolin Wan
2016-08-30 20:39 GMT+09:00 Daniel Wagner :
> Hi Binoy,
>
> On 08/30/2016 12:28 PM, Binoy Jayan wrote:
>>
>> Examples of triggers:
>> echo 'hist:key=latency.log2:val=hitcount:sort=latency' >
>> /sys/kernel/debug/tracing/events/latency/latency_preempt/trigger
>> echo 'hist:key=cpu,latency:val=hitcoun
On Monday, August 29, 2016 05:13:34 PM Pavel Machek wrote:
> On Mon 2016-08-29 15:41:34, Rafael J. Wysocki wrote:
> > On Mon, Aug 29, 2016 at 6:59 AM, Borislav Petkov wrote:
> > > On Mon, Aug 29, 2016 at 12:35:40AM +0800, Chen Yu wrote:
> > >> On some platforms, there is occasional panic triggered
On Mon, Aug 29, 2016 at 05:41:09PM +0200, Peter Zijlstra wrote:
> On Fri, Aug 26, 2016 at 07:40:34PM -0400, Waiman Long wrote:
> > On 08/26/2016 11:18 AM, Peter Zijlstra wrote:
>
> > >Still need to look at adding spinning to the handoff case.
> > >Also need to look at writing (much) better changel
init_idle will set current->sched_class = &idle_sched_class
Signed-off-by: cheng chao
---
kernel/sched/core.c | 5 -
1 file changed, 5 deletions(-)
diff --git a/kernel/sched/core.c b/kernel/sched/core.c
index 556cb07..2f7c08d 100644
--- a/kernel/sched/core.c
+++ b/kernel/sched/core.c
@@ -75
Hi,
On 22 August 2016 at 12:23, Baolin Wang wrote:
> For system debugging, we usually want to know who sets one alarm timer, the
> time of the timer, when the timer started and fired and so on. Thus adding
> tracepoints can help us trace the alarmtimer information.
>
> For example, when we debug
On Tue, Aug 30, 2016 at 01:16:46PM +0200, Oliver Neukum wrote:
> On Tue, 2016-08-30 at 13:04 +0300, Heikki Krogerus wrote:
> > On Tue, Aug 30, 2016 at 11:32:01AM +0200, Oliver Neukum wrote:
>
> Hi,
>
> > > On Mon, 2016-08-29 at 15:36 +0300, Heikki Krogerus wrote:
> > > > +What: /sys/clas
Hi Daniel,
On 30 August 2016 at 17:00, Daniel Wagner wrote:
> Hi Binoy,
>
>
> As Masami has pointed out, the prefix trace_ should not be used. Also having
> trace_latency_ and latency_trace_ is kind of confusing. What about
> {start|stop}_latency_timing()? It would match the existing
> {start|sto
Currently, we try to allocate the cache as a single, large chunk, which
can fail if no big chunks of memory are available. We _do_ try to size
it according to the amount of memory in the box, but if the server is
started well after boot time, then the allocation can fail due to memory
fragmentation
On Tuesday, August 30, 2016 04:35:05 PM joeyli wrote:
> On Mon, Aug 29, 2016 at 03:41:23PM +0200, Borislav Petkov wrote:
> > On Mon, Aug 29, 2016 at 09:15:00AM +0200, Pavel Machek wrote:
> > > Sounds about as easy as hot unplugging arbitrary memory address. IOW
> > > "not easy".
> >
> > Regardless
On Monday, August 29, 2016 03:41:23 PM Borislav Petkov wrote:
> On Mon, Aug 29, 2016 at 09:15:00AM +0200, Pavel Machek wrote:
> > Sounds about as easy as hot unplugging arbitrary memory address. IOW
> > "not easy".
>
> Regardless, forcibly panicking the system more is still the wrong
> approach IM
On Mon, Aug 29, 2016 at 11:06:44AM -0500, Zhi Li wrote:
> On Wed, Aug 17, 2016 at 2:42 PM, Zhengyu Shen wrote:
> > MMDC is a multi-mode DDR controller that supports DDR3/DDR3L x16/x32/x64
> > and LPDDR2 two channel x16/x32 memory types. MMDC is configurable, high
> > performance, and optimized. MM
Hi Binoy,
On 08/30/2016 12:28 PM, Binoy Jayan wrote:
Examples of triggers:
echo 'hist:key=latency.log2:val=hitcount:sort=latency' >
/sys/kernel/debug/tracing/events/latency/latency_preempt/trigger
echo 'hist:key=cpu,latency:val=hitcount:sort=latency if cpu==1' >
/sys/kernel/debug/tracing/event
On Tue, Aug 30, 2016 at 06:59:39PM +0800, wei.guo.si...@gmail.com wrote:
> From: Simon Guo
>
> When one vma was with flag VM_LOCKED|VM_LOCKONFAULT (by invoking
> mlock2(,MLOCK_ONFAULT)), it can again be populated with mlock() with
> VM_LOCKED flag only.
>
> There is a hole in mlock_fixup() which
On Tue, Aug 30, 2016 at 06:59:38PM +0800, wei.guo.si...@gmail.com wrote:
> From: Simon Guo
>
> In do_mlock(), the check against locked memory limitation
> has a hole which will fail following cases at step 3):
> 1) User has a memory chunk from addressA with 50k, and user
> mem lock rlimit is 64k.
Hi Binoy,
On 08/30/2016 12:28 PM, Binoy Jayan wrote:
+static inline void trace_latency_preempt_mark_ts(enum latency_type ltype)
+{
+ this_cpu_write(lat_ts[ltype], (cycle_t) trace_clock_local());
+}
+
+static inline void latency_trace(enum latency_type type)
+{
+ trace_latency_preempt
On 24.08.16 11:50:15, Josh Poimboeuf wrote:
> dump_trace() doesn't add the interrupted instruction's address to the
> trace, so add it manually. This makes the profile more useful, and also
> makes it more consistent with what perf profiling does.
>
> Cc: Robert Richter
> Signed-off-by: Josh Poi
On Sat, Aug 27, 2016 at 04:19:50PM +, Stefan Wahren wrote:
> Patch 7f1d642fbb5c ("drivers/perf: arm-pmu: Fix handling of SPI lacking
> interrupt-affinity property") unintended also fixes perf_event support
> for bcm2835 which doesn't have PMU interrupts. Unfortunately this change
> introduce a
We get 2 warnings about global functions without a declaration
in the scsi driver when building with W=1:
drivers/scsi/scsi_lib.c:467:6: warning: no previous prototype for
'scsi_requeue_run_queue' [-Wmissing-prototypes]
drivers/scsi/scsi_lib.c:2609:6: warning: no previous prototype for
'scsi_evt_
On Tue, Aug 30, 2016 at 12:07:36PM +0100, Marc Zyngier wrote:
> +Mark
> On 30/08/16 11:35, majun (F) wrote:
> > 在 2016/8/30 16:50, Marc Zyngier 写道:
> >> On 30/08/16 05:17, MaJun wrote:
> >>> From: Ma Jun
> >>>
> >>> During system booting, if the interrupt which has no action registered
> >>> is tr
> Subject: Re: [PATCH] PCI: Xilinx NWL PCIe: Updating device tree documentation
> with prefetchable memory space
>
> On Tue, Aug 09, 2016 at 07:30:09PM +0530, Bharat Kumar Gogada wrote:
> > Updating device tree documentation with prefetchable memory sapce.
> > Configuration space shifted to 64-bit
On Tue 2016-08-30 18:39:18, Sergey Senozhatsky wrote:
> On (08/30/16 11:04), Petr Mladek wrote:
> > On Tue 2016-08-30 16:58:34, Sergey Senozhatsky wrote:
> > > Petr,
> > > one more question. Not related to the patch, but still related to NMI.
> > >
> > > can NMI nest?
> >
> > AFAIK, they cannot.
On Tue, 2016-08-30 at 13:04 +0300, Heikki Krogerus wrote:
> On Tue, Aug 30, 2016 at 11:32:01AM +0200, Oliver Neukum wrote:
Hi,
> > On Mon, 2016-08-29 at 15:36 +0300, Heikki Krogerus wrote:
> > > +What: /sys/class/typec//current_data_role
> > > +Date: June 2016
> > > +Contact:
Ups, forgot to fold the fix up into the commit.
---
>From 32c000ea9beb18555ab368e4dd22bac1ca8370e8 Mon Sep 17 00:00:00 2001
From: Michal Hocko
Date: Mon, 29 Aug 2016 17:08:20 +0200
Subject: [PATCH] oom: warn if we go OOM for higher order and compaction is
disabled
Since the lumpy reclaim is gone
From: Michal Hocko
Since the lumpy reclaim is gone there is no source of higher order pages
if CONFIG_COMPACTION=n except for the order-0 pages reclaim which is
unreliable for that purpose to say the least. Hitting an OOM for !costly
higher order requests is therefore all not that hard to imagine
Update:
I found out the bad performance was caused by partition alignment, and not by
the pertition per se (YaST created the partition next to the MBR). I compared
two partitions, number one badly aligned, and number 2 properly aligned. Then I
got these results:
Disk /dev/disk/by-id/dm-name-Fi
+Mark
On 30/08/16 11:35, majun (F) wrote:
>
>
> 在 2016/8/30 16:50, Marc Zyngier 写道:
>> On 30/08/16 05:17, MaJun wrote:
>>> From: Ma Jun
>>>
>>> During system booting, if the interrupt which has no action registered
>>> is triggered, it would cause system panic when try to access the
>>> action
Hi Tony,
On Friday 26 August 2016 09:00 PM, Tony Lindgren wrote:
> * Kishon Vijay Abraham I [160810 05:34]:
>> Since DRA7 has multiple PCIe Rootcomplex, add "linux,pci-domain"
>> property to assign a PCI domain number to each of the host
>> bridges.
>
> Is this patch safe to apply without the ot
From: Simon Guo
When one vma was with flag VM_LOCKED|VM_LOCKONFAULT (by invoking
mlock2(,MLOCK_ONFAULT)), it can again be populated with mlock() with
VM_LOCKED flag only.
There is a hole in mlock_fixup() which increase mm->locked_vm twice even
the two operations are on the same vma and both with
From: Simon Guo
This patch adds mlock() test for multiple invocation on
the same address area, and verify it doesn't mess the
rlimit mlock limitation.
Signed-off-by: Simon Guo
---
tools/testing/selftests/vm/.gitignore | 1 +
tools/testing/selftests/vm/Makefile | 4 +
From: Simon Guo
To prepare mlock2.h whose functionality will be reused.
Signed-off-by: Simon Guo
---
tools/testing/selftests/vm/mlock2-tests.c | 21 +
tools/testing/selftests/vm/mlock2.h | 20
2 files changed, 21 insertions(+), 20 deletions(-)
cr
From: Simon Guo
In do_mlock(), the check against locked memory limitation
has a hole which will fail following cases at step 3):
1) User has a memory chunk from addressA with 50k, and user
mem lock rlimit is 64k.
2) mlock(addressA, 30k)
3) mlock(addressA, 40k)
The 3rd step should have been allow
From: Simon Guo
This patch set fixes some mlock() misbehavior when mlock()/mlock2()
is invoked multiple times on intersect or same address regions.
And add selftest for this case.
Simon Guo (4):
mm: mlock: check against vma for actual mlock() size
mm: mlock: avoid increase mm->locked_vm on
On Tue, Aug 09, 2016 at 02:59:39PM -0700, York Sun wrote:
> Add DDR memory controller nodes to enable EDAC driver.
>
> Signed-off-by: York Sun
The patch subject is too general. I changed it to "arm64: dts: Add DDR
memory controller for Layerscape SoCs", and applied patch.
Shawn
On 30/08/16 10:55, Christoffer Dall wrote:
> On Mon, Aug 29, 2016 at 10:51:14PM -0500, Shanker Donthineni wrote:
>> We are doing an unnecessary stack push/pop operation when restoring
>> the guest registers x0-x18 in __guest_enter(). This patch saves the
>> two instructions by using x18 as a base r
On Tue, Aug 30, 2016 at 10:35:56AM +, Sumit Gupta wrote:
>
> > On Mon, Aug 29, 2016 at 02:32:25PM +0530, Sumit Gupta wrote:
> > > Removed restriction of displaying model name for 32 bit tasks only.
> > > Because of this Processor details were not displayed in "System
> > > setting -> Details"
Hi Binoy,
2016-08-30 19:28 GMT+09:00 Binoy Jayan :
> Latencies of missed timer offsets. Generate a histogram of missed
> timer offsets in microseconds. This will be a based along with irq
> and preemption latencies to calculate the effective process wakeup
> latencies.
>
> The following filter(s)
On Tue, 30 Aug 2016, Mika Westerberg wrote:
> On Tue, Aug 30, 2016 at 10:13:30AM +0100, Lee Jones wrote:
> > On Mon, 29 Aug 2016, Mika Westerberg wrote:
> >
> > > On Mon, Aug 15, 2016 at 10:10:41AM +0300, Mika Westerberg wrote:
> > > > Hi,
> > > >
> > > > This is third version of the series. Pre
of_get_flat_dt_subnode_by_name can return negative value in case of error.
Assigning the result to unsigned variable and checking if the variable
is lesser than zero is incorrect and always false.
The patch fixes it by using signed variable to check the result.
The problem has been detected using
PCIe legacy interrupts start at 1, not at 0.
When testing with multi function device "error: hwirq 0x4 is too large for
dummy" error comes.
So adding one addtional interrupt when creating irq domain.
Signed-off-by: Bharat Kumar Gogada
---
drivers/pci/host/pcie-xilinx-nwl.c | 2 +-
1 file changed
The current driver prints pcie core error, for all core events.
Instead of just printing PCIe core error, now adding prints to show
individual core events occurred.
Signed-off-by: Bharat Kumar Gogada
---
drivers/pci/host/pcie-xilinx-nwl.c | 48 +++---
1 file chang
Joonsoo Kim writes:
> 2016-08-29 18:27 GMT+09:00 Aneesh Kumar K.V :
>> js1...@gmail.com writes:
>>
>>> From: Joonsoo Kim
>>>
>>> Hello,
>>>
>>> Changes from v4
>>> o Rebase on next-20160825
>>> o Add general fix patch for lowmem reserve
>>> o Fix lowmem reserve ratio
>>> o Fix zone span optimiza
在 2016/8/30 16:50, Marc Zyngier 写道:
> On 30/08/16 05:17, MaJun wrote:
>> From: Ma Jun
>>
>> During system booting, if the interrupt which has no action registered
>> is triggered, it would cause system panic when try to access the
>> action member.
>
> And why would that interrupt be enabled? I
> On Mon, Aug 29, 2016 at 02:32:25PM +0530, Sumit Gupta wrote:
> > Removed restriction of displaying model name for 32 bit tasks only.
> > Because of this Processor details were not displayed in "System
> > setting -> Details" in Ubuntu model name display is generic and can be
> > printed for 64
> static inline void check_highest_zone(enum zone_type k)
> {
> - if (k > policy_zone && k != ZONE_MOVABLE)
> + if (k > policy_zone && k != ZONE_MOVABLE && !is_zone_cma_idx(k))
> policy_zone = k;
> }
>
Should we apply policy to allocation from ZONE CMA ?. CMA reser
Signed-off-by: Eric Engestrom
---
drivers/block/skd_main.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/block/skd_main.c b/drivers/block/skd_main.c
index 3822eae..94a7425 100644
--- a/drivers/block/skd_main.c
+++ b/drivers/block/skd_main.c
@@ -1905,7 +1905,7 @@
Latencies of missed timer offsets. Generate a histogram of missed
timer offsets in microseconds. This will be a based along with irq
and preemption latencies to calculate the effective process wakeup
latencies.
The following filter(s) may be used
'hist:key=common_pid.execname'
'hist:key=common_pi
From: Steve Twiss
Dialog Semiconductor support would like to add to the MAINTAINERS search
terms. This update will allow us to follow files for device tree bindings
relating to input onkey driver(s).
Signed-off-by: Steve Twiss
---
Resend with Rob Herring added in the e-mail list.
Hi Dmitry &
This work is based on work by Daniel Wagner. A few tracepoints are added
at the end of the critical section. With the hist trigger in place, the
hist trigger plots may be generated, with per-cpu breakdown of events
captured. It is based on linux kernel's event infrastructure.
The following filter(
Hi,
Thank you Daniel for reviewing v3 throroughly.
These set of patches [v4] capture latency events caused by interrupts and
premption disabled in kernel. The patches are based on the hist trigger
feature developed by Tom Zanussi.
v3: https://lkml.org/lkml/2016/8/29/50
v2: https://lkml.org/lkml/2
601 - 700 of 842 matches
Mail list logo
