Displaying 3 results from an estimated 3 matches for "dumpinfo".
Did you mean:
drm_info
2007 May 29
0
Fw: [RFC] makedumpfile: xen extraction
...e/oda/makedumpfile-1.1.3/ia64.c,v
retrieving revision 1.1
retrieving revision 1.6
diff -u -r1.1 -r1.6
--- ia64.c 26 Apr 2007 02:32:30 -0000 1.1
+++ ia64.c 27 May 2007 23:46:07 -0000 1.6
@@ -48,5 +48,94 @@
return TRUE;
}
+/*
+ * for Xen extraction
+ */
+unsigned long long
+kvtop_xen_ia64(struct DumpInfo *info, unsigned long kvaddr)
+{
+ unsigned long long addr, dirp, entry;
+
+ if (!is_xen_vaddr(kvaddr))
+ return 0;
+
+ if (is_direct(kvaddr))
+ return (unsigned long)kvaddr - DIRECTMAP_VIRT_START;
+
+ if (!is_frame_table_vaddr(kvaddr))
+ return 0;
+
+ addr = kvaddr - VIRT_FRAME_TABLE_ADDR;
+
+ d...
2010 Apr 06
2
[LLVMdev] Get the loop trip count variable
...a pointer to a
Value object), then, I can instrument some code at the IR level to
dump V. As long as I maintain V at this pass stage, I should be able
to dump the loop trip count. This is true, isn't it?
Basically, what I am going to do is to add a function call before the
loop body, such as:
dumpInfo(FILE_NAME, LINE_NUMBER, VALUE_TYPE, Value)
...
for (int i=0; i<num; i++)
of course, this may have some side effects. If the trip count is a
function call, and I need to rewrite the loop header to avoid calling
the function twice. For example, if the loop header is:
for (int i=0; i<foo(a,b,c...
2010 Apr 06
0
[LLVMdev] Get the loop trip count variable
...n, I can instrument some code at the IR level to
> dump V. As long as I maintain V at this pass stage, I should be able
> to dump the loop trip count. This is true, isn't it?
>
> Basically, what I am going to do is to add a function call before the
> loop body, such as:
>
> dumpInfo(FILE_NAME, LINE_NUMBER, VALUE_TYPE, Value)
> ...
> for (int i=0; i<num; i++)
>
> of course, this may have some side effects. If the trip count is a
> function call, and I need to rewrite the loop header to avoid calling
> the function twice. For example, if the loop header is:...