[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [libvirt] [PATCH v5 0/2] Add new HyperV features



Il 21/06/2013 15:56, Daniel P. Berrange ha scritto:
> On Fri, Jun 21, 2013 at 03:51:37PM +0200, Paolo Bonzini wrote:
>> Il 21/06/2013 12:41, Ján Tomko ha scritto:
>>> v1:
>>> https://www.redhat.com/archives/libvir-list/2013-May/msg00173.html
>>>
>>> v2:
>>> https://www.redhat.com/archives/libvir-list/2013-May/msg00184.html
>>> uses virStringSplit instead of strsep
>>> added a missing break to virDomainDefParseXML
>>>
>>> v3:
>>> https://www.redhat.com/archives/libvir-list/2013-June/msg00228.html
>>> rebased to use VIR_STRDUP
>>> fixed a crash on parsing '-cpu qemu32,hv_'
>>>
>>> v4:
>>> https://www.redhat.com/archives/libvir-list/2013-June/msg00717.html
>>> Added state attribute to spinlocks.
>>> CPU command line parsing refactoring is already pushed.
>>> Changed version in docs from 1.0.6 to 1.0.7.
>>> Use 'value' instead of 'hv_tokens[1]' for readability.
>>>
>>> v5:
>>> Use 'retries' attribute for spinlocks instead of using the element body
>>> Prefer decimal numbers for readability
>>> Split XML parsing and QEMU implementation into separate patches
>>> Changed version to 1.1.0 since the ACL patches are ACKed now.
>>>
>>> Ján Tomko (2):
>>>   conf: add vapic and spinlocks to hyperv features
>>>   qemu: add hv_vapic and hv_spinlocks support
>>>
>>>  docs/formatdomain.html.in                       | 17 ++++++-
>>>  docs/schemas/domaincommon.rng                   | 13 +++++
>>>  src/conf/domain_conf.c                          | 64 ++++++++++++++++++++++++-
>>>  src/conf/domain_conf.h                          |  3 ++
>>>  src/qemu/qemu_command.c                         | 48 ++++++++++++++++++-
>>>  tests/qemuxml2argvdata/qemuxml2argv-hyperv.args |  2 +-
>>>  tests/qemuxml2argvdata/qemuxml2argv-hyperv.xml  |  2 +
>>>  7 files changed, 144 insertions(+), 5 deletions(-)
>>>
>>
>> hv_spinlocks is not upstream yet.
> 
> Do you have any feeling for whether it is likely to be accepted,
> and if so a possible timeframe ?

No idea, knowing that Hyper-V state in QEMU is somewhat messy I just
grepped the three options.

Paolo


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]