search for: fastmodel

..., but I need to understand that part a bit better. > I'll reply to that patch in a day or two after looking at how _CCA is > supposed to work. Thanks. I do think that whatever solution we come up with for virtio 1 should influence what we do for legacy. > > We can't detect the fastmodel, > > Surely, it puts a hardware id somewhere? I think you mean > fastmodel isn't always affected, right? I don't think there's a hardware ID. The thing is, the fastmodel is a toolkit for building all sorts of platforms: you can chop and change the CPUs, the peripherals, the m...

..., but I need to understand that part a bit better. > I'll reply to that patch in a day or two after looking at how _CCA is > supposed to work. Thanks. I do think that whatever solution we come up with for virtio 1 should influence what we do for legacy. > > We can't detect the fastmodel, > > Surely, it puts a hardware id somewhere? I think you mean > fastmodel isn't always affected, right? I don't think there's a hardware ID. The thing is, the fastmodel is a toolkit for building all sorts of platforms: you can chop and change the CPUs, the peripherals, the m...

...'ll reply to that patch in a day or two after looking at how _CCA is > >> supposed to work. > > > > Thanks. I do think that whatever solution we come up with for virtio 1 > > should influence what we do for legacy. > > > >>> We can't detect the fastmodel, > >> > >> Surely, it puts a hardware id somewhere? I think you mean > >> fastmodel isn't always affected, right? > > > > I don't think there's a hardware ID. The thing is, the fastmodel is a > > toolkit for building all sorts of platforms:...

...'ll reply to that patch in a day or two after looking at how _CCA is > >> supposed to work. > > > > Thanks. I do think that whatever solution we come up with for virtio 1 > > should influence what we do for legacy. > > > >>> We can't detect the fastmodel, > >> > >> Surely, it puts a hardware id somewhere? I think you mean > >> fastmodel isn't always affected, right? > > > > I don't think there's a hardware ID. The thing is, the fastmodel is a > > toolkit for building all sorts of platforms:...

...!virtio_has_feature(vdev, VIRTIO_F_VERSION_1); >>>> >>>> return false; >>> >>> This is exactly what I feared. >> >> Yes, sorry about this. It works fine for virtio-pci (where "dma-coherent" >> is used) and it also works on the fastmodel if you disable cache-modelling >> (which is needed to make the thing run at a usable pace) so we didn't spot >> this in testing. >> >>> Could we identify fastboot and do the special dance just for it? >> >> [assuming you mean fastmodel instead of fastboot]...

...!virtio_has_feature(vdev, VIRTIO_F_VERSION_1); >>>> >>>> return false; >>> >>> This is exactly what I feared. >> >> Yes, sorry about this. It works fine for virtio-pci (where "dma-coherent" >> is used) and it also works on the fastmodel if you disable cache-modelling >> (which is needed to make the thing run at a usable pace) so we didn't spot >> this in testing. >> >>> Could we identify fastboot and do the special dance just for it? >> >> [assuming you mean fastmodel instead of fastboot]...

...dev->dev) == DEV_DMA_COHERENT) > > return !virtio_has_feature(vdev, VIRTIO_F_VERSION_1); > > > > return false; > > This is exactly what I feared. Yes, sorry about this. It works fine for virtio-pci (where "dma-coherent" is used) and it also works on the fastmodel if you disable cache-modelling (which is needed to make the thing run at a usable pace) so we didn't spot this in testing. > Could we identify fastboot and do the special dance just for it? [assuming you mean fastmodel instead of fastboot] > I'd like to do that instead. It's fa...

...dev->dev) == DEV_DMA_COHERENT) > > return !virtio_has_feature(vdev, VIRTIO_F_VERSION_1); > > > > return false; > > This is exactly what I feared. Yes, sorry about this. It works fine for virtio-pci (where "dma-coherent" is used) and it also works on the fastmodel if you disable cache-modelling (which is needed to make the thing run at a usable pace) so we didn't spot this in testing. > Could we identify fastboot and do the special dance just for it? [assuming you mean fastmodel instead of fastboot] > I'd like to do that instead. It's fa...

...part a bit better. >> I'll reply to that patch in a day or two after looking at how _CCA is >> supposed to work. > > Thanks. I do think that whatever solution we come up with for virtio 1 > should influence what we do for legacy. > >>> We can't detect the fastmodel, >> >> Surely, it puts a hardware id somewhere? I think you mean >> fastmodel isn't always affected, right? > > I don't think there's a hardware ID. The thing is, the fastmodel is a > toolkit for building all sorts of platforms: you can chop and change > t...

Hi all, I noticed that upstream UEFI is now supported ARMv8 on FastModel. I’ve tried it to boot Linux with it. And it works. But it seems it still cannot load Xen hypervisor properly. I’m now looking for the reasons. Is there any difference for a firmware to load Xen and Linux kernel? Cheers, Baozi

...that patch in a day or two after looking at how _CCA is >>>> supposed to work. >>> >>> Thanks. I do think that whatever solution we come up with for virtio 1 >>> should influence what we do for legacy. >>> >>>>> We can't detect the fastmodel, >>>> >>>> Surely, it puts a hardware id somewhere? I think you mean >>>> fastmodel isn't always affected, right? >>> >>> I don't think there's a hardware ID. The thing is, the fastmodel is a >>> toolkit for building all sor...

...'ll reply to that patch in a day or two after looking at how _CCA is > >> supposed to work. > > > > Thanks. I do think that whatever solution we come up with for virtio 1 > > should influence what we do for legacy. > > > >>> We can't detect the fastmodel, > >> > >> Surely, it puts a hardware id somewhere? I think you mean > >> fastmodel isn't always affected, right? > > > > I don't think there's a hardware ID. The thing is, the fastmodel is a > > toolkit for building all sorts of platforms:...

...'ll reply to that patch in a day or two after looking at how _CCA is > >> supposed to work. > > > > Thanks. I do think that whatever solution we come up with for virtio 1 > > should influence what we do for legacy. > > > >>> We can't detect the fastmodel, > >> > >> Surely, it puts a hardware id somewhere? I think you mean > >> fastmodel isn't always affected, right? > > > > I don't think there's a hardware ID. The thing is, the fastmodel is a > > toolkit for building all sorts of platforms:...

...; > > > > > > > > > return false; > > > > > > > > This is exactly what I feared. > > > > > > Yes, sorry about this. It works fine for virtio-pci (where "dma-coherent" > > > is used) and it also works on the fastmodel if you disable cache-modelling > > > (which is needed to make the thing run at a usable pace) so we didn't spot > > > this in testing. > > > > > > > Could we identify fastboot and do the special dance just for it? > > > > > > [assuming...

...gt; > > > > an SMMU for ARM-based machines. > > > > > > > > > > > > > So how come people report failures due to presence of SMMU? > > > > Using some other hypervisor? > > > > > > The failures are reported on the ARM fastmodel (a complete system > > > emulation that runs on an x86 box), where an SMMU *is* present > > > downstream of the virtio-pci masters. There's no qemu involved there. > > > > > I see. And this hypervisor actually coded up looking up > > translations in the S...

...gt; > > > > an SMMU for ARM-based machines. > > > > > > > > > > > > > So how come people report failures due to presence of SMMU? > > > > Using some other hypervisor? > > > > > > The failures are reported on the ARM fastmodel (a complete system > > > emulation that runs on an x86 box), where an SMMU *is* present > > > downstream of the virtio-pci masters. There's no qemu involved there. > > > > > I see. And this hypervisor actually coded up looking up > > translations in the S...

...nding (from talking to Peter Maydell) is that qemu doesn't model > > > an SMMU for ARM-based machines. > > > > > > > So how come people report failures due to presence of SMMU? > > Using some other hypervisor? > > The failures are reported on the ARM fastmodel (a complete system > emulation that runs on an x86 box), where an SMMU *is* present > downstream of the virtio-pci masters. There's no qemu involved there. > > Will I see. And this hypervisor actually coded up looking up translations in the SMMU unconditionally for legacy devices,...

...nding (from talking to Peter Maydell) is that qemu doesn't model > > > an SMMU for ARM-based machines. > > > > > > > So how come people report failures due to presence of SMMU? > > Using some other hypervisor? > > The failures are reported on the ARM fastmodel (a complete system > emulation that runs on an x86 box), where an SMMU *is* present > downstream of the virtio-pci masters. There's no qemu involved there. > > Will I see. And this hypervisor actually coded up looking up translations in the SMMU unconditionally for legacy devices,...

...gt; > return !virtio_has_feature(vdev, VIRTIO_F_VERSION_1); > > > > > > return false; > > > > This is exactly what I feared. > > Yes, sorry about this. It works fine for virtio-pci (where "dma-coherent" > is used) and it also works on the fastmodel if you disable cache-modelling > (which is needed to make the thing run at a usable pace) so we didn't spot > this in testing. > > > Could we identify fastboot and do the special dance just for it? > > [assuming you mean fastmodel instead of fastboot] > > > I...

...MMU for ARM-based machines. >>>>>>> >>>>>> >>>>>> So how come people report failures due to presence of SMMU? >>>>>> Using some other hypervisor? >>>>> >>>>> The failures are reported on the ARM fastmodel (a complete system >>>>> emulation that runs on an x86 box), where an SMMU *is* present >>>>> downstream of the virtio-pci masters. There's no qemu involved there. >>>>> >>>> I see. And this hypervisor actually coded up looking up >&gt...