Skip to contentSkip to conversation

2.6.40 event idx patches

DISCUSSION Michael S. Tsirkin 2 participants 5 messages May 24, 2011 – May 28, 2011 virtio core

lore
Share & tools
lore

Michael S. Tsirkin

author maintainer
#0 lore raw

Just checking: were you going to send the following to Linus for 2.6.40? virtio:event_index_interface.patch virtio:ring_inline_function_to_check_for_events.patch virtio:ring_support_event_idx_feature.patch misc:vhost_support_event_index.patch virtio:test_support_event_index.patch virtio:add_api_for_delayed_callbacks.patch virtio:net_delay_tx_callbacks.patch

I certainly hope so as these modify both host and guest which makes testing them out of tree hard for people.
Once stuff lands on Linus' tree we can patch
qemu and get more people to try out the patches.

Also, Linus said it's going to be a short window so ...

Signature · 1 line
MST
#1 lore raw
Quoted 9 lines · Michael S. Tsirkin

Just checking: were you going to send the following to Linus for 2.6.40? virtio:event_index_interface.patch virtio:ring_inline_function_to_check_for_events.patch virtio:ring_support_event_idx_feature.patch misc:vhost_support_event_index.patch virtio:test_support_event_index.patch virtio:add_api_for_delayed_callbacks.patch virtio:net_delay_tx_callbacks.patch

Quoted 6 lines

I certainly hope so as these modify both host and guest which makes testing them out of tree hard for people.
Once stuff lands on Linus' tree we can patch
qemu and get more people to try out the patches.

Also, Linus said it's going to be a short window so ...

Yes. They've been in linux-next since the weekend (ie. today will be the third linux-next build), and my plan was to push them Friday.

Nothing goes into linux-next which is not for Linus until after Linus closes the merge window.

I also want to find a few cycles to adapt lguest; it's *always* good to have a second implementation.

Cheers,
Rusty.

author maintainer
#2 lore raw
Quoted 15 lines · Rusty Russell
Quoted 14 lines · Michael S. Tsirkin

Just checking: were you going to send the following to Linus for 2.6.40? virtio:event_index_interface.patch virtio:ring_inline_function_to_check_for_events.patch virtio:ring_support_event_idx_feature.patch misc:vhost_support_event_index.patch virtio:test_support_event_index.patch virtio:add_api_for_delayed_callbacks.patch virtio:net_delay_tx_callbacks.patch

I certainly hope so as these modify both host and guest which makes testing them out of tree hard for people.
Once stuff lands on Linus' tree we can patch
qemu and get more people to try out the patches.

Quoted 7 lines
Quoted 1 line

Also, Linus said it's going to be a short window so ...

Yes. They've been in linux-next since the weekend (ie. today will be the third linux-next build), and my plan was to push them Friday.

Nothing goes into linux-next which is not for Linus until after Linus closes the merge window.

I see, there are for-linus tags in the series file, this is what got me worried.

Quoted 5 lines

I also want to find a few cycles to adapt lguest; it's *always* good to have a second implementation.

Cheers,
Rusty.

Absolutely.

Signature · 1 line
MST
author maintainer
#3 lore raw
In reply to Rusty Russell
Quoted 20 lines · Rusty Russell
Quoted 9 lines · Michael S. Tsirkin

Just checking: were you going to send the following to Linus for 2.6.40? virtio:event_index_interface.patch virtio:ring_inline_function_to_check_for_events.patch virtio:ring_support_event_idx_feature.patch misc:vhost_support_event_index.patch virtio:test_support_event_index.patch virtio:add_api_for_delayed_callbacks.patch virtio:net_delay_tx_callbacks.patch

Quoted 6 lines

I certainly hope so as these modify both host and guest which makes testing them out of tree hard for people.
Once stuff lands on Linus' tree we can patch
qemu and get more people to try out the patches.

Also, Linus said it's going to be a short window so ...

Yes. They've been in linux-next since the weekend (ie. today will be the third linux-next build), and my plan was to push them Friday.

Quoted 8 lines

Nothing goes into linux-next which is not for Linus until after Linus closes the merge window.

I also want to find a few cycles to adapt lguest; it's *always* good to have a second implementation.

Cheers,
Rusty.

Couldn't find any pull requests at lkml, and I read the window will likely close May 29. Did you end up not sending it, or did I miss it?

Signature · 1 line
MST
author maintainer
#4 lore raw
Quoted 24 lines · Michael S. Tsirkin
Quoted 23 lines · Rusty Russell
Quoted 9 lines · Michael S. Tsirkin

Just checking: were you going to send the following to Linus for 2.6.40? virtio:event_index_interface.patch virtio:ring_inline_function_to_check_for_events.patch virtio:ring_support_event_idx_feature.patch misc:vhost_support_event_index.patch virtio:test_support_event_index.patch virtio:add_api_for_delayed_callbacks.patch virtio:net_delay_tx_callbacks.patch

Quoted 6 lines

I certainly hope so as these modify both host and guest which makes testing them out of tree hard for people.
Once stuff lands on Linus' tree we can patch
qemu and get more people to try out the patches.

Also, Linus said it's going to be a short window so ...

Yes. They've been in linux-next since the weekend (ie. today will be the third linux-next build), and my plan was to push them Friday.

Nothing goes into linux-next which is not for Linus until after Linus closes the merge window.

Quoted 8 lines
Quoted 5 lines

I also want to find a few cycles to adapt lguest; it's *always* good to have a second implementation.

Cheers,
Rusty.

Couldn't find any pull requests at lkml, and I read the window will likely close May 29. Did you end up not sending it, or did I miss it?

Pls ignore, problem at my end.
Thanks, and sorry about the noise.

Quoted 2 lines
Signature · 1 line
MST