From: Anthony PERARD <anthony.perard@citrix.com>
To: qemu-devel@nongnu.org
Cc: Anthony Perard <anthony.perard@citrix.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Paolo Bonzini <pbonzini@redhat.com>,
xen-devel@lists.xenproject.org
Subject: [Qemu-devel] [PATCH 2/2] xen: Replace few mentions of xend by libxl
Date: Fri, 14 Sep 2018 12:18:30 +0100 [thread overview]
Message-ID: <20180914111830.28466-3-anthony.perard@citrix.com> (raw)
In-Reply-To: <20180914111830.28466-1-anthony.perard@citrix.com>
xend have been replaced by libxenlight (libxl) for many Xen releases
now.
Signed-off-by: Anthony PERARD <anthony.perard@citrix.com>
---
hw/xenpv/xen_machine_pv.c | 2 +-
include/hw/xen/xen.h | 2 +-
qemu-options.hx | 4 ++--
3 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/hw/xenpv/xen_machine_pv.c b/hw/xenpv/xen_machine_pv.c
index 4d03aa59cb..de89b0ee1d 100644
--- a/hw/xenpv/xen_machine_pv.c
+++ b/hw/xenpv/xen_machine_pv.c
@@ -42,7 +42,7 @@ static void xen_init_pv(MachineState *machine)
switch (xen_mode) {
case XEN_ATTACH:
- /* nothing to do, xend handles everything */
+ /* nothing to do, libxl handles everything */
break;
case XEN_EMULATE:
error_report("xen emulation not implemented (yet)");
diff --git a/include/hw/xen/xen.h b/include/hw/xen/xen.h
index 978aaa31fb..ba039c146d 100644
--- a/include/hw/xen/xen.h
+++ b/include/hw/xen/xen.h
@@ -15,7 +15,7 @@
/* xen-machine.c */
enum xen_mode {
XEN_EMULATE = 0, // xen emulation, using xenner (default)
- XEN_ATTACH // attach to xen domain created by xend
+ XEN_ATTACH // attach to xen domain created by libxl
};
extern uint32_t xen_domid;
diff --git a/qemu-options.hx b/qemu-options.hx
index d14a50805a..327bc8c897 100644
--- a/qemu-options.hx
+++ b/qemu-options.hx
@@ -3400,7 +3400,7 @@ DEF("xen-domid", HAS_ARG, QEMU_OPTION_xen_domid,
"-xen-domid id specify xen guest domain id\n", QEMU_ARCH_ALL)
DEF("xen-attach", 0, QEMU_OPTION_xen_attach,
"-xen-attach attach to existing xen domain\n"
- " xend will use this when starting QEMU\n",
+ " libxl will use this when starting QEMU\n",
QEMU_ARCH_ALL)
DEF("xen-domid-restrict", 0, QEMU_OPTION_xen_domid_restrict,
"-xen-domid-restrict restrict set of available xen operations\n"
@@ -3414,7 +3414,7 @@ Specify xen guest domain @var{id} (XEN only).
@item -xen-attach
@findex -xen-attach
Attach to existing xen domain.
-xend will use this when starting QEMU (XEN only).
+libxl will use this when starting QEMU (XEN only).
@findex -xen-domid-restrict
Restrict set of available xen operations to specified domain id (XEN only).
ETEXI
--
Anthony PERARD
next prev parent reply other threads:[~2018-09-14 11:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-14 11:18 [Qemu-devel] [PATCH 0/2] Remove Xen PV domain creation in QEMU Anthony PERARD
2018-09-14 11:18 ` [Qemu-devel] [PATCH 1/2] Remove broken Xen PV domain builder Anthony PERARD
2018-09-14 15:36 ` Stefano Stabellini
2018-09-14 11:18 ` Anthony PERARD [this message]
2018-09-14 15:36 ` [Qemu-devel] [PATCH 2/2] xen: Replace few mentions of xend by libxl Stefano Stabellini
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=20180914111830.28466-3-anthony.perard@citrix.com \
--to=anthony.perard@citrix.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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).