From: "Chen, Tiejun" <tiejun.chen@intel.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Ian Campbell <Ian.Campbell@eu.citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
xen-devel@lists.xen.org, wei.liu2@citrix.com,
stefano.stabellini@eu.citrix.com
Subject: Re: [PATCH] tools/hvmloader: link errno.h from xen internal
Date: Mon, 03 Nov 2014 10:03:23 +0800 [thread overview]
Message-ID: <5456E26B.9040106@intel.com> (raw)
In-Reply-To: <545361450200007800043DBC@mail.emea.novell.com>
On 2014/10/31 17:15, Jan Beulich wrote:
>>>> On 31.10.14 at 03:18, <tiejun.chen@intel.com> wrote:
>
> (You omitted half of the tools maintainers; Cc-ing them now.)
I think I already pick all relevant maintainers to review this patch,
$ ./scripts/get_maintainer.pl
0004-tools-hvmloader-link-errno.h-from-xen-internal.patch
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Wei Liu <wei.liu2@citrix.com>
xen-devel@lists.xen.org
So please tell me whom should be included specifically.
>
>> We will use some error numbers in hvmloader so here just link
>> this head file from xen.
>
> This is not a proper reasoning for using the Xen internal header here.
> You should make clear that we want to act on specific hypercall
> error codes, and hence require the hypervisors view on the errno.h
> values rather than the build environment's (as was sufficient for the
> use in xenbus.c).
>
So rephrase,
tools/hvmloader: link errno.h from xen internal
We need to act on some specific hypercall error numbers, so
require the hypervisor view on the errno.h value rather than
just the build environment's number. So here link this headfile
from xen.
>> --- a/tools/firmware/hvmloader/Makefile
>> +++ b/tools/firmware/hvmloader/Makefile
>> @@ -84,9 +84,13 @@ ROMS += $(SEABIOS_ROM)
>> endif
>>
>> .PHONY: all
>> -all: subdirs-all
>> +all: subdirs-all .dir
>> $(MAKE) hvmloader
>>
>> +.dir:
>> + @rm -rf errno.h
>
> Why?
We should make sure we are linking to create a non-existing file,
otherwise you may see this,
ln: failed to create symbolic link '...': File exists
>
>> --- a/tools/firmware/hvmloader/util.h
>> +++ b/tools/firmware/hvmloader/util.h
>> @@ -6,6 +6,7 @@
>> #include <stddef.h>
>> #include <xen/xen.h>
>> #include <xen/hvm/hvm_info_table.h>
>> +#include "errno.h"
>
> Does this allow xenbus.c to still build? I think this either should go into
I did a test as follows:
1: make clean
2: make xen
3: make tools
4: make clean
5: make tools
Is this covering xenbus?
> the .c file wanting to use the values (preferable - remember my earlier
> comment about introducing unnecessary dependencies?), or the
Okay, I can remove this part, then just add this head file into any
necessary .c files. This will be addressed in other RMRR patches.
Thanks
Tiejun
> respective #include <errno.h> in xenbus.c should be dropped.
>
> Jan
>
>
next prev parent reply other threads:[~2014-11-03 2:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-31 2:18 [PATCH] tools/hvmloader: link errno.h from xen internal Tiejun Chen
2014-10-31 9:15 ` Jan Beulich
2014-11-03 2:03 ` Chen, Tiejun [this message]
2014-11-03 8:50 ` Jan Beulich
2014-10-31 10:04 ` Andrew Cooper
2014-10-31 10:51 ` Jan Beulich
2014-10-31 10:54 ` Andrew Cooper
2014-10-31 10:59 ` Jan Beulich
2014-11-03 2:06 ` Chen, Tiejun
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=5456E26B.9040106@intel.com \
--to=tiejun.chen@intel.com \
--cc=Ian.Campbell@eu.citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=stefano.stabellini@eu.citrix.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 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.