Yu-cheng Yu writes:
> @@ -983,6 +983,7 @@ int copy_xstate_to_kernel(void *kbuf, struct xregs_state
> *xsave, unsigned int of
> {
> unsigned int offset, size;
> struct xstate_header header;
> + int last_off;
> int i;
>
> /*
> @@ -1006,7 +1007,17 @@ int
On Thu, May 07, 2020 at 07:50:09AM -0400, Paolo Bonzini wrote:
> @@ -267,7 +268,7 @@ void enter_svm_guest_mode(struct vcpu_svm *svm, u64
> vmcb_gpa,
> svm->vmcb->save.rsp = nested_vmcb->save.rsp;
> svm->vmcb->save.rip = nested_vmcb->save.rip;
> svm->vmcb->save.dr7 =
On Thu, May 07, 2020 at 02:06:31PM -0400, Rafael Aquini wrote:
> diff --git a/kernel/sysctl.c b/kernel/sysctl.c
> index 8a176d8727a3..b80ab660d727 100644
> --- a/kernel/sysctl.c
> +++ b/kernel/sysctl.c
> @@ -1217,6 +1217,13 @@ static struct ctl_table kern_table[] = {
> .extra1
On 5/7/20, Robin Murphy wrote:
> On 2020-05-06 9:01 pm, vji...@codeaurora.org wrote:
>> From: Vijayanand Jitta
>>
>> When ever a new iova alloc request comes iova is always searched
>> from the cached node and the nodes which are previous to cached
>> node. So, even if there is free iova space
On Thu, May 7, 2020 at 1:11 AM Frankie Chang wrote:
>
> From: "Frankie.Chang"
>
> Record start/end timestamp for binder transaction.
> When transaction is completed or transaction is free,
> it would be checked if transaction latency over threshold (2 sec),
If this is a hard-coded threshold,
On Thu, 7 May 2020 at 20:04, Phil Auld wrote:
>
> Hi Vincent,
>
> On Thu, May 07, 2020 at 05:06:29PM +0200 Vincent Guittot wrote:
> > Hi Phil,
> >
> > On Wed, 6 May 2020 at 20:05, Phil Auld wrote:
> > >
> > > Hi Vincent,
> > >
> > > Thanks for taking a look. More below...
> > >
> > > On Wed, May
- On May 7, 2020, at 2:04 PM, Andy Lutomirski l...@kernel.org wrote:
> On Tue, May 5, 2020 at 7:14 AM Thomas Gleixner wrote:
>>
>> From: Peter Zijlstra
>>
>> A few exceptions (like #DB and #BP) can happen at any location in the code,
>> this then means that tracers should treat events from
On Fri, 8 May 2020 00:58:05 +0900
Masami Hiramatsu wrote:
> On Fri, 8 May 2020 00:56:47 +0900
> Masami Hiramatsu wrote:
>
> > On Thu, 7 May 2020 17:23:36 +0800
> > Yunfeng Ye wrote:
> >
> > > The @data and @fd is leak in the error path of apply_xbc(), so this
> > > patch fix it.
> >
> >
On Thu, May 7, 2020 at 10:48 AM Andi Kleen wrote:
>
> On Thu, May 07, 2020 at 01:14:29AM -0700, Ian Rogers wrote:
> > Metric groups contain metrics. Metrics create groups of events to
> > ideally be scheduled together. Often metrics refer to the same events,
> > for example, a cache hit and cache
According to the latest AM65x Data Manual[1], a different output tap
delay value is optimum for a given speed mode. Update these values.
[1] http://www.ti.com/lit/gpn/am6526
Signed-off-by: Faiz Abbas
---
v2: Rebased to the latest mainline kernel
arch/arm64/boot/dts/ti/k3-am65-main.dtsi | 12
On Fri, 1 May 2020 00:06:17 +0200, Ansuel Smith wrote:
> Document qcom,pcie-ipq8064-v2 needed to use different phy_tx0_term_offset.
> In ipq8064 phy_tx0_term_offset is 7.
> In ipq8064 v2 other SoC it's set to 0 by default.
>
> Signed-off-by: Ansuel Smith
> ---
>
On Thu, May 07, 2020 at 11:33:46PM +0530, Pratyush Yadav wrote:
> On 07/05/20 09:20AM, Daniel Walker wrote:
> > Some chips have 4B opcodes, but there is no way to know if they have
> > them. This device tree option allows platform owners to force enable 4b
> > opcodes when they know their
On Fri, May 01, 2020 at 12:06:16AM +0200, Ansuel Smith wrote:
> From: Sham Muthayyan
>
> Add tx term offset support to pcie qcom driver need in some revision of
> the ipq806x SoC.
> Ipq8064 have tx term offset set to 7.
> Ipq8064-v2 revision and ipq8065 have the tx term offset set to 0.
>
>
It will be needed by schedutil once modularized, export it.
Signed-off-by: Quentin Perret
---
drivers/base/arch_topology.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/base/arch_topology.c b/drivers/base/arch_topology.c
index 4d0a0038b476..b1f0c272da67 100644
---
sched_set_deadline() is an exported symbol, use it instead of
sched_setattr_nocheck() to elevate the sugov kthreads to DL.
Signed-off-by: Quentin Perret
---
kernel/sched/cpufreq_schedutil.c | 18 +++---
1 file changed, 3 insertions(+), 15 deletions(-)
diff --git
It will be needed by schedutil once modularized, export it.
Signed-off-by: Quentin Perret
---
kernel/sched/fair.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
index dadf0a060abe..b7b43aeff969 100644
--- a/kernel/sched/fair.c
+++
The IS_ENABLED() macro evaluates to true when an option is set to =y or
=m. As such, it is a good fit for tristate options.
In preparation for modularizing schedutil, change all the related ifdefs
to use IS_ENABLED().
Signed-off-by: Quentin Perret
---
include/linux/cpufreq.h | 2 +-
It will be needed by schedutil once modularized, export it.
Signed-off-by: Quentin Perret
---
arch/x86/kernel/smpboot.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/x86/kernel/smpboot.c b/arch/x86/kernel/smpboot.c
index 8c89e4d9ad28..a8ccd69ba5ff 100644
---
Now that all requirements to modularize schedutil are met, make the
Kconfig option tristate and add the missing MODULE_*() declarations in
cpufreq_schedutil.c.
Signed-off-by: Quentin Perret
---
drivers/cpufreq/Kconfig | 2 +-
kernel/sched/cpufreq_schedutil.c | 15 ++-
2
On Fri, May 01, 2020 at 12:06:15AM +0200, Ansuel Smith wrote:
> It is now supported the editing of Tx De-Emphasis, Tx Swing and
> Rx equalization params on ipq8064. Document this new optional params.
>
> Signed-off-by: Ansuel Smith
> ---
> .../devicetree/bindings/pci/qcom,pcie.txt | 36
It will be needed by schedutil once modularized, export it.
Signed-off-by: Quentin Perret
---
kernel/time/tick-sched.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/kernel/time/tick-sched.c b/kernel/time/tick-sched.c
index 3e2dc9b8858c..3b1050cabb58 100644
--- a/kernel/time/tick-sched.c
The EAS topology code requires the usage of schedutil on all CPUs of an
rd to actually enable EAS balancing. However, the check implementing
this references the schedutil_gov struct directly, which makes having
schedutil as a module impractical.
To prepare the ground for this modularization,
As all the sched_setscheduler*() exports have been removed, introduce
sched_set_deadline() on the model of sched_set_fifo() to enable modules
to create SCHED_DEADLINE tasks.
Signed-off-by: Quentin Perret
---
include/linux/sched.h | 2 ++
kernel/sched/core.c | 17 +
2 files
CPUFreq calls into sched_cpufreq_governor_change() when switching
governors, which triggers a sched domain rebuild when entering or
exiting schedutil.
Move the function to sched/cpufreq.c to prepare the ground for the
modularization of schedutil.
Signed-off-by: Quentin Perret
---
It will be needed by schedutil once modularized, export it.
Signed-off-by: Quentin Perret
---
kernel/sched/cpufreq.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/kernel/sched/cpufreq.c b/kernel/sched/cpufreq.c
index 82f2dda61a55..f4abe4e4e927 100644
--- a/kernel/sched/cpufreq.c
+++
It will be needed by schedutil once modularized, export it.
Signed-off-by: Quentin Perret
---
kernel/kthread.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/kernel/kthread.c b/kernel/kthread.c
index bfbfa481be3a..c0d84e1fbec2 100644
--- a/kernel/kthread.c
+++ b/kernel/kthread.c
@@ -430,6
The CPU util aggregation code for schedutil and EAS currently resides in
schedutil for historical reasons. However, this complicates modularizing
schedutil as that would make the core kernel call into a (potential)
module. While this could probably be done, it seems significantly
simpler to move
Android is trying very hard to use a single kernel image (commonly
called Generic Kernel Image, or GKI), closely aligned with mainline, to
run on all Android devices regardless of the vendor.
The GKI project intends to not only improve the status quo for Android
users directly (less fragmentation
It will be needed by schedutil once modularized, export it.
Signed-off-by: Quentin Perret
---
This is only needed for cpu_rq() -> cpu_bw_dl() in schedutil, so there is
probably an alternative if exporting this isn't desirable.
---
kernel/sched/core.c | 1 +
1 file changed, 1 insertion(+)
diff
On Fri, May 01, 2020 at 12:06:13AM +0200, Ansuel Smith wrote:
> Use qcom_clear_and_set_dword instead of use the same code many times in
> the entire driver.
>
> Signed-off-by: Ansuel Smith
> ---
> drivers/pci/controller/dwc/pcie-qcom.c | 108 ++---
> 1 file changed, 41
On Wed, May 06, 2020 at 09:39:55AM -0700, Jordan Hand wrote:
Good afternoon, I hope the week is going well for everyone.
> On 4/21/20 2:52 PM, Jarkko Sakkinen wrote:
> > Make the vDSO callable directly from C by preserving RBX and taking leaf
> > from RCX.
> Tested with the Open Enclave SDK
Add documentation for
-scheduler overview
-scheduler state transtion
-CFS overview
-scheduler data structs
Add rst for scheduler APIs and modify sched/core.c
to add kernel-doc comments.
Suggested-by: Lukas Bulwahn
Co-developed-by: Mostafa Chamanara
Signed-off-by: Mostafa Chamanara
Add documentation for introduction to
-context-switch
-x86 context-switch
-MIPS context switch
Suggested-by: Lukas Bulwahn
Co-developed-by: Mostafa Chamanara
Signed-off-by: Mostafa Chamanara
Co-developed-by: Oleg Tsymbal
Signed-off-by: Oleg Tsymbal
Signed-off-by: John Mathew
---
Analogously to the introduction of panic_on_warn, this patch
introduces a kernel option named panic_on_taint in order to
provide a simple and generic way to stop execution and catch
a coredump when the kernel gets tainted by any given taint flag.
This is useful for debugging sessions as it avoids
This patch series updates the scheduler documentation to add more topics
wrt to scheduler overview. New sections are added to provide a brief
overview of the kernel structs used by the scheduler, scheduler invocation
and context switch.
The previous version was reviewed at
Link:
Add new sections to enable addition of new documentation on
the scheduler. Existing documentation is moved under the related
new sections. The sections are
- overview
- sched-features
- arch-specific.rst
- sched-debugging.rst
Suggested-by: Lukas Bulwahn
Signed-off-by: John Mathew
---
On Tue, May 5, 2020 at 7:13 AM Thomas Gleixner wrote:
>
> Folks!
>
> This is the hopefully final version of the rework of the entry and
> exception code to ensure that instrumentation cannot touch the fragile
> parts of the hardware induced entry and exception code trainwreck. It
> further
On Thursday, May 7, 2020 5:38:11 AM CEST Chris Chiu wrote:
> On Wed, May 6, 2020 at 6:19 PM Rafael J. Wysocki wrote:
> >
> > On Wed, May 6, 2020 at 11:32 AM Rafael J. Wysocki wrote:
> > >
> > >
> > > Thanks for the report, the issue evidently is EC-related.
> > >
> > > > @@ -1024,7 +1024,7 @@
On Thu, May 07, 2020 at 07:42:25PM +0200, Paolo Bonzini wrote:
> On 07/05/20 18:38, Peter Xu wrote:
> > On Thu, May 07, 2020 at 06:21:18PM +0200, Paolo Bonzini wrote:
> >> On 07/05/20 18:18, Peter Xu wrote:
> if (vcpu->guest_debug & KVM_GUESTDBG_USE_HW_BP) {
> -
Hi Vincent,
On Thu, May 07, 2020 at 05:06:29PM +0200 Vincent Guittot wrote:
> Hi Phil,
>
> On Wed, 6 May 2020 at 20:05, Phil Auld wrote:
> >
> > Hi Vincent,
> >
> > Thanks for taking a look. More below...
> >
> > On Wed, May 06, 2020 at 06:36:45PM +0200 Vincent Guittot wrote:
> > > Hi Phil,
> >
On Thu, May 07, 2020 at 08:57:50AM -0400, Pavel Tatashin wrote:
> On Wed, May 6, 2020 at 5:15 PM Kees Cook wrote:
> >
> > Refactor device tree size parsing routines to be able to pass a non-zero
> > default value for providing a configurable default for the coming
> > "max_reason" field.
> >
> >
On Tue, May 5, 2020 at 7:14 AM Thomas Gleixner wrote:
>
> From: Peter Zijlstra
>
> A few exceptions (like #DB and #BP) can happen at any location in the code,
> this then means that tracers should treat events from these exceptions as
> NMI-like. The interrupted context could be holding locks
On Thu, May 07, 2020 at 04:14:24PM +, Luis Chamberlain wrote:
> __read_mostly can easily be misused by folks, its not meant for
> just read-only data. There are performance reasons for using it, but
> we also don't provide any guidance about its use. Provide a bit more
> guidance over its use.
On 2020-04-22 17:37, Bjorn Andersson wrote:
Remove the QCOM_GLINK_SSR option from the arm64 defconfig, as the
module
is assimilated by QCOM_GLINK - which is selected by other means.
Signed-off-by: Bjorn Andersson
---
Acked-by: Rishabh Bhatnagar
arch/arm64/configs/defconfig | 1 -
1 file
On 07/05/20 09:20AM, Daniel Walker wrote:
> Some chips have 4B opcodes, but there is no way to know if they have
> them. This device tree option allows platform owners to force enable 4b
> opcodes when they know their chips support it even when it can be
> automatically identified.
Do you mean
On Tue, May 5, 2020 at 7:13 AM Thomas Gleixner wrote:
>
> From: Peter Zijlstra
>
> Convert #MC over to using task_work_add(); it will run the same code
> slightly later, on the return to user path of the same exception.
I think this patch is correct, but I think it's only one small and not
that
On Wed, May 06, 2020 at 11:09:12PM -0500, Gustavo A. R. Silva wrote:
> As mentioned above: "Flexible array members have incomplete type, and
> so the sizeof operator may not be applied. As a quirk of the original
> implementation of zero-length arrays, sizeof evaluates to zero."[1] So,
> the
On 2020-04-22 17:37, Bjorn Andersson wrote:
In all but the very special case of a system with _only_ glink_rpm,
GLINK is dependent on glink_ssr, so move it to rpmsg and combine it
with
qcom_glink_native in the new qcom_glink kernel module.
Signed-off-by: Bjorn Andersson
---
Acked-by:
On Thu, May 7, 2020 at 6:41 AM Randy Dunlap wrote:
>
> Hi--
>
> On 5/6/20 7:39 AM, john mathew wrote:
> > From: John Mathew
> >
> > Add documentation for
> > -scheduler overview
> > -scheduler state transtion
> > -CFS overview
> > -scheduler data structs
> >
> > Add rst for scheduler APIs
On 2020-04-22 17:37, Bjorn Andersson wrote:
Rather than carrying a special purpose blocking notifier for glink_ssr
in remoteproc's qcom_common.c, move it into glink_ssr so allow wider
reuse of the common one.
The rpmsg glink header file is used in preparation for the next patch.
Signed-off-by:
On 5/7/20 9:30 AM, Randy Dunlap wrote:
> On 5/6/20 5:42 PM, Anthony Yznaga wrote:
>> Improve performance by multithreading the work to preserve and restore
>> shmem pages.
>>
>> Add 'pkram_max_threads=' kernel option to specify the maximum number
>> of threads to use to preserve or restore the
On 2020-04-22 17:37, Bjorn Andersson wrote:
Pass ssr_name to glink subdevice in preparation for tying glink_ssr to
the glink subdevice, rather than having its own "ssr subdevice".
Signed-off-by: Bjorn Andersson
---
Acked-by: Rishabh Bhatnagar
drivers/remoteproc/qcom_common.c| 9
On Fri, 1 May 2020 00:06:11 +0200, Ansuel Smith wrote:
> Add missing ext reset used by ipq8064 SoC in PCIe qcom driver.
>
> Fixes: 82a823833f4e PCI: qcom: Add Qualcomm PCIe controller driver
> Signed-off-by: Sham Muthayyan
> Signed-off-by: Ansuel Smith
> Cc: sta...@vger.kernel.org # v4.5+
>
On Fri, 1 May 2020 00:06:10 +0200, Ansuel Smith wrote:
> From: Abhishek Sahu
>
> The deinit issues reset_control_assert for PCI twice and does not contain
> phy reset.
>
> Signed-off-by: Abhishek Sahu
> Signed-off-by: Ansuel Smith
> ---
> drivers/pci/controller/dwc/pcie-qcom.c | 18
On Thu, May 07, 2020 at 02:55:47PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the chrome-platform tree got a conflict in:
>
> drivers/platform/chrome/chromeos_pstore.c
>
> between commit:
>
> 7bddec15c574 ("pstore/ram: Introduce max_reason and convert
On Thu, 2020-05-07 at 13:30 -0400, Steven Rostedt wrote:
> On Thu, 7 May 2020 13:28:28 -0400
> Steven Rostedt wrote:
>
> > > It's perfectly safe to return 0/1 in a boolean function; that said seeing
> > > as this is the second attempt at "fixing" this I'm tempted to say we
> > > should
> > >
On Tue, May 5, 2020 at 7:13 AM Thomas Gleixner wrote:
>
> trace_hardirqs_on/off() is only partially safe vs. RCU idle. The tracer
> core itself is safe, but the resulting tracepoints can be utilized by
> e.g. BPF which is unsafe.
>
> Provide variants which do not contain the lockdep invocation so
On Thu, May 07, 2020 at 06:14:19PM +0100, Catalin Marinas wrote:
> On Wed, May 06, 2020 at 10:40:19AM -0700, Paul E. McKenney wrote:
> > On Wed, May 06, 2020 at 12:22:37PM -0400, Qian Cai wrote:
> > > == call_rcu() leaks ==
> > > Another issue that might be relevant is that it seems sometimes,
> >
On Fri, May 01, 2020 at 12:06:08AM +0200, Ansuel Smith wrote:
> Aux and Ref clk are missing in PCIe qcom driver.
> Add support in the driver to fix PCIe initialization in ipq806x.
>
> Fixes: 82a823833f4e PCI: qcom: Add Qualcomm PCIe controller driver
> Signed-off-by: Sham Muthayyan
>
Hi Pavel,
On Thu, May 7, 2020 at 6:44 PM Pavel Machek wrote:
>
> Hi!
>
>
> > R-Car/RZ-G2x SoC's, this also extends the epf framework to handle multiple
> > windows
> > supported by the controller for mapping PCI address locally.
> >
> > Note:
> > The cadence/rockchip/designware endpoint drivers
On Thu, May 07, 2020 at 04:14:24PM +, Luis Chamberlain wrote:
> __read_mostly can easily be misused by folks, its not meant for
> just read-only data. There are performance reasons for using it, but
> we also don't provide any guidance about its use. Provide a bit more
> guidance over its use.
* Philippe Schenker [200507 15:17]:
> On Thu, 2020-05-07 at 18:12 +0300, Grygorii Strashko wrote:
> > Since commit bcf3440c6dd7 ("net: phy: micrel: add phy-mode support for
> > the
> > KSZ9031 PHY") the networking is broken on boards:
> > am437x-gp-evm
> > am437x-sk-evm
> > am437x-idk-evm
> >
On 07/05/20 18:30, Steven Rostedt wrote:
> On Thu, 7 May 2020 13:28:28 -0400
> Steven Rostedt wrote:
>
>> > It's perfectly safe to return 0/1 in a boolean function; that said seeing
>> > as this is the second attempt at "fixing" this I'm tempted to say we should
>> > pick it up...
>> >
>>
>>
* Philippe Schenker [200507 08:43]:
> On Wed, 2020-05-06 at 22:11 +0300, Grygorii Strashko wrote:
> > Since commit bcf3440c6dd7 ("net: phy: micrel: add phy-mode support for
> > the
> > KSZ9031 PHY") the networking is broken on boards:
> > am571x-idk
> > am572x-idk
> > am574x-idk
> >
On 07.05.2020 20:01, Arnaldo Carvalho de Melo wrote:
> Em Thu, May 07, 2020 at 11:32:53AM +0300, Alexey Budankov escreveu:
>>
>> On 06.05.2020 23:21, Arnaldo Carvalho de Melo wrote:
>>> Em Wed, May 06, 2020 at 09:19:22PM +0300, Alexey Budankov escreveu:
Implement functions of
On Wed, May 06, 2020 at 05:41:47PM -0700, Anthony Yznaga wrote:
> Avoid regions of memory that contain preserved pages when computing
> slots used to select where to put the decompressed kernel.
This is changing the slot-walking code instead of updating
mem_avoid_overlap() -- that's where the
On Thu, May 07, 2020 at 06:29:44PM +0200 Jirka Hladky wrote:
> Hi Mel,
>
> we are not targeting just OMP applications. We see the performance
> degradation also for other workloads, like SPECjbb2005 and
> SPECjvm2008. Even worse, it also affects a higher number of threads.
> For example,
On Thu 07-05-20 10:00:07, Shakeel Butt wrote:
> On Thu, May 7, 2020 at 9:47 AM Michal Hocko wrote:
> >
> > On Thu 07-05-20 09:33:01, Shakeel Butt wrote:
> > [...]
> > > @@ -2600,8 +2596,23 @@ static int try_charge(struct mem_cgroup *memcg,
> > > gfp_t gfp_mask,
> > >
On Thu, May 07, 2020 at 01:14:29AM -0700, Ian Rogers wrote:
> Metric groups contain metrics. Metrics create groups of events to
> ideally be scheduled together. Often metrics refer to the same events,
> for example, a cache hit and cache miss rate. Using separate event
> groups means these metrics
* Tony Lindgren [200505 18:27]:
> * Geert Uytterhoeven [200505 08:08]:
> > Support for TI AM43x SoCs depends on ARCH_MULTI_V7, which selects
> > ARCH_MULTI_V6_V7.
> > As the latter selects MIGHT_HAVE_CACHE_L2X0, there is no need for
> > SOC_AM43XX to select MIGHT_HAVE_CACHE_L2X0.
> >
> >
Markus Elfring writes:
> …
>> +++ b/drivers/net/wireless/ath/wcn36xx/main.c
> …
>> @@ -1359,6 +1359,8 @@ static int wcn36xx_probe(struct platform_device *pdev)
>> out_unmap:
>> iounmap(wcn->ccu_base);
>> iounmap(wcn->dxe_base);
>> +out_channel:
>> +
Hi!
> +struct ec_input_response {
> + u8 reserved;
> + u8 msg_counter:2;
> + u8 count:2;
> + u8 type:4;
> + u8 data[3];
> +} __packed;
Bitfields, and relying on them being in the right place for communication with
hardware.
We don't usually do that, and there may be reasons
On Wed 2020-04-29 15:32:47, Javier Malave wrote:
> This patch set adds the Popcorn Distributed Thread Execution support
> to the kernel. It is based off of Linux 5.2 commit 72a20ce. We are
> looking for feedback on design and implementation from the community.
You may want to cc linux-api mailing
On Tue, May 5, 2020 at 7:13 AM Thomas Gleixner wrote:
>
> This is completely overengineered and definitely not an interface which
> should be made available to anything else than this particular MCE case.
Sorry for the overengineering. :)
--Andy
On Mon, May 4, 2020 at 4:05 AM Emanuele Giuseppe Esposito
wrote:
...
> Statsfs offers a generic and stable API, allowing any kind of
> directory/file organization and supporting multiple kind of aggregations
> (not only sum, but also average, max, min and count_zero) and data types
> (all
Hi!
> This patchset add regulator vibrator driver for MTK Soc. The driver
> controls vibrator through regulator's enable and disable.
We'd prefer not to have vibrators in led subsystem.
>
> Xing Zhang (3):
> dt-bindings: add regulator vibrator documentation
> arm64: mediatek: Add
On Tue 2020-04-21 17:36:18, Daniele Alessandrelli wrote:
> From: Daniele Alessandrelli
>
> Keem Bay bootloader sets up a temporary Isolated Memory Region (IMR) to
> protect itself during pre-Linux boot.
What kind of bootloader is the SoC using? Sounds like bootloader responsibility
to me...
Hi!
> > it uses its own memory and CPUs + its virtio-vsock emulated device for
> > communication with the primary VM.
> >
> > The memory and CPUs are carved out of the primary VM, they are dedicated
> > for the enclave. The Nitro hypervisor running on the host ensures memory
> > and CPU
Hi!
> R-Car/RZ-G2x SoC's, this also extends the epf framework to handle multiple
> windows
> supported by the controller for mapping PCI address locally.
>
> Note:
> The cadence/rockchip/designware endpoint drivers are build tested only.
>
> Changes for v9 (Re-spun this series as there were
On 07/05/20 18:38, Peter Xu wrote:
> On Thu, May 07, 2020 at 06:21:18PM +0200, Paolo Bonzini wrote:
>> On 07/05/20 18:18, Peter Xu wrote:
if (vcpu->guest_debug & KVM_GUESTDBG_USE_HW_BP) {
- vcpu->run->debug.arch.dr6 = vcpu->arch.dr6;
+
From: Masami Hiramatsu
Fix a typo that resulted in an unnecessary double
initialization to addr.
Link:
http://lkml.kernel.org/r/158779374968.6082.2337484008464939919.stgit@devnote2
Cc: Tom Zanussi
Cc: Ingo Molnar
Cc: sta...@vger.kernel.org
Fixes: c7411a1a126f ("tracing/kprobe: Check whether
From: Yiwei Zhang
This change updates the improper comment for the 'size' attribute in the
tracepoint definition. Most gfx drivers pre-fault in physical pages
instead of making virtual allocations. So we drop the 'Virtual' keyword
here and leave this to the implementations.
Link:
From: Wei Yang
As the example below shows, DECLARE_EVENT_CLASS() is used instead of
DEFINE_EVENT_CLASS().
Link: http://lkml.kernel.org/r/20200428214959.11259-1-richard.weiy...@gmail.com
Signed-off-by: Wei Yang
Signed-off-by: Steven Rostedt (VMware)
---
From: Masami Hiramatsu
Reject the new event which has NULL location for kprobes.
For kprobes, user must specify at least the location.
Link:
http://lkml.kernel.org/r/158779376597.6082.1411212055469099461.stgit@devnote2
Cc: Tom Zanussi
Cc: Ingo Molnar
Cc: sta...@vger.kernel.org
Fixes:
From: Masami Hiramatsu
If there is a bootconfig data in the tail of initrd/initramfs,
initrd image sanity check caused an error while decompression
stage as follows.
[0.883882] Unpacking initramfs...
[2.696429] Initramfs unpacking failed: invalid magic at start of compressed
archive
Masami Hiramatsu (4):
bootconfig: Fix to remove bootconfig data from initrd while boot
tracing/kprobes: Fix a double initialization typo
tracing/boottime: Fix kprobe event API usage
tracing/kprobes: Reject new event if loc is NULL
Steven Rostedt (VMware) (2):
From: "Steven Rostedt (VMware)"
Running on a slower machine, it is possible that the preempt delay kernel
thread may still be executing if the module was immediately removed after
added, and this can cause the kernel to crash as the kernel thread might be
executing after its code has been
From: Zou Wei
Fix the following sparse warning:
kernel/trace/trace.c:950:6: warning: symbol 'tracing_snapshot_instance_cond'
was not declared. Should it be static?
Link:
http://lkml.kernel.org/r/1587614905-48692-1-git-send-email-zou_...@huawei.com
Reported-by: Hulk Robot
Signed-off-by: Zou
From: Masami Hiramatsu
Fix boottime kprobe events to use API correctly for
multiple events.
For example, when we set a multiprobe kprobe events in
bootconfig like below,
ftrace.event.kprobes.myevent {
probes = "vfs_read $arg1 $arg2", "vfs_write $arg1 $arg2"
}
This cause an error;
From: "Steven Rostedt (VMware)"
x86_64 lazily maps in the vmalloc pages, and the way this works with per_cpu
areas can be complex, to say the least. Mappings may happen at boot up, and
if nothing synchronizes the page tables, those page mappings may not be
synced till they are used. This causes
…
> +++ b/drivers/net/wireless/ath/wcn36xx/main.c
…
> @@ -1359,6 +1359,8 @@ static int wcn36xx_probe(struct platform_device *pdev)
> out_unmap:
> iounmap(wcn->ccu_base);
> iounmap(wcn->dxe_base);
> +out_channel:
> + rpmsg_destroy_ept(wcn->smd_channel);
> out_wq:
>
On Thu, May 07, 2020 at 06:10:23PM +0200, Peter Zijlstra wrote:
> Thomas would very much like objtool to understand and generate correct
> ORC unwind information for the minimal stack swizzle sequence:
>
> mov %rsp, (%[ts])
> mov %[ts], %rsp
> ...
> pop %rsp
>
> This
Hi Maxime,
Am 24.04.20 um 17:35 schrieb Maxime Ripard:
> Now that the driver is ready for it, let's bring in the HDMI controllers
> variants for the BCM2711.
>
> Signed-off-by: Maxime Ripard
> ---
> drivers/gpu/drm/vc4/vc4_hdmi.c | 276 +-
> drivers/gpu/drm/vc4/vc4_hdmi.h
On Tue, May 5, 2020 at 7:13 AM Thomas Gleixner wrote:
>
> Make sure task_work runs before any kind of userspace -- very much
> including signals -- is invoked.
I certainly approve of the change, but anything that fundamentally
relies on this makes me uneasy. I'll keep an eye out for potential
The pull request you sent on Thu, 7 May 2020 18:16:28 +0200:
> git://git.infradead.org/users/hch/configfs.git tags/configfs-for-5.7
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/de268ccb42d6ec5475ec5a5e60723b665d6e0af2
Thank you!
--
Deet-doot-dot, I am a bot.
The pull request you sent on Thu, 7 May 2020 07:53:32 -0400:
> https://git.kernel.org/pub/scm/virt/kvm/kvm.git tags/for-linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/8c16ec94dc767a4d8c48149d646e8c835512cf8f
Thank you!
--
Deet-doot-dot, I am a bot.
The pull request you sent on Thu, 7 May 2020 17:31:10 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux tags/arm64-fixes
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/6e7f2eacf09811d092c1b41263108ac7fe0d089d
Thank you!
--
Deet-doot-dot, I am a
v7 - Cleanup ehci-brcm.c as requested by Greg Kroah-Hartman.
- Split out Makefile re-order change into a separate commit.
v6 - Remove "contains:" from compatible section of
brcm,bcm7445-ehci.yaml as requested by Rob Herring.
v5 - Use devm_platform_get_and_ioremap_resource() in
> >
> > Please see full log here:
> > ftp://vps418301.ovh.net/incoming/include_mm_h_output.txt
> >
> > I can fix it by adding the kvfree() declaration to the rcutiny.h also:
> > extern void kvfree(const void *addr);
> >
> > what seems wired to me? Also it can be fixed if i move it to the
Add DT bindings for Broadcom STB USB EHCI and XHCI drivers.
NOTE: The OHCI driver is not included because it uses the generic
platform driver.
Signed-off-by: Al Cooper
Reviewed-by: Rob Herring
---
.../bindings/usb/brcm,bcm7445-ehci.yaml | 59 +++
701 - 800 of 1840 matches
Mail list logo
