Re: [PATCH for-4.20] automation: Use a different ImageBuilder repository URL

On 10/07/2024 01:46, Stefano Stabellini wrote: > > > On Tue, 9 Jul 2024, Alejandro Vallejo wrote: >> On Tue Jul 9, 2024 at 1:21 PM BST, Michal Orzel wrote: >>> Switch to using https://gitlab.com/xen-project/imagebuilder.git which >>> should be considered official ImageBuilder repo. >>> >>> Sig

Re: [XEN PATCH v12 5/7] tools/libxc: Allow gsi be mapped into a free pirq

On 2024/7/9 21:26, Jan Beulich wrote: > On 08.07.2024 13:41, Jiqian Chen wrote: >> Hypercall PHYSDEVOP_map_pirq support to map a gsi into a specific >> pirq or a free pirq, it depends on the parameter pirq(>0 or <0). >> But in current xc_physdev_map_pirq, it set *pirq=index when >> parameter pirq i

Re: [XEN PATCH v12 3/7] x86/pvh: Add PHYSDEVOP_setup_gsi for PVH dom0

Hi, On 2024/7/8 19:41, Jiqian Chen wrote: > The gsi of a passthrough device must be configured for it to be > able to be mapped into a hvm domU. > But When dom0 is PVH, the gsis may not get registered(see below > clarification), it causes the info of apic, pin and irq not be > added into irq_2_pin

[XEN PATCH v3 0/2] x86: separate powernow/hwp/acpi cpufreq code

This is another version of a short patch series to make platform-specific parts of cpufreq optional and dependant on INTEL & AMD config options. This is to allow for tuning the build for either AMD or Intel platform exclusively and hence to drop the code that would be left unused. Per-patch change

[XEN PATCH v3 1/2] x86/cpufreq: move ACPI cpufreq driver into separate file

Separate ACPI driver from generic initialization cpufreq code. This way acpi-cpufreq can become optional in the future and be disabled from non-Intel builds. no changes to code were introduced, except: acpi_cpufreq_register() helper added clean up a list of included headers license transform

[XEN PATCH v3 2/2] x86/cpufreq: separate powernow/hwp/acpi cpufreq code

Build AMD Architectural P-state driver when CONFIG_AMD is on, and Intel Hardware P-States driver together with ACPI Processor P-States driver when CONFIG_INTEL is on respectively, allowing for a platform-specific build. Signed-off-by: Sergiy Kibrik CC: Jason Andryuk CC: Jan Beulich --- changes

Re: [PATCH for-4.19] xen: Fix XEN_EXTRAVERSION after 4.19-rc1

Hi, On 02/07/2024 15:14, Jan Beulich wrote: On 02.07.2024 15:43, Andrew Cooper wrote: EXTRAVERSION needs a . separator for numbers. Not exactly. It needs the 0 dropped, if we follow what we've done in the past. Then ... From docs/process/release-technician-checklist.txt: #- XEN_EXTRAVE

Re: [PATCH for-4.19(?)] xen/arm: bootfdt: Fix device tree memory node probing

Hi Michal, On 27/06/2024 13:01, Michal Orzel wrote: +/* + * Check if a node is a proper /memory node according to Devicetree + * Specification v0.4, chapter 3.4. + */ +static bool __init device_tree_is_memory_node(const void *fdt, int node, + int dept

[libvirt test] 186748: tolerable all pass - PUSHED

flight 186748 libvirt real [real] http://logs.test-lab.xenproject.org/osstest/logs/186748/ Failures :-/ but no regressions. Tests which did not succeed, but are not blocking: test-armhf-armhf-libvirt 16 saverestore-support-checkfail like 186728 test-amd64-amd64-libvirt-xsm 15 migrate-s

[PATCH v2] xen: make multicall debug boot time selectable

Today Xen multicall debugging needs to be enabled via modifying a define in a source file for getting debug data of multicall errors encountered by users. Switch multicall debugging to depend on a boot parameter "xen_mc_debug" instead, enabling affected users to boot with the new parameter set in

Re: [XEN PATCH v4 10/14] x86/vmx: guard access to cpu_has_vmx_* in common code

On 09/07/2024 08:05, Sergiy Kibrik wrote: There're several places in common code, outside of arch/x86/hvm/vmx, where cpu_has_vmx_* get accessed without checking whether VMX supported first. These macros rely on global variables defined in vmx code, so when VMX support is disabled accesses to thes

[PATCH 0/2] x86/xen: cleanup of xen private headers

Cleanup the private header files in arch/x86/xen by merging them into one file and by removing unneeded stuff. Juergen Gross (2): x86/xen: make some functions static x86/xen: eliminate some private header files arch/x86/xen/apic.c | 2 - arch/x86/xen/debugfs.c | 2 +- arch

[PATCH 2/2] x86/xen: eliminate some private header files

Under arch/x86/xen there is one large private header file xen-ops.h containing most of the Xen-private x86 related declarations, and then there are several small headers with a handful of declarations each. Merge the small headers into xen-ops.h. While doing that, move the declaration of xen_fifo

[PATCH 1/2] x86/xen: make some functions static

Some functions and variables in arch/x86/xen are used locally only, make them static. Signed-off-by: Juergen Gross --- arch/x86/xen/mmu.h | 4 arch/x86/xen/mmu_pv.c | 11 ++- arch/x86/xen/xen-ops.h | 1 - 3 files changed, 6 insertions(+), 10 deletions(-) diff --git a/arch/x8

[PATCH for-4.20 v2] automation: Use a different ImageBuilder repository URL

Switch to using https://gitlab.com/xen-project/imagebuilder.git which should be considered official ImageBuilder repo. Take the opportunity to truncate the git history when cloning using --depth 1. Signed-off-by: Michal Orzel Reviewed-by: Stefano Stabellini --- Changes in v2: - truncate histor

Re: [PATCH for-4.20 v2] automation: Use a different ImageBuilder repository URL

On 10/07/2024 10:37 am, Michal Orzel wrote: > Switch to using https://gitlab.com/xen-project/imagebuilder.git which > should be considered official ImageBuilder repo. > > Take the opportunity to truncate the git history when cloning using > --depth 1. > > Signed-off-by: Michal Orzel > Reviewed-by:

Re: [PATCH v9 1/5] xen/riscv: use printk() instead of early_printk()

On 02.07.2024 13:23, Oleksii Kurochko wrote: > As common code is available it is better to use printk() instead > of early_printk(). IOW the function is not just available (allowing linking to succeed), but is also fully functional (i.e. the line is making it out, and hence CI, which iirc is looki

Re: [PATCH v9 2/5] xen/riscv: introduce decode_cause() stuff

On 02.07.2024 13:23, Oleksii Kurochko wrote: > The patch introduces stuff needed to decode a reason of an > exception. > > Signed-off-by: Oleksii Kurochko > Acked-by: Alistair Francis Acked-by: Jan Beulich

Re: [PATCH v9 3/5] xen/riscv: introduce trap_init()

On 02.07.2024 13:23, Oleksii Kurochko wrote: > --- a/xen/arch/riscv/traps.c > +++ b/xen/arch/riscv/traps.c > @@ -12,6 +12,18 @@ > #include > #include > > +/* > + * Initialize the trap handling. > + * > + * The function is called after MMU is enabled. > + */ > +void trap_init(void) It may be

[ovmf test] 186751: all pass - PUSHED

flight 186751 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/186751/ Perfect :-) All tests in this flight passed as required version targeted for testing: ovmf 497766f70975b9c1f88df42228c79095198f2b4e baseline version: ovmf f91211049c1522f7db2ae

Re: [PATCH v9 4/5] xen/riscv: enable GENERIC_BUG_FRAME

On 02.07.2024 13:23, Oleksii Kurochko wrote: > Signed-off-by: Oleksii Kurochko > --- > xen/arch/riscv/Kconfig | 1 + > xen/arch/riscv/traps.c | 31 +++ > xen/common/bug.c | 1 + > 3 files changed, 33 insertions(+) > > diff --git a/xen/arch/riscv/Kconfig b/xen/

Re: [PATCH v9 5/5] xen/riscv: test basic handling stuff

On 02.07.2024 13:23, Oleksii Kurochko wrote: > Signed-off-by: Oleksii Kurochko > Acked-by: Alistair Francis > --- > xen/arch/riscv/setup.c | 16 > 1 file changed, 16 insertions(+) > > diff --git a/xen/arch/riscv/setup.c b/xen/arch/riscv/setup.c > index a6a29a1508..4f06203b46 10

Re: [PATCH v9 5/5] xen/riscv: test basic handling stuff

On 10.07.2024 12:06, Jan Beulich wrote: > On 02.07.2024 13:23, Oleksii Kurochko wrote: >> Signed-off-by: Oleksii Kurochko >> Acked-by: Alistair Francis >> --- >> xen/arch/riscv/setup.c | 16 >> 1 file changed, 16 insertions(+) >> >> diff --git a/xen/arch/riscv/setup.c b/xen/arch

Re: [XEN PATCH v4 12/14] x86/ioreq: guard VIO_realmode_completion with CONFIG_VMX

09.07.24 10:28, Jan Beulich: On 09.07.2024 08:09, Sergiy Kibrik wrote: --- a/xen/arch/x86/include/asm/hvm/ioreq.h +++ b/xen/arch/x86/include/asm/hvm/ioreq.h @@ -13,6 +13,11 @@ #define IOREQ_STATUS_UNHANDLED X86EMUL_UNHANDLEABLE #define IOREQ_STATUS_RETRY X86EMUL_RETRY +#ifdef CONF

Re: [XEN PATCH v4 12/14] x86/ioreq: guard VIO_realmode_completion with CONFIG_VMX

On 10.07.2024 12:10, Sergiy Kibrik wrote: > 09.07.24 10:28, Jan Beulich: >> On 09.07.2024 08:09, Sergiy Kibrik wrote: >>> --- a/xen/arch/x86/include/asm/hvm/ioreq.h >>> +++ b/xen/arch/x86/include/asm/hvm/ioreq.h >>> @@ -13,6 +13,11 @@ >>> #define IOREQ_STATUS_UNHANDLED X86EMUL_UNHANDLEABLE >>>

Re: [XEN PATCH v4 01/14] x86: introduce AMD-V and Intel VT-x Kconfig options

09.07.24 10:11, Jan Beulich: On 09.07.2024 07:45, Sergiy Kibrik wrote: From: Xenia Ragiadakou Introduce two new Kconfig options, SVM and VMX, to allow code specific to each virtualization technology to be separated and, when not required, stripped. CONFIG_SVM will be used to enable virtual mac

Re: [PATCH v1 1/5] xen/device-tree: Move Arm's setup.c bootinfo functions to common

On 03.07.2024 12:42, Oleksii Kurochko wrote: > From: Shawn Anastasio > > Arm's setup.c contains a collection of functions for parsing memory map > and other boot information from a device tree. Since these routines are > generally useful on any architecture that supports device tree booting, > mo

Re: [PATCH v1 3/5] xen/riscv: enable CONFIG_HAS_DEVICE_TREE

On 03.07.2024 12:42, Oleksii Kurochko wrote: > --- a/xen/arch/riscv/Kconfig > +++ b/xen/arch/riscv/Kconfig > @@ -5,6 +5,7 @@ config RISCV > config RISCV_64 > def_bool y > select 64BIT > + select HAS_DEVICE_TREE > select GENERIC_BUG_FRAME > > config ARCH_DEFCONFIG Same qu

Re: [XEN PATCH v4 01/14] x86: introduce AMD-V and Intel VT-x Kconfig options

On 10.07.2024 12:21, Sergiy Kibrik wrote: > 09.07.24 10:11, Jan Beulich: >> On 09.07.2024 07:45, Sergiy Kibrik wrote: >>> From: Xenia Ragiadakou >>> >>> Introduce two new Kconfig options, SVM and VMX, to allow code >>> specific to each virtualization technology to be separated and, when not >>> re

Re: [PATCH v1 4/5] xen/riscv: introduce device tree maping function

On 03.07.2024 12:42, Oleksii Kurochko wrote: > Signed-off-by: Oleksii Kurochko > --- > xen/arch/riscv/include/asm/config.h | 6 + > xen/arch/riscv/include/asm/mm.h | 2 ++ > xen/arch/riscv/mm.c | 37 + > 3 files changed, 40 insertions(+), 5 de

Re: [XEN PATCH v4 01/14] x86: introduce AMD-V and Intel VT-x Kconfig options

10.07.24 13:28, Jan Beulich: On 10.07.2024 12:21, Sergiy Kibrik wrote: 09.07.24 10:11, Jan Beulich: On 09.07.2024 07:45, Sergiy Kibrik wrote: From: Xenia Ragiadakou Introduce two new Kconfig options, SVM and VMX, to allow code specific to each virtualization technology to be separated and, w

[PATCH] x86/xen: remove deprecated xen_nopvspin boot parameter

The xen_nopvspin boot parameter is deprecated since 2019. nopvspin can be used instead. Remove the xen_nopvspin boot parameter and replace the xen_pvspin variable use cases with nopvspin. This requires to move the nopvspin variable out of the .initdata section, as it needs to be accessed for cpuh

Re: [PATCH for-4.20 v2] automation: Use a different ImageBuilder repository URL

On Wed Jul 10, 2024 at 10:37 AM BST, Michal Orzel wrote: > Switch to using https://gitlab.com/xen-project/imagebuilder.git which > should be considered official ImageBuilder repo. > > Take the opportunity to truncate the git history when cloning using > --depth 1. > > Signed-off-by: Michal Orzel >

[Announcement] Upcoming Closure of Xen Project Colo Facility

Dear Xen Community, We regret to inform you that the Xen Project is currently experiencing unexpected changes due to the sudden shutdown of our colocated (colo) data center facility by Synoptek. This incident is beyond our control and will impact the continuity of OSSTest (the gating Xen Project C

[ANNOUNCE] Call for agenda items - Community Call 11th July 2024

Hi all, *Please add your proposed agenda items below.* https://cryptpad.fr/pad/#/2/pad/edit/8+z7QnqdirEYBrspUHUJvxCZ/ If any action items are missing or have been resolved, please add/remove them from the sheet. *CALL LINK: https://meet.jit.si/XenProjectCommunityCall

[PATCH for-4.20 v2] xen/arm: bootfdt: Fix device tree memory node probing

Memory node probing is done as part of early_scan_node() that is called for each node with depth >= 1 (root node is at depth 0). According to Devicetree Specification v0.4, chapter 3.4, /memory node can only exists as a top level node. However, Xen incorrectly considers all the nodes with unit node

Re: [PATCH v3 1/1] swiotlb: Reduce swiotlb pool lookups

On Wed, 10 Jul 2024 07:55:20 +0200 Christoph Hellwig wrote: > On Tue, Jul 09, 2024 at 09:08:18PM +0200, Petr Tesařík wrote: > > I'm confused. If you're not a big fan, why are we effectively adding > > them to more places now than before the patch? > > Because I didn't want to second guess the

RE: [PATCH v3 1/1] swiotlb: Reduce swiotlb pool lookups

From: Petr Tesařík Sent: Wednesday, July 10, 2024 4:32 AM > > On Wed, 10 Jul 2024 07:55:20 +0200 > Christoph Hellwig wrote: > > > On Tue, Jul 09, 2024 at 09:08:18PM +0200, Petr Tesařík wrote: > > > I'm confused. If you're not a big fan, why are we effectively adding > > > them to more places no

Re: [XEN PATCH v4 01/14] x86: introduce AMD-V and Intel VT-x Kconfig options

On 10.07.2024 12:52, Sergiy Kibrik wrote: > 10.07.24 13:28, Jan Beulich: >> On 10.07.2024 12:21, Sergiy Kibrik wrote: >>> 09.07.24 10:11, Jan Beulich: On 09.07.2024 07:45, Sergiy Kibrik wrote: > From: Xenia Ragiadakou > > Introduce two new Kconfig options, SVM and VMX, to allow co

Re: [PATCH v1 5/5] xen/riscv: map FDT

On 03.07.2024 12:42, Oleksii Kurochko wrote: > Except mapping of FDT, it is also printing command line passed by > a DTB and initialize bootinfo from a DTB. I'm glad the description isn't empty here. However, ... > --- a/xen/arch/riscv/riscv64/head.S > +++ b/xen/arch/riscv/riscv64/head.S > @@ -41

[linux-linus test] 186749: regressions - FAIL

flight 186749 linux-linus real [real] http://logs.test-lab.xenproject.org/osstest/logs/186749/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-armhf-armhf-xl-qcow2 8 xen-boot fail REGR. vs. 186727 Tests which are fai

Re: [XEN PATCH v3 1/2] x86/cpufreq: move ACPI cpufreq driver into separate file

On 10.07.2024 10:28, Sergiy Kibrik wrote: > Separate ACPI driver from generic initialization cpufreq code. > This way acpi-cpufreq can become optional in the future and be disabled > from non-Intel builds. > > no changes to code were introduced, except: > acpi_cpufreq_register() helper added >

Re: [PATCH v4] xen/riscv: PE/COFF image header for RISC-V target

On Mon, Jul 8, 2024 at 11:32 AM Jan Beulich wrote: > > On 04.07.2024 19:21, Milan Đokić wrote: > > On Wed, Jul 3, 2024 at 5:55 PM Jan Beulich wrote: > >> On 03.07.2024 02:04, Milan Djokic wrote: > >>> +#ifdef CONFIG_RISCV_EFI > >>> +/* > >>> + * This instruction decodes to "MZ" AS

[ovmf test] 186752: all pass - PUSHED

flight 186752 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/186752/ Perfect :-) All tests in this flight passed as required version targeted for testing: ovmf 3abe627f29add4d05a404e9170b81cf72d9c404b baseline version: ovmf 497766f70975b9c1f88df

Re: [PATCH v4] xen/riscv: PE/COFF image header for RISC-V target

On 10.07.2024 16:44, Milan Đokić wrote: > On Mon, Jul 8, 2024 at 11:32 AM Jan Beulich wrote: >> On 04.07.2024 19:21, Milan Đokić wrote: >>> On Wed, Jul 3, 2024 at 5:55 PM Jan Beulich wrote: On 03.07.2024 02:04, Milan Djokic wrote: > +#ifdef CONFIG_RISCV_EFI > +/* > +

[xen-unstable test] 186750: tolerable FAIL

flight 186750 xen-unstable real [real] http://logs.test-lab.xenproject.org/osstest/logs/186750/ Failures :-/ but no regressions. Tests which are failing intermittently (not blocking): test-amd64-amd64-qemuu-freebsd12-amd64 19 guest-localmigrate/x10 fail pass in 186745 test-armhf-armhf-xl-credi

[ovmf test] 186754: all pass - PUSHED

flight 186754 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/186754/ Perfect :-) All tests in this flight passed as required version targeted for testing: ovmf 6c061c4715325494b8b25453158166f9032e0335 baseline version: ovmf 3abe627f29add4d05a404

Re: Serious AMD-Vi(?) issue

On Thu, Jul 04, 2024 at 03:08:00PM -0700, Elliott Mitchell wrote: > On Mon, Jul 01, 2024 at 11:07:57AM -0700, Elliott Mitchell wrote: > > On Thu, Jun 27, 2024 at 05:18:15PM -0700, Elliott Mitchell wrote: > > > > Most processors were mentioned roughly equally. Several had fewer > > mentions, but n

Re: AMD EPYC virtual network performances

On Tue, Jul 09, 2024 at 08:36:18AM +, Andrei Semenov wrote: > > Does anybody notice this behavior on his side?  Can we do something > about it? I hadn't previously noticed this manifestation, but now that I know where to look seems I'm also seeing the issue. It also effects other lines of A

[ovmf test] 186755: all pass - PUSHED

flight 186755 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/186755/ Perfect :-) All tests in this flight passed as required version targeted for testing: ovmf 0f45be16336035e69bb30761f8cd20ba3b0a3f39 baseline version: ovmf 6c061c4715325494b8b25

Re: [PATCH for-4.20 v2] automation: Use a different ImageBuilder repository URL

On Wed, 10 Jul 2024, Andrew Cooper wrote: > On 10/07/2024 10:37 am, Michal Orzel wrote: > > Switch to using https://gitlab.com/xen-project/imagebuilder.git which > > should be considered official ImageBuilder repo. > > > > Take the opportunity to truncate the git history when cloning using > > --de

Re: [PATCH for-4.20 v2] xen/arm: bootfdt: Fix device tree memory node probing

Hi, On 10/07/2024 12:22, Michal Orzel wrote: Memory node probing is done as part of early_scan_node() that is called for each node with depth >= 1 (root node is at depth 0). According to Devicetree Specification v0.4, chapter 3.4, /memory node can only exists as a top level node. However, Xen in

Re: [PATCH RFC] Arm64: amend "xen/arm64: head: Add missing code symbol annotations"

Hi Jan, On 10/06/2024 14:37, Jan Beulich wrote: While the change[1] didn't go in yet, there is the intention for the ELF metadata annotations from xen/linkage.h to also effect honoring of CONFIG_CC_SPLIT_SECTIONS. In code that's placement / ordering sensitive, these annotations therefore need us

[linux-linus test] 186753: tolerable FAIL - PUSHED

flight 186753 linux-linus real [real] http://logs.test-lab.xenproject.org/osstest/logs/186753/ Failures :-/ but no regressions. Tests which are failing intermittently (not blocking): test-armhf-armhf-xl-qcow2 8 xen-boot fail in 186742 pass in 186753 test-armhf-armhf-examine 8 r

Re: [PATCH] xen/arm: Convert comma to semicolon

On Wed, 10 Jul 2024, Chen Ni wrote: > Replace a comma between expression statements by a semicolon. > > Signed-off-by: Chen Ni Reviewed-by: Stefano Stabellini > --- > arch/arm/xen/p2m.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/arch/arm/xen/p2m.c b/arch/arm/xen

[ovmf test] 186759: all pass - PUSHED

flight 186759 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/186759/ Perfect :-) All tests in this flight passed as required version targeted for testing: ovmf 071d2cfab8347e396c8b2709bfb588a18c497bbd baseline version: ovmf 0f45be16336035e69bb30

[linux-linus test] 186756: regressions - FAIL

flight 186756 linux-linus real [real] flight 186758 linux-linus real-retest [real] http://logs.test-lab.xenproject.org/osstest/logs/186756/ http://logs.test-lab.xenproject.org/osstest/logs/186758/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run