The vhost now uses vhost_task and workers as a child of the owner thread.
While this aligns with containerization principles,it confuses some legacy
userspace app, Therefore, we are reintroducing kthread API support.
Introduce a new parameter to enable users to choose between
kthread and task mode
Add a new UAPI to enable setting the vhost device to task mode.
The userspace application can use VHOST_SET_INHERIT_FROM_OWNER
to configure the mode if necessary.
This setting must be applied before VHOST_SET_OWNER, as the worker
will be created in the VHOST_SET_OWNER function
Signed-off-by: Cindy
The function vhost_worker_queue() uses vhost_task_fn and
selects the different mode based on the value of inherit_owner.
Signed-off-by: Cindy Lu
---
drivers/vhost/vhost.c | 7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/drivers/vhost/vhost.c b/drivers/vhost/vhost.c
index
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.
The old function was remove in
commit 6e890c5d5021 ("vhost: use vhost_tas
Add the previously removed function vhost_worker() back
to support the kthread and rename it to vhost_run_work_kthread_list.
The old function vhost_worker was change to support task in
commit 6e890c5d5021 ("vhost: use vhost_tasks for worker threads")
change to xarray in
commit 1cdaafa1b8b4 ("vhost
Hi Frederic and Thorston,
(CC-ing the laptop's owner so that she might help with further
testing...)
在 2024-10-23 18:22，Linux regression tracking (Thorsten Leemhuis) 写道：
On 23.10.24 12:09, Frederic Weisbecker wrote:
Le Wed, Oct 23, 2024 at 10:27:18AM +0200, Linux regression tracking
(Thorste
From: zhouyuhang
The libcap commit aca076443591 ("Make cap_t operations thread safe.")
added a __u8 mutex at the beginning of the struct _cap_struct, it changes
the offset of the members in the structure that breaks the assumption
made in the "struct libcap" definition in clone3_cap_checkpoint_re
On Wed, Oct 09, 2024, Sean Christopherson wrote:
> On Fri, 04 Oct 2024 18:01:53 -0400, Maxim Levitsky wrote:
> > When memslot_perf_test is run nested, first iteration of
> > test_memslot_rw_loop
> > testcase, sometimes takes more than 2 seconds due to build of shadow page
> > tables.
> >
> > Fol
On Thu, Oct 31, 2024, Sean Christopherson wrote:
> On Thu, 24 Oct 2024 10:59:53 +0100, Patrick Roy wrote:
> > The loop in test_create_guest_memfd_invalid that is supposed to test
> > that nothing is accepted as a valid flag to KVM_CREATE_GUEST_MEMFD was
> > initializing `flag` as 0 instead of BIT(0
igs
> enabled so not sure the offset is still valid.
>
> WARN_ON(buf_info->used);
> buf_info->pre_mapped = info->pre_mapped;
>
> This looks like the null pointer would happen if qrtr tried to send
> before mhi_channel_prepare() is called.
I didn't look clo
On 11/4/2024 5:47 PM, Sean Christopherson wrote:
> On Mon, Nov 04, 2024, Pratik R. Sampat wrote:
>>
>>
>> On 10/31/2024 11:27 AM, Sean Christopherson wrote:
>>> On Thu, Oct 31, 2024, Pratik R. Sampat wrote:
Hi Sean,
On 10/30/2024 12:57 PM, Sean Christopherson wrote:
> On Wed,
On 11/04, Joe Damato wrote:
> Add an epoll busy poll test using netdevsim.
>
> This test is comprised of:
> - busy_poller (via busy_poller.c)
> - busy_poll_test.sh which loads netdevsim, sets up network namespaces,
> and runs busy_poller to receive data and socat to send data.
>
> The sel
base: 9852d85ec9d492ebef56dc5f229416c925758edc
patch link:
https://lore.kernel.org/r/20241104-pxa1908-lkml-v13-10-e050609b8d6c%40skole.hr
patch subject: [PATCH RESEND v13 10/12] arm64: Kconfig.platforms: Add config
for Marvell PXA1908 platform
config: arm64-kismet-CONFIG_I2C_GPIO
On 11/04, Joe Damato wrote:
> On Mon, Nov 04, 2024 at 10:14:30AM -0800, Stanislav Fomichev wrote:
> > Only RX side for now and small message to test the setup.
> > In the future, we can extend it to TX side and to testing
> > both sides with a couple of megs of data.
> >
> > make \
> > -C to
On 11/04, Jakub Kicinski wrote:
> On Mon, 4 Nov 2024 10:14:24 -0800 Stanislav Fomichev wrote:
> > -static int configure_flow_steering(void)
> > +static int configure_flow_steering(struct sockaddr_in6 *server_sin)
> > {
> > - return run_command("sudo ethtool -N %s flow-type tcp4 %s %s dst-ip %s
On 11/04, Joe Damato wrote:
> On Mon, Nov 04, 2024 at 10:14:28AM -0800, Stanislav Fomichev wrote:
> > This will be used as a 'probe' mode in the selftest to check whether
> > the device supports the devmem or not. Use hard-coded queue layout
> > (two last queues) and prevent user from passing custo
On 11/04, Joe Damato wrote:
> On Mon, Nov 04, 2024 at 10:14:21AM -0800, Stanislav Fomichev wrote:
> > There is a bunch of places where error() calls look out of place.
> > Use the same error(1, errno, ...) pattern everywhere.
> >
> > Reviewed-by: Mina Almasry
> > Signed-off-by: Stanislav Fomichev
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski :
On Sat, 02 Nov 2024 16:52:17 -0500 you wrote:
> From: David Woodhouse
>
> The VMCLOCK device gives support for accurate timekeeping even across
> live migration, unlike the KVM PTP clock. To help ensure that users c
On Sat, 02 Nov 2024 16:52:17 -0500 David Woodhouse wrote:
> From: David Woodhouse
>
> The VMCLOCK device gives support for accurate timekeeping even across
> live migration, unlike the KVM PTP clock. To help ensure that users can
> always use ptp_vmclock where it's available in preference to ptp
On Mon, 4 Nov 2024 10:14:24 -0800 Stanislav Fomichev wrote:
> -static int configure_flow_steering(void)
> +static int configure_flow_steering(struct sockaddr_in6 *server_sin)
> {
> - return run_command("sudo ethtool -N %s flow-type tcp4 %s %s dst-ip %s
> %s %s dst-port %s queue %d >&2",
> +
On Mon, 4 Nov 2024 16:15:10 -0800 Joe Damato wrote:
> > +with bkg(listen_cmd) as nc:
> > +wait_port_listen(port)
> > +cmd(f"echo -e \"hello\\nworld\"| nc {cfg.v6} {port}",
> > host=cfg.remote, shell=True)
>
> FWIW, in the v3 of the series I submit, Jakub asked me to replace
On 11/4/24 4:07 PM, Shuah Khan wrote:
> On 11/4/24 16:14, Reinette Chatre wrote:
>>
>>
>> On 11/4/24 2:28 PM, Shuah Khan wrote:
>>> On 11/4/24 15:16, Reinette Chatre wrote:
Hi Shuah,
On 10/24/24 3:36 PM, Shuah Khan wrote:
> On 10/24/24 15:18, Reinette Chatre wrote:
>
>
On Tue, Nov 05, 2024 at 12:27:42AM +0100, Frederic Weisbecker wrote:
> Le Tue, Oct 15, 2024 at 09:11:05AM -0700, Paul E. McKenney a écrit :
> > This patch adds srcu_read_lock_lite() and srcu_read_unlock_lite(), which
> > dispense with the read-side smp_mb() but also are restricted to code
> > regio
On 11/1/2024 8:01 AM, Johan Hovold wrote:
Hi,
I just ran into a NULL-deref in a qrts/mhi path during boot of the
x1e80100 CRD for the second time.
First time was with a 6.11 kernel (but I never got around to reporting
it) and today it happened again with 6.12-rc5.
Both times I was using the
On Mon, Nov 04, 2024 at 10:14:30AM -0800, Stanislav Fomichev wrote:
> Only RX side for now and small message to test the setup.
> In the future, we can extend it to TX side and to testing
> both sides with a couple of megs of data.
>
> make \
> -C tools/testing/selftests \
> TARGETS=
On Mon, Nov 04, 2024 at 10:14:27AM -0800, Stanislav Fomichev wrote:
> Use single last queue of the device and probe it dynamically.
>
> Reviewed-by: Mina Almasry
> Signed-off-by: Stanislav Fomichev
> ---
> tools/testing/selftests/net/ncdevmem.c | 40 --
> 1 file changed,
On Mon, Nov 04, 2024 at 10:14:28AM -0800, Stanislav Fomichev wrote:
> This will be used as a 'probe' mode in the selftest to check whether
> the device supports the devmem or not. Use hard-coded queue layout
> (two last queues) and prevent user from passing custom -q and/or -t.
>
> Reviewed-by: Mi
On 11/4/24 16:14, Reinette Chatre wrote:
On 11/4/24 2:28 PM, Shuah Khan wrote:
On 11/4/24 15:16, Reinette Chatre wrote:
Hi Shuah,
On 10/24/24 3:36 PM, Shuah Khan wrote:
On 10/24/24 15:18, Reinette Chatre wrote:
Is this patch series ready to be applied?
It is now ready after receiving an
On Mon, Nov 04, 2024 at 10:14:26AM -0800, Stanislav Fomichev wrote:
> In the next patch the hard-coded queue numbers are gonna be removed.
> So introduce some initial support for ethtool YNL and use
> it to enable header split.
>
> Also, tcp-data-split requires latest ethtool which is unlikely
> t
On Mon, Nov 04, 2024 at 10:14:23AM -0800, Stanislav Fomichev wrote:
> To make it clear what's required and what's not. Also, some of the
> values don't seem like a good defaults; for example eth1.
>
> Move the invocation comment to the top, add missing -s to the client
> and cleanup the client inv
On Mon, Nov 04, 2024 at 10:14:25AM -0800, Stanislav Fomichev wrote:
> ntuple off/on might be not enough to do it on all NICs.
> Add a bunch of shell crap to explicitly remove the rules.
>
> Reviewed-by: Mina Almasry
> Signed-off-by: Stanislav Fomichev
> ---
> tools/testing/selftests/net/ncdevme
On Mon, Nov 04, 2024 at 10:14:24AM -0800, Stanislav Fomichev wrote:
> Use dualstack socket to support both v4 and v6. v4-mapped-v6 address
> can be used to do v4.
>
> Reviewed-by: Mina Almasry
> Signed-off-by: Stanislav Fomichev
> ---
> tools/testing/selftests/net/ncdevmem.c | 99 ++
On Mon, Nov 04, 2024 at 10:14:22AM -0800, Stanislav Fomichev wrote:
> Support 3-tuple filtering by making client_ip optional. When -c is
> not passed, don't specify src-ip/src-port in the filter.
>
> Reviewed-by: Mina Almasry
> Signed-off-by: Stanislav Fomichev
> ---
> tools/testing/selftests/n
On Mon, Nov 04, 2024, Pratik R. Sampat wrote:
>
>
> On 10/31/2024 11:27 AM, Sean Christopherson wrote:
> > On Thu, Oct 31, 2024, Pratik R. Sampat wrote:
> >> Hi Sean,
> >>
> >> On 10/30/2024 12:57 PM, Sean Christopherson wrote:
> >>> On Wed, Oct 30, 2024, Pratik R. Sampat wrote:
> On 10/30/2
On Mon, Nov 04, 2024 at 10:14:21AM -0800, Stanislav Fomichev wrote:
> There is a bunch of places where error() calls look out of place.
> Use the same error(1, errno, ...) pattern everywhere.
>
> Reviewed-by: Mina Almasry
> Signed-off-by: Stanislav Fomichev
> ---
> tools/testing/selftests/net/n
On Mon, Nov 04, 2024 at 10:14:20AM -0800, Stanislav Fomichev wrote:
> So we can plug the other ones in the future if needed.
>
> Reviewed-by: Mina Almasry
> Signed-off-by: Stanislav Fomichev
> ---
> tools/testing/selftests/net/ncdevmem.c | 203 +++--
> 1 file changed, 119 in
On Mon, Nov 04, 2024 at 10:14:19AM -0800, Stanislav Fomichev wrote:
> That should make it possible to do expected payload validation on
> the caller side.
>
> Reviewed-by: Mina Almasry
> Signed-off-by: Stanislav Fomichev
> ---
> tools/testing/selftests/net/ncdevmem.c | 61 +-
Le Tue, Oct 15, 2024 at 09:11:05AM -0700, Paul E. McKenney a écrit :
> This patch adds srcu_read_lock_lite() and srcu_read_unlock_lite(), which
> dispense with the read-side smp_mb() but also are restricted to code
> regions that RCU is watching. If a given srcu_struct structure uses
> srcu_read_l
On 11/4/24 2:28 PM, Shuah Khan wrote:
> On 11/4/24 15:16, Reinette Chatre wrote:
>> Hi Shuah,
>>
>> On 10/24/24 3:36 PM, Shuah Khan wrote:
>>> On 10/24/24 15:18, Reinette Chatre wrote:
>>>
>>> Is this patch series ready to be applied?
>>>
>>
>> It is now ready after receiving anticipated tags. C
On 11/4/24 15:16, Reinette Chatre wrote:
Hi Shuah,
On 10/24/24 3:36 PM, Shuah Khan wrote:
On 10/24/24 15:18, Reinette Chatre wrote:
Is this patch series ready to be applied?
It is now ready after receiving anticipated tags. Could you please consider it
for inclusion?
yes. I will apply t
On Tue, Nov 05, 2024 at 12:31:22AM +0900, Asahi Lina wrote:
>
>
> On 11/4/24 7:57 PM, Jan Kara wrote:
> > On Fri 01-11-24 21:22:31, Asahi Lina wrote:
> >> For virtio-dax, the file/FS blocksize is irrelevant. FUSE always uses
> >> large DAX blocks (2MiB), which will work with all host page sizes.
Hi Shuah,
On 10/24/24 3:36 PM, Shuah Khan wrote:
> On 10/24/24 15:18, Reinette Chatre wrote:
>
> Is this patch series ready to be applied?
>
It is now ready after receiving anticipated tags. Could you please consider it
for inclusion?
Thank you very much.
Reinette
Add an epoll busy poll test using netdevsim.
This test is comprised of:
- busy_poller (via busy_poller.c)
- busy_poll_test.sh which loads netdevsim, sets up network namespaces,
and runs busy_poller to receive data and socat to send data.
The selftest tests two different scenarios:
- bus
On 10/31/2024 11:27 AM, Sean Christopherson wrote:
> On Thu, Oct 31, 2024, Pratik R. Sampat wrote:
>> Hi Sean,
>>
>> On 10/30/2024 12:57 PM, Sean Christopherson wrote:
>>> On Wed, Oct 30, 2024, Pratik R. Sampat wrote:
On 10/30/2024 8:46 AM, Sean Christopherson wrote:
> +/* Minimum firmw
To make it clear what's required and what's not. Also, some of the
values don't seem like a good defaults; for example eth1.
Move the invocation comment to the top, add missing -s to the client
and cleanup the client invocation a bit to make more readable.
Reviewed-by: Mina Almasry
Signed-off-by
The goal of the series is to simplify and make it possible to use
ncdevmem in an automated way from the ksft python wrapper.
ncdevmem is slowly mutated into a state where it uses stdout
to print the payload and the python wrapper is added to
make sure the arrived payload matches the expected one.
Only RX side for now and small message to test the setup.
In the future, we can extend it to TX side and to testing
both sides with a couple of megs of data.
make \
-C tools/testing/selftests \
TARGETS="drivers/hw/net" \
install INSTALL_PATH=~/tmp/ksft
scp ~/tmp/ksft $
This is where all the tests that depend on the HW functionality live in
and this is where the automated test is gonna be added in the next
patch.
Reviewed-by: Mina Almasry
Signed-off-by: Stanislav Fomichev
---
tools/testing/selftests/drivers/net/hw/.gitignore | 1 +
tools/testing/selfte
This will be used as a 'probe' mode in the selftest to check whether
the device supports the devmem or not. Use hard-coded queue layout
(two last queues) and prevent user from passing custom -q and/or -t.
Reviewed-by: Mina Almasry
Signed-off-by: Stanislav Fomichev
---
tools/testing/selftests/ne
Use single last queue of the device and probe it dynamically.
Reviewed-by: Mina Almasry
Signed-off-by: Stanislav Fomichev
---
tools/testing/selftests/net/ncdevmem.c | 40 --
1 file changed, 38 insertions(+), 2 deletions(-)
diff --git a/tools/testing/selftests/net/ncdevm
In the next patch the hard-coded queue numbers are gonna be removed.
So introduce some initial support for ethtool YNL and use
it to enable header split.
Also, tcp-data-split requires latest ethtool which is unlikely
to be present in the distros right now.
(ideally, we should not shell out to eth
ntuple off/on might be not enough to do it on all NICs.
Add a bunch of shell crap to explicitly remove the rules.
Reviewed-by: Mina Almasry
Signed-off-by: Stanislav Fomichev
---
tools/testing/selftests/net/ncdevmem.c | 19 ---
1 file changed, 12 insertions(+), 7 deletions(-)
di
Use dualstack socket to support both v4 and v6. v4-mapped-v6 address
can be used to do v4.
Reviewed-by: Mina Almasry
Signed-off-by: Stanislav Fomichev
---
tools/testing/selftests/net/ncdevmem.c | 99 ++
1 file changed, 71 insertions(+), 28 deletions(-)
diff --git a/tool
Support 3-tuple filtering by making client_ip optional. When -c is
not passed, don't specify src-ip/src-port in the filter.
Reviewed-by: Mina Almasry
Signed-off-by: Stanislav Fomichev
---
tools/testing/selftests/net/ncdevmem.c | 12 +---
1 file changed, 9 insertions(+), 3 deletions(-)
There is a bunch of places where error() calls look out of place.
Use the same error(1, errno, ...) pattern everywhere.
Reviewed-by: Mina Almasry
Signed-off-by: Stanislav Fomichev
---
tools/testing/selftests/net/ncdevmem.c | 16
1 file changed, 8 insertions(+), 8 deletions(-)
So we can plug the other ones in the future if needed.
Reviewed-by: Mina Almasry
Signed-off-by: Stanislav Fomichev
---
tools/testing/selftests/net/ncdevmem.c | 203 +++--
1 file changed, 119 insertions(+), 84 deletions(-)
diff --git a/tools/testing/selftests/net/ncdevmem.c
That should make it possible to do expected payload validation on
the caller side.
Reviewed-by: Mina Almasry
Signed-off-by: Stanislav Fomichev
---
tools/testing/selftests/net/ncdevmem.c | 61 +-
1 file changed, 30 insertions(+), 31 deletions(-)
diff --git a/tools/testin
From: Duje Mihanović
Add the "marvell,pxa1908-padconf" compatible to allow migrating to a
separate pinctrl driver later.
Acked-by: Linus Walleij
Signed-off-by: Duje Mihanović
---
drivers/pinctrl/pinctrl-single.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/pinctrl/pinctrl-singl
The intent here was clearly to use the gfp variable flags instead of
hardcoding GFP_KERNEL. All the callers pass GFP_KERNEL as the gfp
flags so this doesn't affect runtime.
Fixes: b3231d353a51 ("kunit: add a convenience allocation wrapper for SKBs")
Signed-off-by: Dan Carpenter
---
include/kuni
Hello,
This series adds initial support for the Marvell PXA1908 SoC and
"samsung,coreprimevelte", a smartphone using the SoC.
USB works and the phone can boot a rootfs from an SD card, but there are
some warnings in the dmesg:
During SMP initialization:
[0.006519] CPU features: SANITY CHECK:
From: Duje Mihanović
Add DTS for Marvell PXA1908 SoC and Samsung Galaxy Core Prime Value
Edition LTE, a smartphone based on said SoC.
Signed-off-by: Duje Mihanović
---
arch/arm64/boot/dts/marvell/Makefile | 3 +
.../dts/marvell/pxa1908-samsung-coreprimevelte.dts | 336 +
From: Duje Mihanović
Add driver for the MPMU controller block on Marvell's PXA1908 SoC. The
driver is incomplete, currently only supporting the fixed PLL1; dynamic
PLLs 2-4 and CPU/DDR/AXI clock support is missing.
Signed-off-by: Duje Mihanović
---
drivers/clk/mmp/Makefile | 2 +-
From: Duje Mihanović
Add driver for the APBC controller block found on Marvell's PXA1908 SoC.
Signed-off-by: Duje Mihanović
---
drivers/clk/mmp/Makefile | 2 +-
drivers/clk/mmp/clk-pxa1908-apbc.c | 130 +
2 files changed, 131 insertions(+), 1 del
From: Duje Mihanović
Add dt bindings for the Marvell PXA1908 SoC and the Samsung Galaxy Core
Prime VE LTE phone (model number SM-G361F) using the SoC.
The SoC comes with 4 Cortex-A53 cores clocked up to ~1.2GHz and a
Vivante GC7000UL GPU. The phone also has a 4.5" 480x800 touchscreen, 8GB
eMMC a
From: Duje Mihanović
Add ARCH_MMP configuration option for Marvell PXA1908 SoC.
Signed-off-by: Duje Mihanović
---
arch/arm64/Kconfig.platforms | 8
1 file changed, 8 insertions(+)
diff --git a/arch/arm64/Kconfig.platforms b/arch/arm64/Kconfig.platforms
index
6c6d11536b42ec6e878db8d3
From: Duje Mihanović
Add myself as the maintainer for Marvell PXA1908 SoC support.
Signed-off-by: Duje Mihanović
---
MAINTAINERS | 9 +
1 file changed, 9 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index
c27f3190737f8b85779bde5489639c8b899f4fd8..8d50cb7457924e3290810eaf7d3c4
From: Duje Mihanović
Add driver for the APBCP controller block found on Marvell's PXA1908
SoC.
Signed-off-by: Duje Mihanović
---
drivers/clk/mmp/Makefile| 2 +-
drivers/clk/mmp/clk-pxa1908-apbcp.c | 82 +
2 files changed, 83 insertions(+), 1 del
From: Duje Mihanović
Add driver for the APMU controller block found on Marvell's PXA1908 SoC.
This driver is incomplete, lacking support for (at least) GPU, VPU, DSI
and CCIC (camera related) clocks.
Signed-off-by: Duje Mihanović
---
drivers/clk/mmp/Makefile | 2 +-
drivers/clk/mmp
From: Andy Shevchenko
The struct mmp_clk_factor_tbl repeats the generic struct u32_fract.
Kill the custom one and use the generic one instead.
Signed-off-by: Andy Shevchenko
Tested-by: Duje Mihanović
Reviewed-by: Linus Walleij
Reviewed-by: Stephen Boyd
Signed-off-by: Duje Mihanović
---
dri
From: Duje Mihanović
Add dt bindings and documentation for the Marvell PXA1908 clock
controller.
Reviewed-by: Conor Dooley
Reviewed-by: Stephen Boyd
Signed-off-by: Duje Mihanović
---
.../devicetree/bindings/clock/marvell,pxa1908.yaml | 48
include/dt-bindings/clock/marvell,pxa19
From: Duje Mihanović
Add the "marvell,pxa1908-padconf" compatible to allow migrating to a
separate pinctrl driver later.
Reviewed-by: Rob Herring
Acked-by: Linus Walleij
Signed-off-by: Duje Mihanović
---
Documentation/devicetree/bindings/pinctrl/pinctrl-single.yaml | 4
1 file changed,
On Fri, 01 Nov 2024 18:03:09 +0100, Krzysztof Kozlowski wrote:
> Document compatible for Qualcomm SM8750 SoC ADSP PAS which looks fully
> compatible with SM8550 variant. The only difference from bindings point
> of view is one more interrupt ("shutdown-ack"). Marking devices as
> compatible, us
On 11/4/24 7:57 PM, Jan Kara wrote:
> On Fri 01-11-24 21:22:31, Asahi Lina wrote:
>> For virtio-dax, the file/FS blocksize is irrelevant. FUSE always uses
>> large DAX blocks (2MiB), which will work with all host page sizes. Since
>> we are mapping files into the DAX window on the host, the unde
In function __note_gp_changes(), rdp->gpwrap is read using READ_ONCE()
in line 1307:
1307if (IS_ENABLED(CONFIG_PROVE_RCU) && READ_ONCE(rdp->gpwrap))
1308WRITE_ONCE(rdp->last_sched_clock, jiffies);
while read directly in line 1305:
1305if (ULONG_CMP_LT(rdp->gp_seq_needed, rnp-
2024-10-29, 11:47:31 +0100, Antonio Quartulli wrote:
> +static int ovpn_nl_peer_precheck(struct ovpn_struct *ovpn,
> + struct genl_info *info,
> + struct nlattr **attrs)
> +{
> + if (NL_REQ_ATTR_CHECK(info->extack, info->attrs[OVPN_A_PEE
"Matthieu Baerts (NGI0)" writes:
> Recently, the net/lib.sh file has been modified to include defer.sh from
> net/lib/sh/ directory. The Makefile from net/lib has been modified
> accordingly, but not the ones from the sub-targets using net/lib.sh.
>
> Because of that, the new file is not instal
On Mon, 4 Nov 2024 at 12:45, Peter Zijlstra wrote:
>
> On Mon, Nov 04, 2024 at 12:25:03PM +0100, Vlastimil Babka wrote:
> > On 11/4/24 12:11, Vlastimil Babka wrote:
>
> > >> __alloc_pages_noprof+0x292/0x710 mm/page_alloc.c:4771
> > >> alloc_pages_mpol_noprof+0x3e8/0x680 mm/mempolicy.c:2265
> > >
To prepare for the support of TEE remoteproc, create sub-functions
that can be used in both cases, with and without remoteproc TEE support.
Signed-off-by: Arnaud Pouliquen
---
drivers/remoteproc/stm32_rproc.c | 82 +++-
1 file changed, 49 insertions(+), 33 deletions(-
The new TEE remoteproc driver is used to manage remote firmware in a
secure, trusted context. The 'st,stm32mp1-m4-tee' compatibility is
introduced to delegate the loading of the firmware to the trusted
execution context. In such cases, the firmware should be signed and
adhere to the image format de
Add a remoteproc TEE (Trusted Execution Environment) driver
that will be probed by the TEE bus. If the associated Trusted
application is supported on secure part this driver offers a client
interface to load a firmware by the secure part.
This firmware could be authenticated by the secure trusted a
Main updates from version V12[1]:
Fix warning build by fixing the inline declaration in
remoteproc_tee.h (when CONFIG_REMOTEPROC_TEE is not set).
Reported-by: kernel test robot
Closes:
https://lore.kernel.org/oe-kbuild-all/202410262040.pwnrkv2q-...@intel.com/
Main updates from version V11[2]:
-
This patch centralizing the cleanup of the resource table into a new
helper function rproc_release_fw().
More than just factorizing the code into a common function, it is the
first step to integrate the release of the firmware image loaded by the
OP-TEE remoteproc framework.
Suggested-by: Mathieu
This patch updates the rproc_ops struct to include an optional
release_fw function.
The release_fw ops is responsible for releasing the remote processor
firmware image. The ops is called in the following cases:
- An error occurs in rproc_start() between the loading of the segments and
the
The "st,stm32mp1-m4-tee" compatible is utilized in a system configuration
where the Cortex-M4 firmware is loaded by the Trusted Execution Environment
(TEE).
For instance, this compatible is used in both the Linux and OP-TEE device
trees:
- In OP-TEE, a node is defined in the device tree with the
When a resource table is loaded by an external entity such as U-boot or
OP-TEE, we do not necessarily get the device address(da) but the physical
address(pa).
This helper performs similar translation than the rproc_da_to_va()
but based on a physical address.
Signed-off-by: Arnaud Pouliquen
---
d
On Mon, Nov 04, 2024 at 12:25:03PM +0100, Vlastimil Babka wrote:
> On 11/4/24 12:11, Vlastimil Babka wrote:
> >> __alloc_pages_noprof+0x292/0x710 mm/page_alloc.c:4771
> >> alloc_pages_mpol_noprof+0x3e8/0x680 mm/mempolicy.c:2265
> >> stack_depot_save_flags+0x666/0x830 lib/stackdepot.c:627
> >>
On Mon, Nov 04, 2024 at 12:45:06PM +0100, Peter Zijlstra wrote:
> diff --git a/mm/kasan/generic.c b/mm/kasan/generic.c
> index 6310a180278b..ac9f6682bb2f 100644
> --- a/mm/kasan/generic.c
> +++ b/mm/kasan/generic.c
> @@ -521,12 +521,12 @@ size_t kasan_metadata_size(struct kmem_cache *cache,
> bool
../lib.sh \
+ $(wildcard ../lib/sh/*.sh)
---
base-commit: ecf99864ea6b1843773589a935bb026951bf12dd
change-id: 20241104-net-next-selftests-lib-sh-deps-cc359ca5602f
Best regards,
--
Matthieu Baerts (NGI0)
2024-10-29, 11:47:30 +0100, Antonio Quartulli wrote:
> +static int ovpn_peer_reset_sockaddr(struct ovpn_peer *peer,
> + const struct sockaddr_storage *ss,
> + const u8 *local_ip)
> + __must_hold(&peer->lock)
> +{
> + struct ovp
2024-10-29, 11:47:27 +0100, Antonio Quartulli wrote:
> struct ovpn_peer *ovpn_peer_get_by_transp_addr(struct ovpn_struct *ovpn,
> struct sk_buff *skb)
> {
> - struct ovpn_peer *peer = NULL;
> + struct ovpn_peer *tmp, *peer = NULL;
> struc
Hi Paolo,
On 31/10/24 8:07 pm, Paolo Abeni wrote:
>
>
> On 10/24/24 12:30, MD Danish Anwar wrote:
>> From: Murali Karicheri
>>
>> This patch adds support for VLAN ctag based filtering at slave devices.
>> The slave ethernet device may be capable of filtering ethernet packets
>> based on VLAN ID
On Fri 01-11-24 21:22:31, Asahi Lina wrote:
> For virtio-dax, the file/FS blocksize is irrelevant. FUSE always uses
> large DAX blocks (2MiB), which will work with all host page sizes. Since
> we are mapping files into the DAX window on the host, the underlying
> block size of the filesystem and it
From: Li Zhijian
[ Upstream commit dc1308bee1ed03b4d698d77c8bd670d399dcd04d ]
When running watchdog-test with 'make run_tests', the watchdog-test will
be terminated by a timeout signal(SIGTERM) due to the test timemout.
And then, a system reboot would happen due to watchdog not stop. see
the dm
From: Li Zhijian
[ Upstream commit dc1308bee1ed03b4d698d77c8bd670d399dcd04d ]
When running watchdog-test with 'make run_tests', the watchdog-test will
be terminated by a timeout signal(SIGTERM) due to the test timemout.
And then, a system reboot would happen due to watchdog not stop. see
the dm
From: Li Zhijian
[ Upstream commit dc1308bee1ed03b4d698d77c8bd670d399dcd04d ]
When running watchdog-test with 'make run_tests', the watchdog-test will
be terminated by a timeout signal(SIGTERM) due to the test timemout.
And then, a system reboot would happen due to watchdog not stop. see
the dm
From: Li Zhijian
[ Upstream commit dc1308bee1ed03b4d698d77c8bd670d399dcd04d ]
When running watchdog-test with 'make run_tests', the watchdog-test will
be terminated by a timeout signal(SIGTERM) due to the test timemout.
And then, a system reboot would happen due to watchdog not stop. see
the dm
From: Li Zhijian
[ Upstream commit dc1308bee1ed03b4d698d77c8bd670d399dcd04d ]
When running watchdog-test with 'make run_tests', the watchdog-test will
be terminated by a timeout signal(SIGTERM) due to the test timemout.
And then, a system reboot would happen due to watchdog not stop. see
the dm
From: Li Zhijian
[ Upstream commit dc1308bee1ed03b4d698d77c8bd670d399dcd04d ]
When running watchdog-test with 'make run_tests', the watchdog-test will
be terminated by a timeout signal(SIGTERM) due to the test timemout.
And then, a system reboot would happen due to watchdog not stop. see
the dm
From: Li Zhijian
[ Upstream commit dc1308bee1ed03b4d698d77c8bd670d399dcd04d ]
When running watchdog-test with 'make run_tests', the watchdog-test will
be terminated by a timeout signal(SIGTERM) due to the test timemout.
And then, a system reboot would happen due to watchdog not stop. see
the dm
On Thu, Oct 31, 2024 at 11:04:06AM -0500, Konstantin Shkolnyy wrote:
On 10/31/2024 09:16, Stefano Garzarella wrote:
On Tue, Oct 29, 2024 at 09:49:54AM -0500, Konstantin Shkolnyy wrote:
Change parameters of SO_VM_SOCKETS_* to uint64_t so that they are always
In include/uapi/linux/vm_sockets.h
1 - 100 of 115 matches
Mail list logo
