From: Hollis Blanchard <hollisb@us.ibm.com>
To: Avi Kivity <avi@qumranet.com>
Cc: Sam Ravnborg <sam@ravnborg.org>,
kvm-devel <kvm-devel@lists.sourceforge.net>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [kvm-devel] [RFC] Proposed new directory layout for kvm and virtualization
Date: Tue, 11 Dec 2007 12:26:32 -0600 [thread overview]
Message-ID: <1197397592.9632.26.camel@basalt> (raw)
In-Reply-To: <475ECC04.8000609@qumranet.com>
On Tue, 2007-12-11 at 19:42 +0200, Avi Kivity wrote:
>
> > Are there any dependencies between the arch and non-arch files
> > such as they are combined in a single module?
>
> Yes, they are combined into a single module.
>
> In the case of x86, some of arch/x86/... will be combined with
> virt/kvm/ to form kvm.ko, while others will generate kvm-intel.ko and
> kvm-amd.ko.
Also, asm-offsets is a major sticking point. Either we create a
dependency on arch/*/kernel/asm-offsets.c, or we find a way to create a
new arch/*/virt/asm-offsets.c file.
--
Hollis Blanchard
IBM Linux Technology Center
prev parent reply other threads:[~2007-12-11 18:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-11 9:47 [RFC] Proposed new directory layout for kvm and virtualization Avi Kivity
2007-12-11 9:47 ` Avi Kivity
2007-12-11 13:38 ` Christian Borntraeger
2007-12-11 13:38 ` Christian Borntraeger
2007-12-11 13:46 ` Avi Kivity
2007-12-11 13:46 ` Avi Kivity
2007-12-11 15:11 ` Heiko Carstens
2007-12-11 15:52 ` [kvm-devel] " Avi Kivity
2007-12-11 15:52 ` Avi Kivity
2007-12-11 23:14 ` [kvm-devel] " Arnd Bergmann
2007-12-11 23:14 ` Arnd Bergmann
2007-12-13 8:33 ` [kvm-devel] " Avi Kivity
2007-12-13 8:33 ` Avi Kivity
2007-12-13 10:16 ` [kvm-devel] " Carsten Otte
2007-12-11 16:10 ` Sam Ravnborg
2007-12-11 16:15 ` Avi Kivity
2007-12-11 17:37 ` Sam Ravnborg
2007-12-11 17:37 ` Sam Ravnborg
2007-12-11 17:42 ` Avi Kivity
2007-12-11 17:42 ` Avi Kivity
2007-12-11 18:26 ` Hollis Blanchard [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=1197397592.9632.26.camel@basalt \
--to=hollisb@us.ibm.com \
--cc=avi@qumranet.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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.