From: Hollis Blanchard <hollisb-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
To: jyoung5-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org
Cc: kvm-devel
<kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
kvm-ppc-devel
<kvm-ppc-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: [kvm-ppc-devel] [PATCH 2/2] Move all x86 tests to user/tests/x86
Date: Tue, 23 Oct 2007 10:35:35 -0500 [thread overview]
Message-ID: <1193153735.22407.18.camel@basalt> (raw)
In-Reply-To: <1193119069.5887.17.camel@thinkpad>
On Tue, 2007-10-23 at 00:57 -0500, Jerone Young wrote:
> This patch moves all tests currently in kvm tree to a arch specific
> directory. So files user/test/* are now in user/test/x86. These tests
> only relate to x86. Currently this is the case. Later as these share
> then there should be a "common" directory (tests for apic may be here).
...
> diff --git a/user/config-x86-common.mak b/user/config-x86-common.mak
> --- a/user/config-x86-common.mak
> +++ b/user/config-x86-common.mak
> @@ -11,6 +11,33 @@ libkvm.a: kvmctl.o
>
> balloon_ctl: balloon_ctl.o
>
> -flatfiles-common = test/bootstrap test/vmexit.flat test/smp.flat
> +flatfiles-common = $(TEST_DIR)/bootstrap \
> + $(TEST_DIR)/vmexit.flat \
> + $(TEST_DIR)/smp.flat
>
> flatfiles: $(flatfiles-common) $(flatfiles)
> +
> +$(TEST_DIR)/%.o: CFLAGS += -std=gnu99 -ffreestanding
You should be able to do something clever with $(patsubst ...) to avoid
typing TEST_DIR everywhere.
...
> +
> +arch_clean:
> + $(RM) $(TEST_DIR)/bootstrap $(TEST_DIR)/*.o $(TEST_DIR)/*.flat \
> + $(TEST_DIR)/.*.d
I think you need a FORCE or .PHONY or whatever. (Otherwise, creating a
file named "arch_clean" will keep this from working.)
--
Hollis Blanchard
IBM Linux Technology Center
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
next prev parent reply other threads:[~2007-10-23 15:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-23 5:57 [PATCH 2/2] Move all x86 tests to user/tests/x86 Jerone Young
2007-10-23 15:35 ` Hollis Blanchard [this message]
2007-10-23 15:48 ` [kvm-ppc-devel] " Jerone Young
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=1193153735.22407.18.camel@basalt \
--to=hollisb-r/jw6+rmf7hqt0dzr+alfa@public.gmane.org \
--cc=jyoung5-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=kvm-ppc-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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