From: Si-Wei Liu <si-wei.liu@oracle.com>
To: mst@redhat.com, jasowang@redhat.com
Cc: virtualization@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Subject: [PATCH 1/4] vdpa: save vdpa_dev_set_config in struct vdpa_device
Date: Fri, 14 Oct 2022 17:28:07 -0700 [thread overview]
Message-ID: <1665793690-28120-2-git-send-email-si-wei.liu@oracle.com> (raw)
In-Reply-To: <1665793690-28120-1-git-send-email-si-wei.liu@oracle.com>
In order to allow live migration orchestration software to export the
initial set of vdpa attributes with which the device was created, it
will be useful if the vdpa tool can report the config on demand with
simple query. This will ease the orchestration software implementation
so that it doesn't have to keep track of vdpa config change, or have
to persist vdpa attributes across failure and recovery, in fear of
being killed due to accidental software error.
This commit attempts to make struct vdpa_device contain the struct
vdpa_dev_set_config, where all config attributes upon vdpa creation
are carried over. Which will be used in subsequent commits.
Signed-off-by: Si-Wei Liu <si-wei.liu@oracle.com>
---
include/linux/vdpa.h | 23 +++++++++++++----------
1 file changed, 13 insertions(+), 10 deletions(-)
diff --git a/include/linux/vdpa.h b/include/linux/vdpa.h
index 6d0f5e4..f1838f5 100644
--- a/include/linux/vdpa.h
+++ b/include/linux/vdpa.h
@@ -58,6 +58,16 @@ struct vdpa_vq_state {
};
};
+struct vdpa_dev_set_config {
+ u64 device_features;
+ struct {
+ u8 mac[ETH_ALEN];
+ u16 mtu;
+ u16 max_vq_pairs;
+ } net;
+ u64 mask;
+};
+
struct vdpa_mgmt_dev;
/**
@@ -77,6 +87,8 @@ struct vdpa_vq_state {
* @nvqs: maximum number of supported virtqueues
* @mdev: management device pointer; caller must setup when registering device as part
* of dev_add() mgmtdev ops callback before invoking _vdpa_register_device().
+ * @vdev_cfg: initial device config on vdpa creation; useful when instantiate with
+ * the exact same config is needed.
*/
struct vdpa_device {
struct device dev;
@@ -91,6 +103,7 @@ struct vdpa_device {
struct vdpa_mgmt_dev *mdev;
unsigned int ngroups;
unsigned int nas;
+ struct vdpa_dev_set_config vdev_cfg;
};
/**
@@ -103,16 +116,6 @@ struct vdpa_iova_range {
u64 last;
};
-struct vdpa_dev_set_config {
- u64 device_features;
- struct {
- u8 mac[ETH_ALEN];
- u16 mtu;
- u16 max_vq_pairs;
- } net;
- u64 mask;
-};
-
/**
* Corresponding file area for device memory mapping
* @file: vma->vm_file for the mapping
--
1.8.3.1
next prev parent reply other threads:[~2022-10-15 1:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-15 0:28 [PATCH 0/4] vDPA: dev config export via "vdpa dev show" command Si-Wei Liu
2022-10-15 0:28 ` Si-Wei Liu [this message]
2022-10-15 0:28 ` [PATCH 2/4] vdpa: pass initial config to _vdpa_register_device() Si-Wei Liu
2022-10-15 0:28 ` [PATCH 3/4] vdpa: show dev config as-is in "vdpa dev show" output Si-Wei Liu
2022-10-15 0:28 ` [PATCH 4/4] vdpa: fix improper error message when adding vdpa dev Si-Wei Liu
2022-10-17 7:08 ` [PATCH 0/4] vDPA: dev config export via "vdpa dev show" command Jason Wang
2022-10-17 12:28 ` Sean Mooney
2022-10-17 23:35 ` Si-Wei Liu
2022-10-18 7:59 ` Jason Wang
2022-10-19 9:08 ` Sean Mooney
2022-10-21 7:13 ` Jason Wang
2022-10-21 11:51 ` Sean Mooney
2022-10-17 22:58 ` Si-Wei Liu
2022-10-18 8:41 ` Jason Wang
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=1665793690-28120-2-git-send-email-si-wei.liu@oracle.com \
--to=si-wei.liu@oracle.com \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=virtualization@lists.linux-foundation.org \
/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
all inboxes | Powered by JetHome®