public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Sami Mujawar" <sami.mujawar@arm.com>
To: Laszlo Ersek <lersek@redhat.com>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "ardb+tianocore@kernel.org" <ardb+tianocore@kernel.org>,
	"quic_llindhol@quicinc.com" <quic_llindhol@quicinc.com>,
	"kraxel@redhat.com" <kraxel@redhat.com>,
	Matteo Carlini <Matteo.Carlini@arm.com>,
	Akanksha Jain <Akanksha.Jain2@arm.com>,
	Sibel Allinson <Sibel.Allinson@arm.com>, nd <nd@arm.com>
Subject: Re: [edk2-devel] [PATCH v3 1/1] CloudHv: Add CI for CloudHv on AArch64
Date: Thu, 14 Dec 2023 13:54:15 +0000	[thread overview]
Message-ID: <BEBCE005-F457-4801-8F1C-3EE531B9D873@arm.com> (raw)
In-Reply-To: <d5d05153-7ec2-49b2-a361-53dd292f54c9@redhat.com>

Hi Laszlo,


On 14/12/2023, 12:28, "Laszlo Ersek" <lersek@redhat.com <mailto:lersek@redhat.com>> wrote:


On 12/13/23 16:13, Sami Mujawar wrote:
> From: Jianyong Wu <jianyong.wu@arm.com <mailto:jianyong.wu@arm.com>>
> 
> Add the long lost CI for CloudHv on AArch64.
> As CloudHv CI works nearly the same way with other VMMs like KvmTool,
> thus we can easily create its CI configuration based on KvmTool.
> 
> Reviewed-by: Laszlo Ersek <lersek@redhat.com <mailto:lersek@redhat.com>>
> Signed-off-by: Jianyong Wu <jianyong.wu@arm.com <mailto:jianyong.wu@arm.com>>
> Signed-off-by: Sami Mujawar <sami.mujawar@arm.com <mailto:sami.mujawar@arm.com>>
> ---
> 
> The changes can be seen at: https://github.com/samimujawar/edk2/tree/2897_cloudhv_ci_v3 <https://github.com/samimujawar/edk2/tree/2897_cloudhv_ci_v3>
> 
> Notes:
> v3:
> - CI fails to build when merging this patch [Laszlo]
> Ref: https://edk2.groups.io/g/devel/message/112321 <https://edk2.groups.io/g/devel/message/112321>
> - Added missing comma in supported architecture lists [Sami]
> in CloudHvBuild.py to fix the issue.


Huh, singleton tuple!


https://docs.python.org/3/library/stdtypes.html#tuple <https://docs.python.org/3/library/stdtypes.html#tuple>


"Using a trailing comma for a singleton tuple: a, or (a,)"


I guess that broke with the ArchSupported update from v1 to v2:


- ArchSupported = ("AARCH64", "ARM")
+ ArchSupported = ("AARCH64")


Sami, you have push right; can you merge this?
[SAMI] I will get this merged, no problem.

Regards,

Sami Mujawar


Thanks!
Laszlo


> 
> ArmVirtPkg/PlatformCI/.azurepipelines/Ubuntu-GCC5.yml | 13 ++++++++
> ArmVirtPkg/PlatformCI/CloudHvBuild.py | 32 ++++++++++++++++++++
> 2 files changed, 45 insertions(+)
> 
> diff --git a/ArmVirtPkg/PlatformCI/.azurepipelines/Ubuntu-GCC5.yml b/ArmVirtPkg/PlatformCI/.azurepipelines/Ubuntu-GCC5.yml
> index d1772a65fc3a84f7f981971ff4ed6c37d7ba84f6..ab8a2db53026db686ae4e5943044235c63ab3a80 100644
> --- a/ArmVirtPkg/PlatformCI/.azurepipelines/Ubuntu-GCC5.yml
> +++ b/ArmVirtPkg/PlatformCI/.azurepipelines/Ubuntu-GCC5.yml
> @@ -140,6 +140,19 @@ jobs:
> Build.Target: "RELEASE"
> Run: false
> 
> + CLOUDHV_AARCH64_DEBUG:
> + Build.File: "$(package)/PlatformCI/CloudHvBuild.py"
> + Build.Arch: "AARCH64"
> + Build.Flags: ""
> + Build.Target: "DEBUG"
> + Run: false
> + CLOUDHV_AARCH64_RELEASE:
> + Build.File: "$(package)/PlatformCI/CloudHvBuild.py"
> + Build.Arch: "AARCH64"
> + Build.Flags: ""
> + Build.Target: "RELEASE"
> + Run: false
> +
> workspace:
> clean: all
> 
> diff --git a/ArmVirtPkg/PlatformCI/CloudHvBuild.py b/ArmVirtPkg/PlatformCI/CloudHvBuild.py
> new file mode 100644
> index 0000000000000000000000000000000000000000..5100a56f3be5ad6d2b156352a521900f93d1de27
> --- /dev/null
> +++ b/ArmVirtPkg/PlatformCI/CloudHvBuild.py
> @@ -0,0 +1,32 @@
> +# @file
> +# Script to Build ArmVirtPkg UEFI firmware
> +#
> +# Copyright (c) Microsoft Corporation.
> +# SPDX-License-Identifier: BSD-2-Clause-Patent
> +##
> +import os
> +import sys
> +
> +sys.path.append(os.path.dirname(os.path.abspath(__file__)))
> +from PlatformBuildLib import SettingsManager
> +from PlatformBuildLib import PlatformBuilder
> +
> + # ####################################################################################### #
> + # Common Configuration #
> + # ####################################################################################### #
> +class CommonPlatform():
> + ''' Common settings for this platform. Define static data here and use
> + for the different parts of stuart
> + '''
> + PackagesSupported = ("ArmVirtPkg",)
> + ArchSupported = ("AARCH64",)
> + TargetsSupported = ("DEBUG", "RELEASE")
> + Scopes = ('armvirt', 'edk2-build')
> + WorkspaceRoot = os.path.realpath(os.path.join(
> + os.path.dirname(os.path.abspath(__file__)), "..", ".."))
> +
> + DscName = os.path.join("ArmVirtPkg", "ArmVirtCloudHv.dsc")
> + FvQemuArg = "" # ignored
> +
> +import PlatformBuildLib
> +PlatformBuildLib.CommonPlatform = CommonPlatform







-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#112533): https://edk2.groups.io/g/devel/message/112533
Mute This Topic: https://groups.io/mt/103150734/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



  reply	other threads:[~2023-12-14 13:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-13 15:13 [edk2-devel] [PATCH v3 1/1] CloudHv: Add CI for CloudHv on AArch64 Sami Mujawar
2023-12-14 12:27 ` Laszlo Ersek
2023-12-14 13:54   ` Sami Mujawar [this message]
2023-12-14 15:06     ` Sami Mujawar

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-list 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=BEBCE005-F457-4801-8F1C-3EE531B9D873@arm.com \
    --to=devel@edk2.groups.io \
    /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