4.2.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Prarit Bhargava
commit 93d68841a23a5779cef6fb9aa0ef32e7c5bd00da upstream.
ACPICA commit 7a3bd2d962f221809f25ddb826c9e551b916eb25
Set th
4.2.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Maxim Patlasov
commit 7ae8fd0351f912b075149a1e03a017be8b903b9a upstream.
propagate_one(m) calculates "type" argument for copy_tree() lik
4.2.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Anton Blanchard
commit b4c112114aab9aff5ed4568ca5e662bb02cdfe74 upstream.
In create_zero_mask() we have:
addi%1,%2,-1
4.2.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Vitaly Prosyak
commit 5d5b7803c49bbb01bdf4c6e95e8314d0515b9484 upstream.
When crtc/timing is disabled on boot the dig block
should be st
4.2.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Keith Busch
commit 1bdb8970392a68489b469c3a330a1adb5ef61beb upstream.
If x86_vector_alloc_irq() fails x86_vector_free_irqs() is invoked
4.2.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Imre Deak
commit dab9a2663f4e688106c041f7cd2797a721382f0a upstream.
During system resume we depended on pci_enable_device() also putting
4.2.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: James Morse
commit 625fe4f8ffc1b915248558481bb94249f6bd411c upstream.
arm_cpuidle_suspend() may return -EOPNOTSUPP, or any value returne
4.2.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Linus Torvalds
commit 689de1d6ca95b3b5bd8ee446863bf81a4883ea25 upstream.
This is a fairly minimal fixup to the horribly bad behavior of
4.2.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Jiang Liu
commit 111abeba67e0dbdc26537429de9155e4f1d807d8 upstream.
There's a race condition between
x86_vector_free_irqs()
{
f
4.2.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: =?UTF-8?q?Ville=20Syrj=C3=A4l=C3=A4?=
commit 4ea3959018d09edfa36a9e7b5ccdbd4ec4b99e49 upstream.
Somehow my SNB GT1 (Dell XPS 8300) gets
On Sat, May 07, 2016 at 06:21:45PM +0300, Ivaylo Dimitrov wrote:
> With the upcoming removal of legacy boot, lets add support to one of the
> last N900 drivers remaining without it. As the driver still uses omap
> dmtimer, add auxdata as well.
>
> Signed-off-by: Ivaylo Dimitrov
> ---
> .../devic
4.2.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Mika Kahola
commit 992e7a41f9fcc7bcd10e7d346aee5ed7a2c241cb upstream.
It was noticed on bug #94087 that module parameter
i915.edp_vswing
On Sun, May 08, 2016 at 09:06:07PM +0200, Krzysztof Kozlowski wrote:
> The Hardkernel's Odroid XU board was first design with big.LITTLE SoC
> from Samsung: the Exynos5410. Comparing now to more popular Odroid XU3
> the differences are:
> 1. Exynos5410 instead of 5422,
> 2. DisplayPort,
> 3. Main P
On Monday 09 May 2016 21:06:07 Christian Lamparter wrote:
> Uh, Thanks for the participation!
>
> On Monday, May 09, 2016 05:08:48 PM Arnd Bergmann wrote:
> > On Monday 09 May 2016 13:39:50 Felipe Balbi wrote:
> > > Arnd Bergmann writes:
> > > > On Monday 09 May 2016 10:23:22 Benjamin Herrenschmi
4.2.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Roman Pen
commit 346c09f80459a3ad97df1816d6d606169a51001a upstream.
The bug in a workqueue leads to a stalled IO request in MQ ctx->rq_l
4.2.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Imre Deak
commit 5eaa60c7109b40f17ac81090bc8b90482da76cd1 upstream.
The driver's VDD on/off logic assumes that whenever the VDD is on we
4.2.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Michael Neuling
commit d6776bba44d9752f6cdf640046070e71ee4bba7b upstream.
Keep IRQ mappings on context teardown. This won't leak IRQs a
4.2.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Mike Manning
commit 1d377f4d690637a0121eac8701f84a0aa1e69a69 upstream.
The Link ECU is an aftermarket ECU computer for vehicles that pro
4.2.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Hector Marco-Gisbert
commit 8b8addf891de8a00e4d39fc32f93f7c5eb8feceb upstream.
Currently on i386 and on X86_64 when emulating X86_32 in
4.2.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Conrad Kostecki
commit 037e119738120c1cdc460c6ae33871c3000531f3 upstream.
Fixes audio output on a ThinkPad X260, when using Lenovo CES 2
On Mon, 9 May 2016 12:53:36 -0500 Reza Arbab wrote:
> While it is currently possible to rezone memory when it is onlined, there are
> implicit assumptions about the zones:
>
> * To "online_kernel" a block into ZONE_NORMAL, it must currently
> be in ZONE_MOVABLE.
>
> * To "online_movable" a b
4.2.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Jasem Mutlaq
commit 613ac23a46e10d4d4339febdd534fafadd68e059 upstream.
Adding VID:PID for Straizona Focusers to cp210x driver.
Signed-o
On Mon, 9 May 2016 13:11:58 -0700 Andrew Morton
wrote:
> On Mon, 9 May 2016 12:53:36 -0500 Reza Arbab
> wrote:
>
> > While it is currently possible to rezone memory when it is onlined, there
> > are
> > implicit assumptions about the zones:
> >
> > * To "online_kernel" a block into ZONE_NO
4.2.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Michael Ellerman
commit 609d5a1b2b35bb62b4b3750396e55453160c2a17 upstream.
Since commit ea8daa7b9784 ("kbuild: Add option to turn incomp
4.2.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Laszlo Ersek
commit 630ba0cc7a6dbafbdee43795617c872b35cde1b4 upstream.
The variable_matches() function can currently read "var_name[len]
4.2.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Hans Verkuil
commit 3020ca711871fdaf0c15c8bab677a6bc302e28fe upstream.
The VSync polarity was negative instead of positive for the 4k CE
On Mon, May 09, 2016 at 02:51:17PM +0800, Wenyou Yang wrote:
> It is a datasheet bug, for current SoCs, the RB_EDGE3(i.e. bit 27)
> of HSMC_SR register does not exist, the RB_EDGE0 (i.e. bit 24) is
> the ready/busy line edge status bit. So the compatible
> "atmel,sama5d4-nfc" is unneeded.
The comp
On Monday 09 May 2016 22:01:17 Pablo Neira Ayuso wrote:
> On Mon, May 09, 2016 at 09:47:23PM +0200, Arnd Bergmann wrote:
> > A recent commit introduced an unconditional use of an uninitialized
> > variable, as reported in this gcc warning:
> >
> > net/netfilter/nf_conntrack_core.c: In function '__
4.2.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Javier Martinez Canillas
commit 10ff4c5239a137abfc896ec73ef3d15a0f86a16a upstream.
The exynos5 I2C controller driver always prepares and
Em Sat, May 07, 2016 at 02:15:36PM +1000, Michael Ellerman escreveu:
> On Thu, 2016-05-05 at 15:23:19 UTC, "Naveen N. Rao" wrote:
> > Generalize existing macros to serve the purpose.
> >
> > Cc: Wang Nan
> > Cc: Arnaldo Carvalho de Melo
> > Cc: Masami Hiramatsu
> > Cc: Ian Munsie
> > Cc: Micha
4.2.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Mark Brown
commit 47325078f2a3e543150e7df967e45756b2fff7ec upstream.
The dummy component is reused for all cards so we special case and
On Mon, May 09, 2016 at 02:53:54PM +0800, Wei Ni wrote:
> Add HW throttle configuration sub-node for soctherm, which
> is used to describe the throttle event, and worked as a
> cooling device. The "hot" type trip in thermal zone can
> be bound to this cooling device, and trigger the throttle
> func
4.2.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Sugar Zhang
commit 653aa4645244042826f105aab1be3d01b3d493ca upstream.
this patch corrects the interface adc/dac control register definit
4.2.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Krzysztof Kozlowski
commit 07d2390e36ee5b3265e9cc8305f2a106c8721e16 upstream.
In certain probe conditions the interrupt came right after
4.2.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Oleksij Rempel
commit de478a61389cacafe94dc8b035081b681b878f9d upstream.
by moving common code to ar5008_hw_cmn_spur_mitigate i forgot t
4.2.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Ignat Korchagin
commit b348d7dddb6c4fbfc810b7a0626e8ec9e29f7cbb upstream.
Fix potential out-of-bounds write to urb->transfer_buffer
usbi
4.2.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: "cp...@redhat.com"
commit 263efde31f97c498e1ebad30e4d2906609d7ad6b upstream.
We can thank KASAN for finding this, otherwise I probably w
Hello Krzysztof,
On 05/08/2016 03:05 PM, Krzysztof Kozlowski wrote:
> Just like clock driver for Exynos542x/5800, provide the fixed clock here
> so the clock bindings and their consumers would be consistent and
> similar.
>
> However a clock named "fin_pll" is already provided by generic
> fixed-
Upgrading a system from kernel 4.2 to 4.6rc7, there is an extra 2 minute
delay while booting due to these problems:
[ 47.977221] bnx2x :04:00.1: Direct firmware load for
bnx2x/bnx2x-e2-7.13.1.0.fw failed with error -2
[ 48.029997] bnx2x :04:00.1: Falling back to user helper
On 5/9/2016 3:36 AM, Arnd Bergmann wrote:
> On Monday 09 May 2016 10:23:22 Benjamin Herrenschmidt wrote:
>> On Sun, 2016-05-08 at 13:44 +0200, Christian Lamparter wrote:
>>> On Sunday, May 08, 2016 08:40:55 PM Benjamin Herrenschmidt wrote:
On Sun, 2016-05-08 at 00:54 +0200, Christian Lamp
In preparation for being able to detect where to split up contiguous
memory regions that overlap with memory regions to avoid, we need to
pass back what the earliest overlapping region was. This modifies the
overlap checker to return that information.
Based on a separate mem_min_overlap() implemen
From: Baoquan He
The current KASLR implementation randomizes the physical and virtual
addresses of the kernel together (both are offset by the same amount). It
calculates the delta of the physical address where vmlinux was linked
to load and where it is finally loaded. If the delta is not equal t
On Mon, May 09, 2016 at 04:00:12PM +0800, honghui.zh...@mediatek.com wrote:
> From: Honghui Zhang
>
> This patch defines the local arbitor port IDs for mediatek SoC MT2701 and
> add descriptions of binding for mediatek generation one iommu and smi.
>
> Signed-off-by: Honghui Zhang
> ---
> .../
Hello Krzysztof,
On 05/08/2016 03:05 PM, Krzysztof Kozlowski wrote:
> The clk-exynos5410 driver now provides the "fin_pll" external fixed
> clock. Switch the Multi-Core Timer to this clock.
>
> Signed-off-by: Krzysztof Kozlowski
> ---
Reviewed-by: Javier Martinez Canillas
Best regards,
--
Ja
KASLR will be calling get_random_long() twice, but the debug output
won't distinguishing between them. This patch adds a report on when it
is fetching the physical vs virtual address. With this, once the virtual
offset is separate, the report changes from:
KASLR using RDTSC...
KASLR using RDTSC...
From: Yinghai Lu
Currently the physical randomization's lower boundary is the original
kernel load address. For bootloaders that load kernels into very high
memory (e.g. kexec), this means randomization takes place in a very small
window at the top of memory, ignoring the large region of physical
Okay, here's the remaining patches for this series. Hopefully these
are clean and obvious. Technically this is v7 of the series, though
much of it has already been added to -tip already. This is all based on
the work of Yinghai, Baoquan, and myself.
***Background:
Bugs have been reported around kd
There were some files with missing header comments. Since they are
included from both compressed and regular kernels, make note of that.
Also corrects a typo in the mem_avoid comments.
Signed-off-by: Kees Cook
---
arch/x86/boot/compressed/kaslr.c | 2 +-
arch/x86/boot/early_serial_console.c
This patch exchanges the prior slots[] array for the new slot_areas[]
array, and lifts the limitation of KERNEL_IMAGE_SIZE on the physical
address offset for 64-bit. As before, process_e820_entry() walks
memory and populates slot_areas[], splitting on any detected mem_avoid
collisions.
Finally, si
From: Baoquan He
To support randomizing the kernel virtual address separately from the
physical address, this patch adds find_random_virt_addr() to choose
a slot anywhere between LOAD_PHYSICAL_ADDR and KERNEL_IMAGE_SIZE.
Since this address is virtual, not physical, we can place the kernel
anywher
Hello Krzysztof,
On 05/08/2016 03:05 PM, Krzysztof Kozlowski wrote:
> All "fin_pll" clock users are switched to the new one, provided by
s/are switched/were switched
> Exynos5410 clock driver. Remove old DT node.
>
> Signed-off-by: Krzysztof Kozlowski
> ---
Reviewed-by: Javier Martinez Canill
From: Baoquan He
In order to support KASLR moving the kernel anywhere in physical memory
(which could be up to 64TB), we need to handle counting the potential
randomization locations in a more efficient manner.
In the worst case with 64TB, there could be roughly 32 * 1024 * 1024
randomization sl
On Mon, May 09, 2016 at 01:48:27PM +0200, Niklas Cassel wrote:
> From: Niklas Cassel
>
> This commit adds the Device Tree binding documentation that allows to
> describe the PCIe controller found in the Axis ARTPEC-6 SoC.
>
> Signed-off-by: Niklas Cassel
> ---
> Changes since v1:
> - Rename sy
Hello Krzysztof,
On 05/08/2016 03:05 PM, Krzysztof Kozlowski wrote:
> For smooth transition of fin_pll to clk-exynos5410.c from fixed-clock
> driver, initially it was named "fin_pll_new". Fix this here.
>
> Signed-off-by: Krzysztof Kozlowski
> ---
Reviewed-by: Javier Martinez Canillas
Best re
As it turns out, mapping_info DOES need to be initialized every
time. Without this, page tables were not being corrected updated, which
could cause reboots when a physical address beyond 2G was chosen.
Signed-off-by: Kees Cook
---
arch/x86/boot/compressed/pagetable.c | 16 +---
1 fil
On 05/09/2016 08:11 PM, Pantelis Antoniou wrote:
> Insert overlay symbols to the base tree when applied.
> This makes it possible to apply an overlay that references a label
> that a previously inserted overlay had.
>
> Signed-off-by: Pantelis Antoniou
> Tested-by: Geert Uytterhoeven
>
> ---
>
Hi Pantelis,
On Mon, May 9, 2016 at 8:11 PM, Pantelis Antoniou
wrote:
> --- a/drivers/of/base.c
> +++ b/drivers/of/base.c
> @@ -1073,9 +1097,14 @@ struct device_node *of_find_node_by_phandle(phandle
> handle)
> return NULL;
>
> raw_spin_lock_irqsave(&devtree_lock, flags)
On Mon, May 9, 2016 at 5:57 AM, Christoph Hellwig wrote:
> On Sun, May 08, 2016 at 03:35:10PM -0700, Dan Williams wrote:
>> Device DAX is the device-centric analogue of Filesystem DAX
>> (CONFIG_FS_DAX). It allows memory ranges to be allocated and mapped
>> without need of an intervening file sys
On Monday 09 May 2016 13:22:48 John Youn wrote:
> On 5/9/2016 3:36 AM, Arnd Bergmann wrote:
> > On Monday 09 May 2016 10:23:22 Benjamin Herrenschmidt wrote:
> >> On Sun, 2016-05-08 at 13:44 +0200, Christian Lamparter wrote:
> >>> On Sunday, May 08, 2016 08:40:55 PM Benjamin Herrenschmidt wrote:
> >
Hi,
On Tue, May 03, 2016 at 10:32:39AM -0700, Tony Lindgren wrote:
> * Sebastian Reichel [160429 19:11]:
> > Merge omap_ssi and omap_ssi_port into one module. This
> > fixes problems with module cycle dependencies introduced
> > by future patches.
>
> Can you please check against the hardware fo
Hi Vinod,
On Monday 02 May 2016 15:07:12 Vinod Koul wrote:
> On Fri, Apr 22, 2016 at 01:50:04AM +, Kuninori Morimoto wrote:
> > From: Kuninori Morimoto
> >
> > Current rcar_dmac_desc_put() is using list_add_tail() in order to
> > push used descriptor to list of free descriptors, and next DMA
We did not handle XSAVES instructions correctly. There were issues in
converting between standard and compacted format when interfacing with
user-space. These issues have been corrected.
Add a WARN_ONCE() to make it clear that XSAVES supervisor states are not
yet implemented.
Signed-off-by: Yu-ch
Hi,
On 9.05.2016 22:36, Tony Lindgren wrote:
* Ivaylo Dimitrov [160507 08:24]:
once omap_dm_timer_start() is called, which calls omap_dm_timer_enable()
and thus pm_runtime_get_sync(), it doesn't make sense to call PM runtime
functions again before omap_dm_timer_stop is called(). Otherwise PM
Add a warning in case a disabled (not existing) xstate component offset
is requested.
Signed-off-by: Yu-cheng Yu
---
arch/x86/kernel/fpu/xstate.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/x86/kernel/fpu/xstate.c b/arch/x86/kernel/fpu/xstate.c
index 350814c..2e6dbfe 100644
--- a/ar
XSAVES is a kernel-mode instruction. It offers a compacted format and
memory-write optimization. These patches fix issues in the first
implementation. They are intended for discussion and getting feedback
before actually getting applied.
Changes since Version 4:
Patch 4 - Introduce a new check to
Hello Krzysztof,
On 05/08/2016 03:05 PM, Krzysztof Kozlowski wrote:
> Just like other Exynos5 family SoCs, this one has four UARTs. Add
> missing UART3 clocks to the Exynso5410 clock driver.
>
> Add clocks for USB and PWM.
>
> Signed-off-by: Krzysztof Kozlowski
> ---
I don't have an Exynos5410
The arrays xstate_offsets[] and xstate_sizes[] record XSAVE standard-
format offsets and sizes. Values for non-extended state components
fpu and xmm's were not initialized or used. Ptrace format conversion
needs them. Fix it.
Signed-off-by: Yu-cheng Yu
Reviewed-by: Dave Hansen
---
arch/x86/kern
Keep init_fpstate.xsave.header.xfeatures as zero for init optimization.
This is important for init optimization that is implemented in processor.
If a bit corresponding to an xstate in xstate_bv is 0, it means the
xstate is in init status and will not be read from memory to the processor
during XRS
When XSAVES is used, xsave.header.xcomp_bv[63] must be set.
Signed-off-by: Yu-cheng Yu
---
arch/x86/kernel/fpu/core.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/x86/kernel/fpu/core.c b/arch/x86/kernel/fpu/core.c
index 41ab106..25e2605 100644
--- a/arch/x86/kernel/fpu/core.c
+++
CPUID function 0x0d, sub function (i, i > 1) returns in ecx[1] the
alignment requirement of component i when the compacted format is used.
If ecx[1] is 0, component i is located immediately following the preceding
component. If ecx[1] is 1, component i is located on the next 64-byte
boundary follo
CPUID function 0x0d, sub function (i, i > 1) returns in ebx the offset of
xstate component i. Zero is returned for a supervisor state. A supervisor
state can only be saved by XSAVES and XSAVES uses a compacted format.
There is no fixed offset for a supervisor state. This patch checks and
makes sure
Hello Krzysztof,
On 05/08/2016 03:05 PM, Krzysztof Kozlowski wrote:
> The 'sd0_rclk' was put in the middle of SD1 nodes. Remove the confusion.
>
> Signed-off-by: Krzysztof Kozlowski
> ---
Reviewed-by: Javier Martinez Canillas
Best regards,
--
Javier Martinez Canillas
Open Source Group
Samsun
XSAVES is a kernel instruction and uses a compacted format. When working
with user space, the kernel should provide standard-format, non-supervisor
state data. We cannot do __copy_to_user() from a compacted- format kernel
xstate area to a signal frame.
Dave Hansen proposes this method to simplify
XSAVES uses compacted format and is a kernel instruction. The kernel
should use standard-format, non-supervisor state data for PTRACE.
Signed-off-by: Yu-cheng Yu
---
arch/x86/include/asm/fpu/xstate.h | 5 +-
arch/x86/kernel/fpu/regset.c | 56 +
arch/x86/kernel/fpu/xstate.c
When the kernel is using XSAVES compacted format, we cannot do
__copy_from_user() from a signal frame, which has standard-format data.
Fix it by using copyin_to_xsaves().
Signed-off-by: Yu-cheng Yu
---
arch/x86/kernel/fpu/signal.c | 11 +--
1 file changed, 9 insertions(+), 2 deletions(-)
User space uses standard format xsave area. fpstate in signal frame should
have standard format size.
To explicitly distinguish between xstate size in kernel space and the one
in user space, we rename xstate_size to kernel_xstate_size. This patch is
not fixing a bug. It just makes kernel code more
Hello Krzysztof,
On 05/08/2016 03:05 PM, Krzysztof Kozlowski wrote:
> Fro consistency lowercase node labels are used.
>
s/Fro/For
> Signed-off-by: Krzysztof Kozlowski
> ---
Reviewed-by: Javier Martinez Canillas
Best regards,
--
Javier Martinez Canillas
Open Source Group
Samsung Research Am
Hi,
On 9.05.2016 23:06, Rob Herring wrote:
On Sat, May 07, 2016 at 06:21:45PM +0300, Ivaylo Dimitrov wrote:
With the upcoming removal of legacy boot, lets add support to one of the
last N900 drivers remaining without it. As the driver still uses omap
dmtimer, add auxdata as well.
Signed-off-b
Component offset print out was incorrect for XSAVES. Correct it and move
to a separate function.
Signed-off-by: Yu-cheng Yu
Reviewed-by: Dave Hansen
---
arch/x86/kernel/fpu/xstate.c | 18 --
1 file changed, 16 insertions(+), 2 deletions(-)
diff --git a/arch/x86/kernel/fpu/xstat
If "xsaves" is enabled, kernel always uses compacted format of xsave area.
But user space still uses standard format of xsave area. Thus, xstate size
in kernel's xsave area is smaller than xstate size in user's xsave area.
The xstate in signal frame should be in standard format for user's signal
ha
> Josef,
>
> On Mon, 9 May 2016, Josef Bacik wrote:
>
> > I've hit a regression that was introduced by the commit in $SUBJECT.
> > I'm building a minimal kernel config that doesn't have CONFIG_SMP set,
> > which results in the topology for the box to look different than with
> > CONFIG_SMP set.
This patchset contains necessary code changes to support two-level
(Indirection) table walk feature for device table.
Shanker Donthineni (2):
irqchip/gicv3-its: split its_alloc_tables() into two functions
irqchip/gicv3-its: Implement two-level(indirect) device table support
drivers/irqchip/i
On Wed, 4 May 2016 11:40:03 +
Eric Auger wrote:
> iommu_get/put_msi_cookie allocates/frees the resource used to store
> and ref count the MSI doorbell mappings. iommu_msi_set_aperture
> initializes the iova domain used for MSI IOVA allocation and sets the
> iommu domain's msi geometry.
>
>
Hello Krzysztof,
On 05/08/2016 03:05 PM, Krzysztof Kozlowski wrote:
> Configure the pinctrl for MMC0 (eMMC) and MMC2 (microSD card).
>
> Signed-off-by: Krzysztof Kozlowski
> ---
Reviewed-by: Javier Martinez Canillas
Best regards,
--
Javier Martinez Canillas
Open Source Group
Samsung Research
Since device IDs are extremely sparse, the single, a.k.a flat table is
not sufficient for the following two reasons.
1) According to ARM-GIC spec, ITS hw can access maximum of 256(pages)*
64K(pageszie) bytes. In the best case, it supports upto DEVid=21
sparse with minimum device table entry
The function is getting out of control, it has too many goto
statements and would be too complicated for adding a feature
two-level device table. So, it is time for us to cleanup and
move some of the logic to a separate function without affecting
the existing functionality.
Signed-off-by: Shanker
Hello Krzysztof,
On 05/08/2016 03:05 PM, Krzysztof Kozlowski wrote:
> The LED nodes can be shared between Odroid XU3, XU3-Lite and XU (not yet
> added) thus removing duplication.
>
> Signed-off-by: Krzysztof Kozlowski
> ---
Reviewed-by: Javier Martinez Canillas
Best regards,
--
Javier Martin
On Mon, May 9, 2016 at 3:53 PM, Ivaylo Dimitrov
wrote:
> Hi,
>
> On 9.05.2016 23:06, Rob Herring wrote:
>>
>> On Sat, May 07, 2016 at 06:21:45PM +0300, Ivaylo Dimitrov wrote:
>>>
>>> With the upcoming removal of legacy boot, lets add support to one of the
>>> last N900 drivers remaining without i
On 05/09/2016 10:13 AM, Paolo Bonzini wrote:
>
>
> On 02/05/2016 20:31, Andy Lutomirski wrote:
>> And did the SEV implementation remember to encrypt the guest register
>> state? Because, if not, everything of importance will leak out
>> through the VMCB and/or GPRs.
>
> No, it doesn't. And SEV
On 5/9/2016 1:39 PM, Arnd Bergmann wrote:
> On Monday 09 May 2016 13:22:48 John Youn wrote:
>> On 5/9/2016 3:36 AM, Arnd Bergmann wrote:
>>> On Monday 09 May 2016 10:23:22 Benjamin Herrenschmidt wrote:
On Sun, 2016-05-08 at 13:44 +0200, Christian Lamparter wrote:
> On Sunday, May 08, 2016
On Mon, May 9, 2016 at 3:38 PM, Geert Uytterhoeven wrote:
> Hi Pantelis,
>
> On Mon, May 9, 2016 at 8:11 PM, Pantelis Antoniou
> wrote:
>> --- a/drivers/of/base.c
>> +++ b/drivers/of/base.c
>
>> @@ -1073,9 +1097,14 @@ struct device_node *of_find_node_by_phandle(phandle
>> handle)
>>
Em Mon, May 09, 2016 at 01:47:51AM +, Wang Nan escreveu:
> This test checks reading from backward ring buffer.
>
> Test result:
>
> # ~/perf test 'ring buffer'
> 45: Test backward reading from ring buffer : Ok
Thanks, applied and also I added a patch to show that bit when
On Mon, May 09, 2016 at 11:23:03AM -0700, Dan Williams wrote:
> On Mon, May 9, 2016 at 11:12 AM, Toshi Kani wrote:
> > On Sun, 2016-05-08 at 12:14 -0700, Dan Williams wrote:
> >> On Thu, May 5, 2016 at 5:29 PM, Toshi Kani wrote:
> > :
> >> > +int bdev_supports_dax(struct super_block *sb, int blo
The mechanisms for remote CPU updates and slow-path frequency
transitions are relatively expensive - the former is an IPI while the
latter requires waking up a thread to do work. These activities should
be avoided if they are not necessary. To that end, calculate the
actual target-supported frequen
Without calling the cpufreq hook for a remote wakeup it is possible
for such a wakeup to go unnoticed by cpufreq on the target CPU for up
to a full tick. This can occur if the target CPU is running a
CPU-bound task and preemption does not occur. If preemption does occur
then the scheduler is expect
In preparation for the scheduler cpufreq callback happening on remote
CPUs, add support for this in schedutil.
Schedutil currently requires the callback occur on the CPU being
updated in order to support fast frequency switches. Remove this
limitation by checking for the current CPU being outside
Hi Arnd,
On Tue, May 03, 2016 at 05:16:19PM +0200, Arnd Bergmann wrote:
> One patch you added yesterday unfortunately caused (at least) three
> separate build problems with 32-bit ARM randconfig builds.
>
> These three patches should make it all work again.
Sorry for the delayed respones, I was
The cpufreq update hook is presently not called when the target CPU is not the
current CPU. This may cause a delay in adjusting the frequency of the target
CPU to accommodate new task load since the target CPU may not run the scheduler
hook until the next tick.
In order to test this series I wrote
Upcoming support for scheduler cpufreq callbacks on remote wakeups
will require the client to know what the target CPU is that the
callback is being invoked for. Add this information into the callback
data structure.
Signed-off-by: Steve Muckle
---
include/linux/sched.h | 1 +
kernel/sched/cpuf
The rate limit timestamp (last_freq_update_time) is currently advanced
anytime schedutil re-evaluates the policy regardless of whether the CPU
frequency is changed or not. This means that utilization updates which
have no effect can cause much more significant utilization updates
(which require a l
701 - 800 of 1139 matches
Mail list logo
