Re: [PATCH] CI: Drop alpine-3.18-rootfs-export and use test-artefacts

2024-11-04 Thread Andrew Cooper
On 31/10/2024 11:05 pm, Stefano Stabellini wrote: > On Thu, 31 Oct 2024, Andrew Cooper wrote: >> On 31/10/2024 10:46 pm, Stefano Stabellini wrote: >>> On Thu, 31 Oct 2024, Andrew Cooper wrote: The Argo work already moved this artefact into the new form. Reuse that, and drop one tes

Re: [XEN PATCH v1 1/6] CI: Refresh the Debian 12 x86_64 container

2024-11-04 Thread Javi Merino
On Fri, Oct 25, 2024 at 03:46:35PM +0100, Andrew Cooper wrote: > On 24/10/2024 4:10 pm, Javi Merino wrote: > > On Thu, Oct 24, 2024 at 03:04:10PM +0100, Andrew Cooper wrote: > >> On 24/10/2024 11:04 am, Javi Merino wrote: > >>> + > >>> +apt-get update > >> apt-get -y > > apt-get update refreshe

Re: [XEN PATCH v1 3/6] CI: Refresh the Debian 12 arm64 container

2024-11-04 Thread Javi Merino
On Thu, Oct 24, 2024 at 04:03:56PM -0700, Stefano Stabellini wrote: > On Thu, 24 Oct 2024, Javi Merino wrote: > > Rework the container to use heredocs for readability and use apt-get > > --no-install-recommends to keep the size down. Rename the job to > > debian-12-arm64-* to follow the naming sch

Re: [PATCH v4] x86/io-apic: fix directed EOI when using AMD-Vi interrupt remapping

2024-11-04 Thread Jan Beulich
On 31.10.2024 09:57, Roger Pau Monne wrote: > @@ -71,6 +72,24 @@ static int apic_pin_2_gsi_irq(int apic, int pin); > > static vmask_t *__read_mostly vector_map[MAX_IO_APICS]; > > +/* > + * Store the EOI handle when using interrupt remapping. > + * > + * If using AMD-Vi interrupt remapping the

Re: [PATCH v5 1/3] xen/device-tree: Let DT reserve map entries overlap reserved-memory

2024-11-04 Thread Grygorii Strashko
Hi All, On 04.11.24 12:49, Michal Orzel wrote: On 27/09/2024 00:24, Shawn Anastasio wrote: Commit 53dc37829c31 ("xen/arm: Add DT reserve map regions to bootinfo.reserved_mem") changes the way reserve map regions are tracked, and as a result broke bootfdt's ability to handle device trees in

Re: [PATCH 00/12] Boot modules for Hyperlaunch

2024-11-04 Thread Daniel P. Smith
On 11/4/24 03:41, Jan Beulich wrote: On 02.11.2024 18:25, Daniel P. Smith wrote: The Boot Modules for Hyperlaunch series is an effort to split out preliminary changes necessary for the introduction of the Hyperlaunch domain builder logic. These preliminary changes revolve around introducing the

Re: [PATCH v5 1/3] xen/device-tree: Let DT reserve map entries overlap reserved-memory

2024-11-04 Thread Grygorii Strashko
On 04.11.24 14:39, Grygorii Strashko wrote: Hi All, On 04.11.24 12:49, Michal Orzel wrote: On 27/09/2024 00:24, Shawn Anastasio wrote: Commit 53dc37829c31 ("xen/arm: Add DT reserve map regions to bootinfo.reserved_mem") changes the way reserve map regions are tracked, and as a result br

[RFC PATCH v3] iommu/xen: Add Xen PV-IOMMU driver

2024-11-04 Thread Teddy Astie
In the context of Xen, Linux runs as Dom0 and doesn't have access to the machine IOMMU. Although, a IOMMU is mandatory to use some kernel features such as VFIO or DMA protection. In Xen, we added a paravirtualized IOMMU with iommu_op hypercall in order to allow Dom0 to implement such feature. This

[ANNOUNCE] Call for agenda items - Community Call 7th Nov 2024

2024-11-04 Thread Kelly Choi
Hi all, Please add your proposed agenda items below. https://cryptpad.fr/pad/#/2/pad/edit/6eu2rGXaB1e5M2nDrv190JcR/ If any action items are missing or have been resolved, please add/remove them from the sheet. *CALL LINK:* https://meet.jit.si/XenProjectCommunityCall

Re: [PATCH v5 1/3] xen/device-tree: Let DT reserve map entries overlap reserved-memory

2024-11-04 Thread Michal Orzel
On 27/09/2024 00:24, Shawn Anastasio wrote: > > > Commit 53dc37829c31 ("xen/arm: Add DT reserve map regions to > bootinfo.reserved_mem") changes the way reserve map regions are tracked, > and as a result broke bootfdt's ability to handle device trees in which > the reserve map and the `reserve

[XEN RFC PATCH v4 4/5] VT-d: Port IOMMU driver to new subsystem

2024-11-04 Thread Teddy Astie
Port the driver with guidances specified in iommu-contexts.md. Add a arena-based allocator for allocating a fixed chunk of memory and split it into 4k pages for use by the IOMMU contexts. This chunk size is configurable with X86_ARENA_ORDER and dom0-iommu=arena-order=N. Signed-off-by Teddy Astie

[XEN RFC PATCH v4 5/5] xen/public: Introduce PV-IOMMU hypercall interface

2024-11-04 Thread Teddy Astie
Introduce a new pv interface to manage the underlying IOMMU and manage contexts and devices. This interface allows creation of new contexts from Dom0 and addition of IOMMU mappings using guest PoV. This interface doesn't allow creation of mapping to other domains. Signed-off-by Teddy Astie --- C

[XEN RFC PATCH v4 3/5] IOMMU: Introduce redesigned IOMMU subsystem

2024-11-04 Thread Teddy Astie
Based on docs/designs/iommu-contexts.md, implement the redesigned IOMMU subsystem. Signed-off-by Teddy Astie --- Changed in V2: * cleanup some unneeded includes * fix dangling devices in context on detach Changed in V3: * add unlocked _iommu_lookup_page * iommu_check_context+iommu_get_context -

[XEN RFC PATCH v4 1/5] docs/designs: Add a design document for PV-IOMMU

2024-11-04 Thread Teddy Astie
Some operating systems want to use IOMMU to implement various features (e.g VFIO) or DMA protection. This patch introduce a proposal for IOMMU paravirtualization for Dom0. Signed-off-by Teddy Astie --- Changes in v4: * added init and remote_op commands --- docs/designs/pv-iommu.md | 116

[XEN RFC PATCH v4 2/5] docs/designs: Add a design document for IOMMU subsystem redesign

2024-11-04 Thread Teddy Astie
Current IOMMU subsystem has some limitations that make PV-IOMMU practically impossible. One of them is the assumtion that each domain is bound to a single "IOMMU domain", which also causes complications with quarantine implementation. Moreover, current IOMMU subsystem is not entirely well-define

[XEN RFC PATCH v4 0/5] IOMMU subsystem redesign and PV-IOMMU interface

2024-11-04 Thread Teddy Astie
This work has been presented at Xen Summit 2024 during the IOMMU paravirtualization and Xen IOMMU subsystem rework design session. Operating systems may want to have access to a IOMMU in order to do DMA protection or implement certain features (e.g VFIO on Linux). VFIO support is mandatory for

Re: [RFC PATCH 1/4] xen/arm: ffa: Introduce VM to VM support

2024-11-04 Thread Bertrand Marquis
Hi Jan, > On 4 Nov 2024, at 08:46, Jan Beulich wrote: > > On 04.11.2024 08:19, Bertrand Marquis wrote: >> Hi Andrew, >> >>> On 1 Nov 2024, at 12:05, Andrew Cooper wrote: >>> >>> On 16/10/2024 10:21 am, Bertrand Marquis wrote: diff --git a/xen/arch/arm/tee/ffa_partinfo.c b/xen/arch/

Re: [RFC PATCH 4/4] xen/arm: ffa: Enable VM to VM without firmware

2024-11-04 Thread Jens Wiklander
Hi Bertrand, On Mon, Nov 4, 2024 at 8:27 AM Bertrand Marquis wrote: > > Hi Jens, > > > On 1 Nov 2024, at 11:44, Jens Wiklander wrote: > > > > Hi Bertrand, > > > > On Wed, Oct 16, 2024 at 11:22 AM Bertrand Marquis > > wrote: > >> > >> When VM to VM support is activated and there is no suitable F

Re: [PATCH 00/12] Boot modules for Hyperlaunch

2024-11-04 Thread Jan Beulich
On 02.11.2024 18:25, Daniel P. Smith wrote: > The Boot Modules for Hyperlaunch series is an effort to split out preliminary > changes necessary for the introduction of the Hyperlaunch domain builder > logic. These preliminary changes revolve around introducing the struct > boot_module and struct bo

Re: Dom0 crash (BUG_ON(old_mode != XEN_LAZY_NONE) in enter_lazy()) with Linux 6.11.2

2024-11-04 Thread Jürgen Groß
On 01.11.24 13:11, Marek Marczykowski-Górecki wrote: Hi, I've got a report that starting with 6.11 (specifically 6.11.2) dom0 often crashes on a BUG_ON() like in the subject. I'm not sure where the issue is - there is i915 all over the stack trace, but in the end it crashes in a Xen-specific cod

Re: [PATCH 01/13] PCI: Prepare removing devres from pci_intx()

2024-11-04 Thread Philipp Stanner
On Thu, 2024-10-31 at 14:45 +0100, Thomas Gleixner wrote: > On Tue, Oct 15 2024 at 20:51, Philipp Stanner wrote: > > +/** > > + * pci_intx - enables/disables PCI INTx for device dev, unmanaged > > version > > mismatch vs. actual function name. ACK, will fix > > > + * @pdev: the PCI device to op

Re: [PATCH 2/6] xen: add bitmap to indicate per-domain state changes

2024-11-04 Thread Jan Beulich
On 01.11.2024 07:48, Jürgen Groß wrote: > On 31.10.24 11:59, Jan Beulich wrote: >> On 23.10.2024 15:10, Juergen Gross wrote: >>> Add a bitmap with one bit per possible domid indicating the respective >>> domain has changed its state (created, deleted, dying, crashed, >>> shutdown). >>> >>> Register

Re: [XEN RFC PATCH v4 0/5] IOMMU subsystem redesign and PV-IOMMU interface

2024-11-04 Thread Marek Marczykowski-Górecki
On Mon, Nov 04, 2024 at 02:28:38PM +, Teddy Astie wrote: > * introduce "dom0-iommu=no-dma" to make default context block all DMA > (disables HAP and sync-pt), enforcing usage of PV-IOMMU for DMA > Can be used to expose properly "Pre-boot DMA protection" This sounds like it disables HAP com

[PATCH] docs: fusa: Add requirements for mapping domain address to machine address

2024-11-04 Thread Ayan Kumar Halder
The following are the requirements written mapping :- domain virtual address to machine address intermediate physical address to machine address Signed-off-by: Ayan Kumar Halder --- .../design-reqs/arm64/domain_buffer_copy.rst | 172 ++ docs/fusa/reqs/market-reqs/reqs.rst

Re: [QEMU PATCH v9] xen/passthrough: use gsi to map pirq when dom0 is PVH

2024-11-04 Thread Stewart Hildebrand
On 11/4/24 01:03, Chen, Jiqian wrote: > On 2024/11/1 21:09, Stewart Hildebrand wrote: >> On 10/24/24 05:06, Jiqian Chen wrote: >>> diff --git a/hw/xen/xen_pt.c b/hw/xen/xen_pt.c >>> index 3635d1b39f79..5b10d501d566 100644 >>> --- a/hw/xen/xen_pt.c >>> +++ b/hw/xen/xen_pt.c >>> @@ -766,6 +766,50 @@

Re: [PATCH v5 1/3] xen/device-tree: Let DT reserve map entries overlap reserved-memory

2024-11-04 Thread Jan Beulich
On 27.09.2024 00:24, Shawn Anastasio wrote: > Commit 53dc37829c31 ("xen/arm: Add DT reserve map regions to > bootinfo.reserved_mem") changes the way reserve map regions are tracked, > and as a result broke bootfdt's ability to handle device trees in which > the reserve map and the `reserved-memory`

Re: [PATCH v4] x86/io-apic: fix directed EOI when using AMD-Vi interrupt remapping

2024-11-04 Thread Roger Pau Monné
On Mon, Nov 04, 2024 at 10:56:36AM +0100, Jan Beulich wrote: > On 31.10.2024 09:57, Roger Pau Monne wrote: > > @@ -71,6 +72,24 @@ static int apic_pin_2_gsi_irq(int apic, int pin); > > > > static vmask_t *__read_mostly vector_map[MAX_IO_APICS]; > > > > +/* > > + * Store the EOI handle when usin

Ping: [PATCH v7 00/11] (mostly) x86+Arm32: add/convert entry point annotations

2024-11-04 Thread Jan Beulich
On 01.10.2024 17:11, Jan Beulich wrote: > 01: common: honor CONFIG_CC_SPLIT_SECTIONS also for assembly functions > 02: VMX: convert entry point annotations > 03: x86/ACPI: annotate assembly functions with type and size > 04: x86/kexec: convert entry point annotations > 05: x86: convert dom_crash_sy

Re: [PATCH v6 2/3] xen/pci: introduce PF<->VF links

2024-11-04 Thread Alejandro Vallejo
On Sat Nov 2, 2024 at 3:18 PM GMT, Daniel P. Smith wrote: > On 11/1/24 16:16, Stewart Hildebrand wrote: > > +Daniel (XSM mention) > > > > On 10/28/24 13:02, Jan Beulich wrote: > >> On 18.10.2024 22:39, Stewart Hildebrand wrote: > >>> Add links between a VF's struct pci_dev and its associated PF st