All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Beulich <jbeulich@suse.com>
To: Wei Chen <wei.chen@arm.com>
Cc: nd@arm.com, "Stefano Stabellini" <sstabellini@kernel.org>,
	"Julien Grall" <julien@xen.org>,
	"Bertrand Marquis" <bertrand.marquis@arm.com>,
	"Volodymyr Babchuk" <Volodymyr_Babchuk@epam.com>,
	"Andrew Cooper" <andrew.cooper3@citrix.com>,
	"Roger Pau Monné" <roger.pau@citrix.com>, "Wei Liu" <wl@xen.org>,
	"Jiamei Xie" <jiamei.xie@arm.com>,
	xen-devel@lists.xenproject.org
Subject: Re: [PATCH v6 1/8] xen: reuse x86 EFI stub functions for Arm
Date: Thu, 23 Jun 2022 14:53:53 +0200	[thread overview]
Message-ID: <05dadcda-505d-d46a-776a-bb29b8915815@suse.com> (raw)
In-Reply-To: <20220610055316.2197571-2-wei.chen@arm.com>

On 10.06.2022 07:53, Wei Chen wrote:
> --- a/xen/arch/arm/Makefile
> +++ b/xen/arch/arm/Makefile
> @@ -1,6 +1,5 @@
>  obj-$(CONFIG_ARM_32) += arm32/
>  obj-$(CONFIG_ARM_64) += arm64/
> -obj-$(CONFIG_ARM_64) += efi/
>  obj-$(CONFIG_ACPI) += acpi/
>  obj-$(CONFIG_HAS_PCI) += pci/
>  ifneq ($(CONFIG_NO_PLAT),y)
> @@ -20,6 +19,7 @@ obj-y += domain.o
>  obj-y += domain_build.init.o
>  obj-y += domctl.o
>  obj-$(CONFIG_EARLY_PRINTK) += early_printk.o
> +obj-y += efi/
>  obj-y += gic.o
>  obj-y += gic-v2.o
>  obj-$(CONFIG_GICV3) += gic-v3.o
> --- a/xen/arch/arm/efi/Makefile
> +++ b/xen/arch/arm/efi/Makefile
> @@ -1,4 +1,12 @@
>  include $(srctree)/common/efi/efi-common.mk
>  
> +ifeq ($(CONFIG_ARM_EFI),y)
>  obj-y += $(EFIOBJ-y)
>  obj-$(CONFIG_ACPI) +=  efi-dom0.init.o
> +else
> +# Add stub.o to EFIOBJ-y to re-use the clean-files in
> +# efi-common.mk. Otherwise the link of stub.c in arm/efi
> +# will not be cleaned in "make clean".
> +EFIOBJ-y += stub.o
> +obj-y += stub.o
> +endif

This has caused

ld: warning: arch/arm/efi/built_in.o uses 2-byte wchar_t yet the output is to use 4-byte wchar_t; use of wchar_t values across objects may fail

for the 32-bit Arm build that I keep doing every once in a while, with
(if it matters) GNU ld 2.38. I guess you will want to consider building
all of Xen with -fshort-wchar, or to avoid building stub.c with that
option.

Jan


  reply	other threads:[~2022-06-23 12:54 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-10  5:53 [PATCH v6 0/8] Device tree based NUMA support for Arm - Part#1 Wei Chen
2022-06-10  5:53 ` [PATCH v6 1/8] xen: reuse x86 EFI stub functions for Arm Wei Chen
2022-06-23 12:53   ` Jan Beulich [this message]
2022-06-24  7:18     ` Wei Chen
2022-06-24  8:35       ` Julien Grall
2022-06-24  9:33         ` Jan Beulich
2022-06-24  9:49           ` Julien Grall
2022-06-24 10:05             ` Jan Beulich
2022-06-24 10:09               ` Jan Beulich
2022-06-30 11:25                 ` Wei Chen
2022-06-30 11:37                   ` Wei Chen
2022-06-30 12:36                   ` Jan Beulich
2022-07-01  3:11                     ` Wei Chen
2022-07-01  5:54                       ` Jan Beulich
2022-07-01  6:10                         ` Wei Chen
2022-07-01 10:07                           ` Jan Beulich
2022-07-01  5:57                     ` Jan Beulich
2022-06-28  8:30             ` Wei Chen
2022-06-10  5:53 ` [PATCH v6 2/8] xen/arm: Keep memory nodes in device tree when Xen boots from EFI Wei Chen
2022-06-10  5:53 ` [PATCH v6 3/8] xen: introduce an arch helper for default dma zone status Wei Chen
2022-06-10  5:53 ` [PATCH v6 4/8] xen: decouple NUMA from ACPI in Kconfig Wei Chen
2022-06-10  5:53 ` [PATCH v6 5/8] xen/arm: use !CONFIG_NUMA to keep fake NUMA API Wei Chen
2022-06-10  5:53 ` [PATCH v6 6/8] xen/x86: use paddr_t for addresses in NUMA node structure Wei Chen
2022-06-10  5:53 ` [PATCH v6 7/8] xen/x86: add detection of memory interleaves for different nodes Wei Chen
2022-06-10  5:53 ` [PATCH v6 8/8] xen/x86: use INFO level for node's without memory log message Wei Chen
2022-06-17  8:43 ` [PATCH v6 0/8] Device tree based NUMA support for Arm - Part#1 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=05dadcda-505d-d46a-776a-bb29b8915815@suse.com \
    --to=jbeulich@suse.com \
    --cc=Volodymyr_Babchuk@epam.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=bertrand.marquis@arm.com \
    --cc=jiamei.xie@arm.com \
    --cc=julien@xen.org \
    --cc=nd@arm.com \
    --cc=roger.pau@citrix.com \
    --cc=sstabellini@kernel.org \
    --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.