Re: [Xen-devel] [PATCH v5 12/28] x86/xen_hello_world.xsplice: Test payload for patching 'xen_extra_version'.

["Jan Beulich" <jbeulich@xxxxxxxx>]

>>> Konrad Rzeszutek Wilk <konrad@xxxxxxxxxx> 04/06/16 4:05 AM >>>
>On Fri, Apr 01, 2016 at 07:33:54AM -0600, Jan Beulich wrote:
>> >>> On 24.03.16 at 21:00, <konrad.wilk@xxxxxxxxxx> wrote:
>> > --- a/xen/arch/x86/Makefile
>> > +++ b/xen/arch/x86/Makefile
>> > @@ -75,7 +75,12 @@ efi-y := $(shell if [ ! -r 
>> > $(BASEDIR)/include/xen/compile.h -o \
>> >  $(TARGET): $(TARGET)-syms $(efi-y) boot/mkelf32
>> >    ./boot/mkelf32 $(TARGET)-syms $(TARGET) 0x100000 \
>> >    `$(NM) -nr $(TARGET)-syms | head -n 1 | sed -e 's/^\([^ ]*\).*/0x\1/'`
>> > +  $(MAKE) -f $(BASEDIR)/Rules.mk -C test
>> >  
>> > +install:
>> > +  $(MAKE) -f $(BASEDIR)/Rules.mk -C test install
>> > +uninstall:
>> > +  $(MAKE) -f $(BASEDIR)/Rules.mk -C test uninstall
>> 
>> Tests or examples should not be built by default.
>
>I can certainly make a seperate top destination called 'test' that will
>take care of this? Or should it be called 'xsplice' ? 'xsplice-test' ?

The top level one would (imo naturally) be "tests", as there could be more
than just the xSplice one(s).

Jan


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