Skip to content

bidirectional guest channel

Marcin Hajkowski dpdk-dev 6 versions – Applied

Status from this message: Applied, thanks

Get series with b4
b4 am [email protected]

Versions newest first · linked by author and title

  1. v6 Latest4 patches 1 replyApplied
  2. v54 patches 10 repliesSuperseded
  3. v44 patches 1 replySuperseded
Earlier versions · 3
VersionPostedPatchesRepliesStatus
v34 patches9 repliesSuperseded
v24 patches1 replySuperseded
v14 patches3 repliesSuperseded

Changes in v6 from the cover letter

* put map file api's in alphabetical order
* fix checkpatch issue around experimental tag

Patches in v6 Applied

#Subject and filesSizeRepliesApplied
1/4power: fix invalid socket indicator valuelib/librte_power/guest_channel.c+6 -60 replies
2/4power: extend guest channel API for readinglib/librte_power/channel_commands.h lib/librte_power/guest_channel.c lib/librte_power/guest_channel.h +1 more+102 -00 replies
3/4power: process incoming confirmation cmdsexamples/vm_power_manager/guest_cli/Makefile examples/vm_power_manager/guest_cli/vm_power_cli_guest.c+61 -130 replies
4/4power: send confirmation cmd to vm guestexamples/vm_power_manager/channel_monitor.c+62 -60 replies

Reviews trailers per patch

All 4 patches have a Reviewed-by or Acked-by.

PatchMaxime CoquelinAnatoly BurakovDavid HuntLee Daly
1/4R-b A-b
2/4T-b A-b
3/4T-b A-b
4/4T-b A-b

Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes. Scroll the table sideways for all 4 reviewers.

Read the v6 thread

Cover letter [dpdk-dev] [PATCH v6 0/4] bidirectional guest channel

Extend guest channel API to allow bidirectional communication. Modify power manager host and guest side to communicate in both directions.

---

v6:
* put map file api's in alphabetical order
* fix checkpatch issue around experimental tag

v5:
* enhance logging

v4:
* [vm_power_manager] treat 0 as valid socket id
* [guest_manager] use user level logs
* correct code formatting

v3:
* fix global_fds[lcore_id] comparison to invalid value
* check 0 to verify if read function actually read some data
* define _NACK cmd instead of _NAK
* simplify rte_power_guest_channel_receive_msg func logic

v2:
* send ack only if power operation return positive value
* log diffent error for unexpected incoming command and error during ack/nak cmd sending

Marcin Hajkowski (4):
[PATCH v6 1/4] power: fix invalid socket indicator value [PATCH v6 2/4] power: extend guest channel API for reading [PATCH v6 3/4] power: process incoming confirmation cmds [PATCH v6 4/4] power: send confirmation cmd to vm guest