Re: Virtio interrupt remapping

2025-06-16 Thread Jean-Philippe Brucker
[+Eric] On Sat, Jun 14, 2025 at 10:11:52AM +0200, Alyssa Ross wrote: > Demi Marie Obenour writes: > > > On 6/13/25 14:13, Jean-Philippe Brucker wrote: > >> Hi, > >> > >> On Fri, Jun 13, 2025 at 01:08:07PM -0400, Demi Marie Obenour wrote: > >>> I’m working on virtio-IOMMU interrupt remapping for

Re: Virtio interrupt remapping

2025-06-14 Thread Alyssa Ross
Demi Marie Obenour writes: > On 6/13/25 14:13, Jean-Philippe Brucker wrote: >> Hi, >> >> On Fri, Jun 13, 2025 at 01:08:07PM -0400, Demi Marie Obenour wrote: >>> I’m working on virtio-IOMMU interrupt remapping for Spectrum OS [1], >>> and am running into a problem. All of the current interrupt r

Re: Virtio interrupt remapping

2025-06-13 Thread Demi Marie Obenour
On 6/13/25 14:13, Jean-Philippe Brucker wrote: > Hi, > > On Fri, Jun 13, 2025 at 01:08:07PM -0400, Demi Marie Obenour wrote: >> I’m working on virtio-IOMMU interrupt remapping for Spectrum OS [1], >> and am running into a problem. All of the current interrupt remapping >> drivers use __init code

Re: Virtio interrupt remapping

2025-06-13 Thread Jean-Philippe Brucker
Hi, On Fri, Jun 13, 2025 at 01:08:07PM -0400, Demi Marie Obenour wrote: > I’m working on virtio-IOMMU interrupt remapping for Spectrum OS [1], > and am running into a problem. All of the current interrupt remapping > drivers use __init code during initialization, and I’m not sure how to > plumb t

Virtio interrupt remapping

2025-06-13 Thread Demi Marie Obenour
I’m working on virtio-IOMMU interrupt remapping for Spectrum OS [1], and am running into a problem. All of the current interrupt remapping drivers use __init code during initialization, and I’m not sure how to plumb the struct virtio_device * into the IOMMU initialization code. What is the proper