Re: [Qemu-devel] [PATCH V9 10/16] xen: Introduce the Xen mapcache

2011-01-31 Thread Stefano Stabellini
On Wed, 26 Jan 2011, Anthony Liguori wrote: > > +void qemu_invalidate_map_cache(void) > > +{ > > +unsigned long i; > > +MapCacheRev *reventry; > > + > > +qemu_aio_flush(); > > > > This is bizarre? Why is this needed? > Sorry, I forgot to reply to this question. Xen might send an IO

Re: [Qemu-devel] [PATCH V9 10/16] xen: Introduce the Xen mapcache

2011-01-27 Thread Stefano Stabellini
On Wed, 26 Jan 2011, Anthony Liguori wrote: > > +#ifdef MAPCACHE_DEBUG > > +# define DPRINTF(fmt, ...) do { \ > > +fprintf(stderr, "xen_mapcache: " fmt, ## __VA_ARGS__); \ > > +} while (0) > > +#else > > +# define DPRINTF(fmt, ...) do { } while (0) > > +#endif > > + > > +#if defined(__i386__)

Re: [Qemu-devel] [PATCH V9 10/16] xen: Introduce the Xen mapcache

2011-01-26 Thread Anthony Liguori
On 01/25/2011 08:29 AM, anthony.per...@citrix.com wrote: From: Jun Nakajima On IA32 host or IA32 PAE host, at present, generally, we can't create an HVM guest with more than 2G memory, because generally it's almost impossible for Qemu to find a large enough and consecutive virtual address space

[Qemu-devel] [PATCH V9 10/16] xen: Introduce the Xen mapcache

2011-01-25 Thread anthony . perard
From: Jun Nakajima On IA32 host or IA32 PAE host, at present, generally, we can't create an HVM guest with more than 2G memory, because generally it's almost impossible for Qemu to find a large enough and consecutive virtual address space to map an HVM guest's whole physical address space. The at