From: Julien Grall <julien.grall@linaro.org>
To: Jan Beulich <JBeulich@suse.com>
Cc: tim@xen.org, keir@xen.org, ian.campbell@citrix.com,
Andrew Cooper <andrew.cooper3@citrix.com>,
mdontu@bitdefender.com, ian.jackson@eu.citrix.com,
xen-devel@lists.xen.org
Subject: Re: [PATCH v4] xmalloc: add support for checking the pool integrity
Date: Wed, 17 Dec 2014 12:46:59 +0000 [thread overview]
Message-ID: <54917B43.5060903@linaro.org> (raw)
In-Reply-To: <54916BB40200007800050317@mail.emea.novell.com>
Hi Jan,
On 17/12/14 10:40, Jan Beulich wrote:
>>>> On 17.12.14 at 11:24, <julien.grall@linaro.org> wrote:
>> 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.
>
> First of all can you explain what compiler issue there is? Both
> {arm,aarch64}_print_operand() handle 'c' (but of course I can't
> tell whether correctly).
This has been added recently on aarch64 (late 2013) and there was an
outstanding bug on some version of GCC for arm
(https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48637)
FYI, the BUG support has been borrowed from Linux.
> And then can't you possibly find ways to deal with the # prefix
> added when not using 'c'? For the section name (if you need the
> section split in the first place) I would think a # should be fine,
> and the uses in expressions can surely be worked around by
> interposing an assembler macro (even if that macro may end up
> looking quite ugly).
We already have a working solution without BUGFRAME_run_fn. See the
implementation in xen/include/asm-arm.h.
I don't plan to work on modifying this code. But I would be happy if
someone post a patch to support BUGFRAME_run_fn.
Regards,
--
Julien Grall
next prev parent reply other threads:[~2014-12-17 12:46 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
2014-12-17 10:39 ` Andrew Cooper
2014-12-17 10:40 ` Jan Beulich
2014-12-17 12:46 ` Julien Grall [this message]
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=54917B43.5060903@linaro.org \
--to=julien.grall@linaro.org \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.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.