From: "Hunt, David" <david.hunt@intel.com>
To: 20190402082121.5472-1-marcinx.hajkowski@intel.com
Cc: dev@dpdk.org, Marcin Hajkowski <marcinx.hajkowski@intel.com>
Subject: Re: [dpdk-dev] [PATCH v5 2/4] power: extend guest channel API for reading
Date: Thu, 26 Sep 2019 14:00:12 +0100 [thread overview]
Message-ID: <29cd9e80-a972-43a9-4277-1d34617d9f2a@intel.com> (raw)
In-Reply-To: <20190405132455.15468-3-marcinx.hajkowski@intel.com>
On 05/04/2019 14:24, Hajkowski wrote:
> From: Marcin Hajkowski <marcinx.hajkowski@intel.com>
>
> Added new experimental API rte_power_guest_channel_receive_msg
> which gives possibility to receive messages send to guest.
>
> Signed-off-by: Marcin Hajkowski <marcinx.hajkowski@intel.com>
> ---
> lib/librte_power/channel_commands.h | 5 +++
> lib/librte_power/guest_channel.c | 60 ++++++++++++++++++++++++++
> lib/librte_power/guest_channel.h | 35 +++++++++++++++
> lib/librte_power/rte_power_version.map | 1 +
> 4 files changed, 101 insertions(+)
>
> diff --git a/lib/librte_power/channel_commands.h b/lib/librte_power/channel_commands.h
> index e7b93a797..33fd53a6d 100644
> --- a/lib/librte_power/channel_commands.h
> +++ b/lib/librte_power/channel_commands.h
> @@ -28,6 +28,11 @@ extern "C" {
> #define CPU_POWER_SCALE_MIN 4
> #define CPU_POWER_ENABLE_TURBO 5
> #define CPU_POWER_DISABLE_TURBO 6
> +
> +/* Generic Power Command Response */
> +#define CPU_POWER_CMD_ACK 1
> +#define CPU_POWER_CMD_NACK 2
> +
> #define HOURS 24
>
> #define MAX_VFS 10
> diff --git a/lib/librte_power/guest_channel.c b/lib/librte_power/guest_channel.c
> index 9cf7d2cb2..888423891 100644
> --- a/lib/librte_power/guest_channel.c
> +++ b/lib/librte_power/guest_channel.c
> @@ -10,6 +10,7 @@
> #include <fcntl.h>
> #include <string.h>
> #include <errno.h>
> +#include <poll.h>
>
>
> #include <rte_log.h>
> @@ -19,6 +20,9 @@
>
> #define RTE_LOGTYPE_GUEST_CHANNEL RTE_LOGTYPE_USER1
>
> +/* Timeout for incoming message in milliseconds. */
> +#define TIMEOUT 10
> +
> static int global_fds[RTE_MAX_LCORE] = { [0 ... RTE_MAX_LCORE-1] = -1 };
>
> int
> @@ -125,6 +129,62 @@ int rte_power_guest_channel_send_msg(struct channel_packet *pkt,
> return guest_channel_send_msg(pkt, lcore_id);
> }
>
> +int power_guest_channel_read_msg(struct channel_packet *pkt,
> + unsigned int lcore_id)
> +{
> + int ret;
> + struct pollfd fds;
> + void *buffer = pkt;
> + int buffer_len = sizeof(*pkt);
> +
> + fds.fd = global_fds[lcore_id];
> + fds.events = POLLIN;
> +
> + ret = poll(&fds, 1, TIMEOUT);
> + if (ret == 0) {
> + RTE_LOG(DEBUG, GUEST_CHANNEL, "Timeout occurred during poll function.\n");
> + return -1;
> + } else if (ret < 0) {
> + RTE_LOG(ERR, GUEST_CHANNEL, "Error occurred during poll function: %s\n",
> + strerror(ret));
> + return -1;
> + }
> +
> + if (lcore_id >= RTE_MAX_LCORE) {
> + RTE_LOG(ERR, GUEST_CHANNEL, "Channel(%u) is out of range 0...%d\n",
> + lcore_id, RTE_MAX_LCORE-1);
> + return -1;
> + }
> +
> + if (global_fds[lcore_id] < 0) {
> + RTE_LOG(ERR, GUEST_CHANNEL, "Channel is not connected\n");
> + return -1;
> + }
> +
> + while (buffer_len > 0) {
> + ret = read(global_fds[lcore_id],
> + buffer, buffer_len);
> + if (ret < 0) {
> + if (errno == EINTR)
> + continue;
> + return -1;
> + }
> + if (ret == 0) {
> + RTE_LOG(ERR, GUEST_CHANNEL, "Expected more data, but connection has been closed.\n");
> + return -1;
> + }
> + buffer = (char *)buffer + ret;
> + buffer_len -= ret;
> + }
> +
> + return 0;
> +}
> +
> +int rte_power_guest_channel_receive_msg(struct channel_packet *pkt,
> + unsigned int lcore_id)
> +{
> + return power_guest_channel_read_msg(pkt, lcore_id);
> +}
>
> void
> guest_channel_host_disconnect(unsigned int lcore_id)
> diff --git a/lib/librte_power/guest_channel.h b/lib/librte_power/guest_channel.h
> index 373d39898..7c385df39 100644
> --- a/lib/librte_power/guest_channel.h
> +++ b/lib/librte_power/guest_channel.h
> @@ -68,6 +68,41 @@ int guest_channel_send_msg(struct channel_packet *pkt, unsigned int lcore_id);
> int rte_power_guest_channel_send_msg(struct channel_packet *pkt,
> unsigned int lcore_id);
>
> +/**
> + * Read a message contained in pkt over the Virtio-Serial
> + * from the host endpoint.
> + *
> + * @param pkt
> + * Pointer to a populated struct channel_packet
> + *
> + * @param lcore_id
> + * lcore_id.
> + *
> + * @return
> + * - 0 on success.
> + * - Negative on error.
> + */
> +int power_guest_channel_read_msg(struct channel_packet *pkt,
> + unsigned int lcore_id);
> +
> +/**
> + * Receive a message contained in pkt over the Virtio-Serial
> + * from the host endpoint.
> + *
> + * @param pkt
> + * Pointer to a populated struct channel_packet
> + *
> + * @param lcore_id
> + * lcore_id.
> + *
> + * @return
> + * - 0 on success.
> + * - Negative on error.
> + */
> +int __rte_experimental
> +rte_power_guest_channel_receive_msg(struct channel_packet *pkt,
> + unsigned int lcore_id);
> +
> #ifdef __cplusplus
> }
> #endif
> diff --git a/lib/librte_power/rte_power_version.map b/lib/librte_power/rte_power_version.map
> index 042917360..69f5ea3f4 100644
> --- a/lib/librte_power/rte_power_version.map
> +++ b/lib/librte_power/rte_power_version.map
> @@ -44,4 +44,5 @@ EXPERIMENTAL {
> rte_power_empty_poll_stat_update;
> rte_power_poll_stat_fetch;
> rte_power_poll_stat_update;
> + rte_power_guest_channel_receive_msg;
> };
I tested this with the later patches in the set, and the acknowledges
successfully get back to the guest from the host in the form of an Ack
or Nack for various commands sent from the guest.
Tested-by: David Hunt <david.hunt@intel.com>
next prev parent reply other threads:[~2019-09-26 13:00 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-05 13:24 [dpdk-dev] [PATCH v5 0/4] bidirect guest channel Hajkowski
2019-04-05 13:24 ` Hajkowski
2019-04-05 13:24 ` [dpdk-dev] [PATCH v5 1/4] power: fix invalid socket indicator value Hajkowski
2019-04-05 13:24 ` Hajkowski
2019-09-27 8:42 ` [dpdk-dev] [PATCH v6 0/4] bidirectional guest channel Marcin Hajkowski
2019-09-27 8:42 ` [dpdk-dev] [PATCH v6 1/4] power: fix invalid socket indicator value Marcin Hajkowski
2019-09-27 8:42 ` [dpdk-dev] [PATCH v6 2/4] power: extend guest channel API for reading Marcin Hajkowski
2019-09-27 8:42 ` [dpdk-dev] [PATCH v6 3/4] power: process incoming confirmation cmds Marcin Hajkowski
2019-09-27 8:42 ` [dpdk-dev] [PATCH v6 4/4] power: send confirmation cmd to vm guest Marcin Hajkowski
2019-10-27 18:29 ` [dpdk-dev] [PATCH v6 0/4] bidirectional guest channel Thomas Monjalon
2019-04-05 13:24 ` [dpdk-dev] [PATCH v5 2/4] power: extend guest channel API for reading Hajkowski
2019-04-05 13:24 ` Hajkowski
2019-09-26 13:00 ` Hunt, David [this message]
2019-09-26 15:53 ` Daly, Lee
2019-04-05 13:24 ` [dpdk-dev] [PATCH v5 3/4] power: process incoming confirmation cmds Hajkowski
2019-04-05 13:24 ` Hajkowski
2019-09-26 13:01 ` Hunt, David
2019-09-26 15:49 ` Daly, Lee
2019-04-05 13:24 ` [dpdk-dev] [PATCH v5 4/4] power: send confirmation cmd to vm guest Hajkowski
2019-04-05 13:24 ` Hajkowski
2019-09-26 13:06 ` Hunt, David
2019-09-26 15:47 ` Daly, Lee
2019-04-22 20:36 ` [dpdk-dev] [PATCH v5 0/4] bidirect guest channel Thomas Monjalon
2019-04-22 20:36 ` Thomas Monjalon
2019-04-24 8:38 ` Hunt, David
2019-04-24 8:38 ` Hunt, David
2019-04-24 8:44 ` Thomas Monjalon
2019-04-24 8:44 ` Thomas Monjalon
2019-07-04 19:55 ` Thomas Monjalon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=29cd9e80-a972-43a9-4277-1d34617d9f2a@intel.com \
--to=david.hunt@intel.com \
--cc=20190402082121.5472-1-marcinx.hajkowski@intel.com \
--cc=dev@dpdk.org \
--cc=marcinx.hajkowski@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).