Re: [PATCH net-next v6 5/5] tools: virtio: introduce vhost_net_test

2024-03-05 Thread Jason Wang
On Tue, Mar 5, 2024 at 5:47 PM Paolo Abeni wrote: > > On Wed, 2024-02-28 at 17:30 +0800, Yunsheng Lin wrote: > > introduce vhost_net_test for both vhost_net tx and rx basing > > on virtio_test to test vhost_net changing in the kernel. > > > > Steps for vhost_net tx testing: > > 1. Prepare a out

Re: [PATCH net-next v2 3/3] tun: AF_XDP Tx zero-copy support

2024-03-05 Thread Jason Wang
On Sat, Mar 2, 2024 at 2:40 AM Willem de Bruijn wrote: > > Maciej Fijalkowski wrote: > > On Wed, Feb 28, 2024 at 07:05:56PM +0800, Yunjian Wang wrote: > > > This patch set allows TUN to support the AF_XDP Tx zero-copy feature, > > > which can significantly reduce CPU utilization for XDP programs.

Re: [PATCH V4] remoteproc: qcom: q6v5: Get crash reason from specific SMEM partition

2024-03-05 Thread Vignesh Viswanathan
On 3/6/2024 9:25 AM, Bjorn Andersson wrote: > On Wed, Dec 20, 2023 at 11:25:11AM +0530, Vignesh Viswanathan wrote: >> q6v5 fatal and watchdog IRQ handlers always retrieves the crash reason >> information from SMEM global partition (QCOM_SMEM_HOST_ANY). >> >> For some targets like IPQ9574 and

Re: [PATCH V4] remoteproc: qcom: q6v5: Get crash reason from specific SMEM partition

2024-03-05 Thread Bjorn Andersson
On Wed, Dec 20, 2023 at 11:25:11AM +0530, Vignesh Viswanathan wrote: > q6v5 fatal and watchdog IRQ handlers always retrieves the crash reason > information from SMEM global partition (QCOM_SMEM_HOST_ANY). > > For some targets like IPQ9574 and IPQ5332, crash reason information is > present in

Re: [PATCH v6 7/7] Documentation: KVM: Add hypercall for LoongArch

2024-03-05 Thread maobibo
On 2024/3/6 上午2:26, WANG Xuerui wrote: On 3/4/24 17:10, maobibo wrote: On 2024/3/2 下午5:41, WANG Xuerui wrote: On 3/2/24 16:47, Bibo Mao wrote: [snip] +Querying for existence +== + +To find out if we're running on KVM or not, cpucfg can be used with index

[PATCH] ring-buffer: mark racy accesses on work->wait_index

2024-03-05 Thread linke li
Mark data races to work->wait_index as benign using READ_ONCE and WRITE_ONCE. These accesses are expected to be racy. Signed-off-by: linke li --- kernel/trace/ring_buffer.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/kernel/trace/ring_buffer.c

Re: [PATCH net-next v2 3/3] tun: AF_XDP Tx zero-copy support

2024-03-05 Thread Jason Wang
On Mon, Mar 4, 2024 at 7:24 PM wangyunjian wrote: > > > > > -Original Message- > > From: Jason Wang [mailto:jasow...@redhat.com] > > Sent: Monday, March 4, 2024 2:56 PM > > To: wangyunjian > > Cc: m...@redhat.com; willemdebruijn.ker...@gmail.com; k...@kernel.org; > > bj...@kernel.org;

[POC] !!! Re: [PATCH 0/8] tracing: Persistent traces across a reboot or crash

2024-03-05 Thread Steven Rostedt
I forgot to add [POC] to the topic. All these patches are a proof of concept. -- Steve

[PATCH 8/8] ring-buffer: Validate boot range memory events

2024-03-05 Thread Steven Rostedt
From: "Steven Rostedt (Google)" Make sure all the events in each of the sub-buffers that were mapped in a memory region are valid. This moves the code that walks the buffers for time-stamp validation out of the CONFIG_RING_BUFFER_VALIDATE_TIME_DELTAS ifdef block and is used to validate the

[PATCH 7/8] ring-buffer: Add test if range of boot buffer is valid

2024-03-05 Thread Steven Rostedt
From: "Steven Rostedt (Google)" Add a test against the ring buffer memory range to see if it has valid data. The ring_buffer_meta structure is given a new field called "first_buffer" which holds the address of the first sub-buffer. This is used to both determine if the other fields are valid as

[PATCH 5/8] ring-buffer: Add ring_buffer_meta data

2024-03-05 Thread Steven Rostedt
From: "Steven Rostedt (Google)" Populate the ring_buffer_meta array. It holds the pointer to the head_buffer (next to read), the commit_buffer (next to write) the size of the sub-buffers, number of sub-buffers and an array that keeps track of the order of the sub-buffers. This information will

[PATCH 6/8] ring-buffer: Add output of ring buffer meta page

2024-03-05 Thread Steven Rostedt
From: "Steven Rostedt (Google)" Add a buffer_meta per-cpu file for the trace instance that is mapped to boot memory. This shows the current meta-data and can be used by user space tools to record off the current mappings to help reconstruct the ring buffer after a reboot. It does not expose any

[PATCH 3/8] tracing: Create "boot_mapped" instance for memory mapped buffer

2024-03-05 Thread Steven Rostedt
From: "Steven Rostedt (Google)" Add two global variables trace_buffer_start and trace_buffer_size. If they are both set, then a "boot_mapped" instance will be created using the memory specified by these variables as its ring buffer. The instance will exist in:

[PATCH 4/8] HACK: Hard code in mapped tracing buffer address

2024-03-05 Thread Steven Rostedt
From: "Steven Rostedt (Google)" Do not submit! This is for testing purposes only. It hard codes an address that I was using to store the ring buffer range. How the memory actually gets mapped will be another project. Signed-off-by: Steven Rostedt (Google) --- arch/x86/kernel/setup.c | 20

[PATCH 2/8] ring-buffer: Add ring_buffer_alloc_range()

2024-03-05 Thread Steven Rostedt
From: "Steven Rostedt (Google)" In preparation to allowing the trace ring buffer to be allocated in a range of memory that is persistent across reboots, add ring_buffer_alloc_range(). It takes a contiguous range of memory and will split it up evening for the per CPU ring buffers. If there's not

[PATCH 0/8] tracing: Persistent traces across a reboot or crash

2024-03-05 Thread Steven Rostedt
This is a way to map a ring buffer instance across reboots. The requirement is that you have a memory region that is not erased. I tested this on a Debian VM running on qemu on a Debian server, and even tested it on a baremetal box running Fedora. I was surprised that it worked on the baremetal

[PATCH 1/8] ring-buffer: Allow mapped field to be set without mapping

2024-03-05 Thread Steven Rostedt
From: "Steven Rostedt (Google)" In preparation for having the ring buffer mapped to a dedicated location, which will have the same restrictions as user space memory mapped buffers, allow it to use the "mapped" field of the ring_buffer_per_cpu structure without having the user space meta page

[PATCH 3/5] ARM: dts: qcom: msm8974pro-castor: Remove camera button definitions

2024-03-05 Thread Luca Weiss
>From what I can tell, the camera buttons are not part of Z2 Tablet hardware even though other devices based on 'shinano' do have them. Fixes: ab80661883de ("ARM: dts: qcom: msm8974: Add Sony Xperia Z2 Tablet") Signed-off-by: Luca Weiss ---

[PATCH 1/5] ARM: dts: qcom: msm8974pro-castor: Clean up formatting

2024-03-05 Thread Luca Weiss
Clean up some easy things do prepare the dts for further changes. * Move pinctrl-names below pinctrl-* * Move status as last property * Remove default linux,input-type value Signed-off-by: Luca Weiss --- .../qcom-msm8974pro-sony-xperia-shinano-castor.dts | 65 +- 1 file

[PATCH 4/5] ARM: dts: qcom: msm8974pro-castor: Add debounce-interval for keys

2024-03-05 Thread Luca Weiss
Set the debounce-interval for the GPIO keys. Signed-off-by: Luca Weiss --- arch/arm/boot/dts/qcom/qcom-msm8974pro-sony-xperia-shinano-castor.dts | 2 ++ 1 file changed, 2 insertions(+) diff --git a/arch/arm/boot/dts/qcom/qcom-msm8974pro-sony-xperia-shinano-castor.dts

[PATCH 0/5] Some devicetree cleanup for MSM8974 Sony Xperia Z2 Tablet

2024-03-05 Thread Luca Weiss
+- 1 file changed, 32 insertions(+), 51 deletions(-) --- base-commit: 2e397253aae928c6d318beb18c05bc2236f69a8a change-id: 20240305-castor-changes-bc6785ba8458 Best regards, -- Luca Weiss

[PATCH 2/5] ARM: dts: qcom: msm8974pro-castor: Add mmc aliases

2024-03-05 Thread Luca Weiss
Add the mmc0 & mmc1 aliases to make sure internal storage always becomes /dev/mmcblk0 and SD card becomes /dev/mmcblk1 Signed-off-by: Luca Weiss --- arch/arm/boot/dts/qcom/qcom-msm8974pro-sony-xperia-shinano-castor.dts | 2 ++ 1 file changed, 2 insertions(+) diff --git

[PATCH 5/5] ARM: dts: qcom: msm8974pro-castor: Rename wifi node name

2024-03-05 Thread Luca Weiss
Give the wifi node a generic node name 'wifi'. Signed-off-by: Luca Weiss --- arch/arm/boot/dts/qcom/qcom-msm8974pro-sony-xperia-shinano-castor.dts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/arm/boot/dts/qcom/qcom-msm8974pro-sony-xperia-shinano-castor.dts

[PATCH] remoteproc: make rproc_class constant

2024-03-05 Thread Ricardo B. Marliere
.dev_groups = rproc_devgroups, }; --- base-commit: 8b46dc5cfa5ffea279aed0fc05dc4b1c39a51517 change-id: 20240305-class_cleanup-remoteproc2-f1212934f990 Best regards, -- Ricardo B. Marliere

Re: [PATCH 0/3] Restructure init sequence to set aside reserved memory earlier

2024-03-05 Thread Oreoluwa Babatunde
On 2/9/2024 4:29 PM, Oreoluwa Babatunde wrote: > The loongarch, openric, and sh architectures allocate memory from > memblock before it gets the chance to set aside reserved memory regions. > This means that there is a possibility for memblock to allocate from > memory regions that are supposed

Re: [RFC PATCH v3 2/5] mfd: add driver for Marvell 88PM886 PMIC

2024-03-05 Thread Karel Balej
Lee Jones, 2024-03-05T11:44:18+00:00: > > +static struct mfd_cell pm886_devs[] = { > > + { > > + .name = "88pm886-onkey", > > + .num_resources = ARRAY_SIZE(pm886_onkey_resources), > > + .resources = pm886_onkey_resources, > > + }, > > + { > > + .name =

[PATCH] rpmsg: core: make rpmsg_class constant

2024-03-05 Thread Ricardo B. Marliere
f(d, struct rpmsg_driver, drv) -extern struct class *rpmsg_class; +extern const struct class rpmsg_class; /** * struct rpmsg_device_ops - indirection table for the rpmsg_device operations --- base-commit: b03aa6d4e9a74c4289929b6cf3c6bcc80270682d change-id: 20240305-class_cleanup-remoteproc-2b53e26b2817 Best regards, -- Ricardo B. Marliere

Re: [PATCH v6 7/7] Documentation: KVM: Add hypercall for LoongArch

2024-03-05 Thread WANG Xuerui
On 3/4/24 17:10, maobibo wrote: On 2024/3/2 下午5:41, WANG Xuerui wrote: On 3/2/24 16:47, Bibo Mao wrote: [snip] +Querying for existence +== + +To find out if we're running on KVM or not, cpucfg can be used with index +CPUCFG_KVM_BASE (0x4000), cpucfg range between

Re: [PATCH v2] tracing: Limit trace_marker writes to just 4K

2024-03-05 Thread Mathieu Desnoyers
On 2024-03-04 22:34, Steven Rostedt wrote: From: "Steven Rostedt (Google)" Limit the max print event of trace_marker to just 4K string size. This must also be less than the amount that can be held by a trace_seq along with the text that is before the output (like the task name, PID, CPU,

Re: [RFC PATCH v3 2/5] mfd: add driver for Marvell 88PM886 PMIC

2024-03-05 Thread Lee Jones
On Sun, 03 Mar 2024, Karel Balej wrote: > From: Karel Balej > > Marvell 88PM886 is a PMIC which provides various functions such as > onkey, battery, charger and regulators. It is found for instance in the > samsung,coreprimevelte smartphone with which this was tested. > > Only implement basic

Re: [PATCH net-next v6 5/5] tools: virtio: introduce vhost_net_test

2024-03-05 Thread Paolo Abeni
On Wed, 2024-02-28 at 17:30 +0800, Yunsheng Lin wrote: > introduce vhost_net_test for both vhost_net tx and rx basing > on virtio_test to test vhost_net changing in the kernel. > > Steps for vhost_net tx testing: > 1. Prepare a out buf. > 2. Kick the vhost_net to do tx processing. > 3. Do the

Re: [PATCH v3 2/2] riscv: Fix text patching when IPI are used

2024-03-05 Thread Björn Töpel
Conor Dooley writes: > On Tue, Mar 05, 2024 at 08:33:30AM +0530, Anup Patel wrote: >> On Tue, Mar 5, 2024 at 1:54 AM Björn Töpel wrote: >> > >> > Conor Dooley writes: >> > >> > > On Thu, Feb 29, 2024 at 01:10:56PM +0100, Alexandre Ghiti wrote: >> > >> For now, we use stop_machine() to patch

Re: [PATCH v3 2/2] riscv: Fix text patching when IPI are used

2024-03-05 Thread Conor Dooley
On Tue, Mar 05, 2024 at 08:33:30AM +0530, Anup Patel wrote: > On Tue, Mar 5, 2024 at 1:54 AM Björn Töpel wrote: > > > > Conor Dooley writes: > > > > > On Thu, Feb 29, 2024 at 01:10:56PM +0100, Alexandre Ghiti wrote: > > >> For now, we use stop_machine() to patch the text and when we use IPIs for