File valgrind.xen-4.7-fix-domctl-value-in-comment.patch of Package valgrind

Overview Repositories Revisions Requests Users Attributes Meta

File valgrind.xen-4.7-fix-domctl-value-in-comment.patch of Package valgrind

From: Olaf Hering <olaf@aepfle.de>
Date: Sun, 25 Nov 2018 00:19:29 +0100
Subject: xen-4.7: fix domctl value in comment

Commit d73f2c748a8c8d0390641b8c893660ec4f9d6935 ("Implement additional
Xen hypercalls") claimed 0xc is the Xen 4.7 domctl, but in fact Xen 4.7
shares the same value with Xen 4.6.

bz#390553
---
 include/vki/vki-xen-domctl.h | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

--- a/include/vki/vki-xen-domctl.h
+++ b/include/vki/vki-xen-domctl.h
@@ -29,26 +29,25 @@
 /*
  * The domctl interface is versioned via the interface_version
  * field. The structures in this header supports domctl interfaces:
  *
  * - 0x00000003: Xen 3.0.3 (unhandled)
  * - 0x00000004: Xen 3.0.4 (unhandled)
  * - 0x00000005: Xen 3.1 (unhandled)
  * - 0x00000006: Xen 4.0 (unhandled)
  * - 0x00000007: Xen 4.1
  * - 0x00000008: Xen 4.2
  * - 0x00000009: Xen 4.3 & 4.4
  * - 0x0000000a: Xen 4.5
- * - 0x0000000b: Xen 4.6
- * - 0x0000000c: Xen 4.7
+ * - 0x0000000b: Xen 4.6 & 4.7
  *
  * When adding a new subop be sure to include the variants used by all
  * of the above, both here and in syswrap-xen.c
  *
  * Structs which are identical in all supported versions have no
  * version suffix. Structs which do differ are defined multiple times
  * and use the suffix of the earliest version to contain that particular
  * variant.
  */
 
 #define VKI_XEN_DOMCTL_createdomain                   1
 #define VKI_XEN_DOMCTL_destroydomain                  2

Places

File valgrind.xen-4.7-fix-domctl-value-in-comment.patch of Package valgrind

Places