> > When vhost-user backend register memory region based host notifiers,
> > we should return RAM device MR of notify region MR's subregion in
> > virtio_address_space_lookup.
> >
> > In seabios, it will use virtio PCI Configration Access Capability
> > access notify region when assign notify region above 4GB. This will
> > exit to QEMU and invoke virtio_address_space_write. When vhost-user
> > backend register memory region based host notifiers, return RAM device
> > MR instead of notify region MR is suitable.
>
>
> I can't really parse this.
>
When booting from disk, SeaBIOS will invoke the INT 0x13 interrupt handler
to load the MBR. The interrupt handler will eventually utilize the virtio
block driver in SeaBIOS when the disk is a virtio block device,
and after notifying the backend via `vp_notify`, the MBR will be loaded.
When assign the address of notify region in the modern bar above 4G, the
`vp_notify` in SeaBIOS will use PCI Configuration Access Capability to
write notify region. This will trap into QEMU and be handled by the
host bridge when we don't enable mmconfig. QEMU will call
`virtio_write_config`, and since it writes to the BAR region through
the PCI Configuration Access capability, it will call
`virtio_address_space_write`.
When VHOST_USER_PROTOCOL_F_HOST_NOTIFIER protocol feature has been
successfully negotiated and vhost-user backend registers memory region based
host notifiers, QEMU need write the mmap address instead of eventfd notify
the hardware accelerator at the vhost-user backend.
So virtio_address_space_lookup in virtio_address_space_write need return a
host-notifier subregion of notify MR.
> > --- a/hw/virtio/virtio-pci.c
> > +++ b/hw/virtio/virtio-pci.c
> > @@ -610,13 +610,22 @@ static MemoryRegion
> > *virtio_address_space_lookup(VirtIOPCIProxy *proxy,
> > {
> > int i;
> > VirtIOPCIRegion *reg;
> > + MemoryRegion *mr, *submr;
> >
> > for (i = 0; i < ARRAY_SIZE(proxy->regs); ++i) {
> > reg = &proxy->regs[i];
> > if (*off >= reg->offset &&
> > *off + len <= reg->offset + reg->size) {
> > *off -= reg->offset;
> > - return ®->mr;
> > + mr = ®->mr;
> > + QTAILQ_FOREACH(submr, &mr->subregions, subregions_link) {
> > + if (*off >= submr->addr &&
> > + *off + len < submr->addr + submr->size) {
> > + *off -= submr->addr;
> > + return submr;
> > + }
> > + }
> > + return mr;
> > }
> > }
>
> Poking at internals of MR like this is not nice.
> Doesn't memory_region_find work for this?
It seems fine, I’ll try it out.
