On Thu, 21 Mar 2024 11:09:18 +0800 (CST) xu.xi...@zte.com.cn wrote:
> +/* This part must be outside protection */
> +#include
> \ No newline at end of file
In addition to Jason's comments please make sure there is a new line at
the end of the file.
And please post v4 on Monday, net-next is
On Thu, Mar 21, 2024 at 11:09 AM wrote:
>
> From: he peilin
>
> Introduce a tracepoint for icmp_send, which can help users to get more
> detail information conveniently when icmp abnormal events happen.
>
> 1. Giving an usecase example:
> =
> When an application
From: he peilin
Introduce a tracepoint for icmp_send, which can help users to get more
detail information conveniently when icmp abnormal events happen.
1. Giving an usecase example:
=
When an application experiences packet loss due to an unreachable UDP
destination
On Thu, Mar 21, 2024 at 10:12 AM wrote:
>
> From: he peilin
>
>
> Introduce a tracepoint for icmp_send, which can help users to get more
>
> detail information conveniently when icmp abnormal events happen.
>
>
> 1. Giving an usecase example:
>
> =
>
> When an
From: he peilin
Introduce a tracepoint for icmp_send, which can help users to get more
detail information conveniently when icmp abnormal events happen.
1. Giving an usecase example:
=
When an application experiences packet loss due to an unreachable UDP
destination
From: David Stevens
The virtio_balloon driver uses wakeup sources to allow the guest to
enter system power management sleep states (e.g. s2idle) without running
the risk of becoming unresponsive to cooperative memory management
requests from the host. This series fixes an issue where wakeup
From: David Stevens
Treat stats requests as wakeup events to ensure that the driver responds
to device requests in a timely manner.
Signed-off-by: David Stevens
Acked-by: David Hildenbrand
---
drivers/virtio/virtio_balloon.c | 75 -
1 file changed, 46
From: David Stevens
Wakeup sources don't support nesting multiple events, so sharing a
single object between multiple drivers can result in one driver
overriding the wakeup event processing period specified by another
driver. Have the virtio balloon driver use the wakeup source of the
device it
On Wed, 20 Mar 2024 20:46:11 -0400
Waiman Long wrote:
> I have no objection to that. However, there are now 2 function call
> overhead in each iteration if either CONFIG_IRQSOFF_TRACER or
> CONFIG_PREEMPT_TRACER is on. Is it possible to do it with just one
> function call? IOW, make
On 3/20/24 12:20, Steven Rostedt wrote:
From: Steven Rostedt (Google)
I'm debugging some latency issues on a Chromebook and the preemptirqsoff
tracer hit this:
# tracer: preemptirqsoff
#
# preemptirqsoff latency trace v1.1.5 on 5.15.148-21853-g165fd2387469-dirty
#
On Wed, Mar 20, 2024 at 12:15 AM Huang, Ying wrote:
>
> "Ho-Ren (Jack) Chuang" writes:
>
> > The current implementation treats emulated memory devices, such as
> > CXL1.1 type3 memory, as normal DRAM when they are emulated as normal memory
> > (E820_TYPE_RAM). However, these emulated devices
On Wed, 20 Mar 2024 09:27:49 -0400
Steven Rostedt wrote:
> On Wed, 20 Mar 2024 17:10:38 +0900
> "Masami Hiramatsu (Google)" wrote:
>
> > From: Masami Hiramatsu (Google)
> >
> > Fix to initialize 'val' local variable with zero.
> > Dan reported that Smatch static code checker reports an error
Partially revert commit d6cb38e10810 ("tracing: Use div64_u64() instead
of do_div()") and use do_div() again to utilize its faster 64-by-32
division compared to the 64-by-64 division done by div64_u64().
Explicitly cast the divisor bm_cnt to u32 to prevent a Coccinelle
warning reported by
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any
issue:
Reported-and-tested-by: syzbot+70f57d8a3ae84934c...@syzkaller.appspotmail.com
Tested on:
commit: 4bedfb31 mm,page_owner: maintain own list of stack_rec..
git tree:
The license text was copied from:
https://spdx.org/licenses/0BSD.html
Reviewed-by: Jia Tan
Signed-off-by: Lasse Collin
---
Notes:
0BSD is the ISC license without the requirements to preserve copyright
and license notices.
LICENSES/deprecated/0BSD | 23 +++
1
Remove the public domain notices and add SPDX license identifiers.
Change MODULE_LICENSE from "GPL" to "Dual BSD/GPL" because 0BSD should
count as a BSD license variant here.
The switch to 0BSD was done in the upstream XZ Embedded project because
public domain has (real or perceived) legal
On 2024-03-20 13:58, Steven Rostedt wrote:
On Wed, 20 Mar 2024 13:15:39 -0400
Mathieu Desnoyers wrote:
I would like to introduce restart_critical_timings() and place it in
locations that have this behavior.
Is there any way you could move this to need_resched() rather than
sprinkle those
On Thu, Mar 14, 2024 at 04:07:33PM +0100, Bj"orn T"opel wrote:
> After reading Mark's reply, and discussing with OpenJDK folks (who does
> the most crazy text patching on all platforms), having to patch multiple
> instructions (where the address materialization is split over multiple
>
On Wed, 20 Mar 2024 13:15:39 -0400
Mathieu Desnoyers wrote:
> > I would like to introduce restart_critical_timings() and place it in
> > locations that have this behavior.
>
> Is there any way you could move this to need_resched() rather than
> sprinkle those everywhere ?
Because
On Tue, 2024-03-19 at 14:47 +0100, Peter Hilber wrote:
> While the virtio-comment list is not available, now also CC'ing Parav,
> which may be interested in this virtio-rtc spec related discussion thread.
>
> On 14.03.24 15:19, David Woodhouse wrote:
> > On 14 March 2024 11:13:37 CET, Peter
On 2024-03-20 12:20, Steven Rostedt wrote:
From: Steven Rostedt (Google)
I'm debugging some latency issues on a Chromebook and the preemptirqsoff
tracer hit this:
# tracer: preemptirqsoff
#
# preemptirqsoff latency trace v1.1.5 on 5.15.148-21853-g165fd2387469-dirty
#
On Wed, Mar 20, 2024 at 03:24:16PM +1000, Gavin Shan wrote:
>
> Before this patch was posted, I had debugging code to record last 16
> transactions
> to the available and used queue from guest and host side. It did reveal the
> wrong
> head was fetched from the available queue.
>
> [
Hi Honggyu,
On Wed, 20 Mar 2024 16:07:48 +0900 Honggyu Kim wrote:
> Hi SeongJae,
>
> On Mon, 18 Mar 2024 12:07:21 -0700 SeongJae Park wrote:
> > On Mon, 18 Mar 2024 22:27:45 +0900 Honggyu Kim wrote:
> >
> > > Hi SeongJae,
> > >
> > > On Sun, 17 Mar 2024 08:31:44 -0700 SeongJae Park wrote:
Hi Björn,
On Fri, Mar 15, 2024 at 4:50 AM Björn Töpel wrote:
>
> Björn Töpel writes:
>
> > Puranjay Mohan writes:
> >
> >> Björn Töpel writes:
> >>
> >>>
> >>> Hmm, depending on RISC-V's CMODX path, the pro/cons CALL_OPS vs dynamic
> >>> trampolines changes quite a bit.
> >>>
> >>> The more I
On 20. Mar 2024, at 16:01, Thorsten Blum wrote:
>
> Coccinelle also finds this one, but please ignore this patch as I just
> realized
> this was already fixed in another patch of mine from February.
>
> Sorry for the inconvenience.
>
> Link:
>
From: Steven Rostedt (Google)
I'm debugging some latency issues on a Chromebook and the preemptirqsoff
tracer hit this:
# tracer: preemptirqsoff
#
# preemptirqsoff latency trace v1.1.5 on 5.15.148-21853-g165fd2387469-dirty
#
#
On 3/20/24 2:40 AM, Krzysztof Kozlowski wrote:
> On 19/03/2024 15:42, Tanmay Shah wrote:
>>
>>
>> On 3/19/24 12:30 AM, Krzysztof Kozlowski wrote:
>>> On 19/03/2024 01:51, Tanmay Shah wrote:
Hello Krzysztof,
Thanks for reviews. Please find my comments below.
On 3/17/24
On 20. Mar 2024, at 11:27, Masami Hiramatsu (Google)
wrote:
>
> Hmm, strange, trace_do_benchmark() has another do_div(u64, u64).
>
>do {
>last_seed = seed;
>seed = stddev;
>if (!last_seed)
>
Steven,
[
I rebased my queue on top of the v6.8 tag.
]
Tracing:
- Update makefiles for latency-collector and RTLA,
using tools/build/ makefiles like perf does, inheriting
its benefits. For example, having a proper way to
handle dependencies.
-
Similar to '%pD' for printk, use '%pD' for print struct file's name.
Signed-off-by: Ye Bin
---
kernel/trace/trace.c | 2 +-
kernel/trace/trace_probe.c | 57 +++---
2 files changed, 36 insertions(+), 23 deletions(-)
diff --git a/kernel/trace/trace.c
This patch adds test cases for new print format type "%pd/%pD".The test cases
test the following items:
1. Test README if add "%pd/%pD" type;
2. Test "%pd" type for dput();
3. Test "%pD" type for vfs_read();
This test case require enable CONFIG_HAVE_FUNCTION_ARG_ACCESS_API configuration.
This patch adds fprobe test cases for new print format type "%pd/%pD".The
test cases test the following items:
1. Test "%pd" type for dput();
2. Test "%pD" type for vfs_read();
This test case require enable CONFIG_HAVE_FUNCTION_ARG_ACCESS_API configuration.
Signed-off-by: Ye Bin
---
Similar to printk() '%pd' is for fetch dentry's name from struct dentry's
pointer, and '%pD' is for fetch file's name from struct file's pointer.
Signed-off-by: Ye Bin
---
Documentation/trace/kprobetrace.rst | 8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git
During fault locating, the file name needs to be printed based on the
dentry/file address. The offset needs to be calculated each time, which
is troublesome. Similar to printk, kprobe supports printing file names
for dentry/file addresses.
Diff v7 vs v6:
1. Squash [1/8] to [3/8] patches into 1
Support print type '%pd' for print dentry's name.
Signed-off-by: Ye Bin
---
kernel/trace/trace.c| 2 +-
kernel/trace/trace_fprobe.c | 6 +
kernel/trace/trace_kprobe.c | 6 +
kernel/trace/trace_probe.c | 50 +
kernel/trace/trace_probe.h |
On Wed, 20 Mar 2024 13:41:12 +0100
Daniel Bristot de Oliveira wrote:
> On 3/20/24 00:02, Steven Rostedt wrote:
> > On Mon, 18 Mar 2024 18:41:13 +0100
> > Daniel Bristot de Oliveira wrote:
> >
> >> Steven,
> >>
> >> Tracing tooling updates for 6.9
> >>
> >> Tracing:
> >> - Update
On Wed, 20 Mar 2024 17:10:38 +0900
"Masami Hiramatsu (Google)" wrote:
> From: Masami Hiramatsu (Google)
>
> Fix to initialize 'val' local variable with zero.
> Dan reported that Smatch static code checker reports an error that a local
> 'val' variable needs to be initialized. Actually, the
On Wed, 20 Mar 2024 17:10:38 +0900
"Masami Hiramatsu (Google)" wrote:
> From: Masami Hiramatsu (Google)
>
> Fix to initialize 'val' local variable with zero.
> Dan reported that Smatch static code checker reports an error that a local
> 'val' variable needs to be initialized. Actually, the
On Wed, 20 Mar 2024 12:44:23 +0900
Masami Hiramatsu (Google) wrote:
> > > kernel/trace/trace_probe.c
> > > 846 return;
> > > 847
> > > 848 for (i = 0; i < earg->size; i++) {
> > > 849 struct fetch_insn *code = >code[i];
> > > 850
> >
Hi Ye,
BTW, if you have a chance, please squash [1/8] to [3/8] patches
into 1 patch. There is no reason to split these since these are
a local(= the same subsystem) function implementation and callers.
Thank you,
On Fri, 15 Mar 2024 14:55:35 +0800
Ye Bin wrote:
> Support print type '%pd' for
On 3/20/24 00:02, Steven Rostedt wrote:
> On Mon, 18 Mar 2024 18:41:13 +0100
> Daniel Bristot de Oliveira wrote:
>
>> Steven,
>>
>> Tracing tooling updates for 6.9
>>
>> Tracing:
>> - Update makefiles for latency-collector and RTLA,
>> using tools/build/ makefiles like perf
> > From: Peilin He
> >
> > Introduce a tracepoint for icmp_send, which can help users to get more
> > detail information conveniently when icmp abnormal events happen.
> >
> > 1. Giving an usecase example:
> > =
> > When an application experiences packet loss due to
On Tue, Mar 19, 2024 at 03:51:18PM -0500, Mike Christie wrote:
> On 3/19/24 12:19 PM, Stefan Hajnoczi wrote:
> > On Tue, Mar 19, 2024 at 03:40:53AM -0400, Michael S. Tsirkin wrote:
> >> On Tue, Mar 19, 2024 at 12:32:26AM -0700, syzbot wrote:
> >>> Hello,
> >>>
> >>> syzbot found the following
On Wed, Mar 20, 2024 at 06:19:12PM +0800, Wang Rong wrote:
From: Rong Wang
Once enable iommu domain for one device, the MSI
translation tables have to be there for software-managed MSI.
Otherwise, platform with software-managed MSI without an
irq bypass function, can not get a correct memory
On Mon, 18 Mar 2024 11:52:44 +0100
Thorsten Blum wrote:
> Explicitly cast the divisor to u32 to fix a Coccinelle/coccicheck warning
> reported by do_div.cocci.
>
Hmm, strange, trace_do_benchmark() has another do_div(u64, u64).
do {
last_seed = seed;
Hi Ye,
On Fri, 15 Mar 2024 14:55:32 +0800
Ye Bin wrote:
> Sorry for taking so long to post the V6 version. I thought my email was
> sent successfully. I checked the patchwork and it was not sent successfully.
>
> During fault locating, the file name needs to be printed based on the
>
From: Rong Wang
Once enable iommu domain for one device, the MSI
translation tables have to be there for software-managed MSI.
Otherwise, platform with software-managed MSI without an
irq bypass function, can not get a correct memory write event
from pcie, will not get irqs.
The solution is to
Hi Ye,
Can you split this into
(1)
> - "\t symstr, \\[\\]\n"
> + "\t symstr, %pd, \\[\\]\n"
and
(2)
> - "\t symstr, %pd, \\[\\]\n"
> + "\t symstr, %pd/%pD, \\[\\]\n"
And merge (1) into [PATCH 3/8], (2) into [PATCH 5/8], so that
the
On Sun, 17 Mar 2024 10:53:59 -0500
Jinghao Jia wrote:
>
>
> On 3/16/24 08:46, Masami Hiramatsu (Google) wrote:
> > On Thu, 14 Mar 2024 18:56:35 -0500
> > Jinghao Jia wrote:
> >
> >> On 3/14/24 10:17, Masami Hiramatsu (Google) wrote:
> >>> From: Masami Hiramatsu (Google)
> >>>
> >>> Read
From: Masami Hiramatsu (Google)
Fix to initialize 'val' local variable with zero.
Dan reported that Smatch static code checker reports an error that a local
'val' variable needs to be initialized. Actually, the 'val' is expected to
be initialized by FETCH_OP_ARG in the same loop, but it is not
On 19/03/2024 15:42, Tanmay Shah wrote:
>
>
> On 3/19/24 12:30 AM, Krzysztof Kozlowski wrote:
>> On 19/03/2024 01:51, Tanmay Shah wrote:
>>> Hello Krzysztof,
>>>
>>> Thanks for reviews. Please find my comments below.
>>>
>>> On 3/17/24 1:53 PM, Krzysztof Kozlowski wrote:
On 15/03/2024
"Ho-Ren (Jack) Chuang" writes:
> The current implementation treats emulated memory devices, such as
> CXL1.1 type3 memory, as normal DRAM when they are emulated as normal memory
> (E820_TYPE_RAM). However, these emulated devices have different
> characteristics than traditional DRAM, making it
On Wed, Mar 20, 2024 at 03:24:16PM +1000, Gavin Shan wrote:
> On 3/20/24 10:49, Michael S. Tsirkin wrote:>
> > I think you are wasting the time with these tests. Even if it helps what
> > does this tell us? Try setting a flag as I suggested elsewhere.
> > Then check it in vhost.
> > Or here's
Hi SeongJae,
On Mon, 18 Mar 2024 12:07:21 -0700 SeongJae Park wrote:
> On Mon, 18 Mar 2024 22:27:45 +0900 Honggyu Kim wrote:
>
> > Hi SeongJae,
> >
> > On Sun, 17 Mar 2024 08:31:44 -0700 SeongJae Park wrote:
> > > Hi Honggyu,
> > >
> > > On Sun, 17 Mar 2024 17:36:29 +0900 Honggyu Kim
On 1/29/2024 10:03 PM, Michal Koutný wrote:
On Mon, Jan 29, 2024 at 04:18:36PM +0530, Deepak Kumar Singh
wrote:
There is already a patch posted for similar problem -
https://lore.kernel.org/all/20231201110631.669085-1-quic_dee...@quicinc.com/
I was not aware, thanks for the pointer.
Do
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any
issue:
Reported-and-tested-by: syzbot+70f57d8a3ae84934c...@syzkaller.appspotmail.com
Tested on:
commit: 52998cdd Merge branch '6.8/scsi-staging' into 6.8/scsi..
git tree:
Abstract `kmem_put_memory_types()` into `mt_put_memory_types()` to
accommodate various memory types and enhance flexibility,
similar to `mt_find_alloc_memory_type()`.
Signed-off-by: Ho-Ren (Jack) Chuang
---
drivers/dax/kmem.c | 7 +--
include/linux/memory-tiers.h | 6 ++
The current implementation treats emulated memory devices, such as
CXL1.1 type3 memory, as normal DRAM when they are emulated as normal memory
(E820_TYPE_RAM). However, these emulated devices have different
characteristics than traditional DRAM, making it important to
distinguish them. Thus, we
When a memory device, such as CXL1.1 type3 memory, is emulated as
normal memory (E820_TYPE_RAM), the memory device is indistinguishable
from normal DRAM in terms of memory tiering with the current implementation.
The current memory tiering assigns all detected normal memory nodes
to the same DRAM
59 matches
Mail list logo
