How about change the filter_fn to follow:
static bool fsl_edma_filter_fn(struct dma_chan *chan, void *fn_param)
{
struct fsl_edma_filter_param *fparam = fn_param;
struct fsl_edma_chan *fsl_chan = to_fsl_edma_chan(chan);
unsigned char val;
if
From: Namhyung Kim namhyung@lge.com
The set_print_fmt() functions are implemented almost same for
[ku]probes. Move it to a common place and get rid of the duplication.
Acked-by: Masami Hiramatsu masami.hiramatsu...@hitachi.com
Cc: Srikar Dronamraju sri...@linux.vnet.ibm.com
Cc: Oleg
From: Namhyung Kim namhyung@lge.com
Implement uprobe-specific stack and memory fetch functions and add
them to the uprobes_fetch_type_table. Other fetch fucntions will be
shared with kprobes.
Original-patch-by: Hyeoncheol Lee cheol@lge.com
Reviewed-by: Masami Hiramatsu
From: Namhyung Kim namhyung@lge.com
Enable to fetch other types of argument for the uprobes. IOW, we can
access stack, memory, deref, bitfield and retval from uprobes now.
The format for the argument types are same as kprobes (but @SYMBOL
type is not supported for uprobes), i.e:
@ADDR
From: Namhyung Kim namhyung@lge.com
Convert struct trace_uprobe to make use of the common trace_probe
structure.
Reviewed-by: Masami Hiramatsu masami.hiramatsu...@hitachi.com
Cc: Srikar Dronamraju sri...@linux.vnet.ibm.com
Cc: Oleg Nesterov o...@redhat.com
Cc: zhangwei(Jovi)
From: Namhyung Kim namhyung@lge.com
There are functions that can be shared to both of kprobes and uprobes.
Separate common data structure to struct trace_probe and use it from
the shared functions.
Acked-by: Masami Hiramatsu masami.hiramatsu...@hitachi.com
Cc: Srikar Dronamraju
From: Namhyung Kim namhyung@lge.com
Those fetch functions need to be implemented differently for kprobes
and uprobes. Since the deref fetch functions don't call those
directly anymore, we can make them static and implement them
separately.
Acked-by: Masami Hiramatsu
From: Namhyung Kim namhyung@lge.com
This argument is for passing private data structure to each fetch
function and will be used by uprobes.
Acked-by: Masami Hiramatsu masami.hiramatsu...@hitachi.com
Cc: Srikar Dronamraju sri...@linux.vnet.ibm.com
Cc: Oleg Nesterov o...@redhat.com
Cc:
Hello,
This patchset implements memory (address), stack[N], deference,
bitfield and retval (it needs uretprobe tho) fetch methods for
uprobes. It's based on the previous work [1] done by Hyeoncheol Lee.
Now kprobes and uprobes have their own fetch_type_tables and, in turn,
memory and stack
From: Namhyung Kim namhyung@lge.com
Fetching from user space should be done in a non-atomic context. So
use a per-cpu buffer and copy its content to the ring buffer
atomically. Note that we can migrate during accessing user memory
thus use a per-cpu mutex to protect concurrent accesses.
From: Namhyung Kim namhyung@lge.com
The print format of s32 type was ld and it's casted to long. So
it turned out to print 4294967295 for -1 on 64-bit systems. Not
sure whether it worked well on 32-bit systems.
Anyway, it'd be better if we have exact format and type cast for each
types on
From: Hyeoncheol Lee cheol@lge.com
Move kprobes-specific fetch functions to the trace_kprobe.c file.
Also define kprobes_fetch_type_table in the .c file. This table is
shared with uprobes for now, but the uprobes will get its own table
in the later patch.
This is a preparation for
From: Namhyung Kim namhyung@lge.com
The uprobe syntax requires an offset after a file path not a symbol.
Reviewed-by: Masami Hiramatsu masami.hiramatsu...@hitachi.com
Cc: Srikar Dronamraju sri...@linux.vnet.ibm.com
Cc: Oleg Nesterov o...@redhat.com
Cc: zhangwei(Jovi) jovi.zhang...@huawei.com
From: Hyeoncheol Lee cheol@lge.com
The deref fetch methods access a memory region but it assumes that
it's a kernel memory since uprobes does not support them.
Add -fetch and -fetch_size member in order to provide a proper
access methods for supporting uprobes.
Acked-by: Masami Hiramatsu
* Arnaldo Carvalho de Melo a...@infradead.org wrote:
From: Arnaldo Carvalho de Melo a...@ghostprotocols.net
Hi Ingo,
Please consider pulling,
- Arnaldo
The following changes since commit 7bfb7e6bdd906f11ee9e751b3fec4f4fc728e818:
perf: Convert kmalloc_node(...GFP_ZERO...)
On Mon, Sep 2, 2013 at 9:45 PM, Zhi Yong Wu zwu.ker...@gmail.com wrote:
On Mon, Sep 2, 2013 at 4:57 PM, Michel Lespinasse wal...@google.com wrote:
Thanks for the link - I now better understand where you are coming
from with these fixes.
Going back to the original message:
diff --git
(2013/08/30 22:15), Srivatsa S. Bhat wrote:
Given a page, we would like to have an efficient mechanism to find out
the node memory region and the zone memory region to which it belongs.
Since the node is assumed to be divided into equal-sized node memory
regions, the node memory region can be
Hello Maintainers:
Maybe... I still miss some important mail addresses? or this patch is
not suitable for applying?
Hmm... but I still want to try the last time: please help check this
patch, when you have time.
And next, I should not send additional tracing mail again, that will be
really
1001 - 1018 of 1018 matches
Mail list logo
