From: Juan Quintela <quintela@redhat.com>
To: KVM devel mailing list <kvm@vger.kernel.org>,
qemu-devel qemu-devel <qemu-devel@nongnu.org>
Subject: KVM call minutes for 2014-02-18
Date: Tue, 18 Feb 2014 16:05:13 +0100 [thread overview]
Message-ID: <87eh30cvh2.fsf@elfo.mitica> (raw)
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?
next reply other threads:[~2014-02-18 15:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-18 15:05 Juan Quintela [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-02-18 15:05 KVM call minutes for 2014-02-18 Juan Quintela
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87eh30cvh2.fsf@elfo.mitica \
--to=quintela@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox