From: Ian Campbell <ian.campbell@citrix.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>, Wei Liu <wei.liu2@citrix.com>
Cc: Doug Goldstein <cardoe@cardoe.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Jan Beulich <JBeulich@suse.com>,
Xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH] hvmloader: Use xen/errno.h rather than the host systems errno.h
Date: Fri, 19 Feb 2016 11:16:25 +0000 [thread overview]
Message-ID: <1455880585.6225.97.camel@citrix.com> (raw)
In-Reply-To: <56C6F7CE.5040306@citrix.com>
On Fri, 2016-02-19 at 11:09 +0000, Andrew Cooper wrote:
> On 19/02/16 11:00, Ian Campbell wrote:
> > On Fri, 2016-02-19 at 10:50 +0000, Andrew Cooper wrote:
> > > On 19/02/16 10:40, Wei Liu wrote:
> > > > On Thu, Feb 18, 2016 at 10:10:09PM +0000, Andrew Cooper wrote:
> > > > > Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
> > > > > ---
> > > > > CC: Jan Beulich <JBeulich@suse.com>
> > > > > CC: Ian Campbell <Ian.Campbell@citrix.com>
> > > > > CC: Ian Jackson <Ian.Jackson@eu.citrix.com>
> > > > > CC: Wei Liu <wei.liu2@citrix.com>
> > > > > CC: Doug Goldstein <cardoe@cardoe.com>
> > > > > ---
> > > > > tools/firmware/hvmloader/xenbus.c | 2 +-
> > > > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > > > >
> > > > > diff --git a/tools/firmware/hvmloader/xenbus.c
> > > > > b/tools/firmware/hvmloader/xenbus.c
> > > > > index d0ed993..947d865 100644
> > > > > --- a/tools/firmware/hvmloader/xenbus.c
> > > > > +++ b/tools/firmware/hvmloader/xenbus.c
> > > > > @@ -27,7 +27,7 @@
> > > > >
> > > > > #include "util.h"
> > > > > #include "hypercall.h"
> > > > > -#include <errno.h>
> > > > > +#include <xen/errno.h>
> > > > This doesn't seem to compile for me. Xen's error numbers live in a
> > > > different name space.
> > > It compiled fine for me. HVMLoader should use __XEN_TOOLS__.
> > It shouldn't and doesn't, see 3237645813d7 which stopped setting
> > __XEN_TOOLS__ globally for all of tools/* and consequently removed the
> > -U__XEN_TOOLS__ from hvmloader.
> >
> > In any case I don't think __XEN_TOOLS__ has any impact on xen/errno.h
> > (which is, perhaps confusingly, xen/include/public/errno.h and not
> > xen/include/xen/errno.h)
> >
> > For normal userspace uses of __XEN_TOOLS__ you wouldn't want unprefixed
> > Xen
> > errno values added to your namespace anyway -- since you need to deal
> > with
> > OS errno names/values.
>
> HVMloader is an unhosted 32bit environment, which is why it should not
> be using the hosts errno.h in the first place.
Of course I know this, and it has nothing to do with anything I explained
above.
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-02-19 11:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-18 22:10 [PATCH] hvmloader: Use xen/errno.h rather than the host systems errno.h Andrew Cooper
2016-02-19 2:21 ` Doug Goldstein
2016-02-19 2:32 ` Konrad Rzeszutek Wilk
2016-02-19 10:40 ` Wei Liu
2016-02-19 10:50 ` Andrew Cooper
2016-02-19 10:53 ` Wei Liu
2016-02-19 11:00 ` Ian Campbell
2016-02-19 11:09 ` Andrew Cooper
2016-02-19 11:16 ` Ian Campbell [this message]
2016-02-19 10:55 ` Ian Campbell
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=1455880585.6225.97.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=cardoe@cardoe.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).