From: Daniel Henrique Barboza <danielhb413@gmail.com>
To: qemu-devel@nongnu.org
Cc: Daniel Henrique Barboza <danielhb413@gmail.com>,
qemu-ppc@nongnu.org, clg@kaod.org,
Shivaprasad G Bhat <sbhat@linux.ibm.com>,
david@gibson.dropbear.id.au
Subject: [PATCH for-7.1 4/4] hw/ppc: use qdev to register spapr_nvdimm vmsd
Date: Tue, 22 Mar 2022 15:38:54 -0300 [thread overview]
Message-ID: <20220322183854.196063-5-danielhb413@gmail.com> (raw)
In-Reply-To: <20220322183854.196063-1-danielhb413@gmail.com>
Make the code a little more maintainable by using dc->vmsd to register
the vmstate instead of using vmstate_(un)register calls.
'instance_id' was being set to VMSTATE_INSTANCE_ID_ANY so there is no need
for qdev_set_legacy_instance_id() calls.
spapr_nvdimm_unrealize() was removed since it was only being used to
call vmstate_unregister().
Cc: Shivaprasad G Bhat <sbhat@linux.ibm.com>
Signed-off-by: Daniel Henrique Barboza <danielhb413@gmail.com>
---
hw/ppc/spapr_nvdimm.c | 11 ++---------
1 file changed, 2 insertions(+), 9 deletions(-)
diff --git a/hw/ppc/spapr_nvdimm.c b/hw/ppc/spapr_nvdimm.c
index c4c97da5de..973e9d0fbe 100644
--- a/hw/ppc/spapr_nvdimm.c
+++ b/hw/ppc/spapr_nvdimm.c
@@ -866,14 +866,6 @@ static void spapr_nvdimm_realize(NVDIMMDevice *dimm, Error **errp)
if (!is_pmem || pmem_override) {
s_nvdimm->hcall_flush_required = true;
}
-
- vmstate_register(NULL, VMSTATE_INSTANCE_ID_ANY,
- &vmstate_spapr_nvdimm_states, dimm);
-}
-
-static void spapr_nvdimm_unrealize(NVDIMMDevice *dimm)
-{
- vmstate_unregister(NULL, &vmstate_spapr_nvdimm_states, dimm);
}
static Property spapr_nvdimm_properties[] = {
@@ -888,8 +880,9 @@ static void spapr_nvdimm_class_init(ObjectClass *oc, void *data)
DeviceClass *dc = DEVICE_CLASS(oc);
NVDIMMClass *nvc = NVDIMM_CLASS(oc);
+ dc->vmsd = &vmstate_spapr_nvdimm_states;
+
nvc->realize = spapr_nvdimm_realize;
- nvc->unrealize = spapr_nvdimm_unrealize;
device_class_set_props(dc, spapr_nvdimm_properties);
}
--
2.35.1
next prev parent reply other threads:[~2022-03-22 18:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-22 18:38 [PATCH for-7.1 0/4] use dc->vmsd with spapr devices vmstate Daniel Henrique Barboza
2022-03-22 18:38 ` [PATCH for-7.1 1/4] hw/ppc: use qdev to register logical DRC vmstates Daniel Henrique Barboza
2022-03-22 18:38 ` [PATCH for-7.1 2/4] hw/ppc: use qdev to register physical " Daniel Henrique Barboza
2022-03-23 1:48 ` David Gibson
2022-03-23 21:44 ` Daniel Henrique Barboza
2022-03-22 18:38 ` [PATCH for-7.1 3/4] hw/ppc: use qdev to register spapr_iommu tcet vmstate Daniel Henrique Barboza
2022-03-22 18:38 ` Daniel Henrique Barboza [this message]
2022-03-23 1:49 ` [PATCH for-7.1 0/4] use dc->vmsd with spapr devices vmstate David Gibson
2022-03-23 21:47 ` Daniel Henrique Barboza
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=20220322183854.196063-5-danielhb413@gmail.com \
--to=danielhb413@gmail.com \
--cc=clg@kaod.org \
--cc=david@gibson.dropbear.id.au \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=sbhat@linux.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.