All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: keir@xen.org, lccycc123@gmail.com, george.dunlap@eu.citrix.com,
	msw@linux.com, dario.faggioli@citrix.com,
	stefano.stabellini@eu.citrix.com, ian.jackson@eu.citrix.com,
	xen-devel@lists.xen.org, Elena Ufimtseva <ufimtseva@gmail.com>
Subject: Re: [PATCH v9 1/9] xen: vnuma topology and subop hypercalls
Date: Fri, 5 Sep 2014 12:45:07 +0100	[thread overview]
Message-ID: <1409917507.10156.64.camel@kazak.uk.xensource.com> (raw)
In-Reply-To: <5409BBB302000078000316C4@mail.emea.novell.com>

On Fri, 2014-09-05 at 12:33 +0100, Jan Beulich wrote:
> >>> On 05.09.14 at 13:25, <Ian.Campbell@citrix.com> wrote:
> > On Thu, 2014-08-28 at 23:04 -0400, Elena Ufimtseva wrote:
> >> Define interface, structures and hypercalls for toolstack to
> >> build vnuma topology and for guests that wish to retrieve it.
> >> Two subop hypercalls introduced by patch:
> >> XEN_DOMCTL_setvnumainfo to define vNUMA domain topology per domain
> >> and XENMEM_get_vnumainfo to retrieve that topology by guest.
> > 
> > This (or a related patch) seems to have broken the build on ARM
> > http://www.chiark.greenend.org.uk/~xensrcts/logs/30120/build-armhf/5.ts-xen- 
> > build.log
> > In file included from xenctrl.h:38:0,
> >                  from xc_private.h:32,
> >                  from xc_gnttab.c:20:
> > /local/scratch/osstest/osstest/build.30120.build-armhf/xen/tools/libxc/../..
> > /tools/include/xen/domctl.h:1101:33: error: field 'vnuma' has incomplete type
> > 
> > It looks like the definition of xen_domctl_vnuma is under a 
> >         #if defined(__i386__) || defined(__x86_64__)
> > but the uses are not.
> > 
> > It would probably be best for now to simply ifdef the uses in libxc too.
> 
> Actually the hypervisor build seems to be broken for ARM too (if you
> look a little further down in the log) - we just should move the #endif
> up, as there's nothing architecture specific here (even if ARM may
> not immediately make use of this).

Right, there doesn't seem to be anything x86 specific there.

> So Elena, going forward please at least build test your changes on
> ARM too.

Getting an ARM userspace is a bit tricky, but at least for the
hypervisor it cross builds quite easily. I use the cross toolchains from
Linaro.

Ian.

  reply	other threads:[~2014-09-05 11:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-29  3:04 [PATCH v9 0/9] vNUMA introduction Elena Ufimtseva
2014-08-29  3:04 ` [PATCH v9 1/9] xen: vnuma topology and subop hypercalls Elena Ufimtseva
2014-08-29 10:37   ` Jan Beulich
2014-09-03  0:46     ` Elena Ufimtseva
2014-09-03  8:28       ` Jan Beulich
2014-09-05  3:27         ` Elena Ufimtseva
2014-09-05  8:04           ` Jan Beulich
2014-09-05 11:25   ` Ian Campbell
2014-09-05 11:33     ` Jan Beulich
2014-09-05 11:45       ` Ian Campbell [this message]
2014-09-05 11:52         ` Jan Beulich
2014-09-08 19:58           ` Elena Ufimtseva

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=1409917507.10156.64.camel@kazak.uk.xensource.com \
    --to=ian.campbell@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=dario.faggioli@citrix.com \
    --cc=george.dunlap@eu.citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=keir@xen.org \
    --cc=lccycc123@gmail.com \
    --cc=msw@linux.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=ufimtseva@gmail.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 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.