All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Orzel <michal.orzel@amd.com>
To: Julien Grall <julien@xen.org>, <xen-devel@lists.xenproject.org>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
	George Dunlap <george.dunlap@citrix.com>,
	Jan Beulich <jbeulich@suse.com>,
	"Stefano Stabellini" <sstabellini@kernel.org>,
	Wei Liu <wl@xen.org>
Subject: Re: [PATCH] SUPPORT.md: clarify support of booting 32-bit Xen on ARMv8
Date: Thu, 29 Feb 2024 13:42:07 +0100	[thread overview]
Message-ID: <216e9119-a7f9-43f3-80f9-f1c15685cad3@amd.com> (raw)
In-Reply-To: <544718e1-4855-4af1-a450-6362a8cd08f0@xen.org>



On 29/02/2024 13:40, Julien Grall wrote:
> 
> 
> On 29/02/2024 12:37, Michal Orzel wrote:
>> Hi Julien,
> 
> Hi Michal,
> 
>>
>> On 29/02/2024 13:35, Julien Grall wrote:
>>> On 29/02/2024 12:13, Michal Orzel wrote:
>>>> Since commit bd1001db0af1 ("xen/arm: arm32: Allow Xen to boot on
>>>> unidentified CPUs"), it's been possible to boot 32-bit Xen on ARMv8A CPUs
>>>> in AArch32 state (assuming HW supports EL2 execution in AArch32). Clarify
>>>> the support statement and mark it as Tech Preview, as this use case is
>>>> uncommon and hasn't really been tested/hardened.
>>>>
>>>> Signed-off-by: Michal Orzel <michal.orzel@amd.com>
>>>> ---
>>>>    SUPPORT.md | 1 +
>>>>    1 file changed, 1 insertion(+)
>>>>
>>>> diff --git a/SUPPORT.md b/SUPPORT.md
>>>> index a90d1108c9d9..acc61230bb5e 100644
>>>> --- a/SUPPORT.md
>>>> +++ b/SUPPORT.md
>>>> @@ -40,6 +40,7 @@ supported in this document.
>>>>        Status: Supported
>>> I would consider to use 'Status, Xen in aarch64 mode: Supported' and then...
>>>
>>>>        Status, Cortex A57 r0p0-r1p1: Supported, not security supported
>>>>        Status, Cortex A77 r0p0-r1p0: Supported, not security supported
>>>> +    Status, Xen in AArch32 mode: Tech Preview
>>>
>>> ... move this line closer. What do you think?
>> That works for me too (+AArch64 instead of aarch64).
> 
> Ah yes. I keep forgetting capitalizing properly :).
> 
>> Shall I respin the patch?
> 
> Up to you. I am happy to fix it. But I will wait a day or two just to
> give a chance for the others to comment.
That works for me, let's wait for Bertrand and Stefano.

~Michal


  reply	other threads:[~2024-02-29 12:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-29 12:13 [PATCH] SUPPORT.md: clarify support of booting 32-bit Xen on ARMv8 Michal Orzel
2024-02-29 12:35 ` Julien Grall
2024-02-29 12:37   ` Michal Orzel
2024-02-29 12:40     ` Julien Grall
2024-02-29 12:42       ` Michal Orzel [this message]
2024-02-29 21:07         ` Stefano Stabellini
2024-03-06  9:40           ` Julien Grall

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=216e9119-a7f9-43f3-80f9-f1c15685cad3@amd.com \
    --to=michal.orzel@amd.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=george.dunlap@citrix.com \
    --cc=jbeulich@suse.com \
    --cc=julien@xen.org \
    --cc=sstabellini@kernel.org \
    --cc=wl@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.