From: Vignesh Viswanathan
Currently the SSR subdevice notifies the client driver on crash of the
rproc from the recovery workqueue using the BEFORE_SHUTDOWN event.
However, the client driver might be interested to know that the device
has crashed immediately to pause any further transactions with
On Mon, Aug 19, 2024 at 2:56 PM Ira Weiny wrote:
>
> Philip Chen wrote:
> > If a pmem device is in a bad status, the driver side could wait for
> > host ack forever in virtio_pmem_flush(), causing the system to hang.
>
> I assume this was supposed to be v2 and you resent this as a proper v2
> with
Huacai,
On 2024/8/19 下午9:34, Huacai Chen wrote:
Hi, Bibo,
On Mon, Aug 12, 2024 at 11:02 AM Bibo Mao wrote:
Interrupts can be routed to maximal four virtual CPUs with one HW
EIOINTC interrupt controller model, since interrupt routing is encoded with
CPU bitmap and EIOINTC node combined method
Huacai,
Thanks for reviewing my patch.
I reply inline.
On 2024/8/19 下午9:32, Huacai Chen wrote:
Hi, Bibo,
On Mon, Aug 12, 2024 at 11:02 AM Bibo Mao wrote:
Export kernel paravirt features to user space, so that VMM can control
the single paravirt feature. By default paravirt features will be
Matthew Maurer writes:
> On Fri, Aug 16, 2024 at 4:04 PM Michael Ellerman wrote:
>> Matthew Maurer writes:
>> > Adds a new format for MODVERSIONS which stores each field in a separate
>> > ELF section. This initially adds support for variable length names, but
>> > could later be used to add add
On Mon, 19 Aug 2024 12:02:44 -0400
Steven Rostedt wrote:
> On Tue, 20 Aug 2024 00:56:49 +0900
> Masami Hiramatsu (Google) wrote:
> >
> > >
> > > We may need to add "noinline" or something to make sure those functions
> > > don't get inlined for LTO.
> >
> > Yeah, we need such option at leas
From: Masami Hiramatsu (Google)
With ftrace boot-time selftest, kmemleak reported some memory leaks in
the new test case for function graph storage for multiple tracers.
unreferenced object 0x888005060080 (size 32):
comm "swapper/0", pid 1, jiffies 4294676440
hex dump (first 32 bytes):
On Fri, Aug 16, 2024 at 4:04 PM Michael Ellerman wrote:
>
> Matthew Maurer writes:
> > Adds a new format for MODVERSIONS which stores each field in a separate
> > ELF section. This initially adds support for variable length names, but
> > could later be used to add additional fields to MODVERSION
Hi,
On Mon, Aug 19, 2024 at 12:30 AM Sibi Sankar wrote:
>
> Any write access to the IMEM region when the Q6 is setting up XPU
> protection on it will result in a XPU violation. Fix this by ensuring
> IMEM writes related to the MBA post-mortem logs happen before the Q6
> is brought out of reset.
>
On Mon, 19 Aug 2024 12:02:44 -0400
Steven Rostedt wrote:
> On Tue, 20 Aug 2024 00:56:49 +0900
> Masami Hiramatsu (Google) wrote:
> >
> > >
> > > We may need to add "noinline" or something to make sure those functions
> > > don't get inlined for LTO.
> >
> > Yeah, we need such option at leas
On 8/19/2024 7:09 AM, Yue Haibing wrote:
There is no caller and implementation in tree.
Signed-off-by: Yue Haibing
---
drivers/vdpa/ifcvf/ifcvf_base.h | 3 ---
drivers/vdpa/pds/cmds.h | 1 -
2 files changed, 4 deletions(-)
diff --git a/drivers/vdpa/ifcvf/ifcvf_base.h b/drivers/vdp
On Thu, 27 Jun 2024 11:23:35 -0400
Mathieu Desnoyers wrote:
> To cover scenarios where the scope of the guard differs from the scope
> of its activation, introduce DEFINE_INACTIVE_GUARD() and activate_guard().
>
> Here is an example use for a conditionally activated guard variable:
>
> void fun
Hello:
This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko :
On Mon, 19 Aug 2024 18:28:03 +0200 you wrote:
> From: Matteo Croce
>
> Enable some BPF kfuncs and the helper bpf_current_task_under_cgroup()
> for program types BPF_CGROUP_*.
> These will be used by systemd-network
Hi Johannes,
I finally got around to testing your patches.
I did the following:
# cat /sys/kernel/tracing/events/*/*/format
and hit this:
BUG: unable to handle page fault for address: 8e6333d0
#PF: supervisor read access in kernel mode
#PF: error_code(0x) - not-present page
PGD
On 19.08.24 21:38, Sami Tolvanen wrote:
> Hi Benno,
>
> On Sat, Aug 17, 2024 at 01:19:55PM +, Benno Lossin wrote:
>>
>> For this use-case (the one in the patch), I don't really know if we want
>> to copy the approach from C. Do we even support exporting kABI from
>> Rust? If yes, then we I wou
On Mon, Jul 22, 2024 at 11:06:20AM +0200, Petr Pavlu wrote:
> Allow enabling the in-kernel module decompression support separately,
> without requiring to enable also the automatic compression during
> 'make modules_install'.
Applied and pushed, thanks!
Luis
On Wed, Jul 24, 2024 at 05:04:25PM +, Sami Tolvanen wrote:
> Hi Luis,
>
> On Thu, Jul 18, 2024 at 5:15 PM Luis Chamberlain wrote:
> >
> > On Tue, Jul 09, 2024 at 12:08:16PM +0200, Miguel Ojeda wrote:
> > > On Mon, Jul 8, 2024 at 11:42 PM Luis Chamberlain
> > > wrote:
> > > >
> > > > The rat
Philip Chen wrote:
> If a pmem device is in a bad status, the driver side could wait for
> host ack forever in virtio_pmem_flush(), causing the system to hang.
I assume this was supposed to be v2 and you resent this as a proper v2
with a change list from v1?
Ira
>
> Signed-off-by: Philip Chen
On 19.08.24 20:25, Greg Kroah-Hartman wrote:
> On Sat, Aug 17, 2024 at 01:19:55PM +, Benno Lossin wrote:
>> On 17.08.24 09:41, Greg Kroah-Hartman wrote:
>>> On Fri, Aug 16, 2024 at 08:50:53AM -0700, Sami Tolvanen wrote:
On Fri, Aug 16, 2024 at 12:20 AM Greg Kroah-Hartman
wrote:
>
On Mon, Aug 19, 2024 at 6:41 AM Oleg Nesterov wrote:
>
> On 08/12, Andrii Nakryiko wrote:
> >
> > Avoid taking refcount on uprobe in prepare_uretprobe(), instead take
> > uretprobe-specific SRCU lock and keep it active as kernel transfers
> > control back to user space.
> ...
> > include/linux/up
On Wed, Jul 24, 2024 at 05:04:25PM GMT, Sami Tolvanen wrote:
> Hi Luis,
>
> On Thu, Jul 18, 2024 at 5:15 PM Luis Chamberlain wrote:
> >
> > On Tue, Jul 09, 2024 at 12:08:16PM +0200, Miguel Ojeda wrote:
> > > On Mon, Jul 8, 2024 at 11:42 PM Luis Chamberlain
> > > wrote:
> > > >
> > > > The ratio
Hi Benno,
On Sat, Aug 17, 2024 at 01:19:55PM +, Benno Lossin wrote:
>
> For this use-case (the one in the patch), I don't really know if we want
> to copy the approach from C. Do we even support exporting kABI from
> Rust? If yes, then we I would recommend we tag it in the source code
> inste
On Sat, Aug 17, 2024 at 01:19:55PM +, Benno Lossin wrote:
> On 17.08.24 09:41, Greg Kroah-Hartman wrote:
> > On Fri, Aug 16, 2024 at 08:50:53AM -0700, Sami Tolvanen wrote:
> >> On Fri, Aug 16, 2024 at 12:20 AM Greg Kroah-Hartman
> >> wrote:
> >>> On Thu, Aug 15, 2024 at 05:39:20PM +, Sami
AMD-Xilinx zynqmp platform contains on-chip sram memory (OCM).
R5 cores can access OCM and access is faster than DDR memory but slower
than TCM memories available. Sram region can have optional multiple
power-domains. Platform management firmware is responsible
to operate these power-domains.
Sign
From: Jan Kiszka
When k3_r5_cluster_rproc_exit is run, core 1 is shutdown and removed
first. When core 0 should then be stopped before its removal, it will
find core1->rproc as NULL already and crashes. Happens on rmmod e.g.
Fixes: 3c8a9066d584 ("remoteproc: k3-r5: Do not allow core1 to power up
On Fri, Aug 09, 2024 at 11:31:32AM +0530, Beleswar Padhi wrote:
> From: Udit Kumar
>
> Few times, core1 was scheduled to boot first before core0, which leads
> to error:
>
> 'k3_r5_rproc_start: can not start core 1 before core 0'.
>
> This was happening due to some scheduling between prepare an
From: Matteo Croce
The helper bpf_current_task_under_cgroup() currently is only allowed for
tracing programs, allow its usage also in the BPF_CGROUP_* program types.
Move the code from kernel/trace/bpf_trace.c to kernel/bpf/helpers.c,
so it compiles also without CONFIG_BPF_EVENTS.
This will be
From: Matteo Croce
These kfuncs are enabled even in BPF_PROG_TYPE_TRACING, so they
should be safe also in BPF_CGROUP_* programs.
Since all BPF_CGROUP_* programs share the same hook,
call register_btf_kfunc_id_set() only once.
In enum btf_kfunc_hook, rename BTF_KFUNC_HOOK_CGROUP_SKB to a more
gen
From: Matteo Croce
Enable some BPF kfuncs and the helper bpf_current_task_under_cgroup()
for program types BPF_CGROUP_*.
These will be used by systemd-networkd:
https://github.com/systemd/systemd/pull/32212
v5->v6:
Called register_btf_kfunc_id_set() only once
Fixed build error with !CONFIG_CGROU
On Tue, 20 Aug 2024 00:56:49 +0900
Masami Hiramatsu (Google) wrote:
>
> >
> > We may need to add "noinline" or something to make sure those functions
> > don't get inlined for LTO.
>
> Yeah, we need such option at least for function call test.
Could you add the noinline, and if it fixes the
On Mon, 19 Aug 2024 11:29:02 -0400
Steven Rostedt wrote:
> On Mon, 19 Aug 2024 17:11:52 +0900
> Masami Hiramatsu (Google) wrote:
>
> > CONFIG_LTO=y
> > CONFIG_LTO_CLANG=y
>
> Hi Masami,
>
> Does it still fail if you disable the above?
No, I found that caused these failure.
> I wonder if tha
On 8/19/24 10:39 AM, Krzysztof Kozlowski wrote:
On 19/08/2024 17:32, Mathieu Poirier wrote:
Please remove.
Forget this comment since it would cause an error in __rproc_detach().
Other than the above I'm good with this driver. That said I can't move forward
without a nod from the DT crew. I
On 19/08/2024 17:32, Mathieu Poirier wrote:
Please remove.
>>> Forget this comment since it would cause an error in __rproc_detach().
>>>
Other than the above I'm good with this driver. That said I can't move
forward
without a nod from the DT crew. I also noticed a fair am
Hey Vignesh.
On Mon, Aug 19, 2024 at 02:02:31PM +0530, Vignesh Raghavendra wrote:
> [...]
>
> Hi Mathieu
>
> On 16/08/24 20:06, Mathieu Poirier wrote:
> >>> +/*
> >>> + * Attach to a running M4 remote processor (IPC-only mode)
> >>> + *
> >>> + * The remote processor is already booted, so there
On Mon, 19 Aug 2024 17:11:52 +0900
Masami Hiramatsu (Google) wrote:
> CONFIG_LTO=y
> CONFIG_LTO_CLANG=y
Hi Masami,
Does it still fail if you disable the above?
I wonder if that causes functions to not be part of the available filter
functions that the ftrace filter test is using :-/
We may ne
From: Jan Kiszka
By simply bailing out, the driver was violating its rule and internal
assumptions that either both or no rproc should be initialized. E.g.,
this could cause the first core to be available but not the second one,
leading to crashes on its shutdown later on while trying to derefere
On 8/16/24 1:17 PM, Michael S. Tsirkin wrote:
> On Fri, Aug 16, 2024 at 11:10:32AM -0700, Sean Christopherson wrote:
>> On Fri, Aug 16, 2024, syzbot wrote:
On Wed, May 29, 2024, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit:9b62e02e6336
There is no caller and implementation in tree.
Signed-off-by: Yue Haibing
---
drivers/vdpa/ifcvf/ifcvf_base.h | 3 ---
drivers/vdpa/pds/cmds.h | 1 -
2 files changed, 4 deletions(-)
diff --git a/drivers/vdpa/ifcvf/ifcvf_base.h b/drivers/vdpa/ifcvf/ifcvf_base.h
index 0f347717021a..aa36de
On 08/12, Andrii Nakryiko wrote:
>
> Avoid taking refcount on uprobe in prepare_uretprobe(), instead take
> uretprobe-specific SRCU lock and keep it active as kernel transfers
> control back to user space.
...
> include/linux/uprobes.h | 49 ++-
> kernel/events/uprobes.c | 294 +++
From: Andreas Hindborg
This patch includes changes required for Rust kernel modules to utilize
module parameters. This code implements read only support for integer
types without `sysfs` support.
This code is a reduced and updated version of code by Adam available in the
original `rust` branch [
Hi, Bibo,
On Mon, Aug 12, 2024 at 11:02 AM Bibo Mao wrote:
>
> Interrupts can be routed to maximal four virtual CPUs with one HW
> EIOINTC interrupt controller model, since interrupt routing is encoded with
> CPU bitmap and EIOINTC node combined method. Here add the EIOINTC virt
> extension suppo
Hi, Bibo,
On Mon, Aug 12, 2024 at 11:02 AM Bibo Mao wrote:
>
> Export kernel paravirt features to user space, so that VMM can control
> the single paravirt feature. By default paravirt features will be the same
> with kvm supported features if VMM does not set it.
>
> Also a new feature KVM_FEATU
On Sun, Aug 18, 2024 at 10:21:01PM +0200, Luca Weiss wrote:
> Some FSA4480-compatible chips like the OCP96011 used on Fairphone 5
> return 0x00 from the CHIP_ID register. Handle that gracefully and only
> fail probe when the I2C read has failed.
>
> With this the dev_dbg will print 0 but otherwise
Add a new UAPI to support setting the vhost device to
use kthread mode. The user space application needs to use
VHOST_SET_USE_KTHREAD to set the mode. This setting must
be set before VHOST_SET_OWNER is set.
Signed-off-by: Cindy Lu
---
drivers/vhost/vhost.c | 11 ++-
include/uapi/lin
Add back the previously removed cgroup function to support the kthread
The biggest change for this part is in vhost_attach_cgroups() and
vhost_worker_cgroups_kthread(). This is because of the change in
struct dev->worker_xa.
Signed-off-by: Cindy Lu
---
drivers/vhost/vhost.c | 52
Split the function vhost_worker_create to support both task and kthread
Added back the previous old function vhost_worker_create and rename it to
vhost_worker_create_khtread to support the khtread.
The new vhost_worker_queue will be selected which to use based on the
value of the parameter
Add back the previously removed vhost_worker function to support the kthread
and rename it vhost_run_work_kthread_list.
Signed-off-by: Cindy Lu
---
drivers/vhost/vhost.c | 38 ++
1 file changed, 38 insertions(+)
diff --git a/drivers/vhost/vhost.c b/drivers/vh
Added back the previously removed function vhost_workers_free() and
renamed it to vhost_workers_free_khtread(). The new vhost_workers_free()
will select the different mode based on the value of the parameter.
Signed-off-by: Cindy Lu
---
drivers/vhost/vhost.c | 52
Added back the previously removed function vhost_worker_queue() and
renamed it to vhost_worker_queue_khtread(). The new vhost_worker_queue()
will select the different mode based on the value of the parameter.
Signed-off-by: Cindy Lu
---
drivers/vhost/vhost.c | 30 --
Add a new module parameter to enable kthread while loading modules.
This parameter will identify if the vhost will use kthread or a task.
The default value will be true.
Signed-off-by: Cindy Lu
---
drivers/vhost/vhost.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/vhost/vhost.c
In commit 6e890c5d5021 ("vhost: use vhost_tasks for worker threads"),
vhost removed the support for the kthread API. However, there are
still situations where there is a request to use kthread.
In this RFC, the support of kthread is added back. Additionally,
a module_param is added to identify whic
On 18/08/2024 22:21, Luca Weiss wrote:
Some FSA4480-compatible chips like the OCP96011 used on Fairphone 5
return 0x00 from the CHIP_ID register. Handle that gracefully and only
fail probe when the I2C read has failed.
With this the dev_dbg will print 0 but otherwise continue working.
[0
Am 02.08.24 um 17:21 schrieb Andrew Davis:
Building the TSP structure is common for users of the TI-SCI processor
control interface. Factor out this function and put it with the rest
of the TI-SCI processor control functions.
Signed-off-by: Andrew Davis
Tested-by: Wadim Egorov
---
driv
Am 02.08.24 um 17:21 schrieb Andrew Davis:
Hello all,
This is the continuation of the M4F RProc support series from here[0].
I'm helping out with the upstream task for Hari and so versions (v8+)
is a little different than the previous(v7-) postings[0]. Most notable
change I've introduced bein
Am 02.08.24 um 17:21 schrieb Andrew Davis:
From: Hari Nagalla
The AM62x SoCs of the TI K3 family have a Cortex M4F core in the MCU
domain. This core can be used by non safety applications as a remote
processor. When used as a remote processor with virtio/rpmessage IPC,
two carveout reserved
Am 02.08.24 um 17:21 schrieb Andrew Davis:
From: Martyn Welch
The AM62x and AM64x SoCs of the TI K3 family has a Cortex M4F core in
the MCU domain. This core is typically used for safety applications in a
stand alone mode. However, some application (non safety related) may
want to use the M4
[...]
Hi Mathieu
On 16/08/24 20:06, Mathieu Poirier wrote:
>>> +/*
>>> + * Attach to a running M4 remote processor (IPC-only mode)
>>> + *
>>> + * The remote processor is already booted, so there is no need to issue any
>>> + * TI-SCI commands to boot the M4 core. This callback is used only in
>
Any write access to the IMEM region when the Q6 is setting up XPU
protection on it will result in a XPU violation. Fix this by ensuring
IMEM writes related to the MBA post-mortem logs happen before the Q6
is brought out of reset.
Fixes: 318130cc9362 ("remoteproc: qcom_q6v5_mss: Add MBA log extract
58 matches
Mail list logo
