[VirtIO] Support for various devices in Xen

Hello, As I've mentioned in previous discussion threads in the xen-devel community, we are running Xen 4.17 (uprev to 4.18 in progress) on NXP S32G automotive processors (Cortex-A53 cores) and we wanted to know more about the support for various VirtIO device types in Xen. In the Xen 4.17

Re: [ARM][xencons] PV Console hangs due to illegal ring buffer accesses

Hello, Julien, Stefano, Thank you for your replies. On 21/07/2023 02:25, Stefano Stabellini wrote: > > On Thu, 20 Jul 2023, Julien Grall wrote: >> (+ Juergen) >> >> On 19/07/2023 17:13, Andrei Cherechesu (OSS) wrote: >>> Hello, >> >> Hi Andrei, &g

[ARM][xencons] PV Console hangs due to illegal ring buffer accesses

Hello, As we're running Xen 4.17 (with platform-related support added) on NXP S32G SoCs (ARMv8), with a custom Linux distribution built through Yocto, and we've set some Xen-based demos up, we encountered some issues which we think might not be related to our hardware. For additional context,

[PATCH v3 0/2] Fix ARM Generic Timer interrupt parsing

From: Andrei Cherechesu This 2-patch series fixes the parsing of the ARM Generic Timer interrupts from the device tree. If the generic timer interrupts order in the DT was different than the expected order in Xen code, these interrupts would no longer be correctly parsed and registered by Xen,

[PATCH v3 1/2] arch/arm: irq: Add platform_get_irq_byname() implementation

From: Andrei Cherechesu Moved implementation for the function which parses the IRQs of a DT node by the "interrupt-names" property from the SMMU-v3 driver to the IRQ core code and made it non-static to be used as helper. Also changed it to receive a "struct dt_device_node*" as parameter, like

[PATCH v3 2/2] arch/arm: time: Add support for parsing interrupts by names

From: Andrei Cherechesu Added support for parsing the ARM generic timer interrupts DT node by the "interrupt-names" property, if it is available. If not available, the usual parsing based on the expected IRQ order is performed. Also treated returning 0 as an error case for the

[PATCH v2 2/2] arch/arm: time: Add support for parsing interrupts by names

From: Andrei Cherechesu Added support for parsing the ARM generic timer interrupts DT node by the "interrupt-names" property, if it is available. If not available, the usual parsing based on the expected IRQ order is performed. Also changed to treating returning 0 as an error case for the

[PATCH v2 1/2] arch/arm: irq: Add platform_get_irq_byname() implementation

From: Andrei Cherechesu Moved implementation for the function which parses the IRQs of a DT node by the "interrupt-names" property from the SMMU-v3 driver to the IRQ core code and made it non-static to be used as helper. Also changed it to receive a "struct dt_device_node*" as parameter, like

[PATCH v2 0/2] Fix ARM Generic Timer interrupt parsing

From: Andrei Cherechesu This 2-patch series fixes the parsing of the ARM Generic Timer interrupts from the device tree. If the generic timer interrupts order in the DT was different than the expected order in Xen code, these interrupts would no longer be correctly parsed and registered by Xen,

[PATCH v1 2/2] arch/arm: time: Add support for parsing interrupts by names

From: Andrei Cherechesu Added support for parsing the ARM generic timer interrupts DT node by the "interrupt-names" property, if it is available. If not available, the usual parsing based on the expected IRQ order is performed. Also added the "hyp-virt" PPI to the timer PPI list, even though

[PATCH v1 1/2] arch/arm: irq: Add platform_get_irq_byname() implementation

From: Andrei Cherechesu Moved implementation for the function which parses the IRQs of a DT node by the "interrupt-names" property from the SMMU-v3 driver to the IRQ core code and made it non-static to be used as helper. Also changed it to receive a "struct dt_device_node*" as parameter, like

[PATCH v1 0/2] Fix ARM Generic Timer interrupt parsing

From: Andrei Cherechesu This 2-patch series fixes the parsing of the ARM Generic Timer interrupts from the device tree. If the generic timer interrupts order in the DT was different than the expected order in Xen code, these interrupts would no longer be correctly parsed and registered by Xen,

[PATCH v4 1/1] uboot-script-gen: Dynamically compute addr and size when loading binaries

From: Andrei Cherechesu Normally, the Imagebuilder would precompute the sizes of the loaded binaries and addresses where they are loaded before generating the script, and the sizes and addresses that needed to be provided to Xen via /chosen would be hardcoded in the boot script. Added an option

[ImageBuilder][PATCH v4 0/1] Imagebuilder dynamic addresses and sizes

From: Andrei Cherechesu This sent patch adds support for dynamically computing the addresses and sizes for loaded binaries via the boot script generated by Imagebuilder. Compared to the v3 version of the patch, this includes Stefano's suggestions of not adding as many "if" statements on the

[ImageBuilder][PATCH v3 3/3] uboot-script-gen: Enable not adding boot command to script

From: Andrei Cherechesu If the "BOOT_CMD" variable is set to "none" inside the config file, the boot command (i.e. "booti") will not by added to the generated script, to allow the user to customize the u-boot env or the device-tree after executing the script commands and before actually booting.

[ImageBuilder][PATCH v3 2/3] uboot-script-gen: Enable appending extra commands to boot script

From: Andrei Cherechesu Added the parsing for APPEND_EXTRA_CMDS variable, which enables the user to specify the path to a text file that contains, on each line, u-boot commands that will be added to the generated script as "fixups", before the boot command. The file specified by the

[ImageBuilder][PATCH v3 0/3] Add extra ImageBuilder features

From: Andrei Cherechesu Hello, This the v3 version for the patches which have not yet been commited. Changes in v3: - Dropped the [PATCH v2 1/4] from the previous series since it's already been commited - For PATCH 1/3: No changes - For PATCH 2/3: Dropped the "-a" parameter and instead sourced

[ImageBuilder][PATCH v3 1/3] uboot-script-gen: Dynamically compute addr and size when loading binaries

From: Andrei Cherechesu Normally, the script would precompute the sizes of the loaded binaries and addresses where they are loaded before generating the script, and the sizes and addresses that needed to be provided to Xen via /chosen would be hardcoded in the boot script. Added option via "-s"

[ImageBuilder][PATCH v2 3/4] uboot-script-gen: Enable appending extra commands to boot script

From: Andrei Cherechesu Added the "-a" parameter which stands for APPEND_EXTRA_CMDS option, which enables the user to specify the path to a text file that contains, on each line, u-boot commands that will be added to the generated script as "fixups", before the boot command. The file specified

[ImageBuilder][PATCH v2 2/4] uboot-script-gen: Dynamically compute addr and size when loading binaries

From: Andrei Cherechesu Normally, the script would precompute the sizes of the loaded binaries and addresses where they are loaded before generating the script, and the sizes and addresses that needed to be provided to Xen via /chosen would be hardcoded in the boot script. Added option via "-s"

[ImageBuilder][PATCH v2 0/4] Add extra ImageBuilder features

From: Andrei Cherechesu Hello, Sorry for the late re-submission of patches, but I had some company internal work to take care of. I managed to include the changes mentioned by Stefano S. and Ayan K. H. in the discussions for the first version of patches. Changes in v2: - Dropped the patch

[ImageBuilder][PATCH v2 1/4] scripts: Add support for prepending path to file names

From: Andrei Cherechesu Added support for prepending path to file names in the final generated u-boot script, for the use-case where we have the files in a separate folder that can be accessed with a given $LOAD_CMD. For example, we can have "fatload mmc 0:2" as LOAD_CMD but the files would

[ImageBuilder][PATCH v2 4/4] uboot-script-gen: Enable not adding boot command to script

From: Andrei Cherechesu If the "BOOT_CMD" variable is set to "none" inside the config file, the boot command (i.e. "booti") will not by added to the generated script, to allow the user to customize the u-boot env or the device-tree after executing the script commands and before actually booting.