From: Razvan Cojocaru <rcojocaru@bitdefender.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: ian.jackson@eu.citrix.com, JBeulich@suse.com, xen-devel@lists.xen.org
Subject: Re: [PATCH] tools/libxc: Fix ARM build broken by XEN_DOMCTL_getvcpuextstate commit
Date: Wed, 15 Mar 2017 12:01:10 +0200 [thread overview]
Message-ID: <b7ad1ca0-acfc-6393-06e9-024b8d1036d2@bitdefender.com> (raw)
In-Reply-To: <20170315095942.42zlmqg3hm7oqzga@citrix.com>
On 03/15/2017 11:59 AM, Wei Liu wrote:
> On Wed, Mar 15, 2017 at 11:20:30AM +0200, Razvan Cojocaru wrote:
>> The previous "tools/libxc: Exposed XEN_DOMCTL_getvcpuextstate" broke
>> the ARM build (the hypercall does not have a corresponding DOMCTL
>> ARM struct). This patch fixes the build by returning -ENODEV for
>> ARM from xc_vcpu_get_extstate().
>>
>> Signed-off-by: Razvan Cojocaru <rcojocaru@bitdefender.com>
>
> Acked-by: Wei Liu <wei.liu2@citrix.com>
>
>> ---
>> tools/libxc/xc_domain.c | 4 +++-
>> 1 file changed, 3 insertions(+), 1 deletion(-)
>>
>> diff --git a/tools/libxc/xc_domain.c b/tools/libxc/xc_domain.c
>> index 71e5d93..c7e8065 100644
>> --- a/tools/libxc/xc_domain.c
>> +++ b/tools/libxc/xc_domain.c
>> @@ -560,7 +560,8 @@ int xc_vcpu_get_extstate(xc_interface *xch,
>> uint32_t vcpu,
>> xc_vcpu_extstate_t *extstate)
>> {
>> - int rc;
>> + int rc = -ENODEV;
>> +#if defined (__i386) || defined(__x86_64__)
>
> This should be __i386__ for consistency.
>
> Assuming you've tested ARM build, I will fix this up while committing.
Thank you. I did test it (I've cross-compiled in an ARM chroot).
Thanks,
Razvan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2017-03-15 10:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-15 9:20 [PATCH] tools/libxc: Fix ARM build broken by XEN_DOMCTL_getvcpuextstate commit Razvan Cojocaru
2017-03-15 9:59 ` Wei Liu
2017-03-15 10:01 ` Razvan Cojocaru [this message]
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=b7ad1ca0-acfc-6393-06e9-024b8d1036d2@bitdefender.com \
--to=rcojocaru@bitdefender.com \
--cc=JBeulich@suse.com \
--cc=ian.jackson@eu.citrix.com \
--cc=wei.liu2@citrix.com \
--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 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).