On Tue, Aug 02, 2016 at 03:20:41PM -0400, Paolo Bonzini wrote:
[...]
> > I have just noticed that this fell through the cracks, sorry.
> > Applied to numa-next. Thanks!
>
> Actually I am just finishing tests of a pull request that included it
> (because I was the one that caused the regression).
- Original Message -
> From: "Eduardo Habkost"
> To: "Igor Mammedov"
> Cc: "Greg Kurz" , "Thomas Huth" ,
> qemu-devel@nongnu.org, pbonz...@redhat.com
> Sent: Tuesday, August 2, 2016 8:00:06 PM
> Subject: Re: [Qemu-devel]
On Tue, Jul 19, 2016 at 12:07:53PM +0200, Igor Mammedov wrote:
> On Tue, 19 Jul 2016 10:28:35 +0200
> Greg Kurz wrote:
>
> > Commit 2aece63 "hostmem: detect host backend memory is being used properly"
> > added a way to know if a memory backend is busy or available for use. It
> > caused a slight
On Tue, 19 Jul 2016 10:28:35 +0200
Greg Kurz wrote:
> Commit 2aece63 "hostmem: detect host backend memory is being used properly"
> added a way to know if a memory backend is busy or available for use. It
> caused a slight regression if we pass the same backend to a NUMA node and
> to a pc-dimm d
Commit 2aece63 "hostmem: detect host backend memory is being used properly"
added a way to know if a memory backend is busy or available for use. It
caused a slight regression if we pass the same backend to a NUMA node and
to a pc-dimm device:
-m 1G,slots=2,maxmem=2G \
-object memory-backend-ram,s
