Re: [PATCH V5 0/3] Intel Platform Monitoring Technology

MCTP and PLDM are the latest in Platform management Technology. Sw application and drivers can be implemented on the PCIe platform. Previously I spent some time on this. On Mon, Aug 10, 2020 at 7:49 PM David E. Box wrote: > > Friendly ping. > > On Wed, 2020-07-29 at 14:37 -0700, David E. Box

[PATCH] drivers:staging: Fix alignment warnings reported by tool

From: Umesh3034 Fix alignment warnings reported by checkpatch.pl Signed-off-by: Umesh3034 --- drivers/staging/clocking-wizard/clk-xlnx-clock-wizard.c | 17 ++--- 1 file changed, 10 insertions(+), 7 deletions(-) diff --git

[PATCH] drivers:staging: Fix alignment warnings reported by tool

From: Umesh3034 Fix alignment warnings reported by checkpatch.pl Signed-off-by: Umesh3034 --- drivers/staging/clocking-wizard/clk-xlnx-clock-wizard.c | 17 ++--- 1 file changed, 10 insertions(+), 7 deletions(-) diff --git a/drivers/staging/clocking-wizard/clk-xlnx-clock-wizard.c

Re: Kernel bio layer is sending bio size more than our block device is capable of handling

>From the kernel source code i came to know below things. 4.1 kernel version onward *""nr_pages = min(sdio->pages_in_io, bio_get_nr_vecs(map_bh->b_bdev))""* line has been removed which was considering max_sectors_kb of queue. Now new code is something like this* "nr_pages =

Re: Kernel bio layer is sending bio size more than our block device is capable of handling

>From the kernel source code i came to know below things. 4.1 kernel version onward *""nr_pages = min(sdio->pages_in_io, bio_get_nr_vecs(map_bh->b_bdev))""* line has been removed which was considering max_sectors_kb of queue. Now new code is something like this* "nr_pages =

RE: Kernel bio layer is sending bio size more than our block device is capable of handling

Hi Christoph Hellwig, So 4.4.0-59-generic is not stable one ?. If not then probably it would be problem for us if customer want the same kernel version!. Thanks, Umesh -Original Message- From: Christoph Hellwig [mailto:h...@infradead.org] Sent: Thursday, March 2, 2017 9:34 PM

RE: Kernel bio layer is sending bio size more than our block device is capable of handling

Hi Christoph Hellwig, So 4.4.0-59-generic is not stable one ?. If not then probably it would be problem for us if customer want the same kernel version!. Thanks, Umesh -Original Message- From: Christoph Hellwig [mailto:h...@infradead.org] Sent: Thursday, March 2, 2017 9:34 PM

RE: Kernel bio layer is sending bio size more than our block device is capable of handling

Hi Christoph Hellwig, Thanks for reply. BTW (since I'm new) what is linux-block list ?. Is it subscribe ?. Can you please let me know which is latest kernel version ? Thanks, Umesh -Original Message- From: Christoph Hellwig [mailto:h...@infradead.org] Sent: Thursday, March 2, 2017 9

RE: Kernel bio layer is sending bio size more than our block device is capable of handling

Hi Christoph Hellwig, Thanks for reply. BTW (since I'm new) what is linux-block list ?. Is it subscribe ?. Can you please let me know which is latest kernel version ? Thanks, Umesh -Original Message- From: Christoph Hellwig [mailto:h...@infradead.org] Sent: Thursday, March 2, 2017 9

Kernel bio layer is sending bio size more than our block device is capable of handling

Hello, We are registering bio size of our device with linux kernel with below available kernel API. blk_queue_max_hw_sectors(dev->osdev.queue, (dev->aggr_max_size >> KERNEL_SECTOR_SHIFT));. Max size of bio that our block device can handle is 106496 bytes (104KB) but linux block device is

Kernel bio layer is sending bio size more than our block device is capable of handling

Hello, We are registering bio size of our device with linux kernel with below available kernel API. blk_queue_max_hw_sectors(dev->osdev.queue, (dev->aggr_max_size >> KERNEL_SECTOR_SHIFT));. Max size of bio that our block device can handle is 106496 bytes (104KB) but linux block device is

mm_struct

Does kernel thread has process space?

mm_struct

Does kernel thread has process space?

MCTP Protocol driver

I need to implement firmware download software on MCTP( Management Component Transport Protocol) protocol & PLDM . I am not sure whether any driver/software available in linux on MCTP. Please letme know any driver software available in Linux. -- To unsubscribe from this list: send the line

MCTP Protocol driver

I need to implement firmware download software on MCTP( Management Component Transport Protocol) protocol & PLDM . I am not sure whether any driver/software available in linux on MCTP. Please letme know any driver software available in Linux. -- To unsubscribe from this list: send the line

MCTP

Is driver suppport available in linux for MCTP (management component transport protocol) ? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please

MCTP

Is driver suppport available in linux for MCTP (management component transport protocol) ? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please

[PATCH] ftrace-update-tracing_thresh-info

This patch updates the tracing_thresh information in ftrace documentation file(ftrace.txt). Signed-off-by: Umesh Tiwari --- Documentation/trace/ftrace.txt |9 +++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/Documentation/trace/ftrace.txt b/Documentation/trace

[PATCH] ftrace-update-tracing_thresh-info

This patch updates the tracing_thresh information in ftrace documentation file(ftrace.txt). Signed-off-by: Umesh Tiwari umes...@samsung.com --- Documentation/trace/ftrace.txt |9 +++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/Documentation/trace/ftrace.txt b

[PATCH v2] ftrace: add tracing_thresh to function profile

This patch extends tracing_thresh functionality to function profile tracer. If tracing_thresh is set, print those entries only, whose average is > tracing thresh. Signed-off-by: Umesh Tiwari --- kernel/trace/ftrace.c |9 +++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --

[PATCH v2] ftrace: add tracing_thresh to function profile

This patch extends tracing_thresh functionality to function profile tracer. If tracing_thresh is set, print those entries only, whose average is tracing thresh. Signed-off-by: Umesh Tiwari umes...@samsung.com --- kernel/trace/ftrace.c |9 +++-- 1 file changed, 7 insertions(+), 2

[PATCH] ftrace: add tracing_thresh to function profile

From: Himanshu Maithani This patch extends tracing_thresh functionality to function profile tracer. If tracing_thresh is set, print those entries only, whose average is > tracing thresh. Signed-off-by: Umesh Tiwari --- kernel/trace/ftrace.c | 10 -- 1 file changed, 8 inserti

[PATCH] ftrace: correct the counter increment for trace_buffer data

In ftrace_dump, for disabling buffer, iter.tr->trace_buffer.data is used. But for enabling, iter.trace_buffer->data is used. Even though, both point to same buffer, for readability, same convention should be used. Signed-off-by: Umesh Tiwari --- kernel/trace/trace.c |2 +- 1 file chan

[PATCH] ftrace: correct the counter increment for trace_buffer data

In ftrace_dump, for disabling buffer, iter.tr-trace_buffer.data is used. But for enabling, iter.trace_buffer-data is used. Even though, both point to same buffer, for readability, same convention should be used. Signed-off-by: Umesh Tiwari umes...@samsung.com --- kernel/trace/trace.c |2

[PATCH] ftrace: add tracing_thresh to function profile

From: Himanshu Maithani himansh...@samsung.com This patch extends tracing_thresh functionality to function profile tracer. If tracing_thresh is set, print those entries only, whose average is tracing thresh. Signed-off-by: Umesh Tiwari umes...@samsung.com --- kernel/trace/ftrace.c | 10

kernel Error

net/ipv4/tcp.c (1348) KERNEL: assertion (flags & MSG_PEEK) failed at net/ipv4/tcp.c (1284) Umesh - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

kernel Error

(flags MSG_PEEK) failed at net/ipv4/tcp.c (1284) Umesh - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/