From: Andrew Cooper <andrew.cooper3@citrix.com>
To: "Julien Grall" <julien.grall@linaro.org>,
"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: Tue, 16 Dec 2014 23:26:53 +0000 [thread overview]
Message-ID: <5490BFBD.7010809@citrix.com> (raw)
In-Reply-To: <5490BAE4.5070108@linaro.org>
On 16/12/2014 23:06, Julien Grall wrote:
> Hi,
>
> On 16/12/2014 20:28, Andrew Cooper wrote:
>> I suspect you also would be better, and certainly more brief, with
>> "run_in_exception_handler(show_stack)" instead, which will just print a
>> stack trace, but nothing more.
>
> FIY, run_in_exception_handler doesn't exists on ARM.
>
> Regards,
>
In which case it even more lucky that __bug() and __warn() are orphaned
functions, as they don't work correctly on arm. Even more reason to
remove them.
It doesn't look like run_in_exception_handler() would be hard to add to
arm at all. It already has broadly similar bug/warn/assert infrastructure.
~Andrew
next prev parent reply other threads:[~2014-12-16 23:26 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 [this message]
2014-12-16 23:37 ` Julien Grall
2014-12-17 10:11 ` Andrew Cooper
2014-12-17 10:24 ` Julien Grall
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=5490BFBD.7010809@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=julien.grall@linaro.org \
--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.