On 2019-04-25, Aleksa Sarai wrote:
> On 2019-04-23, Kees Cook wrote:
> > This series provides solutions to so many different race and confusion
> > issues, I'd really like to see it land. What's the next step here? Is
> > this planned to go directly to Linus for v5.2, or is it going to live
> > i
On Fri, Apr 12, 2019 at 04:41:14PM +0300, Heikki Krogerus wrote:
> It looks like the child device is often matched with a name.
> This introduces a helper that does it automatically.
>
> Signed-off-by: Heikki Krogerus
Acked-by: Greg Kroah-Hartman
Enable the aspeed-p2a-ctrl node and configure with memory-region to
enable mmap access.
Signed-off-by: Patrick Venture
---
arch/arm/boot/dts/aspeed-bmc-quanta-q71l.dts | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm/boot/dts/aspeed-bmc-quanta-q71l.dts
b/arch/arm/boot/dts/aspee
Add a node for the aspeed-p2a-ctrl module. This node, when enabled will
disable the PCI-to-AHB bridge and then allow control of this bridge via
ioctls, and access via mmap.
Signed-off-by: Patrick Venture
---
arch/arm/boot/dts/aspeed-g4.dtsi | 4
arch/arm/boot/dts/aspeed-g5.dtsi | 5 +
On Thu, 25 Apr 2019, Dmitry Safonov wrote:
> From: Andrei Vagin
>
> Add monotonic time virtualisation for time namespace.
> Introduce timespec for monotionic clock into timens offsets and wire
> clock_gettime() syscall.
That's a bit meager. It should at least explain the concept how this is
supp
This patch adds support for CPU-wide trace scenarios by making sure that
only the sources monitoring the same process have access to a common sink.
Because the sink is shared between sources, the first source to use the
sink switches it on while the last one does the cleanup. Any attempt to
modify
In preparation to handle device reference counting inside of the sink
drivers, add a return code to the sink::disable() operation so that
proper action can be taken if a sink has not been disabled.
Signed-off-by: Mathieu Poirier
Reviewed-by: Suzuki K Poulose
Tested-by: Leo Yan
Tested-by: Robert
In preparation to support CPU-wide trace scenarios, introduce the notion
of process ID to ETR devices. That way events monitoring the same process
can use the same etr_buf, allowing multiple CPUs to use the same sink.
Signed-off-by: Mathieu Poirier
Tested-by: Leo Yan
Tested-by: Robert Walker
-
Resource selector pair 0 is always implemented and reserved. As such
it should not be explicitly programmed.
Signed-off-by: Mathieu Poirier
Reviewed-by: Suzuki K Poulose
Tested-by: Leo Yan
Tested-by: Robert Walker
---
drivers/hwtracing/coresight/coresight-etm4x.c | 7 +--
1 file changed,
When operating in CPU-wide trace scenarios and working with an N:1
source/sink HW topology, update() functions need to be made atomic
in order to avoid racing with start and stop operations.
Signed-off-by: Mathieu Poirier
Reviewed-by: Suzuki K Poulose
Tested-by: Leo Yan
Tested-by: Robert Walker
This patch uses the PID of the process being traced to allocate and free
ETR memory buffers for CPU-wide scenarios. The implementation is tailored
to handle both N:1 and 1:1 source/sink HW topologies.
Signed-off-by: Mathieu Poirier
Tested-by: Leo Yan
Tested-by: Robert Walker
---
.../hwtracing
Make struct perf_event available to sink buffer allocation functions in
order to use the pid they carry to allocate and free buffer memory along
with regimenting access to what source a sink can collect data for.
Signed-off-by: Mathieu Poirier
Tested-by: Leo Yan
Tested-by: Robert Walker
---
dr
Buffer allocation is different when dealing with per-thread and
CPU-wide sessions. In preparation to support CPU-wide trace scenarios
simplify things by keeping allocation functions for both type separate.
Signed-off-by: Mathieu Poirier
Tested-by: Leo Yan
Tested-by: Robert Walker
---
.../hwtr
There is no point in allocating sink memory for a trace session if
there is not a way to free it once it is no longer needed. As such make
sure the sink API function to allocate and free memory have been
implemented before moving ahead with the establishment of a trace
session.
Signed-off-by: Mat
From: Suzuki K Poulose
We fail to disable the clock in case of a failure during the
probe. Clean this up. Also, we are supposed to drop the pm reference
only when the probing is successful.
Cc: Mathieu Poirier
Signed-off-by: Suzuki K Poulose
Signed-off-by: Mathieu Poirier
---
.../coresight/c
When disabling a sink the reference counter ensures the operation goes
through if nobody else is using it. As such if drvdata::mode is already
set do CS_MODE_DISABLED, it is an error and should be reported as such.
Signed-off-by: Mathieu Poirier
Reviewed-by: Suzuki K Poulose
Tested-by: Leo Yan
In CPU-wide scenarios with an N:1 source/sink topology, sources share
the same sink. In order to reuse the same sink for all sources an
IDR is needed to archive events that have already been accounted for.
Signed-off-by: Mathieu Poirier
Tested-by: Leo Yan
Tested-by: Robert Walker
---
drivers/
From: Arnd Bergmann
Clang points out a syntax error, as the etr_catu_buf_ops structure is
declared 'static' before the type is known:
In file included from drivers/hwtracing/coresight/coresight-tmc-etr.c:12:
drivers/hwtracing/coresight/coresight-catu.h:116:40: warning: tentative
definition of v
On Fri, Apr 19, 2019 at 04:19:22PM +0200, Lukasz Luba wrote:
> The device tree bindings for LPDDR3 SDRAM memories.
>
> For specifying the AC timing parameters of the memory device
> the 'lpddr3' binding uses binding 'lpddr2-timings'.
>
> Signed-off-by: Lukasz Luba
> ---
> .../devicetree/binding
Good day Greg,
Please consider the following for inclusion in the 5.2 cycle when you have
the time.
Regards,
Mathieu
Arnd Bergmann (1):
coresight: catu: fix clang build warning
Mathieu Poirier (20):
coresight: pmu: Adding ITRACE property to cs_etm PMU
coresight: etm4x: Add kernel configu
Add to the capabilities the ITRACE property so that ITRACE START events
are generated when the PMU is switched on by the core.
Signed-off-by: Mathieu Poirier
Acked-by: Suzuki K Poulose
Tested-by: Leo Yan
Tested-by: Robert Walker
---
drivers/hwtracing/coresight/coresight-etm-perf.c | 3 ++-
1
* Nadav Amit wrote:
> > On Apr 25, 2019, at 12:29 PM, Ingo Molnar wrote:
> >
> >
> > * Nadav Amit wrote:
> >
> >> Move flush_tlb_info variables off the stack. This allows to align
> >> flush_tlb_info to cache-line and avoid potentially unnecessary cache
> >> line movements. It also allows
This patch adds support for CPU-wide trace scenarios by making sure that
only the sources monitoring the same process have access to a common sink.
Because the sink is shared between sources, the first source to use the
sink switches it on while the last one does the cleanup. Any attempt to
modify
This patch adds support for CPU-wide trace scenarios by making sure that
only the sources monitoring the same process have access to a common sink.
Because the sink is shared between sources, the first source to use the
sink switches it on while the last one does the cleanup. Any attempt to
modify
On Wed, Apr 24, 2019 at 06:19:26PM +0800, Yuyang Du wrote:
> These two functions now handle different check results themselves. A new
> check_path function is added to check whether there is a path in the
> dependency graph. No functional change.
This looks good, however I completely forgot we sti
This patch adds reference counting to struct etr_buf so that, in CPU-wide
trace scenarios, shared buffers can be disposed of when no longer used.
Signed-off-by: Mathieu Poirier
Tested-by: Leo Yan
Tested-by: Robert Walker
---
drivers/hwtracing/coresight/coresight-tmc-etr.c | 5 +
drivers/hw
On Wed, Apr 24, 2019 at 06:19:28PM +0800, Yuyang Du wrote:
> The new bit can be any possible lock usage except it is garbage, so the
s/except it/except when it/ ?
> cases in switch can be made simpler. Warn early on if wrong usage bit is
> passed without taking locks. No functional change.
>
> S
* Fenghua Yu wrote:
> On Thu, Apr 25, 2019 at 07:45:11AM +0200, Ingo Molnar wrote:
> >
> > * Fenghua Yu wrote:
> >
> > > A new MSR_IA32_CORE_CAPABILITY (0xcf) is defined. Each bit in the MSR
> > > enumerates a model specific feature. Currently bit 5 enumerates split
> > > lock detection. Whe
From: Suzuki K Poulose
Rename the dynamic replicator specific routines for merging with the
replicator driver. Also re-arrange the probe routine to make it easier
to merge.
Cc: Mathieu Poirier
Signed-off-by: Suzuki K Poulose
Signed-off-by: Mathieu Poirier
---
.../coresight/coresight-dynamic-
When operating in CPU-wide mode with an N:1 source/sink HW topology,
multiple CPUs can access a sink concurrently. As such reference counting
needs to happen when the device's spinlock is held to avoid racing with
other operations (start(), update(), stop()), such as:
session A
From: Suzuki K Poulose
Drop the power only when we have successfully probed. Otherwise
leave it to the amba probe to do the rest.
Cc: Mathieu Poirier
Signed-off-by: Suzuki K Poulose
[Removed extra newline left after original modification]
Signed-off-by: Mathieu Poirier
---
drivers/hwtracing/
From: YueHaibing
Fix sparse warnings:
drivers/hwtracing/coresight/coresight-catu.c:488:35: warning:
symbol 'catu_helper_ops' was not declared. Should it be static?
drivers/hwtracing/coresight/coresight-catu.c:493:28: warning:
symbol 'catu_ops' was not declared. Should it be static?
Signed-off
Set the proper bit in the configuration register when contextID tracing
has been requested by user space. That way PE_CONTEXT elements are
generated by the tracers when a process is installed on a CPU.
Signed-off-by: Mathieu Poirier
Reviewed-by: Suzuki K Poulose
Tested-by: Leo Yan
Tested-by: R
Remove return in void function to get rid of checkpatch warning.
Signed-off-by: Vatsala Narang
---
drivers/staging/rtl8723bs/core/rtw_xmit.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/staging/rtl8723bs/core/rtw_xmit.c
b/drivers/staging/rtl8723bs/core/rtw_xmit.c
index 094d61bcb
On Fri, Apr 05, 2019 at 09:53:06PM +0800, Chengguang Xu wrote:
> When allocating dynamic major, the minor range overlap check
> in __register_chrdev_region() will not fail, so actually
> there is no real case to passing non negative error code to
> caller. However, set variable ret to -EBUSY before
On Thu, 2019-04-25 at 07:55 -0400, Mimi Zohar wrote:
> On Wed, 2019-04-24 at 14:33 +, Robert Holmes wrote:
> > This patch completes commit 278311e417be ("kexec, KEYS: Make use of
> > platform keyring for signature verify") which, while adding the
> > platform keyring for bzImage verification, n
Refactoring function tmc_etr_setup_perf_buf() so that it only deals
with the high level etr_perf_buffer, leaving the allocation of the
backend buffer (i.e etr_buf) to another function.
That way the backend buffer allocation function can decide if it wants
to reuse an existing buffer (CPU-wide trac
On Fri, Apr 19, 2019 at 04:19:22PM +0200, Lukasz Luba wrote:
> The device tree bindings for LPDDR3 SDRAM memories.
Also, 'dt-bindings: ddr: ' for the subject. You've got a mixture of
subjects with no consistency.
>
> For specifying the AC timing parameters of the memory device
> the 'lpddr3' bi
On Wed, Apr 24, 2019 at 06:19:29PM +0800, Yuyang Du wrote:
> The bitmaps keep track of which locks are irqsafe. Update the bitmaps
> when there is new irqsafe usage and when an irqsafe lock is zapped.
>
> Signed-off-by: Yuyang Du
> ---
> kernel/locking/lockdep.c | 39
From: Suzuki K Poulose
As a preparatory step to merge the separate drivers for static and
dynamic replicators, annotate the static replicator specific details.
Also refactor the probe routine to make it generic in order to merge
the drivers easily.
Cc: Mathieu Poirier
Signed-off-by: Suzuki K Po
From: Suzuki K Poulose
Merge the drivers for the two varieties of replicators into
a singel one. The dynamic replicator has programming base
which can be programmed to filter the trace data. The driver
detects the type based on the "base" address value of the
device, which is NULL for the static
From: Suzuki K Poulose
If we failed to setup the DMA mask for TMC-ETR, report the
error before failing the probe.
Cc: Mathieu Poirier
Signed-off-by: Suzuki K Poulose
Signed-off-by: Mathieu Poirier
---
drivers/hwtracing/coresight/coresight-tmc.c | 7 ++-
1 file changed, 6 insertions(+), 1
Function free_event_data() is already busy and is bound to become
worse with the addition of CPU-wide trace scenarios. As such spin
off a new function to strickly take care of the sink buffers.
Signed-off-by: Mathieu Poirier
Reviewed-by: Suzuki K Poulose
Tested-by: Leo Yan
Tested-by: Robert Wa
On Thu, Apr 25, 2019 at 12:13:18PM -0700, Paul Walmsley wrote:
>
>
> On Thu, 11 Apr 2019, Christoph Hellwig wrote:
>
> > No need to have two names for the same thing.
> >
> > Signed-off-by: Christoph Hellwig
>
> This is probably worth cleaning up across the entire tree.
>
> asm-{generic,x8
Configure timestamps to be emitted at regular intervals in the trace
stream to temporally correlate instructions executed on different CPUs.
Signed-off-by: Mathieu Poirier
Tested-by: Leo Yan
Tested-by: Robert Walker
---
drivers/hwtracing/coresight/coresight-etm4x.c | 102 +-
1
From: Suzuki K Poulose
Drop the power only if we were successful in probing the device.
Cc: Mathieu Poirier
Signed-off-by: Suzuki K Poulose
Signed-off-by: Mathieu Poirier
---
drivers/hwtracing/coresight/coresight-tmc.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/d
From: Suzuki K Poulose
With commit c2c729415b2d2132 ("coresight: platform: Cleanup coresight
connection handling"), we switched to re-using coresight_connections
for the coresight_device. However, that introduced a mismatch in the
alloc/free of the connections. The allocation is made using devm_*
From: Suzuki K Poulose
Drop the power handle only if we were successful. Otherwise
the AMBA bus code would do the rest.
Cc: Mathieu Poirier
Signed-off-by: Suzuki K Poulose
Signed-off-by: Mathieu Poirier
---
drivers/hwtracing/coresight/coresight-catu.c | 3 ++-
1 file changed, 2 insertions(+)
From: Suzuki K Poulose
We drop the power before we complete the probe successfully. We
are supposed to drop it only when we are successful. Also, probing
the etb_buffer_length happens with the power turned up. So we don't
need to do that again in the helper.
Cc: Mathieu Poirier
Signed-off-by: S
I made the same typo when trying to grep for uses of smp_wmb and figured
I might as well fix it.
Signed-off-by: Palmer Dabbelt
---
arch/powerpc/kvm/book3s_hv.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/powerpc/kvm/book3s_hv.c b/arch/powerpc/kvm/book3s_hv.c
index 06
On Thu, 11 Apr 2019, Christoph Hellwig wrote:
> This way any override of pm_power_off also affects the halt path and
> we don't need additional infrastructure for it.
>
> Also remove the pm_power_off export - at least for now we don't have
> any modular drivers overriding it.
I'd propose that we
On Fri, Apr 19, 2019 at 04:19:24PM +0200, Lukasz Luba wrote:
> The patch adds description for DT binding for a new Exynos5422 Dynamic
> Memory Controller device.
>
> Signed-off-by: Lukasz Luba
> ---
> .../bindings/memory-controllers/exynos5422-dmc.txt | 73
> ++
> 1 file cha
On Thu, Apr 25, 2019 at 03:00:10PM -0400, Joel Fernandes (Google) wrote:
>
> +void *test_pidfd_poll_exec_thread(void *priv)
I think everything in this file can be static, there's this one and
3-4 below.
> +int test_pidfd_poll_exec(int use_waitpid)
> +{
> + int pid, pidfd = 0;
> + int stat
Did i miss preliminary agenda somewhere ? In previous year i think
there use to be one by now :)
Cheers,
Jérôme
On Thu, Apr 25, 2019 at 07:21:02PM +, Peter Rosin wrote:
> On 2019-04-25 16:37, Serge Semin wrote:
> > On Wed, Apr 24, 2019 at 09:25:24PM +, Peter Rosin wrote:
> >
> > Hello Peter,
> >
> >> On 2019-04-24 14:34, Serge Semin wrote:
> >>> The main idea of this patchset was to add the dt-base
On Wed, Apr 24, 2019 at 06:19:30PM +0800, Yuyang Du wrote:
> In mark_lock_irq(), the following checks are performed:
>
>--
> | -> | unsafe | read unsafe |
> |--|
> | safe | F B |F* B*|
> |---
On Thu, 25 Apr 2019, Christoph Hellwig wrote:
> On Thu, Apr 25, 2019 at 12:13:18PM -0700, Paul Walmsley wrote:
> >
> >
> > On Thu, 11 Apr 2019, Christoph Hellwig wrote:
> >
> > > No need to have two names for the same thing.
> > >
> > > Signed-off-by: Christoph Hellwig
> >
> > This is pro
On Wed, Apr 24, 2019 at 06:19:32PM +0800, Yuyang Du wrote:
> Since there is no need for backward dependecy searching, remove this
> extra function layer.
OK, so $subject confused the heck out of me, I thought you were going to
remove the whole bfs machinery. May I suggest retaining
__bfs_backwards
On Fri, 1 Feb 2019 21:39:59 +0100 Albert Vaca Cintora
wrote:
> Adds a readonly 'current_inotify_watches' entry to the user sysctl table.
> The handler for this entry is a custom function that ends up calling
> proc_dointvec. Said sysctl table already contains 'max_inotify_watches'
> and it gets
On Thu, Apr 25, 2019 at 05:13:53PM +0100, Dmitry Safonov wrote:
>
> diff --git a/include/linux/time_namespace.h b/include/linux/time_namespace.h
> index 8f75d34cf34a..5f0da6858b10 100644
> --- a/include/linux/time_namespace.h
> +++ b/include/linux/time_namespace.h
> @@ -48,6 +48,14 @@ static inlin
* Kees Cook wrote:
> On Wed, Apr 24, 2019 at 10:42 PM Ingo Molnar wrote:
> > Just to make clear, is the change from the old behavior, in essence:
> >
> >
> >CPU: | lacks NX | has NX, ia32 | has NX, x86_64 |
> > ELF: | | |
On Thu, Apr 25, 2019 at 02:23:59PM -0400, Jeff Layton wrote:
> I took a quick look at the dcache code to see if we had something like
> that before I did this, but I guess I didn't look closely enough. Those
> routines do look nicer than my hand-rolled version.
>
> I'll look at spinning up a patc
On Thu, Apr 25, 2019 at 07:28:52PM +, Peter Rosin wrote:
> On 2019-04-25 17:47, Serge Semin wrote:
> > On Wed, Apr 24, 2019 at 09:25:50PM +, Peter Rosin wrote:
> >> On 2019-04-24 14:34, Serge Semin wrote:
> >>> It's pointless and might be even errors prone to proceed with further
> >>> init
I see that the schedule is not full yet for the mm track and i would
really like to be able to have a discussion on this topic
Schedule:
https://docs.google.com/spreadsheets/d/1Z1pDL-XeUT1ZwMWrBL8T8q3vtSqZpLPgF3Bzu_jejfk/edit#gid=0
On Fri, Jan 18, 2019 at 12:45:13PM -0500, Jerome Glisse wrote:
On Wed, 10 Apr 2019 15:44:47 PDT (-0700), atish.pa...@wdc.com wrote:
CONFIG_DEBUG_TLBFLUSH was added in 'commit 3df3212f9722 ("x86/tlb: add
tlb_flushall_shift knob into debugfs")' to support tlb_flushall_shift
knob. The knob was removed in 'commit e9f4e0a9fe27 ("x86/mm: Rip out
complicated, out-o
On Wed, 10 Apr 2019 15:44:48 PDT (-0700), atish.pa...@wdc.com wrote:
The TLB flush counters under vmstat seems to be very helpful while
debugging TLB flush performance in RISC-V.
Update the counters in every TLB flush methods respectively.
Signed-off-by: Atish Patra
---
arch/riscv/include/asm
On Wed, Apr 03, 2019 at 04:11:19PM +0200, Alexandre Belloni wrote:
> The TCBs that have children are using the new (proper) DT bindings and
> don't need to be handled by tclib.
>
> Signed-off-by: Alexandre Belloni
> ---
> drivers/misc/atmel_tclib.c | 3 +++
> 1 file changed, 3 insertions(+)
>
On Fri, 26 Apr 2019, Vatsala Narang wrote:
> Remove return in void function to get rid of checkpatch warning.
>
> Signed-off-by: Vatsala Narang
Acked-by: Julia Lawall
> ---
> drivers/staging/rtl8723bs/core/rtw_xmit.c | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/drivers/staging
Fixup compiler warnings:
- 108 warning: ISO C90 forbids mixed declarations and code
- 264 warning: unused variable 'value'
- 335 warning: unused variable 'res'
Signed-off-by: Patrick Venture
---
drivers/misc/aspeed-p2a-ctrl.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff -
On Tue, Apr 09, 2019 at 11:06:43AM +0100, Dragan Cvetic wrote:
> Add the Soft Decision Forward Error Correction (SDFEC) Engine
> bindings which is available for the Zynq UltraScale+ RFSoC
> FPGA's.
>
> Signed-off-by: Dragan Cvetic
> Signed-off-by: Derek Kiernan
> ---
> .../devicetree/bindings/m
On Tue, Apr 09, 2019 at 11:06:44AM +0100, Dragan Cvetic wrote:
> +++ b/include/uapi/misc/xilinx_sdfec.h
> @@ -0,0 +1,42 @@
> +/* SPDX-License-Identifier: GPL-2.0+ */
That is not the proper SPDX license for a UAPI kernel header file :(
Please fix this up.
Also, why do you need a uapi file at all?
On Tue, Apr 09, 2019 at 01:46:01PM -0500, richard.g...@linux.intel.com wrote:
> From: Richard Gong
>
> Describe Intel Stratix10 Remote System Update (RSU) device attributes
>
> Signed-off-by: Richard Gong
> Reviewed-by: Alan Tull
> ---
> .../testing/sysfs-devices-platform-stratix10-rsu | 78
On Tue, Apr 09, 2019 at 01:46:01PM -0500, richard.g...@linux.intel.com wrote:
> From: Richard Gong
>
> Describe Intel Stratix10 Remote System Update (RSU) device attributes
>
> Signed-off-by: Richard Gong
> Reviewed-by: Alan Tull
> ---
> .../testing/sysfs-devices-platform-stratix10-rsu | 78
Hi Greg,
On Thu, 25 Apr 2019 19:46:15 +0200 Greg Kroah-Hartman
wrote:
>
> On Tue, Apr 16, 2019 at 06:03:58PM +0900, Jason A. Donenfeld wrote:
> > On Tue, Apr 16, 2019 at 4:27 PM Stephen Rothwell
> > wrote:
> > >
> > > In preparation to enabling -Wimplicit-fallthrough, mark switch cases
> > >
On Thu, Apr 25, 2019 at 8:32 AM Christopher Lameter wrote:
>
> On Wed, 24 Apr 2019, Matthew Garrett wrote:
>
> > Applications that hold secrets and wish to avoid them leaking can use
> > mlock() to prevent the page from being pushed out to swap and
> > MADV_DONTDUMP to prevent it from being includ
On Tue, Apr 09, 2019 at 01:46:00PM -0500, richard.g...@linux.intel.com wrote:
> +/*
> + * This driver exposes some optional features of the Intel Stratix 10 SoC
> FPGA.
> + * The SysFS interfaces exposed here are FPGA Remote System Update (RSU)
It has never been "SysFS", it has always been "sysfs
A typical kernel image has hundreds of static struct of_device_id
instances (a lot of which are sentinel all-zeroes), each occupying
~200 bytes. Nobody initializes the .compatible member with strings
anywhere near 128 bytes, so a lot of that memory is simply wasted.
To verify, I first had the 0day
On 25/04/2019 12:38:55-0700, Stephen Boyd wrote:
> Quoting Alexandre Belloni (2019-04-02 05:50:56)
> > diff --git a/drivers/clk/at91/sam9x60.c b/drivers/clk/at91/sam9x60.c
> > new file mode 100644
> > index ..22bf51c55bdc
> > --- /dev/null
> > +++ b/drivers/clk/at91/sam9x60.c
> > @@ -0,
On Tue, Apr 09, 2019 at 01:46:00PM -0500, richard.g...@linux.intel.com wrote:
> +static ssize_t reboot_image_store(struct device *dev,
> + struct device_attribute *attr,
> + const char *buf, size_t count)
> +{
> + struct stratix10_rsu_
On Thu, Apr 25, 2019 at 01:23:47PM -0700, Patrick Venture wrote:
> Fixup compiler warnings:
> - 108 warning: ISO C90 forbids mixed declarations and code
> - 264 warning: unused variable 'value'
> - 335 warning: unused variable 'res'
>
> Signed-off-by: Patrick Venture
Reported-by: kbuild...
I
On Thu, Apr 25, 2019 at 1:36 PM Greg KH wrote:
>
> On Thu, Apr 25, 2019 at 01:23:47PM -0700, Patrick Venture wrote:
> > Fixup compiler warnings:
> > - 108 warning: ISO C90 forbids mixed declarations and code
> > - 264 warning: unused variable 'value'
> > - 335 warning: unused variable 'res'
> >
On Mon, Apr 22, 2019 at 11:57:58AM -0700, Rick Edgecombe wrote:
> Add a new flag VM_FLUSH_RESET_PERMS, for enabling vfree operations to
> immediately clear executable TLB entries before freeing pages, and handle
> resetting permissions on the directmap. This flag is useful for any kind
> of memory
On Thu, Apr 25, 2019 at 5:37 AM Michal Hocko wrote:
> Besides that you inherently assume that the user would do mlock because
> you do not try to wipe the swap content. Is this intentional?
Yes, given MADV_DONTDUMP doesn't imply mlock I thought it'd be more
consistent to keep those independent.
On Thu, Apr 25, 2019 at 06:42:52PM +0200, Marco Davids wrote:
> Op Thu, Apr 25, 2019 at 13:22, Nico Schottelius wrote:
> > if I cannot turn off IPv4, I cannot test what needs to be fixed.
>
> You know what? I actually agree with Nico on this.
>
> It's 2019 and the adoption of IPv6 is actually gai
On 4/25/19 11:05 AM, Kees Cook wrote:
On Thu, Apr 25, 2019 at 9:52 AM shuah wrote:
On 4/24/19 5:12 PM, wrote:
This refactors the selftest Makefiles to extract the test running logic
to be reused between "run_tests" and "emit_tests", while also fixing
up the test output to be TAP version 13 c
On Thu, Apr 25, 2019 at 5:43 AM Jann Horn wrote:
> An interesting effect of this is that it will be possible to set this
> on a CoW anon VMA in a fork() child, and then the semantics in the
> parent will be subtly different - e.g. if the parent vmsplice()d a
> CoWed page into a pipe, then forked a
On Thu, Apr 25, 2019 at 5:44 AM Vlastimil Babka wrote:
>
> On 4/25/19 2:14 PM, Michal Hocko wrote:
> > Please cc linux-api for user visible API proposals (now done). Keep the
> > rest of the email intact for reference.
> >
> > On Wed 24-04-19 14:10:39, Matthew Garrett wrote:
> >> From: Matthew Gar
On Mon, Apr 22, 2019 at 11:57:42AM -0700, Rick Edgecombe wrote:
> Andy Lutomirski (1):
> x86/mm: Introduce temporary mm structs
>
> Nadav Amit (15):
> Fix "x86/alternatives: Lockdep-enforce text_mutex in text_poke*()"
> x86/jump_label: Use text_poke_early() during early init
> x86/mm: Save
On Thu, Apr 25, 2019 at 10:48:20PM +0200, Peter Zijlstra wrote:
> On Mon, Apr 22, 2019 at 11:57:42AM -0700, Rick Edgecombe wrote:
> > Andy Lutomirski (1):
> > x86/mm: Introduce temporary mm structs
> >
> > Nadav Amit (15):
> > Fix "x86/alternatives: Lockdep-enforce text_mutex in text_poke*()"
Quoting Dmitry Osipenko (2019-04-14 12:23:18)
> The timings parser doesn't append timings, but instead it parses only
> the first timing and hence doesn't store all of the timings when
> device-tree has timings for multiple RAM codes. In a result EMC scaling
> doesn't work if timings are missing.
>
Quoting Dmitry Osipenko (2019-04-14 12:23:19)
> When a clk user requests rate that is higher than the maximum possible,
> the rate shall be clamped to the maximum and not to the current value.
>
> Signed-off-by: Dmitry Osipenko
> ---
Applied to clk-next
Quoting Dmitry Osipenko (2019-04-14 12:23:20)
> There is no justification for the BUG() in this code.
>
> Signed-off-by: Dmitry Osipenko
> ---
Applied to clk-next
Quoting Dmitry Osipenko (2019-04-14 12:23:17)
> The EMC clock marked as critical, hence it is already enabled at the
> registration time.
>
> Signed-off-by: Dmitry Osipenko
> ---
Applied to clk-next
Quoting Dmitry Osipenko (2019-04-14 12:23:21)
> The Memory Controller (MC) clock rate can't be simply changed and nothing
> in kernel need to change the rate, hence let's make the clock read-only.
> This id also needed for the EMC driver because timing configuration may
> require the MC clock diver
Quoting Alexandre Belloni (2019-04-25 13:31:39)
> On 25/04/2019 12:38:55-0700, Stephen Boyd wrote:
> > Quoting Alexandre Belloni (2019-04-02 05:50:56)
> > > diff --git a/drivers/clk/at91/sam9x60.c b/drivers/clk/at91/sam9x60.c
> > > new file mode 100644
> > > index ..22bf51c55bdc
> > > -
Currently, there is no fast mechanism to get the virtual memory size of
the current process from userspace. This information is available to the
user through several means, one being a linear search of the entire address
space. This is the method used by a component of the libhugetlb kernel
test, a
On Wed, Apr 24, 2019 at 05:50:02PM +0100, Lorenzo Pieralisi wrote:
> On Wed, Apr 24, 2019 at 12:29:18AM +0200, Remi Pommarel wrote:
> > Hi,
> >
> > On Tue, Apr 23, 2019 at 05:32:15PM +0100, Lorenzo Pieralisi wrote:
> > > On Wed, Mar 13, 2019 at 10:37:52PM +0100, Remi Pommarel wrote:
> > > > When c
On Wed, Apr 24, 2019 at 02:20:13PM -0400, Joel Savitz wrote:
> In the event of an oom kill, useful information about the killed
> process is printed to dmesg. Users, especially system administrators,
> will find it useful to immediately see the UID of the process.
>
> In the following example, abu
On Thu, Apr 25, 2019 at 04:57:47PM -0400, Joel Savitz wrote:
> Currently, there is no fast mechanism to get the virtual memory size of
> the current process from userspace. This information is available to the
> user through several means, one being a linear search of the entire address
> space. Th
Hi all,
In commit
8c380ab4b7b5 ("ext4: avoid drop reference to iloc.bh twice")
Fixes tag
Fixes: fb265c9cb49e("ext4: add ext4_sb_bread() to disambiguate ENOMEM cases")
has these problem(s):
- missing space between the SHA1 and the subject.
--
Cheers,
Stephen Rothwell
pgpJRYQ71jFt4.pg
601 - 700 of 901 matches
Mail list logo
