From: David Vrabel <david.vrabel@citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>,
David Vrabel <david.vrabel@citrix.com>
Cc: xen-devel@lists.xenproject.org,
Ian Jackson <ian.jackson@eu.citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [PATCH 3/8] libxc: allow xc_get/set_hvm_param() to get/set 64-bit values
Date: Thu, 12 Jun 2014 12:05:47 +0100 [thread overview]
Message-ID: <5399898B.1020407@citrix.com> (raw)
In-Reply-To: <1402567271.9177.27.camel@kazak.uk.xensource.com>
On 12/06/14 11:01, Ian Campbell wrote:
>
> On Tue, 2014-06-10 at 19:07 +0100, David Vrabel wrote:
>> HVMOP_get_param and HVMOP_set_param take a uint32_t for the parameter
>> index and a uint64_t for the value. So, make the corresponding libxc
>> function take the same types.
>>
>> Signed-off-by: David Vrabel <david.vrabel@citrix.com>
>
> Removes a pleasing number of casts!
>
> I was about to ack and apply but for a stubdom build:
> xc_domain_save.c: In function ‘xc_domain_save’:
> xc_domain_save.c:1736:26: error: passing argument 4 of ‘xc_get_hvm_param’ from incompatible pointer type [-Werror]
> In file included from xc_private.h:32:0,
> from xc_domain_save.c:30:
> xenctrl.h:1812:5: note: expected ‘uint64_t *’ but argument is of type ‘long unsigned int *’
> xc_domain_save.c:1748:26: error: passing argument 4 of ‘xc_get_hvm_param’ from incompatible pointer type [-Werror]
> In file included from xc_private.h:32:0,
> from xc_domain_save.c:30:
> xenctrl.h:1812:5: note: expected ‘uint64_t *’ but argument is of type ‘long unsigned int *’
> cc1: all warnings being treated as errors
> make[3]: *** [xc_domain_save.o] Error 1
> make[3]: *** Waiting for unfinished jobs....
> make[3]: *** wait: No child processes. Stop.
> make[2]: *** [build] Error 2
I think you have a stale xc_domain_save.c (and presumably other files as
well) in your stubdom build. The stubdom build works for me.
David
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2014-06-12 11:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-10 18:07 [PATCHv4 0/8] tools: rework VM Generation ID David Vrabel
2014-06-10 18:07 ` [PATCH 1/8] docs: update docs for the ~/platform/generation-id key David Vrabel
2014-06-10 18:07 ` [PATCH 2/8] hvm: add HVM_PARAM_VM_GENERATION_ID_ADDR David Vrabel
2014-06-12 9:19 ` Ian Campbell
2014-06-10 18:07 ` [PATCH 3/8] libxc: allow xc_get/set_hvm_param() to get/set 64-bit values David Vrabel
2014-06-12 10:01 ` Ian Campbell
2014-06-12 11:05 ` David Vrabel [this message]
2014-06-12 11:21 ` Ian Campbell
2014-06-12 11:31 ` David Vrabel
2014-06-10 18:07 ` [PATCH 4/8] libxl: const-ify libxl_uuid_*() API David Vrabel
2014-06-12 10:31 ` Ian Campbell
2014-06-10 18:07 ` [PATCH 5/8] hvmloader: add helper functions to get/set HVM params David Vrabel
2014-06-10 18:07 ` [PATCH 6/8] libxc, libxl, hvmloader: strip out outdated VM generation ID implementation David Vrabel
2014-06-10 18:07 ` [PATCH 7/8] libxl: allow a generation ID to be specified at domain creation David Vrabel
2014-06-10 18:07 ` [PATCH 8/8] xl: generate a new random VM generation ID if requested David Vrabel
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=5399898B.1020407@citrix.com \
--to=david.vrabel@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=stefano.stabellini@eu.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.