From: Anthony Liguori <aliguori@us.ibm.com>
To: Avi Kivity <avi@redhat.com>
Cc: qemu-devel@nongnu.org, Hollis Blanchard <hollisb@us.ibm.com>
Subject: Re: [Qemu-devel] [PATCH] Import KVM headers including Makefile andimport script
Date: Sun, 03 May 2009 10:06:39 -0500 [thread overview]
Message-ID: <49FDB2FF.3060001@us.ibm.com> (raw)
In-Reply-To: <49FD341C.8030205@redhat.com>
Avi Kivity wrote:
> Anthony Liguori wrote:
>> These are the headers from Linux 2.6.29 that have been modified to
>> work under
>> QEMU. This includes the necessary scripts to generate the headers
>> from the
>> original Linux source tree.
>>
>> Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
>> ---
>> configure | 7 +-
>> include/HEAD | 1 +
>> include/Makefile | 26 ++
>> include/README | 6 +
>> include/asm-powerpc/kvm.h | 55 ++++
>> include/asm-powerpc/kvm_para.h | 37 +++
>> include/asm-x86/kvm.h | 218 ++++++++++++++++
>> include/asm-x86/kvm_para.h | 147 +++++++++++
>> include/fixup.sed | 11 +
>> include/linux/kvm.h | 533
>> ++++++++++++++++++++++++++++++++++++++++
>> include/linux/kvm_para.h | 44 ++++
>>
>
> Can we put them under kvm/, as include/ looks like a generic include
> directory, which this isn't. Also, this generates a gratuitous
> conflict with qemu-kvm.git, and we have enough of those already.
I'd rather put them under linux/ because right now, we depend on a
number of Linux headers (for USB pass through, for instance).
The qemu-kvm.git layout is kvm/kernel/include. That doesn't seem to
make a lot of sense for QEMU.
> I also suggest using arch/*/include/asm as a way of avoiding the
> symlink, instead of the extra hack in fixup.sed.
>
I did it the current way to avoid deep directory layouts. We would end
up with an extra level of directories via linux/arch-x86/asm/foo.h as
opposed to linux/asm-x86/foo.h.
Did you have a reason for wanting to avoid the sed hacks verses a layout
like this other than to avoid the hack?
The fixup certainly can be made more readable. For instance:
# Expand asm/ includes to avoid having to do symlink trickery
s:^#include <asm/kvm\(.*\)>$:\
#if defined(__x86_64__) || defined(__i386__) \
#include <asm-x86/kvm\1> \
#elif defined(__powerpc__) \
#include <asm-powerpc/kvm\1> \
#endif\
:g
--
Regards,
Anthony Liguori
next prev parent reply other threads:[~2009-05-03 15:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-02 21:02 [Qemu-devel] [PATCH] Import KVM headers including Makefile and import script Anthony Liguori
2009-05-02 21:04 ` [Qemu-devel] " Anthony Liguori
2009-05-03 6:05 ` [Qemu-devel] " Avi Kivity
2009-05-03 15:06 ` Anthony Liguori [this message]
2009-05-03 15:19 ` [Qemu-devel] [PATCH] Import KVM headers including Makefile andimport script Avi Kivity
2009-05-03 21:59 ` [Qemu-devel] [PATCH] Import KVM headers including Makefile andimportscript Anthony Liguori
2009-05-04 7:59 ` Avi Kivity
2009-05-03 15:29 ` [Qemu-devel] [PATCH] Import KVM headers including Makefile and import script Avi Kivity
2009-05-03 22:02 ` [Qemu-devel] [PATCH] Import KVM headers including Makefile andimport script Anthony Liguori
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=49FDB2FF.3060001@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=avi@redhat.com \
--cc=hollisb@us.ibm.com \
--cc=qemu-devel@nongnu.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).