All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@linaro.org>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: xen-devel@lists.xenproject.org, tim@xen.org,
	stefano.stabellini@citrix.com
Subject: Re: [PATCH] xen/arm: Correctly support WARN_ON
Date: Thu, 10 Jul 2014 16:07:31 +0100	[thread overview]
Message-ID: <53BEAC33.9000501@linaro.org> (raw)
In-Reply-To: <1405004797.26155.19.camel@kazak.uk.xensource.com>



On 10/07/14 16:06, Ian Campbell wrote:
> On Tue, 2014-07-01 at 19:51 +0100, Julien Grall wrote:
>> Currently the hypervisor will hang if it hits a WARN_ON.
>>
>> The implemention uses an undefined instruction, made ourself because ARM
>> doesn't provide one, to implement BUG/ASSERT/WARN_ON, and sets up the
>> different tables (one for each type) which contain useful information.
>>
>> This is based on the x86 implementation (include/asm-x86/bug.h). Unfortunately
>> the structure can't be shared because many ARM{32,64} gcc versions doesn't
>> correctly support %c. The support of executing a function in an exception handler
>> is also keep unimplemented on ARM.
>>
>> TODO:
>> I haven't yet hook the code on ARM64 as I'm not sure how undefined instruction
>> are handled. It looks like there is multiple way to get it via HSR.
>>
>> Signed-off-by: Julien Grall <julien.grall@linaro.org>
>
> Apart from the lack of arm64 support this looks good to me.

I will try to send a new version with the arm64 support next week.

Regards,

-- 
Julien Grall

      reply	other threads:[~2014-07-10 15:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-01 18:51 [PATCH] xen/arm: Correctly support WARN_ON Julien Grall
2014-07-03 10:30 ` Ian Campbell
2014-07-03 12:33   ` Julien Grall
2014-07-03 13:44     ` Ian Campbell
2014-07-10 15:06 ` Ian Campbell
2014-07-10 15:07   ` Julien Grall [this message]

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=53BEAC33.9000501@linaro.org \
    --to=julien.grall@linaro.org \
    --cc=Ian.Campbell@citrix.com \
    --cc=stefano.stabellini@citrix.com \
    --cc=tim@xen.org \
    --cc=xen-devel@lists.xenproject.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.