hellokitty
2011-Jul-15 02:42 UTC
[Xen-devel] How to use valgrind to detect xen hypervisor''s memory leak
Hi all,
Thanks to Ian Campbell, I am a student and now i am doing a research
about using valgrind to detect xen hypervisor''s memory leak .
The procedure of my detection is as follows:
First I follow the patch
http://xen.1045712.n5.nabble.com/PATCHv2-valgrind-support-for-Xen-privcmd-ioctls-hypercalls-tc2640861.html#a4568310
to let valgrind support Xen privcmd/hypercall.
Second I compile the source code of valgrind (have patched the upper
patch)
Third I use the valgrind tool to detect the hypervisor''s memory
leak .
And the issues now i have are as follows:
1 , Now i come to second step , and i run the commands to compile the
source code :
1) ./configure --with-xen=/usr/include/xen/
2) make && make install
here i encounter the following error messages, how to fix it ?
--------------------------------------------------------------------------------------
echo "# This is a generated file, composed of the following suppression
rules:" > default.supp
echo "# " exp-ptrcheck.supp xfree-3.supp xfree-4.supp
glibc-2.X-drd.supp
glibc-2.34567-NPTL-helgrind.supp glibc-2.X.supp >> default.supp
cat exp-ptrcheck.supp xfree-3.supp xfree-4.supp glibc-2.X-drd.supp
glibc-2.34567-NPTL-helgrind.supp glibc-2.X.supp >> default.supp
make all-recursive
make[1]: Entering directory `/home/popo/valgrind-3.6.1''
Making all in include
make[2]: Entering directory `/home/popo/valgrind-3.6.1/include''
make[2]: Nothing to be done for `all''.
make[2]: Leaving directory `/home/popo/valgrind-3.6.1/include''
Making all in VEX
make[2]: Entering directory `/home/popo/valgrind-3.6.1/VEX''
make all-am
make[3]: Entering directory `/home/popo/valgrind-3.6.1/VEX''
make[3]: Nothing to be done for `all-am''.
make[3]: Leaving directory `/home/popo/valgrind-3.6.1/VEX''
make[2]: Leaving directory `/home/popo/valgrind-3.6.1/VEX''
Making all in coregrind
make[2]: Entering directory `/home/popo/valgrind-3.6.1/coregrind''
make all-am
make[3]: Entering directory `/home/popo/valgrind-3.6.1/coregrind''
gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I../include -I../VEX/pub -DVGA_x86=1
-DVGO_linux=1 -DVGP_x86_linux=1 -I../coregrind
-DVG_LIBDIR="\"/usr/local/lib/valgrind"\"
-DVG_PLATFORM="\"x86-linux\""
-m32 -mpreferred-stack-boundary=2 -O2 -g -Wall -Wmissing-prototypes
-Wshadow
-Wpointer-arith -Wstrict-prototypes -Wmissing-declarations
-Wno-format-zero-length -fno-strict-aliasing @XEN_CFLAGS@ -Wno-long-long
-Wno-pointer-sign -fno-stack-protector -MT
libcoregrind_x86_linux_a-m_debuglog.o -MD -MP -MF
.deps/libcoregrind_x86_linux_a-m_debuglog.Tpo -c -o
libcoregrind_x86_linux_a-m_debuglog.o `test -f
''m_debuglog.c'' || echo
''./''`m_debuglog.c
gcc: @XEN_CFLAGS@ïŒdoesn''t exist the file or directory
make[3]: *** [libcoregrind_x86_linux_a-m_debuglog.o] error 1
make[3]: Leaving directory `/home/popo/valgrind-3.6.1/coregrind''
make[2]: *** [all] error 2
make[2]: Leaving directory `/home/popo/valgrind-3.6.1/coregrind''
make[1]: *** [all-recursive] error 1
make[1]: Leaving directory `/home/popo/valgrind-3.6.1''
make: *** [all] error 2
--------------------------------------------------------------------------------------
2, Suppose that i come to the third step, is it right to use the command
to do the detection ?
"valgrind --tool=memcheck --leak-check=yes ./xen" (here xen is
the
binary file compiled by the source code of xen_4.0.1)
3,Does anyone here ever detect the xen hypervisor''s memory leak
before ? Does someone have the valgrind tool support for hypervisor well ,
can you send me one ?
Thank You & Best Wishes !
--
View this message in context:
http://xen.1045712.n5.nabble.com/How-to-use-valgrind-to-detect-xen-hypervisor-s-memory-leak-tp4589174p4589174.html
Sent from the Xen - Dev mailing list archive at Nabble.com.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Ian Campbell
2011-Jul-15 07:19 UTC
Re: [Xen-devel] How to use valgrind to detect xen hypervisor''s memory leak
On Fri, 2011-07-15 at 03:42 +0100, hellokitty wrote:> Hi all, > Thanks to Ian Campbell, I am a student and now i am doing a research > about using valgrind to detect xen hypervisor''s memory leak . > The procedure of my detection is as follows: > First I follow the patch > http://xen.1045712.n5.nabble.com/PATCHv2-valgrind-support-for-Xen-privcmd-ioctls-hypercalls-tc2640861.html#a4568310 > to let valgrind support Xen privcmd/hypercall. > Second I compile the source code of valgrind (have patched the upper > patch)Please post your modified version of the patch.> Third I use the valgrind tool to detect the hypervisor''s memory leak . > > And the issues now i have are as follows: > 1 , Now i come to second step , and i run the commands to compile the > source code :You seem to have missed step 0) which is to regenerate configure and Makefile.* using autoconf/automake as I described in a previous mail.> 1) ./configure --with-xen=/usr/include/xen/ > 2) make && make install > here i encounter the following error messages, how to fix it ? > > --------------------------------------------------------------------------------------[..]> gcc: @XEN_CFLAGS@ïŒdoesn''t exist the file or directoryThe configure script should have substituted this out, but if you didn''t regenerate it after apply the patch then it won''t know to do this.> [...]> -------------------------------------------------------------------------------------- > 2, Suppose that i come to the third step, is it right to use the command > to do the detection ? > "valgrind --tool=memcheck --leak-check=yes ./xen" (here xen is the > binary file compiled by the source code of xen_4.0.1)Wait, are you trying to use valgrind on the hypervisor itself? The Xen hypervisor is an "Operating System" and runs on bare metal -- you can''t run it as a process under Linux and therefore you cannot run a tool like valgrind on it. The valgrind support in my patch is useful for debugging the Xen toolstack (e.g. "xl"), but not the hypervisor itself.> 3,Does anyone here ever detect the xen hypervisor''s memory leak > before ? Does someone have the valgrind tool support for hypervisor well , > can you send me one ?Either Valgrind or Xen does not work how you seem to think it works. I think you should consult with your advisor before trying to progress this approach any further. You might want to investigate the Linux kernel''s "kmemleak" stuff, I suppose something like that could be ported to Xen (although I expect it to be a non-trivial amount of work). Ian. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
hellokitty
2011-Jul-15 09:15 UTC
[Xen-devel] Re: How to use valgrind to detect xen hypervisor''s memory leak
> Please post your modified version of the patch.My patch is in the attach file named xen_patch.patch http://xen.1045712.n5.nabble.com/file/n4589993/xen_patch.patch xen_patch.patch> You seem to have missed step 0) which is to regenerate configure and > Makefile.* using autoconf/automake as I described in a previous mail.Oh , here before i run 1) ./configure --with-xen=/usr/include/xen/ && 2) make && make install i had run automake/autoconf tool , and the errors still like what i got . So how to fix it ?> Wait, are you trying to use valgrind on the hypervisor itself? > The Xen hypervisor is an "Operating System" and runs on bare metal -- > you can''t run it as a process under Linux and therefore you cannot run a > tool like valgrind on it.> The valgrind support in my patch is useful for debugging the Xen > toolstack (e.g. "xl"), but not the hypervisor itself.Oh , I know that, maybe i didn''t express the right meaning . Now , i am more clearer . Yes , what i want to detect is the Xen toolstack''s memory leak not the hypervisor itself . and so suppose that i come to the third step, is it right to use the command to do the detection ? "valgrind --tool=memcheck --leak-check=yes xm" and more does someone have the valgrind tool support for hypervisor well , can you send me one ? Thank you and best wishes . -- View this message in context: http://xen.1045712.n5.nabble.com/How-to-use-valgrind-to-detect-xen-hypervisor-s-memory-leak-tp4589174p4589993.html Sent from the Xen - Dev mailing list archive at Nabble.com. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Ian Campbell
2011-Jul-15 09:43 UTC
Re: [Xen-devel] Re: How to use valgrind to detect xen hypervisor''s memory leak
On Fri, 2011-07-15 at 10:15 +0100, hellokitty wrote:> > Please post your modified version of the patch. > My patch is in the attach file named xen_patch.patch > http://xen.1045712.n5.nabble.com/file/n4589993/xen_patch.patch > xen_patch.patch > > > You seem to have missed step 0) which is to regenerate configure and > > Makefile.* using autoconf/automake as I described in a previous mail. > Oh , here before i run > 1) ./configure --with-xen=/usr/include/xen/ && > 2) make && make install > i had run automake/autoconf tool , and the errors still like what i got . > So how to fix it ?I''m not sure to be honest. It would help if you would post the actual patch you are using (including your modifications etc). Also which specific baseline valgrind are you using? I''m afraid you will most likely need to roll your sleeves up and get stuck into the build system to figure out why the @XEN_CFLAGS@ macro isn''t getting substituted.> > Wait, are you trying to use valgrind on the hypervisor itself? > > The Xen hypervisor is an "Operating System" and runs on bare metal -- > > you can''t run it as a process under Linux and therefore you cannot run a > > tool like valgrind on it. > > > The valgrind support in my patch is useful for debugging the Xen > > toolstack (e.g. "xl"), but not the hypervisor itself. > > Oh , I know that, maybe i didn''t express the right meaning . Now , i am more > clearer . Yes , what i want to detect is the Xen toolstack''s memory leak not > the hypervisor itself . > > and so suppose that i come to the third step, is it right to use the command > to do the detection ? > "valgrind --tool=memcheck --leak-check=yes xm"I think you can use any of the valgrind options in the normal way. Personally I was using (with xl) --track-origins=yes --trace-children=yes --leak-check=full --show-reachable=yes I''ve not got any experience with running valgrind on python programs but since python is interpreted and garbage collected I expect that what you will actually end up tracking is bugs in the python runtime and what you will miss is any kind of leak due to something not getting garbage collected when you might expect etc. I''m not sure what kind of tools are available for tracking memory "leaks" of this sort in python. (In other words I''m not sure there is much utility to running python programs under valgrind, but I suppose you know different) Note that xm is really just an RPC client to the xend server, so you won''t actually be checking the toolstack by running valgrind on xm, only the client RPC implementation. To actually measure anything useful you would need to measure xend itself (also note that xend is not generally well supported these days and xl is generally preferred for new development). My patch was written to support all the hypercalls done by "xl create" on my specific guest configuration -- you may find you need to implement support within Valgrind for other hypercalls if you step outside this limited usage.> and more does someone have the valgrind tool support for hypervisor well , > can you send me one ?Um, I think I explained in my previous mail why this isn''t possible and that this request doesn''t make sense. (plus you stated right above that you don''t want to do this on the hypervisor!) Ian. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
hellokitty
2011-Jul-15 13:39 UTC
[Xen-devel] Re: How to use valgrind to detect xen hypervisor''s memory leak
> It would help if you would post the actual patch you are using (includingyour modifications etc). Also which specific baseline valgrind are you using? The patch i upload is the actual one i am using , and i just modify some lines that do not match the valgrind source code . such as 1608 of "@@ -1608,6 +1608,11 @@ " , and the version of valgrind is 3.6.1 . Thanks to your advise , now i know i should focus on the detection of xend(xl create) , but first i have to use the upload patch to build in the source code of valgrind , but that''s the point , and i can''t fix it . sigh...> and more does someone have the valgrind tool support for hypervisor well , > can you send me one ?> Um, I think I explained in my previous mail why this isn''t possible and > that this request doesn''t make senseSorry , i know the discipline , and but can you tell me your version of valgrind according to your patch ?? Thank you and Best Wishes! -- View this message in context: http://xen.1045712.n5.nabble.com/How-to-use-valgrind-to-detect-xen-hypervisor-s-memory-leak-tp4589174p4590704.html Sent from the Xen - Dev mailing list archive at Nabble.com. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Ian Campbell
2011-Jul-15 15:15 UTC
Re: [Xen-devel] Re: How to use valgrind to detect xen hypervisor''s memory leak
On Fri, 2011-07-15 at 14:39 +0100, hellokitty wrote:> > It would help if you would post the actual patch you are using (including > your modifications etc). Also which specific baseline valgrind are you > using? > The patch i uploadupload where? Please post the patch you are using as an attachment to an email on this list.> is the actual one i am using , and i just modify some > lines that do not match the valgrind source code . such as 1608 of "@@ > -1608,6 +1608,11 @@ " , and the version of valgrind is 3.6.1 . > > > Thanks to your advise , now i know i should focus on the detection of > xend(xl create) , but first i have to use the upload patch to build in the > source code of valgrind , but that''s the point , and i can''t fix it . > sigh... > > > and more does someone have the valgrind tool support for hypervisor well , > > can you send me one ? > > > Um, I think I explained in my previous mail why this isn''t possible and > > that this request doesn''t make sense > > Sorry , i know the discipline , and but can you tell me your version of > valgrind according to your patch ??My patch was based on r11231 from the valgrind subversion repository.> > Thank you and Best Wishes! > > -- > View this message in context: http://xen.1045712.n5.nabble.com/How-to-use-valgrind-to-detect-xen-hypervisor-s-memory-leak-tp4589174p4590704.html > Sent from the Xen - Dev mailing list archive at Nabble.com. > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Ian Campbell
2011-Jul-15 15:35 UTC
Re: [Xen-devel] Re: How to use valgrind to detect xen hypervisor''s memory leak
On Fri, 2011-07-15 at 14:39 +0100, hellokitty wrote:> > It would help if you would post the actual patch you are using (including > your modifications etc). Also which specific baseline valgrind are you > using? > The patch i upload is the actual one i am using , and i just modify some > lines that do not match the valgrind source code . such as 1608 of "@@ > -1608,6 +1608,11 @@ " , and the version of valgrind is 3.6.1 .I downloaded 3.6.1, applied the attached patch and ran: aclocal && autoheader && automake -a && autoconf (per the autogen.sh in valgrind SVN) Then I ran: ./configure --with-xen && make and it built fine (since it defaults to looking in /usr/include for headers). I also tried "./configure --with-xen=/usr/include" which also worked. However --with-xen=/usr/include/xen (as you had) did not work because the path is wrong and should not include the final /xen (since the #includes in the code are of the form <xen/thing.h>), although my error messages in this case were not the same as yours. Ian. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
hellokitty
2011-Jul-16 02:33 UTC
[Xen-devel] Re: How to use valgrind to detect xen hypervisor''s memory leak
here is the patch , can''t you receive it ? http://xen.1045712.n5.nabble.com/file/n4592915/xen_patch.patch xen_patch.patch -- View this message in context: http://xen.1045712.n5.nabble.com/How-to-use-valgrind-to-detect-xen-hypervisor-s-memory-leak-tp4589174p4592915.html Sent from the Xen - Dev mailing list archive at Nabble.com. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
hellokitty
2011-Jul-16 06:19 UTC
[Xen-devel] Re: How to use valgrind to detect xen hypervisor''s memory leak
> I downloaded 3.6.1, applied the attached patch and ran: > aclocal && autoheader && automake -a && autoconf (per the autogen.sh in > valgrind SVN) > Then I ran: > ./configure --with-xen && make > and it built fine (since it defaults to looking in /usr/include for > headers). > I also tried "./configure --with-xen=/usr/include" which also worked. > However --with-xen=/usr/include/xen (as you had) did not work because > the path is wrong and should not include the final /xen (since the > #includes in the code are of the form <xen/thing.h>), although my > error > messages in this case were not the same as yours.Here , i follow your step , and use the "X" patch you uploaded , and run "aclocal && autoheader && automake -a && autoconf " ,goes well and then run "./configure --with-xen && make" , and when it comes to make , it has the errors below : Making all in coregrind make[2]: Entering directory `/home/popo/valgrind-3.6.1/coregrind'' make all-am make[3]: Entering directory `/home/popo/valgrind-3.6.1/coregrind'' gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I../include -I../VEX/pub -DVGA_x86=1 -DVGO_linux=1 -DVGP_x86_linux=1 -I../coregrind -DVG_LIBDIR="\"/usr/local/lib/valgrind"\" -DVG_PLATFORM="\"x86-linux\"" -m32 -mpreferred-stack-boundary=2 -O2 -g -Wall -Wmissing-prototypes -Wshadow -Wpointer-arith -Wstrict-prototypes -Wmissing-declarations -Wno-format-zero-length -fno-strict-aliasing -Iyes -Wno-long-long -Wno-pointer-sign -fno-stack-protector -MT libcoregrind_x86_linux_a-syswrap-xen.o -MD -MP -MF .deps/libcoregrind_x86_linux_a-syswrap-xen.Tpo -c -o libcoregrind_x86_linux_a-syswrap-xen.o `test -f ''m_syswrap/syswrap-xen.c'' || echo ''./''`m_syswrap/syswrap-xen.c m_syswrap/syswrap-xen.c: In function ‘vgSysWrap_xen_ioctl_privcmd_hypercall_before’: m_syswrap/syswrap-xen.c:119: error: ‘MMUEXT_MARK_SUPER’ undeclared (first use in this function) m_syswrap/syswrap-xen.c:119: error: (Each undeclared identifier is reported only once m_syswrap/syswrap-xen.c:119: error: for each function it appears in.) m_syswrap/syswrap-xen.c:120: error: ‘MMUEXT_UNMARK_SUPER’ undeclared (first use in this function) m_syswrap/syswrap-xen.c:136: error: ‘MMUEXT_FLUSH_CACHE_GLOBAL’ undeclared (first use in this function) m_syswrap/syswrap-xen.c:263: error: ‘XEN_SYSCTL_cpupool_op’ undeclared (first use in this function) m_syswrap/syswrap-xen.c:264: error: ‘union <anonymous>’ has no member named ‘cpupool_op’ m_syswrap/syswrap-xen.c:264: error: ‘union <anonymous>’ has no member named ‘cpupool_op’ m_syswrap/syswrap-xen.c:266: error: ‘union <anonymous>’ has no member named ‘cpupool_op’ m_syswrap/syswrap-xen.c:267: error: ‘XEN_SYSCTL_CPUPOOL_OP_CREATE’ undeclared (first use in this function) m_syswrap/syswrap-xen.c:268: error: ‘XEN_SYSCTL_CPUPOOL_OP_DESTROY’ undeclared (first use in this function) m_syswrap/syswrap-xen.c:269: error: ‘XEN_SYSCTL_CPUPOOL_OP_INFO’ undeclared (first use in this function) m_syswrap/syswrap-xen.c:270: error: ‘XEN_SYSCTL_CPUPOOL_OP_ADDCPU’ undeclared (first use in this function) m_syswrap/syswrap-xen.c:271: error: ‘XEN_SYSCTL_CPUPOOL_OP_RMCPU’ undeclared (first use in this function) m_syswrap/syswrap-xen.c:272: error: ‘XEN_SYSCTL_CPUPOOL_OP_MOVEDOMAIN’ undeclared (first use in this function) m_syswrap/syswrap-xen.c:273: error: ‘union <anonymous>’ has no member named ‘cpupool_op’ m_syswrap/syswrap-xen.c:273: error: ‘union <anonymous>’ has no member named ‘cpupool_op’ m_syswrap/syswrap-xen.c:276: error: ‘union <anonymous>’ has no member named ‘cpupool_op’ m_syswrap/syswrap-xen.c:277: error: ‘union <anonymous>’ has no member named ‘cpupool_op’ m_syswrap/syswrap-xen.c:277: error: ‘union <anonymous>’ has no member named ‘cpupool_op’ m_syswrap/syswrap-xen.c:279: error: ‘union <anonymous>’ has no member named ‘cpupool_op’ m_syswrap/syswrap-xen.c:280: error: ‘union <anonymous>’ has no member named ‘cpupool_op’ m_syswrap/syswrap-xen.c:280: error: ‘union <anonymous>’ has no member named ‘cpupool_op’ m_syswrap/syswrap-xen.c:282: error: ‘union <anonymous>’ has no member named ‘cpupool_op’ m_syswrap/syswrap-xen.c:283: error: ‘union <anonymous>’ has no member named ‘cpupool_op’ m_syswrap/syswrap-xen.c:284: error: ‘union <anonymous>’ has no member named ‘cpupool_op’ m_syswrap/syswrap-xen.c:284: error: ‘union <anonymous>’ has no member named ‘cpupool_op’ m_syswrap/syswrap-xen.c: In function ‘vgSysWrap_xen_ioctl_privcmd_hypercall_after’: m_syswrap/syswrap-xen.c:558: error: ‘XEN_SYSCTL_cpupool_op’ undeclared (first use in this function) m_syswrap/syswrap-xen.c:559: error: ‘union <anonymous>’ has no member named ‘cpupool_op’ m_syswrap/syswrap-xen.c:559: error: ‘XEN_SYSCTL_CPUPOOL_OP_CREATE’ undeclared (first use in this function) m_syswrap/syswrap-xen.c:560: error: ‘union <anonymous>’ has no member named ‘cpupool_op’ m_syswrap/syswrap-xen.c:560: error: ‘XEN_SYSCTL_CPUPOOL_OP_INFO’ undeclared (first use in this function) m_syswrap/syswrap-xen.c:561: error: ‘union <anonymous>’ has no member named ‘cpupool_op’ m_syswrap/syswrap-xen.c:561: error: ‘union <anonymous>’ has no member named ‘cpupool_op’ m_syswrap/syswrap-xen.c:562: error: ‘union <anonymous>’ has no member named ‘cpupool_op’ m_syswrap/syswrap-xen.c:563: error: ‘union <anonymous>’ has no member named ‘cpupool_op’ m_syswrap/syswrap-xen.c:563: error: ‘union <anonymous>’ has no member named ‘cpupool_op’ m_syswrap/syswrap-xen.c:564: error: ‘union <anonymous>’ has no member named ‘cpupool_op’ m_syswrap/syswrap-xen.c:564: error: ‘union <anonymous>’ has no member named ‘cpupool_op’ m_syswrap/syswrap-xen.c:566: error: ‘union <anonymous>’ has no member named ‘cpupool_op’ m_syswrap/syswrap-xen.c:567: error: ‘union <anonymous>’ has no member named ‘cpupool_op’ m_syswrap/syswrap-xen.c:567: error: ‘XEN_SYSCTL_CPUPOOL_OP_FREEINFO’ undeclared (first use in this function) m_syswrap/syswrap-xen.c:568: error: ‘union <anonymous>’ has no member named ‘cpupool_op’ m_syswrap/syswrap-xen.c:568: error: ‘union <anonymous>’ has no member named ‘cpupool_op’ m_syswrap/syswrap-xen.c:576: error: ‘struct xen_sysctl_physinfo’ has no member named ‘nr_nodes’ m_syswrap/syswrap-xen.c:576: error: ‘struct xen_sysctl_physinfo’ has no member named ‘nr_nodes’ m_syswrap/syswrap-xen.c:658: error: ‘struct xen_domctl_getdomaininfo’ has no member named ‘cpupool’ m_syswrap/syswrap-xen.c:658: error: ‘struct xen_domctl_getdomaininfo’ has no member named ‘cpupool’ make[3]: *** [libcoregrind_x86_linux_a-syswrap-xen.o] Error 1 make[3]: Leaving directory `/home/popo/valgrind-3.6.1/coregrind'' make[2]: *** [all] Error 2 make[2]: Leaving directory `/home/popo/valgrind-3.6.1/coregrind'' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/popo/valgrind-3.6.1'' make: *** [all] Error 2 How about you ? and i don''t know how to fix it yet ..... -- View this message in context: http://xen.1045712.n5.nabble.com/How-to-use-valgrind-to-detect-xen-hypervisor-s-memory-leak-tp4589174p4593243.html Sent from the Xen - Dev mailing list archive at Nabble.com. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Ian Campbell
2011-Jul-16 06:23 UTC
Re: [Xen-devel] Re: How to use valgrind to detect xen hypervisor''s memory leak
On Sat, 2011-07-16 at 07:19 +0100, hellokitty wrote:> ‘vgSysWrap_xen_ioctl_privcmd_hypercall_before’: > m_syswrap/syswrap-xen.c:119: error: ‘MMUEXT_MARK_SUPER’ undeclared (first > use in this function)The patch requires Xen 4.1 or later. Ian. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
hellokitty
2011-Jul-16 06:40 UTC
[Xen-devel] Re: How to use valgrind to detect xen hypervisor''s memory leak
> The patch requires Xen 4.1 or later.So in all , the problem is the version problem ? and do you have the patch for valgrind requires Xen 3.3.0 ? -- View this message in context: http://xen.1045712.n5.nabble.com/How-to-use-valgrind-to-detect-xen-hypervisor-s-memory-leak-tp4589174p4593261.html Sent from the Xen - Dev mailing list archive at Nabble.com. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Ian Campbell
2011-Jul-16 06:43 UTC
Re: [Xen-devel] Re: How to use valgrind to detect xen hypervisor''s memory leak
On Sat, 2011-07-16 at 07:40 +0100, hellokitty wrote:> > The patch requires Xen 4.1 or later. > So in all , the problem is the version problem ? and do you have the patch > for valgrind requires Xen 3.3.0 ?No I don''t. 3.3.0 is a pretty ancient version of Xen (released in 2008, 3 major releases ago). If you don''t want to base your work on something newer then I''m afraid you will need to backport the patch yourself. Ian.> > -- > View this message in context: http://xen.1045712.n5.nabble.com/How-to-use-valgrind-to-detect-xen-hypervisor-s-memory-leak-tp4589174p4593261.html > Sent from the Xen - Dev mailing list archive at Nabble.com. > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
hellokitty
2011-Jul-16 15:24 UTC
[Xen-devel] Re: How to use valgrind to detect xen hypervisor''s memory leak
Thank you lan , finally i get the Xen 4.1.1 version and patch the valgrind using your attach "X" and it works !! Thank you so much , now i can use the new valgrind to do the work well ! Thank you . -- View this message in context: http://xen.1045712.n5.nabble.com/How-to-use-valgrind-to-detect-xen-hypervisor-s-memory-leak-tp4589174p4594076.html Sent from the Xen - Dev mailing list archive at Nabble.com. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel