From: Jeff Dike <jdike@addtoit.com>
To: John Reiser <jreiser@BitWagon.com>
Cc: valgrind-developers@lists.sourceforge.net,
user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] running UserModeLinux under Valgrind(memcheck)
Date: Wed, 2 Jan 2008 10:28:38 -0500 [thread overview]
Message-ID: <20080102152838.GA5629@c2.user-mode-linux.org> (raw)
In-Reply-To: <477AAFA1.9060807@BitWagon.com>
On Tue, Jan 01, 2008 at 01:24:49PM -0800, John Reiser wrote:
> The web page http://bitwagon.com/valgrind+uml/index.html
> now exists with news, history, commentary, scripts, links
> on getting User Mode Linux for i686 to run under memcheck on i686.
You refer to kmalloc and kfree as keeping object state intact between
kfree and kmalloc, thus not being semantically the same as malloc and
free. However, this is true of kmem_cache_alloc and kmem_cache_free,
not kmalloc and kfree.
Object contents are destroyed between kfree and kmalloc.
As far as kmem_cache_alloc and kmem_cache_free are concerned, would it
work to say that they are like malloc and free, except that if there's
a constructor, it is always called before kmem_cache_alloc returns?
Jeff
--
Work email - jdike at linux dot intel dot com
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2008-01-02 15:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-27 18:38 [uml-devel] running UserModeLinux under Valgrind(memcheck) John Reiser
2007-12-27 19:55 ` [uml-devel] [Valgrind-developers] " Michael Abshoff
2008-01-01 2:00 ` [uml-devel] " Jeff Dike
2008-01-01 21:24 ` John Reiser
2008-01-02 15:28 ` Jeff Dike [this message]
2008-01-02 22:42 ` John Reiser
2008-01-03 5:18 ` Jeff Dike
2008-01-03 16:08 ` Geert Uytterhoeven
2008-01-04 16:37 ` Jeff Dike
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080102152838.GA5629@c2.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=jreiser@BitWagon.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
--cc=valgrind-developers@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.