OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

virtio message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] (VIRTIO-28) Implement new balloon device (ID 13)


     [ https://tools.oasis-open.org/issues/browse/VIRTIO-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Tsirkin updated VIRTIO-28:
----------------------------------

    Resolution: Passed in minutes of 2014-02-25 meeting, committed as r279 (deprecation and introduction of new number for future device). 

> Implement new balloon device (ID 13)
> ------------------------------------
>
>                 Key: VIRTIO-28
>                 URL: https://tools.oasis-open.org/issues/browse/VIRTIO-28
>             Project: OASIS Virtual I/O Device (VIRTIO) TC
>          Issue Type: New Feature
>            Reporter: Rusty Russell
>            Assignee: Rusty Russell
>
> The current virtio balloon device is bad enough that fixing it yields something completely incompatible:
> 1) The page size is 4096, always, rather than some configurable page size.
> 2) Page numbers are 32 bits.
> 3) The deflate queue is not actually used by any device implementation (see issue virtio-25).
> 4) The "actual" number is kind of useless, and (along with the deflate queue) requires the guest to track pages, rather than just faulting them in.
> 5) The config is little-endian by mistake (may not matter).
> We could just move the entire thing to legacy, and have a new balloon device, like:
> 1) An incoming queue for balloon size updates or stats request.
> 2) An outgoing queue for giving 64 bit address/length pairs to balloon, answering stats.
> 3) No config space, no features.
> Thoughts?



--
This message was sent by Atlassian JIRA
(v6.1.1#6155)


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]