From: Avi Kivity <avi@redhat.com>
To: Mark McLoughlin <markmc@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH] kvm: user: include arch specific headers from $(KERNELDIR)
Date: Mon, 18 May 2009 01:18:01 +0300 [thread overview]
Message-ID: <4A108D19.2060907@redhat.com> (raw)
In-Reply-To: <1242203541-12959-1-git-send-email-markmc@redhat.com>
Mark McLoughlin wrote:
> Currently we only include $(KERNELDIR)/include in CFLAGS,
> but we also have $(KERNELDIR)/arch/$(arch)/include or else
> we'll get mis-matched headers.
>
> Signed-off-by: Mark McLoughlin <markmc@redhat.com>
> ---
> kvm/user/config-i386.mak | 1 -
> kvm/user/config-ia64.mak | 1 +
> kvm/user/config-powerpc.mak | 1 +
> kvm/user/config-x86-common.mak | 2 ++
> kvm/user/config-x86_64.mak | 1 -
> 5 files changed, 4 insertions(+), 2 deletions(-)
>
>
> diff --git a/kvm/user/config-ia64.mak b/kvm/user/config-ia64.mak
> index c4c639e..e8803a0 100644
> --- a/kvm/user/config-ia64.mak
> +++ b/kvm/user/config-ia64.mak
> @@ -2,6 +2,7 @@ bits = 64
> CFLAGS += -m64
> CFLAGS += -D__ia64__
> CFLAGS += -I $(KERNELDIR)/include
> +CFLAGS += -I $(KERNELDIR)/arch/ia64/include
> (TEST_DIR)/stringio.flat \
>
Can we have arch/$(ARCH)/include in some central place instead? I can't
bear the thought of touching this again when we merge ARM.
btw, I'd like to see the kvm/user/test stuff ported to load with qemu
-kernel instead of the custom bootstrap. We lose the simplicity of
kvmctl, but we don't really need it now (kvmctl predates qemu-kvm; it
was how we ran virtual machines until we noticed we didn't have a device
model).
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
prev parent reply other threads:[~2009-05-17 22:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-13 8:32 [PATCH] kvm: user: include arch specific headers from $(KERNELDIR) Mark McLoughlin
2009-05-13 21:57 ` Arnd Bergmann
2009-05-14 7:52 ` Mark McLoughlin
2009-05-14 8:02 ` Avi Kivity
2009-05-14 15:49 ` Arnd Bergmann
2009-05-14 15:55 ` Avi Kivity
2009-05-14 16:07 ` Arnd Bergmann
2009-05-17 22:18 ` Avi Kivity [this message]
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=4A108D19.2060907@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=markmc@redhat.com \
/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