On 02/20/17 15:57, Igor Mammedov wrote: > On Thu, 16 Feb 2017 15:15:32 -0800 > b...@skyportsystems.com wrote: > >> From: Ben Warren <b...@skyportsystems.com> >> >> This patch set adds support for passing a GUID to Windows guests. It is a >> re-implementation of previous patch sets written by Igor Mammedov et al, but >> this time passing the GUID data as a fw_cfg blob. >> >> This patch set has dependencies on new guest functionality, in particular the >> support for a new linker-loader command and the ability to write back data >> to QEMU over a DMA link. Work is in flight in both SeaBIOS and OVMF to >> support this. >> >> v7->v8: >> - Rebased to top of tree. >> - Fixed two small bugs in "write pointer" function >> - minor re-ordering of data in patches >> - Fixed unit test by adding delays/retries to reading RSDP table > Michael, > > series looks good for merging. > Patch > [PATCH v8 7/8] tests: Add unit tests for the VM Generation ID feature > needs updated seabios blob to make 'make check' happy > so we probably should merge/update seabios first > [PATCH v5 0/5] QEMU: Add capability to write back fw_cfg address to QEMU > > CCing Gerd and Kevin. >
That's sort of a circular dependency, as Kevin generally prefers to merge SeaBIOS patches once the underlying QEMU code has been committed :) For a total ordering, all QEMU patches except v8 7/8 could be merged in QEMU, then the v5 SeaBIOS patches could be merged, then Gerd could refresh the bundled SeaBIOS binaries, then QEMU patch v8 7/8 could be merged. I'm not actually suggesting that though, given that the soft freeze is in about a week. Kevin, can you please make an exception this time and merge the SeaBIOS patches ahead of the QEMU patches? Thanks! Laszlo
