From: Denis Plotnikov <dplotnikov@virtuozzo.com>
To: qemu-block@nongnu.org
Cc: kwolf@redhat.com, vsementsov@virtuozzo.com, berrange@redhat.com,
ehabkost@redhat.com, qemu-devel@nongnu.org, mreitz@redhat.com,
pbonzini@redhat.com, den@virtuozzo.com
Subject: [PATCH v0 1/2] qdev-properties-system: extend set_pionter for unrealized devices
Date: Sun, 10 Nov 2019 22:03:09 +0300 [thread overview]
Message-ID: <20191110190310.19799-2-dplotnikov@virtuozzo.com> (raw)
In-Reply-To: <20191110190310.19799-1-dplotnikov@virtuozzo.com>
Some device's property can be changed if the device has been already
realized. For example, it could be "drive" property of a scsi disk device.
So far, set_pointer could operate only on a relized device. The patch
extends its interface for operation on an unrealized device.
Signed-off-by: Denis Plotnikov <dplotnikov@virtuozzo.com>
---
hw/core/qdev-properties-system.c | 32 +++++++++++++++++++++-----------
1 file changed, 21 insertions(+), 11 deletions(-)
diff --git a/hw/core/qdev-properties-system.c b/hw/core/qdev-properties-system.c
index ba412dd2ca..c534590dcd 100644
--- a/hw/core/qdev-properties-system.c
+++ b/hw/core/qdev-properties-system.c
@@ -38,9 +38,14 @@ static void get_pointer(Object *obj, Visitor *v, Property *prop,
}
static void set_pointer(Object *obj, Visitor *v, Property *prop,
- void (*parse)(DeviceState *dev, const char *str,
- void **ptr, const char *propname,
- Error **errp),
+ void (*parse_realized)(DeviceState *dev,
+ const char *str, void **ptr,
+ const char *propname,
+ Error **errp),
+ void (*parse_unrealized)(DeviceState *dev,
+ const char *str, void **ptr,
+ const char *propname,
+ Error **errp),
const char *name, Error **errp)
{
DeviceState *dev = DEVICE(obj);
@@ -48,11 +53,6 @@ static void set_pointer(Object *obj, Visitor *v, Property *prop,
void **ptr = qdev_get_prop_ptr(dev, prop);
char *str;
- if (dev->realized) {
- qdev_prop_set_after_realize(dev, name, errp);
- return;
- }
-
visit_type_str(v, name, &str, &local_err);
if (local_err) {
error_propagate(errp, local_err);
@@ -63,7 +63,17 @@ static void set_pointer(Object *obj, Visitor *v, Property *prop,
*ptr = NULL;
return;
}
- parse(dev, str, ptr, prop->name, errp);
+
+ if (dev->realized) {
+ if (parse_realized) {
+ parse_realized(dev, str, ptr, prop->name, errp);
+ } else {
+ qdev_prop_set_after_realize(dev, name, errp);
+ }
+ } else {
+ parse_unrealized(dev, str, ptr, prop->name, errp);
+ }
+
g_free(str);
}
@@ -178,13 +188,13 @@ static void get_drive(Object *obj, Visitor *v, const char *name, void *opaque,
static void set_drive(Object *obj, Visitor *v, const char *name, void *opaque,
Error **errp)
{
- set_pointer(obj, v, opaque, parse_drive, name, errp);
+ set_pointer(obj, v, opaque, NULL, parse_drive, name, errp);
}
static void set_drive_iothread(Object *obj, Visitor *v, const char *name,
void *opaque, Error **errp)
{
- set_pointer(obj, v, opaque, parse_drive_iothread, name, errp);
+ set_pointer(obj, v, opaque, NULL, parse_drive_iothread, name, errp);
}
const PropertyInfo qdev_prop_drive = {
--
2.17.0
next prev parent reply other threads:[~2019-11-10 19:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-10 19:03 [PATCH v0 0/2] allow to set 'drive' property on a realized block device Denis Plotnikov
2019-11-10 19:03 ` Denis Plotnikov [this message]
2019-11-18 18:54 ` [PATCH v0 1/2] qdev-properties-system: extend set_pionter for unrealized devices Eduardo Habkost
2019-11-22 11:36 ` Denis Plotnikov
2019-11-25 15:30 ` Eduardo Habkost
2019-11-26 6:49 ` Denis Plotnikov
2019-11-26 16:38 ` Kevin Wolf
2019-11-10 19:03 ` [PATCH v0 2/2] block: allow to set 'drive' property on a realized block device Denis Plotnikov
2019-11-10 19:08 ` Denis Plotnikov
2019-11-18 10:50 ` Denis Plotnikov
2019-12-13 7:30 ` [PING]Re: " Denis Plotnikov
2019-12-13 10:32 ` Kevin Wolf
2019-12-16 14:51 ` Denis Plotnikov
2019-12-16 15:38 ` Kevin Wolf
2019-12-16 15:58 ` Denis Plotnikov
2019-11-18 10:30 ` [PATCH v0 0/2] " Denis Plotnikov
2020-03-02 13:38 ` Kevin Wolf
2020-03-02 13:55 ` Denis Plotnikov
2020-03-02 15:39 ` Kevin Wolf
2020-03-03 7:43 ` Vladimir Sementsov-Ogievskiy
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=20191110190310.19799-2-dplotnikov@virtuozzo.com \
--to=dplotnikov@virtuozzo.com \
--cc=berrange@redhat.com \
--cc=den@virtuozzo.com \
--cc=ehabkost@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@virtuozzo.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).