[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <561F7FF8.9030703@citrix.com>
Date: Thu, 15 Oct 2015 11:29:12 +0100
From: David Vrabel <david.vrabel@...rix.com>
To: Mikko Rapeli <mikko.rapeli@....fi>, <linux-kernel@...r.kernel.org>
CC: Stefano Stabellini <stefano.stabellini@...citrix.com>,
Russell King <linux@....linux.org.uk>,
Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>,
Boris Ostrovsky <boris.ostrovsky@...cle.com>,
<xen-devel@...ts.xenproject.org>,
<linux-arm-kernel@...ts.infradead.org>, <linux-api@...r.kernel.org>
Subject: Re: [PATCH v4 75/79] include/uapi/xen/privcmd.h: fix compilation
in userspace
On 15/10/15 06:56, Mikko Rapeli wrote:
> xen/interface/xen.h is not exported from kernel headers so remove the
> dependency and provide needed defines for domid_t and xen_pfn_t if they
> are not already defined by some other e.g. Xen specific headers.
>
> Suggested by Andrew Cooper <andrew.cooper3@...rix.com> on lkml message
> <5569F9C9.8000607@...rix.com>.
>
> The ifdef for ARM is ugly but did not find better solutions for it.
>
> Fixes userspace compilation error:
>
> xen/privcmd.h:38:31: fatal error: xen/interface/xen.h: No such file or directory
[...]
> --- a/include/uapi/xen/privcmd.h
> +++ b/include/uapi/xen/privcmd.h
> @@ -35,7 +35,19 @@
>
> #include <linux/types.h>
> #include <linux/compiler.h>
> -#include <xen/interface/xen.h>
> +
> +/* Might be defined by Xen specific headers, but if not */
> +#ifndef domid_t
> +typedef __u16 domid_t;
> +#endif /* domid_t */
As the kbuild bot points out, this does not work since the existence of
a typedef cannot be checked with #ifdef.
I'm not really sure what problem you're trying to solve. A user space
program making use of this interface gets the domid_t and xen_pfn_t etc
typedefs from the headers provided as part of the libxenctrl library.
David
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists