xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH] don't compile XEN_TMEM on ARM adn ARM64
Date: Mon, 24 Jun 2013 12:15:02 -0400	[thread overview]
Message-ID: <20130624161502.GA24095@phenom.dumpdata.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1306241704310.4782@kaball.uk.xensource.com>

On Mon, Jun 24, 2013 at 05:12:38PM +0100, Stefano Stabellini wrote:
> On Mon, 24 Jun 2013, Konrad Rzeszutek Wilk wrote:
> > On Mon, Jun 24, 2013 at 04:51:17PM +0100, Stefano Stabellini wrote:
> > > Hi Konrad,
> > > XEN_TMEM doesn't work on ARM64. This commit break Xen ARM64 in
> > > linux-next:
> > > 
> > > commit 10a7a0771399a57a297fca9615450dbb3f88081a
> > > Author: Dan Magenheimer <dan.magenheimer@oracle.com>
> > > Date:   Tue Apr 30 15:27:00 2013 -0700
> > > 
> > >     xen: tmem: enable Xen tmem shim to be built/loaded as a module
> > > 
> > > I suggest fixing it by disabling XEN_TMEM on everything non-x86.
> > 
> > Hm, what is the compile issue?
> 
> drivers/xen/tmem.c: In function ‘xen_tmem_op’:
> drivers/xen/tmem.c:105:2: error: implicit declaration of function ‘HYPERVISOR_tmem_op’ [-Werror=implicit-function-declaration]
> 
> Alternatively I can provide the implementation of HYPERVISOR_tmem_op.

I think that might be better. Thanks!
> 
> ---
> 
> Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
> 
> diff --git a/arch/arm/include/asm/xen/hypercall.h b/arch/arm/include/asm/xen/hypercall.h
> index 799f42e..f546b27 100644
> --- a/arch/arm/include/asm/xen/hypercall.h
> +++ b/arch/arm/include/asm/xen/hypercall.h
> @@ -47,6 +47,7 @@ unsigned long HYPERVISOR_hvm_op(int op, void *arg);
>  int HYPERVISOR_memory_op(unsigned int cmd, void *arg);
>  int HYPERVISOR_physdev_op(int cmd, void *arg);
>  int HYPERVISOR_vcpu_op(int cmd, int vcpuid, void *extra_args);
> +int HYPERVISOR_tmem_op(void *arg);
>  
>  static inline void
>  MULTI_update_va_mapping(struct multicall_entry *mcl, unsigned long va,
> diff --git a/arch/arm/xen/hypercall.S b/arch/arm/xen/hypercall.S
> index 199cb2d..d1cf7b7 100644
> --- a/arch/arm/xen/hypercall.S
> +++ b/arch/arm/xen/hypercall.S
> @@ -88,6 +88,7 @@ HYPERCALL2(hvm_op);
>  HYPERCALL2(memory_op);
>  HYPERCALL2(physdev_op);
>  HYPERCALL3(vcpu_op);
> +HYPERCALL1(tmem_op);
>  
>  ENTRY(privcmd_call)
>  	stmdb sp!, {r4}
> diff --git a/arch/arm64/xen/hypercall.S b/arch/arm64/xen/hypercall.S
> index 2816c47..531342e 100644
> --- a/arch/arm64/xen/hypercall.S
> +++ b/arch/arm64/xen/hypercall.S
> @@ -79,6 +79,7 @@ HYPERCALL2(hvm_op);
>  HYPERCALL2(memory_op);
>  HYPERCALL2(physdev_op);
>  HYPERCALL3(vcpu_op);
> +HYPERCALL1(tmem_op);
>  
>  ENTRY(privcmd_call)
>  	mov x16, x0


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

      reply	other threads:[~2013-06-24 16:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-24 15:51 [PATCH] don't compile XEN_TMEM on ARM adn ARM64 Stefano Stabellini
2013-06-24 15:58 ` Jan Beulich
2013-06-24 16:00 ` Konrad Rzeszutek Wilk
2013-06-24 16:12   ` Stefano Stabellini
2013-06-24 16:15     ` Konrad Rzeszutek Wilk [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=20130624161502.GA24095@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xensource.com \
    /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).