On Tue, Sep 03, 2019 at 04:03:54PM +0100, Peter Maydell wrote: > On Wed, 28 Aug 2019 at 19:40, Eduardo Habkost <[email protected]> wrote: > > > > Sorry for taking so long after 4.1.0 to send this. I had to sort > > out some conflicts with recent header cleanups. > > > > The following changes since commit 23919ddfd56135cad3cb468a8f54d5a595f024f4: > > > > Merge remote-tracking branch 'remotes/aperard/tags/pull-xen-20190827' > > into staging (2019-08-27 15:52:36 +0100) > > > > are available in the Git repository at: > > > > git://github.com/ehabkost/qemu.git tags/machine-next-pull-request > > > > for you to fetch changes up to f4abcc0a75f1310dbe66b852ed97ec7caf2708d5: > > > > i386/vmmouse: Properly reset state (2019-08-27 16:50:14 -0300) > > > > ---------------------------------------------------------------- > > Machine + x86 queue, 2019-08-28 > > > > Bug fixes: > > * Fix die-id validation regression (Eduardo Habkost) > > * vmmouse: Properly reset state (Jan Kiszka) > > * hostmem-file: fix pmem file size check (Stefan Hajnoczi) > > > > Cleanups: > > * NUMA code cleanups (Tao Xu) > > * Remove stale externs from includes (Alex Bennée) > > > > Features: > > * qapi: report the default CPU type for each machine (Daniel P. Berrangé) > > > > ---------------------------------------------------------------- > > Hi. This generates extra warnings during 'make check' > that all look like: > > qemu-system-ppc64: warning: Default splitting of RAM between nodes is > deprecated, Use '-numa node,memdev' to explictly define RAM allocation > per node > > Can you suppress them, please (or fix them if they are > legitimate)?
I'm removing the patch that causes the spurious warnings, and I'll send a new pull request soon. -- Eduardo
