From: Julien Grall <julien.grall@citrix.com>
To: Dario Faggioli <dario.faggioli@citrix.com>
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
xen-devel@lists.xenproject.org, tim@xen.org,
ian.campbell@citrix.com, stefano.stabellini@citrix.com
Subject: Re: [PATCH] xen/sched_rt: Use the correct type for _cpumask_scratch
Date: Thu, 4 Jun 2015 10:00:47 +0100 [thread overview]
Message-ID: <557013BF.4030502@citrix.com> (raw)
In-Reply-To: <1433408243.2745.19.camel@citrix.com>
Hi Dario,
On 04/06/2015 09:57, Dario Faggioli wrote:
> On Tue, 2015-06-02 at 16:07 +0100, Julien Grall wrote:
>> The commit 376bbbabbda607d2039b8f839f15ff02721597d2 "sched_rt: print useful
>> affinity info when dumping" breaks build on ARM64:
>>
>> sched_rt.c: In function ‘rt_init’:
>> sched_rt.c:442:26: error: assignment from incompatible pointer type [-Werror]
>> _cpumask_scratch = xmalloc_array(cpumask_var_t, nr_cpu_ids);
>> ^
>> sched_rt.c: In function ‘rt_alloc_pdata’:
>> sched_rt.c:489:29: error: passing argument 1 of ‘alloc_cpumask_var’ from incompatible pointer type [-Werror]
>> if ( !alloc_cpumask_var(&_cpumask_scratch[cpu]) )
>>
>> This is because cpumask_var_t is not a type alias to cpumask_t** when
>> the number of CPU > 2 * BITS_PER_LONG. The correct type for
>> _cpumask_scratch should be cpumask_var_t.
>>
> Oh, right.
>
> Sorry for this, I didn't have an ARM build test sat up when working on
> this patch and, although now I have it, I did not run it through it when
> resending the patch (although, this is probably not only ARM related!).
It's only present on ARM64 build. ARM32 build perfectly fine.
Regards,
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
prev parent reply other threads:[~2015-06-04 9:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-02 15:07 [PATCH] xen/sched_rt: Use the correct type for _cpumask_scratch Julien Grall
2015-06-04 8:57 ` Dario Faggioli
2015-06-04 9:00 ` Julien Grall [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=557013BF.4030502@citrix.com \
--to=julien.grall@citrix.com \
--cc=dario.faggioli@citrix.com \
--cc=george.dunlap@eu.citrix.com \
--cc=ian.campbell@citrix.com \
--cc=stefano.stabellini@citrix.com \
--cc=tim@xen.org \
--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.