From: Anthony PERARD <anthony.perard@citrix.com>
To: Luca Fancellu <luca.fancellu@arm.com>
Cc: xen-devel@lists.xenproject.org, bertrand.marquis@arm.com,
wei.chen@arm.com, "Wei Liu" <wl@xen.org>,
"Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>,
"Andrew Cooper" <andrew.cooper3@citrix.com>
Subject: Re: [PATCH 1/2] tools: Fix ifdef for aarch64 that should include also arm
Date: Tue, 4 Jul 2023 10:42:01 +0100 [thread overview]
Message-ID: <66c3d183-460d-4f34-a331-01ac4d65fc9d@perard> (raw)
In-Reply-To: <20230608135913.560413-1-luca.fancellu@arm.com>
On Thu, Jun 08, 2023 at 02:59:12PM +0100, Luca Fancellu wrote:
> Commit 56a7aaa16bfe introduced some SVE related code that is protected by
> '#if defined(__aarch64__)', the issue is that this doesn't take into
> consideration when the toolstack is compiled for an arm32 Dom0 running on
> an arm64 platform, it should be able to create SVE enabled guests but with
> the current code it's not.
>
> So fix the issue by compiling the code when the toolstack is compiled for
> both arm32 and arm64.
>
> Fixes: 56a7aaa16bfe ("tools: add physinfo arch_capabilities handling for Arm")
> Signed-off-by: Luca Fancellu <luca.fancellu@arm.com>
> Reported-by: Andrew Cooper <andrew.cooper3@citrix.com>
Acked-by: Anthony PERARD <anthony.perard@citrix.com>
Thanks,
--
Anthony PERARD
next prev parent reply other threads:[~2023-07-04 9:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-08 13:59 [PATCH 1/2] tools: Fix ifdef for aarch64 that should include also arm Luca Fancellu
2023-06-08 13:59 ` [PATCH 2/2] tools/python: Fix memory leak on error path Luca Fancellu
2023-06-22 9:17 ` Luca Fancellu
2023-06-26 18:07 ` Marek Marczykowski-Górecki
2023-06-27 12:29 ` Marek Marczykowski-Górecki
2023-06-27 17:21 ` Julien Grall
2023-06-22 9:17 ` [PATCH 1/2] tools: Fix ifdef for aarch64 that should include also arm Luca Fancellu
2023-06-26 18:52 ` Marek Marczykowski-Górecki
2023-07-04 9:42 ` Anthony PERARD [this message]
2023-07-04 19:11 ` Julien Grall
2023-07-05 6:26 ` Luca Fancellu
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=66c3d183-460d-4f34-a331-01ac4d65fc9d@perard \
--to=anthony.perard@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=bertrand.marquis@arm.com \
--cc=luca.fancellu@arm.com \
--cc=marmarek@invisiblethingslab.com \
--cc=wei.chen@arm.com \
--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.