From: Dirk Behme <dirk.behme@gmx.de>
To: Ian Campbell <ian.campbell@citrix.com>, xen-devel@lists.xen.org
Cc: Dirk Behme <dirk.behme@de.bosch.com>, Dirk Behme <dirk.behme@gmail.com>
Subject: Re: [PATCH] xen/arm64: Make sure we get all debug output
Date: Wed, 17 Feb 2016 17:49:10 +0100 [thread overview]
Message-ID: <56C4A486.4000102@gmx.de> (raw)
In-Reply-To: <56B3856B.7080303@gmail.com>
On 04.02.2016 18:07, Dirk Behme wrote:
> On 04.02.2016 18:00, Ian Campbell wrote:
>> On Thu, 2016-02-04 at 17:49 +0100, Dirk Behme wrote:
>>> From: Dirk Behme <dirk.behme@de.bosch.com>
>>>
>>> Starting in the wrong ELx mode I get the following debug output:
>>>
>>> ...
>>> - Current EL 00000004 -
>>> - Xen must be entered in NS EL2 mode -
>>> - Boot failed -
>>>
>>> The output of "Please update the bootloader" is missing here.
>>>
>>> Make sure this is output, too. With this, we get
>>>
>>> ...
>>> - Current EL 00000004 -
>>> - Xen must be entered in NS EL2 mode -
>>> - Please update the bootloader -
>>> - Boot failed -
>>>
>>> as intended.
>>
>> Ah, this is because gas does not concatenate strings in the same way
>> as C,
>> i.e. in C:
>> "A" "B" "C"
>>
>> becomes 'A', 'B', 'C', '\0'
>>
>> while in gas it becomes 'A', '\0', 'B', '\0', 'C', '\0'
>>
>> I'd like to modify the "...is missing here" above to go a bit further:
>>
>> ...is missing here, because string concatenation in gas, unlike
>> in C,
>> keeps the \0 between each individual string.
>>
>> Would that be OK with you? (I can do it on commit if you are happy
>> with it)
>
>
> Sure, fine with me :)
Could this be applied, then?
Best regards
Dirk
>>>
>>> Signed-off-by: Dirk Behme <dirk.behme@de.bosch.com>
>>> ---
>>> xen/arch/arm/arm64/head.S | 4 ++--
>>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/xen/arch/arm/arm64/head.S b/xen/arch/arm/arm64/head.S
>>> index 9ed9a93..19fa2bb 100644
>>> --- a/xen/arch/arm/arm64/head.S
>>> +++ b/xen/arch/arm/arm64/head.S
>>> @@ -309,8 +309,8 @@ common_start:
>>> b.eq el2 /* Yes */
>>>
>>> /* OK, we're boned. */
>>> - PRINT("- Xen must be entered in NS EL2 mode -\r\n" \
>>> - "- Please update the bootloader -\r\n")
>>> + PRINT("- Xen must be entered in NS EL2 mode -\r\n")
>>> + PRINT("- Please update the bootloader -\r\n")
>>> b fail
>>>
>>> el2: PRINT("- Xen starting at EL2 -\r\n")
>>
>
next prev parent reply other threads:[~2016-02-17 16:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-04 16:49 [PATCH] xen/arm64: Make sure we get all debug output Dirk Behme
2016-02-04 17:00 ` Ian Campbell
2016-02-04 17:07 ` Dirk Behme
2016-02-17 16:49 ` Dirk Behme [this message]
2016-02-18 10:15 ` Ian Campbell
2016-02-18 10:21 ` Jan Beulich
2016-02-19 17:13 ` Ian Jackson
2016-02-19 17:16 ` Jan Beulich
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=56C4A486.4000102@gmx.de \
--to=dirk.behme@gmx.de \
--cc=dirk.behme@de.bosch.com \
--cc=dirk.behme@gmail.com \
--cc=ian.campbell@citrix.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).