tim at xen
May 8, 2012, 1:50 AM
Post #1 of 1
At 09:49 +0100 on 08 May (1336470591), Tim Deegan wrote:
Re: ioreq pages in vm memory and ioreq demux
> Ccing xen-devel.
Actually this time.
> At 11:29 -0700 on 07 May (1336390171), Christian Limpach wrote:
> > > The current version of Xen allocates the shared page directly
> > > in vm memory with other pages (like XenStore page) called
> > > special pages. I just begin to hack Xen, so I used the same
> > > technique. If you have another idea I'm interested.
> > Yes, I think the ioreq pages should be allocated from the xen heap.
> > As far as I can tell, they don't need to be guest accessible. Your
> > approach is fine, but since we're making the number of pages dynamic,
> > now might be a good time to change this.
> > I was hoping for someone to remember the reason why the pages are
> > where they are in the first place, anybody?
> Before my time, but one advantage of it is that the pages are allocated
> up front as part of the VM's memory so the balloon code in the toolstack
> doesn't need to know about it. That's not a big deal, but if you're
> going to change it it would be good to update xl, and at least contact
> the XCP devs about it.
Xen-devel mailing list
Xen-devel [at] lists