From: Olaf Hering <olaf@aepfle.de>
To: xen-devel@lists.xen.org
Subject: libxl_device handling for nic and vtmp
Date: Thu, 18 Feb 2016 16:13:21 +0100 [thread overview]
Message-ID: <20160218151321.GA10541@aepfle.de> (raw)
What is the point of libxl__update_config_nic and
libxl__update_config_vtmp?
In libxl__device_type_add (called from DEFINE_DEVICE_ADD) the input
type is copied with libxl_device_type_copy to type_saved, which is a
1:1 copy. If needed, a new devid is assigned to the input. Later the
copy is updated with one of the two helper functions mentioned above.
But the helpers do not only update devid, also mac or uuid.
To me it looks like the double assignment can be removed. The new
pvusb code does not do it this way, it makes a copy of the fully
initialized type.
Perhaps the two helpers are useful in the context of domcreate_complete,
I have not reviewed that part of the code.
Olaf
next reply other threads:[~2016-02-18 15:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-18 15:13 Olaf Hering [this message]
2016-02-18 15:52 ` libxl_device handling for nic and vtmp Wei Liu
2016-02-18 16:54 ` Olaf Hering
2016-02-18 17:02 ` Wei Liu
2016-02-18 17:19 ` Olaf Hering
2016-02-18 17:25 ` Wei Liu
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=20160218151321.GA10541@aepfle.de \
--to=olaf@aepfle.de \
--cc=xen-devel@lists.xen.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 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.