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: Re: Outstanding issues for next meeting.

On Thu, Oct 24, 2013 at 02:14:08PM +1030, Rusty Russell wrote:
> Hi all,
>         As stated before, I'd like to get close to a first draft after
> the next meeting.    That means if you think you have rough consensus
> on a patch, please OPEN the corresponding bug report, eg:
> VIRTIO-43 	ccw: Support for adapter interrupts.
> VIRTIO-42 	ccw: Provide a revision mechanism.
> VIRTIO-41 	mmio: Remove 'align' and use explicit addresses for used/avail.
> VIRTIO-40 	ccw: Remove 'align' and use explicit addresses for used/avail.
> Michael, do you want to come up with a patch proposal for this one?
> VIRTIO-39 	pci device operation without BAR access
> These will be resolved if we decide to accept the new ballon device
> (Daniel?):
> VIRTIO-37 	allow >4G 4K pages in balloon 	Unassigned
> VIRTIO-36 	balloon: align val in virtio_balloon_stat
> VIRTIO-25 	balloon: remove VIRTIO_BALLOON_F_MUST_TELL_HOST and deflate queue.
> VIRTIO-24 	balloon: don't define endianness separately for config space.

I have just sent my comments. Sorry for delay but I am very busy now.

> I'm about to propose changes for these two:
> VIRTIO-16 	Allow anyone to whql their windows drivers
> VIRTIO-11 	Method to stop activity on a queue?
> And this I'm happy to leave to the formatting phase:
> VIRTIO-33 	Clearly identify feature dependencies in spec.

I have added two issues:

VIRTIO-45 	Timer/Clock device
VIRTIO-46 	Verify that VIRTIO devices could be implemented in Xen environment

I think that both of them do not block release of first working draft
but they should be solved before releasing next one.


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