In preparation to add more program headers, keep a count of phdrs.
Signed-off-by: Adrian Hunter
---
tools/perf/util/symbol-elf.c | 9 -
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git a/tools/perf/util/symbol-elf.c b/tools/perf/util/symbol-elf.c
index b13873a6f368..4e7b71e8ac
Identify extra kernel maps by name so that they can be distinguished from
the kernel map and module maps.
Signed-off-by: Adrian Hunter
---
tools/perf/util/event.c | 2 +-
tools/perf/util/machine.c | 8 ++--
tools/perf/util/map.c | 22 ++
tools/perf/util/map.h
In preparation to add more program headers, iterate phdrs instead of
assuming there is only one for the kernel text and one for the modules.
Signed-off-by: Adrian Hunter
---
tools/perf/util/symbol-elf.c | 25 ++---
1 file changed, 10 insertions(+), 15 deletions(-)
diff --git
In preparation to add more program headers, calculate offset from the
number of phdrs.
Signed-off-by: Adrian Hunter
---
tools/perf/util/symbol-elf.c | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/tools/perf/util/symbol-elf.c b/tools/perf/util/symbol-elf.c
index 4e7b71e8
Identify and copy any sections for x86 PTI entry trampolines.
Signed-off-by: Adrian Hunter
---
tools/perf/util/symbol-elf.c | 42 ++
1 file changed, 42 insertions(+)
diff --git a/tools/perf/util/symbol-elf.c b/tools/perf/util/symbol-elf.c
index 37d9324c27
In preparation to add more program headers, layout the relative offset of
each section.
Signed-off-by: Adrian Hunter
---
tools/perf/util/symbol-elf.c | 25 ++---
1 file changed, 22 insertions(+), 3 deletions(-)
diff --git a/tools/perf/util/symbol-elf.c b/tools/perf/util/symb
x86 PTI entry trampolines all map to the same physical page. If that is
reflected in the program headers of /proc/kcore, then do the same for the
copy of kcore.
Signed-off-by: Adrian Hunter
---
tools/perf/util/symbol-elf.c | 53 ++--
1 file changed, 51 ins
In preparation to add more program headers, get rid of kernel_map and
modules_map by moving ->kernel_map and ->modules_map to newly allocated
entries in the ->phdrs list.
Signed-off-by: Adrian Hunter
---
tools/perf/util/symbol-elf.c | 70
1 file chang
Currently, kcore_copy makes 2 program headers, one for the kernel text
(namely kernel_map) and one for the modules (namely modules_map). Now more
program headers are needed, but treating each program header as a special
case results in much more code.
Instead, in preparation to add more program he
Like the kernel text, the location of x86 PTI entry trampolines must be
recorded in the perf.data file. Like the kernel, synthesize a mmap event
for that, and add processing for it.
Signed-off-by: Adrian Hunter
---
tools/perf/arch/x86/util/Build | 1 +
tools/perf/arch/x86/util/event.c | 76 ++
Hi
Here is V3 of patches to support x86 PTI entry trampolines in perf tools.
Patches also here:
http://git.infradead.org/users/ahunter/linux-perf.git/shortlog/refs/heads/perf-tools-kpti-v3
git://git.infradead.org/users/ahunter/linux-perf.git perf-tools-kpti-v3
V2 patches also he
The logic in update_iter_mod() is overcomplicated and gets worse every time
another get_ksymbol_* function is added.
In preparation for adding another get_ksymbol_* function, simplify logic in
update_iter_mod().
Signed-off-by: Adrian Hunter
---
kernel/kallsyms.c | 20 ++--
1 fil
When kernel symbols are derived from /proc/kallsyms only (not using vmlinux
or /proc/kcore) map_groups__split_kallsyms() is used. However that function
makes assumptions that are not true with entry trampoline symbols. For now,
remove the entry trampoline symbols at that point, as they are no longe
On 22-05-18, 12:50, Rafael J. Wysocki wrote:
> Ugly indeed.
Hehe. I was thinking, maybe we can write wrapper helpers around lock/unlock
which are stored as pointers in sg_policy. So that those are only set to
non-NULL values (or non-Noop routines) for slow-switching single policy or
any-switching
On 22-May 16:04, Viresh Kumar wrote:
> Okay, me and Rafael were discussing this patch, locking and races around this.
>
> On 18-05-18, 11:55, Joel Fernandes (Google.) wrote:
> > @@ -382,13 +386,27 @@ sugov_update_shared(struct update_util_data *hook,
> > u64 time, unsigned int flags)
> > static
On Tuesday, May 22, 2018 12:50:06 PM CEST Viresh Kumar wrote:
> On 22-05-18, 16:04, Viresh Kumar wrote:
> > Okay, me and Rafael were discussing this patch, locking and races around
> > this.
> >
> > On 18-05-18, 11:55, Joel Fernandes (Google.) wrote:
> > > diff --git a/kernel/sched/cpufreq_schedu
On 22-05-18, 16:04, Viresh Kumar wrote:
> Okay, me and Rafael were discussing this patch, locking and races around this.
>
> On 18-05-18, 11:55, Joel Fernandes (Google.) wrote:
> > diff --git a/kernel/sched/cpufreq_schedutil.c
> > b/kernel/sched/cpufreq_schedutil.c
> > index e13df951aca7..5c482ec
On 22 May 2018 at 02:40, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.16.11 release.
> There are 110 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses
On Mon, 21 May 2018 09:58:28 -0400
William Breathitt Gray wrote:
> On Sun, May 20, 2018 at 04:53:02PM +0100, Jonathan Cameron wrote:
> >On Wed, 16 May 2018 13:52:39 -0400
> >William Breathitt Gray wrote:
> >
> >> This patch removes the IIO counter subdirectory which is now superceded
> >> by t
Hello Viresh,
Thanks for your comments.
On 5/22/2018 12:36 AM, skan...@codeaurora.org wrote:
On 2018-05-21 02:01, Viresh Kumar wrote:
On 19-05-18, 23:04, Taniya Das wrote:
The CPUfreq FW present in some QCOM chipsets offloads the steps
necessary
for changing the frequency of CPUs. The driver
://github.com/0day-ci/linux/commits/Sibi-Sankar/remoteproc-Introduce-prepare-unprepare-ops-for-rproc-coredump/20180522-133348
config: arm64-allyesconfig (attached as .config)
compiler: aarch64-linux-gnu-gcc (Debian 7.2.0-11) 7.2.0
reproduce:
wget
https://raw.githubusercontent.com/intel/lkp-tests
On Tue, May 22, 2018 at 4:15 AM, Vincent Chen wrote:
> On Fri, May 11, 2018 at 01:17:05PM +0800, Kito Cheng wrote:
>> Hi Arnd:
>>
>> I am GCC guy from Andes, we've missed the release schedule for GCC 8,
>> we didn't upstream the Linux support on time.
>>
>> Our plan is put our GCC 8 on github and
Hi Viresh,
thanks for clarifying...
On 22-May 15:53, Viresh Kumar wrote:
> On 21-05-18, 10:20, Joel Fernandes wrote:
> > On Mon, May 21, 2018 at 06:00:50PM +0100, Patrick Bellasi wrote:
> > > If that's the case, this means that if, for example, during a
> > > frequency switch you get a request to
Okay, me and Rafael were discussing this patch, locking and races around this.
On 18-05-18, 11:55, Joel Fernandes (Google.) wrote:
> diff --git a/kernel/sched/cpufreq_schedutil.c
> b/kernel/sched/cpufreq_schedutil.c
> index e13df951aca7..5c482ec38610 100644
> --- a/kernel/sched/cpufreq_schedutil.
On 21-May 11:05, Joel Fernandes wrote:
> On Mon, May 21, 2018 at 11:50:55AM +0100, Patrick Bellasi wrote:
> > On 18-May 11:55, Joel Fernandes (Google.) wrote:
> > > From: "Joel Fernandes (Google)"
> > >
> > > Currently there is a chance of a schedutil cpufreq update request to be
> > > dropped if
On 21-05-18, 10:20, Joel Fernandes wrote:
> On Mon, May 21, 2018 at 06:00:50PM +0100, Patrick Bellasi wrote:
> > If that's the case, this means that if, for example, during a
> > frequency switch you get a request to reduce the frequency (e.g.
> > deadline task passing the 0-lag time) and right aft
From: owner-linux...@kvack.org On Behalf Of Christoph Hellwig
> This seems to be missing patch 1 and generally be in somewhat odd format.
> Can you try to resend it with git-send-email and against current Linus'
> tree?
>
Sure, I will rebase them to current mainline ASAP.
> Also I'd suggest you d
On Tue, May 22, 2018 at 03:08:35PM +1000, Benjamin Herrenschmidt wrote:
> Hence my question: Is is still acceptable these days to use
> set_fs(KERNEL_DS) for simple cases like this ?
Not at all.
> Or is it really
> deprecated and all new users should use the iovec's ?
Yes, please use iov_iter.
The i2c-bus property for sfp modules was made mandatory. Update the
documentation to keep it in sync with the driver's behaviour.
Signed-off-by: Antoine Tenart
---
Documentation/devicetree/bindings/net/sff,sfp.txt | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentat
In case no Tx disable pin is available the SFP modules will always be
emitting. This could be an issue when using modules using laser as their
light source as we would have no way to disable it when the fiber is
removed. This patch adds a warning when registering an SFP cage which do
not have its t
This patch makes the i2c-bus property mandatory when using a device
tree. If the sfp i2c bus isn't described it's impossible to guess the
protocol to use for a given module, and the sfp module would then not
work in most cases.
Signed-off-by: Antoine Tenart
---
drivers/net/phy/sfp.c | 28 +++
Hi Russell, David,
A small series of patches improving the SFP support by adding a warning
when no Tx disable pin is available, and making the i2c-bus property
mandatory.
Thanks!
Antoine
Since v1:
- Removed the patch fixing the sfp driver when no i2c bus was described.
- Made two new patches
On Mon, May 21, 2018 at 5:47 AM, Randy Dunlap wrote:
> On 05/20/2018 08:33 PM, Ulf Magnusson wrote:
>> On Mon, May 21, 2018 at 4:45 AM, Randy Dunlap wrote:
>>> On 05/19/2018 09:47 PM, Ulf Magnusson wrote:
On Sun, May 20, 2018 at 6:03 AM, Randy Dunlap
wrote:
> On 05/19/2018 08:45 P
From: owner-linux...@kvack.org On Behalf Of Christoph Hellwig
>
> This code doesn't exist in current mainline. What kernel version
> is your patch against?
>
> On Mon, May 21, 2018 at 11:20:23PM +0800, Huaisheng Ye wrote:
> > From: Huaisheng Ye
> >
> > Use __GFP_ZONE_MASK to replace (__GFP_DMA
Hi,
I looked again into the llvm-bug #37512 and mentioned patches, so I
give this a 2nd try (see attached patchset).
Regards,
- Sedat -
From 6b78d2ecfae1cd3de35c8871605f0881df174b35 Mon Sep 17 00:00:00 2001
From: Nick Desaulniers
Date: Sat, 7 Oct 2017 13:23:23 -0700
Subject: [PATCH 1/4] kbuild:
Hi,
this patches solves the problem with slow shrink_slab() occuring
on the machines having many shrinkers and memory cgroups (i.e.,
with many containers). The problem is complexity of shrink_slab()
is O(n^2) and it grows too fast with the growth of containers
numbers.
Let we have 200 containers,
The patch introduces shrinker::id number, which is used to enumerate
memcg-aware shrinkers. The number start from 0, and the code tries
to maintain it as small as possible.
This will be used as to represent a memcg-aware shrinkers in memcg
shrinkers map.
Since all memcg-aware shrinkers are based
We have to free memory again when we cancel onlining, otherwise a later
onlining attempt will fail.
Signed-off-by: David Hildenbrand
---
mm/kasan/kasan.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/mm/kasan/kasan.c b/mm/kasan/kasan.c
index 135ce2838c89..53564229674b 100644
--- a/mm/kasan
These two pairs of blocks of code are under
the same #ifdef #else #endif.
Signed-off-by: Kirill Tkhai
---
mm/list_lru.c | 18 --
1 file changed, 8 insertions(+), 10 deletions(-)
diff --git a/mm/list_lru.c b/mm/list_lru.c
index d9c84c5bda1d..37d712924e56 100644
--- a/mm/list_lr
The patch adds list_lru::shrinker_id field, and populates
it by registered shrinker id.
This will be used to set correct bit in memcg shrinkers
map by lru code in next patches, after there appeared
the first related to memcg element in list_lru.
Signed-off-by: Kirill Tkhai
---
fs/super.c
Next patch requires these defines are above their current
position, so here they are moved to declarations.
Signed-off-by: Kirill Tkhai
---
mm/memcontrol.c | 30 +++---
1 file changed, 15 insertions(+), 15 deletions(-)
diff --git a/mm/memcontrol.c b/mm/memcontrol.c
ind
Using module_init() is wrong. E.g. ACPI adds and onlines memory before
our memory notifier gets registered.
This makes sure that ACPI memory detected during boot up will not
result in a kernel crash.
Easily reproducable with QEMU, just specify a DIMM when starting up.
Signed-off-by: David Hilden
This is just refactoring to allow next patches to have
lru pointer in memcg_drain_list_lru_node().
Signed-off-by: Kirill Tkhai
---
mm/list_lru.c |5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/mm/list_lru.c b/mm/list_lru.c
index 43cbec52a48a..cab8fad7f7e2 100644
--- a
This is just refactoring to allow next patches to have
dst_memcg pointer in memcg_drain_list_lru_node().
Signed-off-by: Kirill Tkhai
---
include/linux/list_lru.h |2 +-
mm/list_lru.c| 11 ++-
mm/memcontrol.c |2 +-
3 files changed, 8 insertions(+), 7 deleti
>>> On 22.05.18 at 05:54, wrote:
> We are making calls to C code (e.g. xen_prepare_pvh()) which may use
> stack canary (stored in GS segment).
>
> Signed-off-by: Boris Ostrovsky
Reviewed-by: Jan Beulich
We need to differ the situations, when shrinker has
very small amount of objects (see vfs_pressure_ratio()
called from super_cache_count()), and when it has no
objects at all. Currently, in the both of these cases,
shrinker::count_objects() returns 0.
The patch introduces new SHRINK_EMPTY return v
Hi Richard,
I'm going to make a PTP clock driver patch for FSL DPAA ethernet controller.
(drivers/net/ethernet/freescale/dpaa/)
Actually the 1588 timer module on FSL DPAA is same with the one on FSL eTSEC in
hardware.(whose PTP clock driver is
drivers/net/ethernet/freescale/gianfar_ptp.c)
So t
To avoid further unneed calls of do_shrink_slab()
for shrinkers, which already do not have any charged
objects in a memcg, their bits have to be cleared.
This patch introduces a lockless mechanism to do that
without races without parallel list lru add. After
do_shrink_slab() returns SHRINK_EMPTY t
From: Vladimir Davydov
The patch makes shrink_slab() be called for root_mem_cgroup
in the same way as it's called for the rest of cgroups.
This simplifies the logic and improves the readability.
Signed-off-by: Vladimir Davydov
ktkhai: Description written.
Signed-off-by: Kirill Tkhai
---
mm/vm
This creates a minor conflict with my iomap series, but that should
be easy to merge if needed.
Otherwise looks good:
Reviewed-by: Christoph Hellwig
cg_name(const char *root, const char *name) is always called with
non-empty root and name arguments, so there is no sense in checking
it in the function body (after using in strlen()).
Signed-off-by: Roman Gushchin
Reported-by: Dan Carpenter
Cc: linux-kselft...@vger.kernel.org
---
tools/testing
On Tue, May 22, 2018 at 5:18 PM, Andy Shevchenko
wrote:
> On Tue, May 15, 2018 at 4:41 PM, Benjamin Berg wrote:
>
>> I had a quick chat with Bastien about this. The conclusion was that
>> reusing the TOGGLE key may be problematic for gnome-settings-daemon.
>> And the alternative of a new CYCLE ke
Looks good,
Reviewed-by: Christoph Hellwig
> On 21 May 2018, at 00.25, Kent Overstreet wrote:
>
> Signed-off-by: Kent Overstreet
> ---
> drivers/lightnvm/pblk-core.c | 30 ++---
> drivers/lightnvm/pblk-init.c | 72
> drivers/lightnvm/pblk-read.c | 4 +-
> drivers/lightnvm/pblk-recovery.c
Using the preparations made in previous patches, in case of memcg
shrink, we may avoid shrinkers, which are not set in memcg's shrinkers
bitmap. To do that, we separate iterations over memcg-aware and
!memcg-aware shrinkers, and memcg-aware shrinkers are chosen
via for_each_set_bit() from the bitma
Hi Robin,
Several comments inside.
Sascha
On Fri, Mar 23, 2018 at 12:18:19AM +0800, Robin Gong wrote:
> The legacy sdma driver has below limitations or drawbacks:
> 1. Hardcode the max BDs number as "PAGE_SIZE / sizeof(*)", and alloc
> one page size for one channel regardless of only few
Introduce set_shrinker_bit() function to set shrinker-related
bit in memcg shrinker bitmap, and set the bit after the first
item is added and in case of reparenting destroyed memcg's items.
This will allow next patch to make shrinkers be called only,
in case of they have charged objects at the mom
Looks good,
Reviewed-by: Christoph Hellwig
This will be used in next patch.
Signed-off-by: Kirill Tkhai
---
include/linux/memcontrol.h | 10 ++
mm/memcontrol.c|5 -
2 files changed, 10 insertions(+), 5 deletions(-)
diff --git a/include/linux/memcontrol.h b/include/linux/memcontrol.h
index e51c6e953d7a..24ab
This is just refactoring to allow next patches to have
memcg pointer in list_lru_from_kmem().
Signed-off-by: Kirill Tkhai
---
mm/list_lru.c | 25 +
1 file changed, 17 insertions(+), 8 deletions(-)
diff --git a/mm/list_lru.c b/mm/list_lru.c
index dde9ecae7cb5..151fa77eb
Looks good,
Reviewed-by: Christoph Hellwig
Looks good,
Reviewed-by: Christoph Hellwig
This patch introduces new config option, which is used
to replace repeating CONFIG_MEMCG && !CONFIG_SLOB pattern.
Next patches add a little more memcg+kmem related code,
so let's keep the defines more clearly.
Signed-off-by: Kirill Tkhai
---
include/linux/list_lru.h |4 ++--
include/linux/
Do two list_lru_init_memcg() calls after prealloc_super().
destroy_unused_super() in fail path is OK with this.
Next patch needs such the order.
Signed-off-by: Kirill Tkhai
---
fs/super.c |8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/fs/super.c b/fs/super.c
index
If onlining of pages fails (is canceled), we don't properly free up memory.
Also, the memory hotplug notifier is not registered early enough, still
failing on certain setups where memory is detected, added and onlined
early.
v1 -> v2:
- s/MEM_CANCEL_OFFLINE/MEM_CANCEL_ONLINE
David Hildenbrand (2)
Use prealloc_shrinker()/register_shrinker_prepared()
instead of register_shrinker(). This will be used
in next patch.
Signed-off-by: Kirill Tkhai
---
mm/workingset.c |7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/mm/workingset.c b/mm/workingset.c
index 40ee02c83978
This provides a clock driver for the Renesas RZ/N1 parts (#R09A06G0xx).
This uses a structure derived from both the RCAR gen2 driver as well as
the renesas-cpg-mssr driver.
Signed-off-by: Michel Pollet
---
drivers/clk/renesas/Kconfig | 6 +
drivers/clk/renesas/Makefile | 1 +
driv
This adds a base device tree file for the RZN1-DB board, with only the
basic support allowing the system to boot to a prompt. Only one UART is
used, with only a single CPU running.
Signed-off-by: Michel Pollet
---
arch/arm/boot/dts/Makefile | 1 +
arch/arm/boot/dts/r9a06g032-rz
Imagine a big node with many cpus, memory cgroups and containers.
Let we have 200 containers, every container has 10 mounts,
and 10 cgroups. All container tasks don't touch foreign
containers mounts. If there is intensive pages write,
and global reclaim happens, a writing task has to iterate
over a
This adds the constants necessary to use the renesas,rzn1-clocks driver.
Signed-off-by: Michel Pollet
---
include/dt-bindings/clock/rzn1-clocks.h | 187
1 file changed, 187 insertions(+)
create mode 100644 include/dt-bindings/clock/rzn1-clocks.h
diff --git a/in
This adds the Renesas RZ/N1D (Part #R9A06G032) SoC bare
bone support.
This currently only handles generic parts (gic, architected timer)
and a UART.
For simplicity sake, this also relies on the bootloader to set the
pinctrl and clocks.
Signed-off-by: Michel Pollet
---
arch/arm/boot/dts/r9a06g03
The Renesas RZ/N1 Family (Part #R9A06G0xx) requires a driver
to provide the SoC clock infrastructure for Linux.
This documents the driver bindings.
Signed-off-by: Michel Pollet
---
.../bindings/clock/renesas,rzn1-clocks.txt | 44 ++
1 file changed, 44 insertions(+)
This series adds the plain basic support for booting a bare
kernel on the RZ/N1D-DB Board. It's been trimmed to the strict
minimum as a 'base', further patches that will add the
rest of the support.
Special note on the clock driver: Current usage of the clocks on Linux
involves Linux 'claiming' al
This documents the RZ/N1 bindings for the RZN1D-DB board.
Signed-off-by: Michel Pollet
Reviewed-by: Rob Herring
---
Documentation/devicetree/bindings/arm/shmobile.txt | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/arm/shmobile.txt
b/Do
Looks good,
Reviewed-by: Christoph Hellwig
Looks good,
Reviewed-by: Christoph Hellwig
On Mon, May 21, 2018 at 09:01:44AM -0700, adam.manzana...@wdc.com wrote:
> From: Adam Manzanares
>
> In order to avoid kiocb bloat for per command iopriority support, rw_hint
> is converted from enum to a u16. Added a guard around ki_hint assigment.
>
> Signed-off-by: Adam Manzanares
Looks goo
On Tue, May 22, 2018 at 01:20:01AM +0300, Andy Shevchenko wrote:
> On Mon, May 21, 2018 at 2:57 PM, Yisheng Xie wrote:
> > match_string() returns the index of an array for a matching string,
> > which can be used intead of open coded variant.
>
> > - int err, i;
> > + int ret;
>
> in
Hi Abhishek,
Some nitpicking below.
On Thu, 3 May 2018 17:50:36 +0530, Abhishek Sahu
wrote:
> QCOM NAND layout protect available OOB data bytes with ECC also so
^controller
> when ecc->write_oob (qcom_nandc_write_oob) is being called then it
You can just state "->write_oob()"
>
On Mon, May 21, 2018 at 6:13 PM, Joel Fernandes wrote:
> On Mon, May 21, 2018 at 10:29:52AM +0200, Rafael J. Wysocki wrote:
>> On Mon, May 21, 2018 at 7:14 AM, Viresh Kumar
>> wrote:
>> > On 18-05-18, 11:55, Joel Fernandes (Google.) wrote:
>> >> From: "Joel Fernandes (Google)"
>> >>
>> >> Curre
This routine checks if the CPU running this code belongs to the policy
of the target CPU or if not, can it do remote DVFS for it remotely. But
the current name of it implies as if it is only about doing remote
updates.
Rename it to make it more relevant.
Reported-by: Rafael J. Wysocki
Signed-off
On 22.05.2018 11:55, David Hildenbrand wrote:
> We have to free memory again when we cancel onlining, otherwise a later
> onlining attempt will fail.
>
> Signed-off-by: David Hildenbrand
> ---
> mm/kasan/kasan.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/mm/kasan/kasan.c b/mm/kasa
Using module_init() is wrong. E.g. ACPI adds and onlines memory before
our memory notifier gets registered.
This makes sure that ACPI memory detected during boot up will not
result in a kernel crash.
Easily reproducable with QEMU, just specify a DIMM when starting up.
Signed-off-by: David Hilden
If onlining of pages fails, we don't properly free up memory.
Also, the memory hotplug notifier is not registered early enough, still
failing on certain setups where memory is detected, added and onlined
early.
David Hildenbrand (2):
kasan: free allocated shadow memory on MEM_CANCEL_OFFLINE
ka
We have to free memory again when we cancel onlining, otherwise a later
onlining attempt will fail.
Signed-off-by: David Hildenbrand
---
mm/kasan/kasan.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/mm/kasan/kasan.c b/mm/kasan/kasan.c
index 135ce2838c89..8baefe1a674b 100644
--- a/mm/kasan
On Tue, May 22, 2018 at 04:39:20PM +0800, Leo Yan wrote:
[...]
Rather than the patch I posted in my previous email, I think below new
patch is more reasonable for me.
In the below change, 'etmq->prev_packet' is only used to store the
previous CS_ETM_RANGE packet, we don't need to save CS_ETM_TRA
Acked-by: Peter Zijlstra (Intel)
On Mon, May 21, 2018 at 12:33:05PM -0500, Alan Tull wrote:
> On Sun, May 20, 2018 at 10:03 PM, Wu Hao wrote:
> > On Mon, May 07, 2018 at 04:09:06PM -0500, Alan Tull wrote:
> >> On Tue, May 1, 2018 at 9:50 PM, Wu Hao wrote:
> >>
> >> Hi Hao,
> >>
> >> Looks good!
> >>
> >> > This patch introduces
On 05/22/2018 05:26 PM, Maarten Lankhorst wrote:
Op 20-05-18 om 19:17 schreef Randy Li:
This pixel format is a fully packed and 10bits variant of NV12.
A luma pixel would take 10bits in memory, without any
filled bits between pixels in a stride. The color gamut
follows the BT.2020 standard.
S
On Tue, 2018-05-22 at 11:14 +0200, Sebastian Andrzej Siewior wrote:
> On 2018-05-22 10:24:22 [+0200], Mike Galbraith wrote:
>
> > If I were in your shoes, I think I'd just stop caring about UV until a
> > real user appears. AFAIK, I'm the only guy who ever ran RT on UV, and
> > I only did so beca
On Mon, May 21, 2018 at 03:34:53PM +, Adam Thomson wrote:
> On 21 May 2018 15:56, Heikki Krogerus wrote:
>
> > On Mon, May 21, 2018 at 01:58:16PM +, Adam Thomson wrote:
> > > Hi Heikki,
> > >
> > > On 21 May 2018 14:20, Heikki Krogerus wrote:
> > >
> > > > On Wed, May 16, 2018 at 05:00:46P
Before splitting the code to support multiple platform devices to
be probed (one for the ICU, one per interrupt group), let's switch to
regmap first by creating one in the ->probe().
Signed-off-by: Miquel Raynal
---
drivers/irqchip/irq-mvebu-icu.c | 45 +++--
Make the current MSI irq_domain local to ease the split between ICU
platform device code and NSR platform device code.
Signed-off-by: Miquel Raynal
Reviewed-by: Thomas Petazzoni
---
drivers/irqchip/irq-mvebu-icu.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers
The ICU is an IRQ chip found in Armada CP110. It currently has 207 wired
inputs. Its purpose is to aggregate all CP interrupts and report them to
the AP through MSIs. The ICU writes into GIC registers (AP side) by way
of the interconnect. These interrupts can be of several groups:
- SecuRe (SR);
-
NSR (non-secure interrupts) are handled in the ICU driver like if there
was only this type of interrupt in the ICU. Change this behavior to
prepare the introduction of SEI (System Error Interrupts) support by
moving the NSR code in a separate function. This is done under the form
of a 'probe' funct
The ICU can handle several type of interrupt, each of them being handled
differently on AP side. On CP side, the ICU should be able to make the
distinction between each interrupt group by pointing to the right parent.
This is done through the introduction of new bindings, presenting the ICU
node a
An SEI driver provides an MSI domain through which it is possible to
raise SEIs.
Handle the NSR probe function in a more generic way to support other
type of interrupts (ie. the SEIs).
For clarity we do not use tree IRQ domains for now but linear ones
instead, allocating the 207 ICU lines for eac
Enable the newly introduced Marvell SEI driver for the 64-bit Marvell
EBU platforms.
Suggested-by: Haim Boot
Signed-off-by: Miquel Raynal
Reviewed-by: Gregory CLEMENT
---
arch/arm64/Kconfig.platforms | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/Kconfig.platforms b/arch/arm64/
Change the documentation to reflect the new bindings used for Marvell
ICU. This involves describing each interrupt group as a subnode of the
ICU node. Each of them having their own compatible.
Signed-off-by: Miquel Raynal
---
.../bindings/interrupt-controller/marvell,icu.txt | 81 ++
ICU size in CP110 is not 0x10 but at least 0x440 bytes long (from the
specification).
Signed-off-by: Miquel Raynal
Reviewed-by: Rob Herring
Reviewed-by: Thomas Petazzoni
---
Documentation/devicetree/bindings/interrupt-controller/marvell,icu.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletio
1001 - 1100 of 1253 matches
Mail list logo
