Re: [Xen-devel] gross qemu behavior

[Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>]

On Fri, 4 Apr 2014, Jan Beulich wrote:
> >>> On 04.04.14 at 15:53, <stefano.stabellini@xxxxxxxxxxxxx> wrote:
> > On Fri, 4 Apr 2014, Jan Beulich wrote:
> >> No, it should just never appear at the wrong address. As I said above,
> >> I'd consider it halfway acceptable if it remained mapped despite an
> >> unmap, but I do think that a proper solution (properly unmapping
> >> without de-allocating) can and should be found.
> > 
> > There is no way to do it today AFAICT.
> > Would you care of proposing an hypercall that would support this
> > scenario?
> 
> Hypercall? Everything you need is there afaict.

Maybe I am missing something.

Moving the PCI ROM to the right place in the guest physmap is easy.
However how do you think we could unmap the memory (remove it from the
guest physmap) without deallocating it?
The only hypercall we have is xc_domain_add_to_physmap at the moment.

Unless you are thinking of allocating the ROM in a QEMU buffer, but that
would still go against QEMU's way and has the same bad side effects of
the other approach.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel