From: Julien Grall <julien.grall@linaro.org>
To: "Andrew Cooper" <andrew.cooper3@citrix.com>,
"Mihai Donțu" <mdontu@bitdefender.com>,
xen-devel@lists.xen.org
Cc: keir@xen.org, ian.jackson@eu.citrix.com, ian.campbell@citrix.com,
jbeulich@suse.com, tim@xen.org
Subject: Re: [PATCH v4] xmalloc: add support for checking the pool integrity
Date: Wed, 17 Dec 2014 10:24:20 +0000 [thread overview]
Message-ID: <549159D4.2040304@linaro.org> (raw)
In-Reply-To: <549156C1.5000708@citrix.com>
On 17/12/2014 10:11, Andrew Cooper wrote:
> On 16/12/14 23:37, Julien Grall wrote:
> Introducing a new bugframe is precicely what I meant by "this doesn't
> look hard". x86 currently has one more bugframe than arm, being
> BUGFRAME_run_fn.
And how do you pass the pointer of the function? As I said, ARM lacks of
%c because of compiler issue.
I'm out of idea on how to do simply on ARM. Let me know if you have a
good solution.
What I meant with introduce a new bug frame adding BUGFRAM_dump_stack.
Regards,
--
Julien Grall
next prev parent reply other threads:[~2014-12-17 10:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-16 19:33 [PATCH v4] xmalloc: add support for checking the pool integrity Mihai Donțu
2014-12-16 20:28 ` Andrew Cooper
2014-12-16 23:06 ` Julien Grall
2014-12-16 23:26 ` Andrew Cooper
2014-12-16 23:37 ` Julien Grall
2014-12-17 10:11 ` Andrew Cooper
2014-12-17 10:24 ` Julien Grall [this message]
2014-12-17 10:39 ` Andrew Cooper
2014-12-17 10:40 ` Jan Beulich
2014-12-17 12:46 ` Julien Grall
2014-12-17 9:59 ` Jan Beulich
2014-12-17 10:08 ` Andrew Cooper
2014-12-17 10:22 ` Jan Beulich
2015-01-07 15:41 ` Jan Beulich
2015-01-07 15:52 ` Andrew Cooper
2015-01-07 19:20 ` Andrew Cooper
2015-05-12 18:14 ` Mihai Donțu
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=549159D4.2040304@linaro.org \
--to=julien.grall@linaro.org \
--cc=andrew.cooper3@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=keir@xen.org \
--cc=mdontu@bitdefender.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xen.org \
/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.