From: Wei Liu <wei.liu2@citrix.com>
To: Xen-devel <xen-devel@lists.xenproject.org>
Cc: Anthony PERARD <anthony.perard@citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
Paul Durrant <paul.durrant@citrix.com>,
Wei Liu <wei.liu2@citrix.com>
Subject: [PATCH v2 2/2] libxendevicemodel: initialise extent to zero
Date: Thu, 28 Sep 2017 11:36:25 +0100 [thread overview]
Message-ID: <20170928103625.896-3-wei.liu2@citrix.com> (raw)
In-Reply-To: <20170928103625.896-1-wei.liu2@citrix.com>
The pad field needs to be zero as required by the hypervisor.
Instead of setting the pad separately, use C99 initialiser to clear
extent.
Signed-off-by: Wei Liu <wei.liu2@citrix.com>
---
Cc: Ian Jackson <ian.jackson@eu.citrix.com>
Cc: Paul Durrant <paul.durrant@citrix.com>
Backport to 4.9
---
tools/libs/devicemodel/core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/libs/devicemodel/core.c b/tools/libs/devicemodel/core.c
index fcb260d29b..986f147658 100644
--- a/tools/libs/devicemodel/core.c
+++ b/tools/libs/devicemodel/core.c
@@ -483,7 +483,7 @@ int xendevicemodel_modified_memory(
xendevicemodel_handle *dmod, domid_t domid, uint64_t first_pfn,
uint32_t nr)
{
- struct xen_dm_op_modified_memory_extent extent;
+ struct xen_dm_op_modified_memory_extent extent = { };
extent.first_pfn = first_pfn;
extent.nr = nr;
--
2.11.0
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-09-28 10:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-28 10:36 [PATCH v2 0/2] Fix bugs in dmop code Wei Liu
2017-09-28 10:36 ` [PATCH v2 1/2] x86/hvm/dmop: fix EFAULT condition Wei Liu
2017-09-28 10:39 ` Paul Durrant
2017-09-28 10:36 ` Wei Liu [this message]
2017-09-28 10:40 ` [PATCH v2 2/2] libxendevicemodel: initialise extent to zero Paul Durrant
2017-09-28 10:46 ` Wei Liu
2017-09-28 10:48 ` Paul Durrant
2017-09-28 10:40 ` [PATCH v2 0/2] Fix bugs in dmop code Andrew Cooper
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=20170928103625.896-3-wei.liu2@citrix.com \
--to=wei.liu2@citrix.com \
--cc=anthony.perard@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=paul.durrant@citrix.com \
--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 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.