* KVM call minutes for 2014-02-18
@ 2014-02-18 15:05 Juan Quintela
0 siblings, 0 replies; 2+ messages in thread
From: Juan Quintela @ 2014-02-18 15:05 UTC (permalink / raw)
To: KVM devel mailing list, qemu-devel qemu-devel
2014-02-18
----------
* [Qemu-devel] [PATCH V17 00/11] Add support for binding guest numa
nodes
Any news about this? (Vinod)
* Should we change anything to get more people to sign for the call?
There hasn't been a call in quite a long time. Ideas? (me)
* x2apic?
- Pending patch for cpu feature flag.
- Should this be the default.
- It is not for 32bits, but should it be for 64bit?
- libvirt always use x2apic, unconditionally?
- What happens if one side of migration uses -m <cpu_something and the
other -m cpu_something+x2apic
- disabling if for all old machine types
- Use the same that hyperv flags?
* release
- No Anthony
- People happy (on happy enough) with current schedule
* Maintenance?
- How is being handling patches for the stable release?
CC: stable@ for stable maintance.
- add documentation about what/how to send patches for stable release
- Regressions deserve a backport almost always?
- There is no stable tree public where we see what patches are being integrated?
- How can we make more people additoally to Michael to work with stable branches
- Should we change anynthing?
^ permalink raw reply [flat|nested] 2+ messages in thread
* KVM call minutes for 2014-02-18
@ 2014-02-18 15:05 Juan Quintela
0 siblings, 0 replies; 2+ messages in thread
From: Juan Quintela @ 2014-02-18 15:05 UTC (permalink / raw)
To: KVM devel mailing list, qemu-devel qemu-devel
2014-02-18
----------
* x2apic?
- Pending patch for cpu feature flag.
- Should this be the default.
- It is not for 32bits, but should it be for 64bit?
- libvirt always use x2apic, unconditionally?
- What happens if one side of migration uses -m <cpu_something and the
other -m cpu_something+x2apic
- disabling if for all old machine types
- Use the same that hyperv flags?
* release
- No Anthony
- People happy (on happy enough) with current schedule
* Maintenance?
- How is being handling patches for the stable release?
CC: stable@ for stable maintance.
- add documentation about what/how to send patches for stable release
- Regressions deserve a backport almost always?
- There is no stable tree public where we see what patches are being integrated?
- How can we make more people additoally to Michael to work with stable branches
- Should we change anynthing?
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2014-02-18 15:05 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-02-18 15:05 KVM call minutes for 2014-02-18 Juan Quintela
-- strict thread matches above, loose matches on Subject: below --
2014-02-18 15:05 Juan Quintela
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox