On 01/26/2010 02:17 PM, Adam Litke wrote:
The changes in V8 of this patch are related to the monitor infrastructure. No
changes to the virtio interface core have been made since V4. This is intended
to apply on top of my API for asynchronous monitor commands patch.
Changes since V7:
- Ported
The changes in V8 of this patch are related to the monitor infrastructure. No
changes to the virtio interface core have been made since V4. This is intended
to apply on top of my API for asynchronous monitor commands patch.
Changes since V7:
- Ported to the asynchronous monitor API
Changes sin
This version improves support for multiple monitors and has been ported up to
HEAD as of 01/14.
Changes since V6:
- Integrated with virtio qdev feature bit changes
(specifically: Use VirtIODevice 'guest_features' to check if memory stats
is a negotiated feature)
- Track which monitor initi
After some good discussion, V6 of this patch integrates well with the new QMP
support. When the monitor is in QMP mode, the query-balloon command triggers a
stats refresh request to the guest. This request is asynchronous. If the
guest does not respond then nothing further happens. When stats a
This iteration addresses all of the comments from the last round. Thanks to
everyone for their careful reviews and helpful comments. The most significant
change in this version is my use of the QObject API, so a concentrated review
in that area would be most appreciated. I am hoping to target 0.
Rusty and Anthony,
If I've addressed all outstanding issues, please consider this patch for
inclusion. Thanks.
Changes since V2:
- Increase stat field size to 64 bits
- Report all sizes in kb (not pages)
- Drop anon_pages stat and fix endianness conversion
Changes since V1:
- Use a virtqueue
virtio: Add memory statistics reporting to the balloon driver (V2)
Changes since V1:
- Use a virtqueue instead of the device config space
When using ballooning to manage overcommitted memory on a host, a system for
guests to communicate their memory usage to the host can provide information
that
When using ballooning to manage overcommitted memory on a host, a system for
guests to communicate their memory usage to the host can provide information
that will minimize the impact of ballooning on the guests. The current method
employs a daemon running in each guest that communicates memory st
Here are the corresponding changes to the Linux virtio driver...
virtio: Add memory statistics reporting to the balloon driver
When using ballooning to manage overcommitted memory on a host, a system for
guests to communicate their memory usage to the host can provide information
