From: Lei Li <lilei@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Cc: aliguori@us.ibm.com, Lei Li <lilei@linux.vnet.ibm.com>,
armbru@redhat.com, kraxel@redhat.com, pbonzini@redhat.com
Subject: [Qemu-devel] [PATCH 2/2] chardev: Get filename for new qapi backend
Date: Tue, 21 May 2013 18:27:59 +0800 [thread overview]
Message-ID: <1369132079-11377-3-git-send-email-lilei@linux.vnet.ibm.com> (raw)
In-Reply-To: <1369132079-11377-1-git-send-email-lilei@linux.vnet.ibm.com>
This patch sets the filename when the new qapi backend
init from opts.
The previous patch and discussions as link below:
http://patchwork.ozlabs.org/patch/243896/
If anyone who have better idea to fix this please let
me know your suggestions.
Signed-off-by: Lei Li <lilei@linux.vnet.ibm.com>
---
qemu-char.c | 2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/qemu-char.c b/qemu-char.c
index ebeed04..781e969 100644
--- a/qemu-char.c
+++ b/qemu-char.c
@@ -3276,6 +3276,7 @@ CharDriverState *qemu_chr_new_from_opts(QemuOpts *opts,
ChardevReturn *ret = NULL;
const char *id = qemu_opts_id(opts);
const char *bid = NULL;
+ char *filename = g_strdup(qemu_opt_get(opts, "backend"));
if (qemu_opt_get_bool(opts, "mux", 0)) {
bid = g_strdup_printf("%s-base", id);
@@ -3308,6 +3309,7 @@ CharDriverState *qemu_chr_new_from_opts(QemuOpts *opts,
}
chr = qemu_chr_find(id);
+ chr->filename = filename;
qapi_out:
qapi_free_ChardevBackend(backend);
--
1.7.7.6
next prev parent reply other threads:[~2013-05-21 10:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-21 10:27 [Qemu-devel] [PATCH 0/2 v2] Chardev related fixes Lei Li
2013-05-21 10:27 ` [Qemu-devel] [PATCH 1/2] chardev: Make the name of memory device consistent Lei Li
[not found] ` <519B4DB4.6080900@redhat.com>
2013-05-21 12:19 ` Lei Li
2013-05-21 12:38 ` Eric Blake
2013-05-21 12:50 ` Paolo Bonzini
2013-05-21 12:57 ` Eric Blake
2013-05-21 10:27 ` Lei Li [this message]
2013-05-22 22:58 ` [Qemu-devel] [PATCH 0/2 v2] Chardev related fixes Anthony Liguori
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=1369132079-11377-3-git-send-email-lilei@linux.vnet.ibm.com \
--to=lilei@linux.vnet.ibm.com \
--cc=aliguori@us.ibm.com \
--cc=armbru@redhat.com \
--cc=kraxel@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).