On Wed, Jan 09 2019 at 12:37 -0700, Rob Herring wrote:
On Wed, Jan 9, 2019 at 11:31 AM Lina Iyer wrote:
On Tue, Jan 08 2019 at 07:49 -0700, Rob Herring wrote:
>On Mon, Jan 7, 2019 at 12:51 PM Lina Iyer wrote:
>>
>> On Fri, Dec 28 2018 at 17:07 -0700, Rob Herring wrote:
>> >On Wed, Dec 19, 201
On 2/12/19 9:05 AM, James Bottomley wrote:
> The problem is that the default for MQ is not to gather entropy,
> whereas the default for the legacy queue was always to gather it. The
> original attempt to fix entropy gathering for rotational disks under MQ
> added an else branch in sd_read_block_ch
Good day,
My name is Mr.Louis Smith am Financial Consultant, one of my client have
interest in Investing in your country into a Joint venture Agreement. Kindly
contact me via my email if you are interested so that we can talk more. this is
my personal email: louissmith...@yahoo.com
I await you
On Mon 11-02-19 09:22:58, Dan Williams wrote:
> On Mon, Feb 11, 2019 at 2:24 AM Jan Kara wrote:
> >
> > On Fri 08-02-19 12:50:37, Dan Williams wrote:
> > > On Fri, Feb 8, 2019 at 3:11 AM Jan Kara wrote:
> > > >
> > > > On Fri 08-02-19 15:43:02, Dave Chinner wrote:
> > > > > On Thu, Feb 07, 2019 a
On Tue, Feb 12, 2019 at 06:51:01PM +0800, Xin Long wrote:
> In sctp_stream_init(), after sctp_stream_outq_migrate() freed the
> surplus streams' ext, but sctp_stream_alloc_out() returns -ENOMEM,
> stream->outcnt will not be set to 'outcnt'.
>
> With the bigger value on stream->outcnt, when closing
On 2/12/19 9:42 AM, Andrey Konovalov wrote:
> On Tue, Feb 12, 2019 at 2:43 PM Qian Cai wrote:
>>
>>
>>
>> On 2/12/19 8:26 AM, Andrey Konovalov wrote:
>>> Hm, did you apply all 6 patches (the one that you sent and these five)
>> Yes.
>
> I'm failing to reproduce this in QEMU. You're still using
From: Colin Ian King
There are some statements that are indented incorrectly. Fix these.
Signed-off-by: Colin Ian King
---
drivers/net/ethernet/qlogic/qlge/qlge_ethtool.c | 4 ++--
drivers/net/ethernet/qlogic/qlge/qlge_main.c| 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff
On Tue, Feb 12, 2019 at 11:21:29AM +0100, Michal Hocko wrote:
> From: Michal Hocko
>
> Tetsuo has reported that creating a thousands of processes sharing MM
> without SIGHAND (aka alien threads) and setting
> /proc//oom_score_adj will swamp the kernel log and takes ages [1]
> to finish. This is e
On Tue, Feb 12, 2019 at 04:19:38PM +0200, Matti Vaittinen wrote:
> read ROHM BD71837 / BD71847 specific device tree bindings for
> controlling the PMIC shutdown/reset states and voltages for
> different HW states. The PMIC was designed to be used with NXP
> i.MX8 SoC and it supports SNVS low power
On Tue 12-02-19 15:39:38, Amir Goldstein wrote:
> > > My other thought is that perhaps sb_start_write() should invoke
> > > s_ops->start_write() so that overlay can do the freeze protection on
> > > the upper early.
> >
> > So my understanding of overlayfs is pretty basic so I'm sorry if I miss
> >
Hi,
Here is the v3 series of kprobes blacklist bugfix and improvements mainly
on x86 (since I started testing on qemu-x86).
This version is just rebased on top of -tip master branch and
add bsearch nokprobe patch by Andrea (Thanks!)
This has been started from discussion about KPROBE_ENENTS_ON_NO
On Wed, Feb 06, 2019 at 08:44:26AM +, Haggai Eran wrote:
> On 1/29/2019 6:58 PM, jgli...@redhat.com wrote:
> > Convert ODP to use HMM so that we can build on common infrastructure
> > for different class of devices that want to mirror a process address
> > space into a device. There is no fu
Prohibit probing on optprobe template code, since it is not
a code but a template instruction sequence. If we modify
this template, copied template must be broken.
Signed-off-by: Masami Hiramatsu
Fixes: 9326638cbee2 ("kprobes, x86: Use NOKPROBE_SYMBOL() instead of __kprobes
annotation")
Cc: sta.
Move optprobe trampoline code into RODATA since it is
not executed, but copied and modified to be used on
a trampoline buffer.
Signed-off-by: Masami Hiramatsu
---
arch/x86/kernel/kprobes/opt.c |9 ++---
1 file changed, 2 insertions(+), 7 deletions(-)
diff --git a/arch/x86/kernel/kprobes
Prohibit probing on the functions called before kprobe_int3_handler()
in do_int3(). More specifically, ftrace_int3_handler(),
poke_int3_handler(), and ist_enter(). And since rcu_nmi_enter() is
called by ist_enter(), it also should be marked as NOKPROBE_SYMBOL.
Since those are handled before kprobe
Prohibit probing on IRQ handlers in irqentry_text because
if it interrupts user mode, at that point we haven't changed
to kernel space yet and which eventually leads a double fault.
E.g.
# echo p apic_timer_interrupt > kprobe_events
# echo 1 > events/kprobes/enable
PANIC: double fault, error_co
Since kprobes breakpoint handling involves hardirq tracer,
probing these functions cause breakpoint recursion problem.
Prohibit probing on those functions.
Signed-off-by: Masami Hiramatsu
Acked-by: Steven Rostedt (VMware)
---
kernel/trace/trace_irqsoff.c|9 +++--
kernel/trace/trace
Newer gcc can generate some different instances of a function
with suffixed symbols if the function is optimized and only
has a part of that. (e.g. .constprop, .part etc.)
In this case, it is not enough to check the entry of kprobe
blacklist because it only records non-suffixed symbol address.
To
Since kprobe itself depends on RCU, probing on RCU debug
routine can cause recursive breakpoint problem.
Prohibit probing on RCU debug routines.
int3
->do_int3()
->ist_enter()
->RCU_LOCKDEP_WARN()
->debug_lockdep_rcu_enabled() -> int3
Signed-off-by: Masami Hiramatsu
---
kernel/r
Since kprobes depends on preempt disable/enable, probing
on the preempt debug routine can cause recursive breakpoint
problem.
Signed-off-by: Masami Hiramatsu
---
lib/smp_processor_id.c |7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/lib/smp_processor_id.c b/lib/smp_
In remove(), use cancel_delayed_work_sync() to cancel the
delayed work. Otherwise there's a chance that this work
will continue to run until after the device has been removed.
While we're here, fix the deallocation order in remove(),
to correspond to the inverse of the probe() allocation
order. Th
Some lockdep functions can be involved in breakpoint handling
and probing on those functions can cause a breakpoint recursion.
Prohibit probing on those functions by blacklist.
Signed-off-by: Masami Hiramatsu
---
kernel/locking/lockdep.c |7 ++-
1 file changed, 6 insertions(+), 1 deletio
On Tue, Feb 12, 2019 at 06:47:30PM +0800, Xin Long wrote:
> Jianlin reported a panic when running sctp gso over gre over vlan device:
>
> [ 84.772930] RIP: 0010:do_csum+0x6d/0x170
> [ 84.790605] Call Trace:
> [ 84.791054] csum_partial+0xd/0x20
> [ 84.791657] gre_gso_segment+0x2c3
On Tue, Feb 12, 2019 at 04:20:03PM +1100, Stephen Rothwell wrote:
> Caused by commit
>
> a3e4d3f97ec8 ("XArray: Redesign xa_alloc API")
>
> interacting with commits
>
> e59178d895af ("RDMA/devices: Use xarray to store the clients")
> 0df91bb67334 ("RDMA/devices: Use xarray to store the cli
On 2/11/19 11:27 PM, Ben Finney wrote:
> Martin Steigerwald writes:
>
>> Well the file has in its header:
>>
>> /* Fast hashing routine for a long.
>>(C) 2002 William Lee Irwin III, IBM */
>>
>> /*
>> * Knuth recommends primes in approximately golden ratio to the maximum
>> * integer repres
From: Andrea Righi
Since kprobe breakpoing handler is using bsearch(), probing on this
routine can cause recursive breakpoint problem.
int3
->do_int3()
->ftrace_int3_handler()
->ftrace_location()
->ftrace_location_range()
->bsearch() -> int3
Prohibit probing on bsearch(
On Tue, Feb 12, 2019 at 11:14 AM Sven Van Asbroeck wrote:
>
> In remove(), use cancel_delayed_work_sync() to cancel the
> delayed work. Otherwise there's a chance that this work
> will continue to run until after the device has been removed.
>
> While we're here, fix the deallocation order in remo
On Tue, 12 Feb 2019 at 13:10, Rafael J. Wysocki wrote:
>
> From: Rafael J. Wysocki
>
> Commit 4080ab083000 ("PM-runtime: Take suppliers into account in
> __pm_runtime_set_status()") introduced a race condition that may
> trigger if __pm_runtime_set_status() is used incorrectly (that is,
> if it i
On 2/12/19 2:54 AM, Greg KH wrote:
On Tue, Feb 12, 2019 at 06:29:39PM +0800, Kyle Tso wrote:
On Thu, Jan 31, 2019 at 3:02 PM Greg KH wrote:
On Thu, Jan 31, 2019 at 11:54:11AM +0800, Kyle Tso wrote:
Provide a function to get the partner Source Capabilities.
Signed-off-by: Kyle Tso
---
dri
On Tue, Feb 12, 2019 at 4:06 PM Greg Kroah-Hartman
wrote:
>
> On Tue, Feb 12, 2019 at 03:52:53PM +0100, Ulf Hansson wrote:
> > On Tue, 12 Feb 2019 at 15:09, Greg Kroah-Hartman
> > wrote:
> > >
> > > On Tue, Feb 12, 2019 at 01:01:13PM +0100, Rafael J. Wysocki wrote:
> > > > Hi Greg at al,
> > > >
In remove(), use cancel_delayed_work_sync() to cancel the
delayed work. Otherwise there's a chance that this work
will continue to run until after the device has been removed.
While we're here, fix the deallocation order in remove(),
to correspond to the inverse of the probe() allocation
order. Th
Hi Alexey,
I love your patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v5.0-rc4]
[cannot apply to next-20190212]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com
Hi,
* Lokesh Vutla [190212 07:43]:
> +Example:
> +
> +The following example demonstrates both interrupt router node and the
> consumer
> +node(main gpio) on the AM654 SoC:
> +
> +main_intr: interrupt-controller0 {
> + compatible = "ti,sci-intr";
> + interrupt-controller;
> +
On Tue, Feb 12, 2019 at 08:15:28AM -0800, Matthew Wilcox wrote:
> On Tue, Feb 12, 2019 at 04:20:03PM +1100, Stephen Rothwell wrote:
> > Caused by commit
> >
> > a3e4d3f97ec8 ("XArray: Redesign xa_alloc API")
> >
> > interacting with commits
> >
> > e59178d895af ("RDMA/devices: Use xarray to
As there is restriction to access to EMAC System Manager registers in
the kernel for Intel Stratix10, the use of SMC calls are required and
added in dwmac-socfpga driver.
Signed-off-by: Ooi, Joyce
---
.../net/ethernet/stmicro/stmmac/dwmac-socfpga.c| 101
1 files changed
On Mon, 11 Feb 2019 at 19:51, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.20.8 release.
> There are 352 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.
>
> Res
From: Julia Cartwright
In order to enable the queuing of kthread work items from hardirq
context even when PREEMPT_RT_FULL is enabled, convert the worker
spin_lock to a raw_spin_lock.
This is only acceptable to do because the work performed under the lock
is well-bounded and minimal.
Cc: Sebast
The TIMER_IRQSAFE was introduced in commit
22597dc3d97b1 ("kthread: initial support for delayed kthread work")
which modelled the delayed kthread code after workqueue's code. The
workqueue code requires the flag TIMER_IRQSAFE for synchronisation
purpose. This is not true for kthread's delay tim
On Tue, Feb 12, 2019 at 5:18 PM Ulf Hansson wrote:
>
> On Tue, 12 Feb 2019 at 13:10, Rafael J. Wysocki wrote:
> >
> > From: Rafael J. Wysocki
> >
> > Commit 4080ab083000 ("PM-runtime: Take suppliers into account in
> > __pm_runtime_set_status()") introduced a race condition that may
> > trigger
On Mon 11-02-19 11:06:54, Jason Gunthorpe wrote:
> On Mon, Feb 11, 2019 at 09:22:58AM -0800, Dan Williams wrote:
>
> > I honestly don't like the idea that random subsystems can pin down
> > file blocks as a side effect of gup on the result of mmap. Recall that
> > it's not just RDMA that wants thi
Add bindings for the Amlogic G12A AO Clock and Reset controllers.
Signed-off-by: Neil Armstrong
---
.../bindings/clock/amlogic,gxbb-aoclkc.txt| 1 +
include/dt-bindings/clock/g12a-aoclkc.h | 34 +++
include/dt-bindings/reset/g12a-aoclkc.h | 18 ++
3 files
This patchset add support for the Amlogic G12A SoC family Always-On
clock and reset controller.
This adds support for clocks on the Always-On domain like :
- Always-On UARTS & I2C Controllers
- CEC Controllers
- SARADC source and bus clock
- Infrared Decoder/Encoder bus clock
- USB 32K reference c
Add the Amlogic G12A AO Clock and Reset controller driver handling
generation of Always-On clocks :
- AO Clocks and Reset for Always-On modules
- 32K Generation for USB and CEC
- SAR ADC controller clock
Signed-off-by: Neil Armstrong
Signed-off-by: Jerome Brunet
---
drivers/clk/meson/Kconfig
The timer is initialized with TIMER_IRQSAFE flag. It does look like the
timer callback requires this flag at all. Its sole purpose is to ensure
synchronisation in the workqueue code.
Remove TIMER_IRQSAFE flag because it is not required.
Cc: Jani Nikula
Cc: Joonas Lahtinen
Cc: Rodrigo Vivi
Cc:
Hi,
* Lokesh Vutla [190212 07:43]:
> +The Interrupt Router (INTR) module provides a mechanism to route M
> +interrupt inputs to N interrupt outputs, where all M inputs are selectable
> +to be driven per N output. There is one register per output (MUXCNTL_N) that
> +controls the selection.
> +
> +
On Mon, Feb 11, 2019 at 6:31 PM Marcos Paulo de Souza
wrote:
>
> Hello João,
>
> On 2/11/19 5:14 PM, João Paulo Rechi Vita wrote:
> > Hello Marcos,
> >
> > On Sun, Feb 10, 2019 at 5:05 PM Marcos Paulo de Souza
> > wrote:
> >>
> >>
> >>
> >> On 2/10/19 9:45 PM, Andy Shevchenko wrote:
> >>> On Sun,
On Mon 11-02-19 14:09:56, Jason Gunthorpe wrote:
> On Mon, Feb 11, 2019 at 01:02:37PM -0800, Dan Williams wrote:
> > On Mon, Feb 11, 2019 at 12:49 PM Jason Gunthorpe wrote:
> > >
> > > On Mon, Feb 11, 2019 at 11:58:47AM -0800, Dan Williams wrote:
> > > > On Mon, Feb 11, 2019 at 10:40 AM Matthew Wi
On Mon, Jan 28, 2019 at 09:49:32PM -0800, Maya Nakamura wrote:
> On Sun, Jan 27, 2019 at 05:11:48AM +, Michael Kelley wrote:
> > From: Maya Nakamura Sent: Saturday, January
> > 26, 2019 12:52 AM
> > >
> > > Remove a duplicate definition of VP set (hv_vp_set) and use the common
> > > definit
On Mon, 11 Feb 2019, Dan Williams wrote:
> An mmap write after a fault due to a hole punch is free to trigger
> SIGBUS if the subsequent page allocation fails. So no, I don't see
> them as the same unless you're allowing for the holder of the MR to
> receive a re-fault failure.
Order 0 page alloc
Add the bindings for the Bifrost family of ARM Mali GPUs.
The Bifrost GPU architecture is similar to the Midgard family,
but with a different Shader Core & Execution Engine structures.
Bindings are based on the Midgard family bindings, but the inner
architectural changes makes it a separate famil
On Tue, Feb 12, 2019 at 06:39:31PM +0300, Eugeniy Paltsev wrote:
> Handle U-boot arguments paranoidly:
> * don't allow to pass unknown tag.
> * try to use external device tree blob only if corresponding tag
>(TAG_DTB) is set.
> * check that magic number is correct.
> * don't check uboot_tag
On Mon, 11 Feb 2019, John Hubbard wrote:
> But anyway, Jan's proposal a bit earlier today [1] is finally sinking into
> my head--if we actually go that way, and prevent the caller from setting up
> a problematic gup pin in the first place, then that may make this point sort
> of moot.
Ok well can
On 2/11/19 6:18 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.9.156 release.
There are 137 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 should be made
On 2/11/19 6:16 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.14.99 release.
There are 205 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 should be made
On Thu, Feb 07, 2019 at 06:00:08PM +0100, Sylwester Nawrocki wrote:
> I am not entirely sure we should be removing the
> SND_DMAENGINE_PCM_FLAG_CUSTOM_CHANNEL_NAME flag like this, it might all
> be a bit more explicit with the flag.
I'm fairly happy with what you're doing here and the Samsung dri
On 2/11/19 6:14 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.19.21 release.
There are 313 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 should be made
On 2/12/19 8:39 AM, LABBE Corentin wrote:
>> While I'm at it refactor U-boot arguments handling code.
>>
> Hello
>
> I have tried to test this serie, but this patch does not apply anymore on
> current next tree.
> It conflicts with "ARC: boot: robustify u-boot arg referencing".
I was carrying tha
On 2/11/19 6:13 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.20.8 release.
There are 352 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 should be made
On 2/11/19 10:50 PM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20190211:
>
on i386 or x86_64:
ld: drivers/platform/chrome/wilco_ec/core.o: in function `wilco_ec_remove':
core.c:(.text+0x46): undefined reference to `cros_ec_lpc_mec_destroy'
ld: drivers/platform/chrome/wilco_ec/core.o:
On Tue 12-02-19 16:36:36, Christopher Lameter wrote:
> On Mon, 11 Feb 2019, Dan Williams wrote:
>
> > An mmap write after a fault due to a hole punch is free to trigger
> > SIGBUS if the subsequent page allocation fails. So no, I don't see
> > them as the same unless you're allowing for the holder
On 2/12/19 7:39 AM, Eugeniy Paltsev wrote:
> Handle U-boot arguments paranoidly:
> * don't allow to pass unknown tag.
> * try to use external device tree blob only if corresponding tag
>(TAG_DTB) is set.
> * check that magic number is correct.
> * don't check uboot_tag if kernel build with
Hello,
Wen, thank you for the patch.
On Mon, Feb 11, 2019 at 11:24:15AM +0100, j...@8bytes.org wrote:
> Adding a few more people to Cc.
>
> On Sun, Feb 03, 2019 at 10:27:09AM +, wen yang wrote:
> > Make sure to drop the reference to the device taken by
> > of_find_device_by_node() on driver
On Tue, Feb 12, 2019 at 02:51:00PM +0100, Thomas Gleixner wrote:
> On Tue, 12 Feb 2019, Peter Zijlstra wrote:
>
> > On Mon, Feb 11, 2019 at 11:16:43AM -0800, Fenghua Yu wrote:
> > > 4. The feature can be disabled by kernel option
> > > "clearcpuid=split_lock_detection" during early boot time.
> >
On Mon, 11 Feb 2019 14:50:56 +0100
Ingo Molnar wrote:
>
> * Masami Hiramatsu wrote:
>
> > Hi Ingo,
> >
> > Can I ask you to pick this series and Andrea's patch?
> > Or would I better update this series on the latest tip/master?
>
> Yeah, an updated series with Andrea's patch included, agains
On Tue, Feb 12, 2019 at 02:43:59PM +, Mark Brown wrote:
> Mason had submitted a new verison a couple of weeks ago and there'd been
> no replies on the new version so I'd thought that all the prior issues
> had been addressed. I guess that's not the case? The thread on the
> version before wa
On Tue, 12 Feb 2019, Alexey Kardashevskiy wrote:
> Now it is 3 independent accesses (actually 4 but the last one is
> diagnostic) with no locking around them. Why do not we need a lock
> anymore precisely? Thanks,
Updating a regular counter is racy and requires a lock. It was converted
to be an a
On 02/12, Eric W. Biederman wrote:
>
> > Here I was trying for the simple minimal change and I hit this landmine.
> > Which leaves me with the question of what should be semantics of signal
> > handling after exit.
Yes, currently it is undefined. Even signal_pending() is random.
> > I think from
On 2/12/19 8:48 AM, Peter Zijlstra wrote:
>>> IFF clearcpuid lives, it should also employ CPUID faulting and clear it
>>> for userspace too.
>> We have it already,
> D'0h right, I thought that was introduced here, but that's just
> extending it to multiple arguments.
... and making it take strings
The one thing that currently needs doing from an architecture
point of view is associating the GI domain with its nearest
memory domain. This allows all the standard NUMA aware code
to get a 'reasonable' answer.
A clever driver might elect to do load balancing etc
if there are multiple host / mem
ACPI 6.3 introduced a new entity that can be part of a NUMA proximity domain.
It may share such a domain with the existing options (memory, cpu etc) but it
may also exist on it's own.
The intent is to allow the description of the NUMA properties (particulary
via HMAT) of accelerators and other ini
Generic Initiators are a new ACPI concept that allows for
the description of proximity domains that contain a
device which performs memory access (such as a network card)
but neither host CPU nor memory.
This first patch has the parsing code and provides the
infrastructure for an architecture to a
Until we tell ACPI that we support generic initiators, it will have
to operate in fall back domain mode and all _PXM entries should
be on existing non GI domains.
This patch sets the relevant OSC bit to make that happen.
Signed-off-by: Jonathan Cameron
---
Note that this will need platform guar
On Mon, Feb 11, 2019 at 09:51:25PM +0100, Pavel Machek wrote:
Hi!
4.9-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit f36797ee43802b367e59f0f9a9805304a4ff0c98 ]
The device-tree booted MMP2 needs to enable the timer clock, otherwise
On Tue, 12 Feb 2019, Jan Kara wrote:
> > Isn't that already racy? If the mmap user is fast enough can't it
> > prevent the page from becoming freed in the first place today?
>
> No, it cannot. We block page faulting for the file (via a lock), tear down
> page tables, free pages and blocks. Then we
The patch
ASoC: samsung: dmaengine: Allow to specify custom DMA device
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hou
The patch
ASoC: samsung: i2s: Convert to single component with multiple DAIs
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next
The patch
ASoC: samsung: i2s: Fix prescaler setting for the secondary DAI
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24
The patch
ASoC: dmaengine: Extend use of chan_names provided in custom DMA config
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the
The patch
ASoC: dmaengine: Improve of_node test in dmaengine_pcm_request_chan_of()
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the
Jens,
>> The fix is to set the non-rotational and add-randomness flags
>> unconditionally early on in the disk initialization path, so they can
>> be reset only if the device actually reports being non-rotational via
>> the VPD page.
>
> Reviewed-by: Jens Axboe
Yeah, this looks good to me. I'l
On Tue, Feb 12, 2019 at 03:25:49PM +0100, Mike Looijmans wrote:
> Standard unit for temperature is millidegrees Celcius, whereas this driver
> was reporting in degrees. Fix the scale factor in the driver.
>
> Signed-off-by: Mike Looijmans
> ---
> drivers/iio/gyro/bmg160_core.c | 5 +++--
> 1 file
Hi all,
I'd like to propose a discussion about the workflow of the stable trees
when it comes to fs/ and mm/. In the past year we had some friction with
regards to the policies and the procedures around picking patches for
stable tree, and I feel it would be very useful to establish better flow
w
On Fri, Jan 25, 2019 at 08:10:13AM +, Peng Ma wrote:
> Add SATA device nodes for fsl-lx2160a and enable support
> for QDS and RDB boards.
>
> Signed-off-by: Peng Ma
> ---
> changed for V5:
> - no change
>
> arch/arm64/boot/dts/freescale/fsl-lx2160a-qds.dts | 16 +++
> arch/arm64
On Tue, Feb 12, 2019 at 5:06 AM Moritz Fischer wrote:
Hi Nava,
> > + mgr = fpga_mgr_create(dev, "Xilinx ZynqMP FPGA Manager",
> > + &zynqmp_fpga_ops, priv);
Please use the new devm_fpga_mgr_create()
> > + if (!mgr)
> > + return -ENOMEM;
> >
From: Christoph Hellwig
Date: Mon, 11 Feb 2019 14:19:56 +0100
> We still have a few drivers which pass a NULL struct device pointer
> to DMA API functions, which generally is a bad idea as the API
> implementations rely on the device not only for ops selection, but
> also the dma mask and various
On 2/9/19 7:38 PM, Michael S. Tsirkin wrote:
> On Fri, Feb 08, 2019 at 02:05:09PM -0800, Alexander Duyck wrote:
>> On Fri, Feb 8, 2019 at 1:38 PM Michael S. Tsirkin wrote:
>>> On Fri, Feb 08, 2019 at 03:41:55PM -0500, Nitesh Narayan Lal wrote:
>> I am also planning to try Michael's suggestion
Hello Julien-
On Fri, Feb 08, 2019 at 04:55:13PM +, Julien Grall wrote:
> When the kernel is compiled with CONFIG_KERNEL_MODE_NEON, some part of
> the kernel may be able to use FPSIMD/SVE. This is for instance the case
> for crypto code.
>
> Any use of FPSIMD/SVE in the kernel are clearly mar
In order to support softirq per-vector locking validation, we could
simply iterate over all enabled vectors and perform separate validation
for all of them on every lock event. We can expect that to introduce a
severe performance penalty though.
Therefore, we instead plan to validate the LOCK_USED
The usage mask is going to expand to validate softirq related usages in
a per-vector finegrained way.
The current bitmap layout is:
LOCK_USEDHARDIRQ bits
\/
\ /
0
In order to perform softirq vector-finegrained locking validation we'll
need to be able to check multiple vector usages at once. Prepare the low
level usage mask check functions for that purpose.
Signed-off-by: Frederic Weisbecker
Cc: Mauro Carvalho Chehab
Cc: Joel Fernandes
Cc: Thomas Gleixner
Now that mark_lock() is going to handle multiple softirq vectors at
once for a given lock usage, the current fast path optimization that
simply check if the new bit usage is already present won't work anymore.
Indeed if the new usage is only partially present, such as for some
softirq vectors and
We are going to save as much traces as we have softirq vectors involved
in a given usage. Expand the stack trace record code accordingly.
Signed-off-by: Frederic Weisbecker
Cc: Mauro Carvalho Chehab
Cc: Joel Fernandes
Cc: Thomas Gleixner
Cc: Pavan Kondeti
Cc: Paul E . McKenney
Cc: David S .
Define the softirq vectors through macros so that we can later include
them in the automated definition of lockdep usage states.
Signed-off-by: Frederic Weisbecker
Cc: Mauro Carvalho Chehab
Cc: Joel Fernandes
Cc: Thomas Gleixner
Cc: Pavan Kondeti
Cc: Paul E . McKenney
Cc: David S . Miller
C
check_prev_add_irq() tests all incompatible scenarios one after the
other while adding a lock (@next) to a tree dependency (@prev):
LOCK_USED_IN_HARDIRQ vs LOCK_ENABLED_HARDIRQ
LOCK_USED_IN_HARDIRQ_READ vs LOCK_ENABLED_HARDIRQ
LOCK_USED_IN_SOFTI
We are going to extend the softirq bits with an enabled vector mask.
Provide the field with a more generic name to later layout the pending
states on the lower bits and the enabled states on the higher bits.
Signed-off-by: Frederic Weisbecker
Cc: Mauro Carvalho Chehab
Cc: Joel Fernandes
Cc: Tho
We are going to need a nand version of softirq_pending_or() in order
to clear specific bits from the pending mask.
But instead of naming the mutators after their implementation, rather
name them after their high level purpose.
Suggested-by: Linus Torvalds
Signed-off-by: Frederic Weisbecker
Cc:
Disabling the softirqs is currently an all-or-nothing operation: either
all softirqs are enabled or none of them. However we plan to introduce a
per vector granularity of this ability to improve latency response and
make each softirq vector interruptible by the others.
The first step carried here
From: Frederic Weisbecker
Use the subsystem as the prefix to name the __softirq_data accessors.
They are going to be extended and want a more greppable and standard
naming sheme.
Signed-off-by: Frederic Weisbecker
Cc: Mauro Carvalho Chehab
Cc: Joel Fernandes
Cc: Thomas Gleixner
Cc: Pavan Kon
mark_lock_irq() is going to deal with lock usages that gather multiple
softirq vectors at once. Therefore the validation through valid_state()
will need to handle expanded usage masks.
So enhance valid_state() to that purpose.
Signed-off-by: Frederic Weisbecker
Cc: Mauro Carvalho Chehab
Cc: Joe
Now that the code is mostly ready to play at this finegrained level,
reuse the macrofied vector list to define the usual 4 lock usage states
for each softirq vectors. This way we can perform the validations
independently for each of them.
The new usage mask layout becomes:
601 - 700 of 1653 matches
Mail list logo
