From: Julien Grall <julien.grall@linaro.org>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: xen-devel@lists.xenproject.org, tim@xen.org,
ian.campbell@citrix.com, stefano.stabellini@citrix.com
Subject: Re: [PATCH for-4.5] xen/arm: Correct the opcode for BUG_INSTR on arm32
Date: Fri, 05 Dec 2014 10:53:00 +0000 [thread overview]
Message-ID: <54818E8C.3060004@linaro.org> (raw)
In-Reply-To: <20141204193434.GB6225@laptop.dumpdata.com>
Hi Konrad,
On 04/12/2014 19:34, Konrad Rzeszutek Wilk wrote:
> On Thu, Dec 04, 2014 at 07:26:55PM +0000, Julien Grall wrote:
>> A 0 was forgotten when the arm32 BUG instruction opcode has been added in commit
>> 3e802c6ca1fb9a9549258c2855a57cad483f3cbd "xen/arm: Correctly support WARN_ON".
>>
>> This will result to use a valid instruction (mcreq 0, 3, r0, cr15, cr0, {7}),
>> and inhibit usage of BUG/WARN_ON and co.
>>
>> Signed-off-by: Julien Grall <julien.grall@linaro.org>
>>
>> ---
>>
>> Not sure, why I dropped the 0 when I implemented the patch...
>> This is a bug fixed for Xen 4.5. This is only affected ARM32 where the
>> BUG opcode was malformed.
>>
>> With the malformed opcode, the ASSERT/BUG_ON is skipped and the
>> processor may execute another patch (because the compiler has optimized
>
> s/patch/path/ ?
Yes.
>> due the unreachable in both macro).
>>
>> The code modified is only executed when Xen is in bad state.
>
> Release-Acked-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Thanks!
Regards,
--
Julien Grall
next prev parent reply other threads:[~2014-12-05 10:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-04 19:26 [PATCH for-4.5] xen/arm: Correct the opcode for BUG_INSTR on arm32 Julien Grall
2014-12-04 19:34 ` Konrad Rzeszutek Wilk
2014-12-05 10:53 ` Julien Grall [this message]
2014-12-05 10:54 ` Ian Campbell
2014-12-09 15:06 ` Ian Campbell
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=54818E8C.3060004@linaro.org \
--to=julien.grall@linaro.org \
--cc=ian.campbell@citrix.com \
--cc=konrad.wilk@oracle.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.