All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@qumranet.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	kvm-devel <kvm-devel@lists.sourceforge.net>
Subject: Re: [RFC] Proposed new directory layout for kvm and virtualization
Date: Tue, 11 Dec 2007 19:42:28 +0200	[thread overview]
Message-ID: <475ECC04.8000609@qumranet.com> (raw)
In-Reply-To: <20071211173717.GA26368@uranus.ravnborg.org>

Sam Ravnborg wrote:
>
>>> So use arch/*/virt/kvm/ if kvm really requires
>>> a subdirectory of it own. Preferably not.
>>> A handful of files named kvm* does not warrant their own
>>> subdirectory IMO.
>>>
>>>  
>>>       
>> We'll have 5-6 x86 specific files.
>>
>> Where do you suggest we place them?
>>     
> /arch/x86/virt/
>
>   

But, I want to place the arch independent files in virt/kvm/, so as to 
leave room for virt/lguest/.

> Seems logical and fit the way we handle mm/ versus arch/*/mm,
> kernel/ arch/*/kernel etc.
>   

Exactly, so virt/kvm/ -> arch/x86/virt/kvm/.

> 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.

-- 
error compiling committee.c: too many arguments to function


WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Sam Ravnborg <sam-uyr5N9Q2VtJg9hUCZPvPmw@public.gmane.org>
Cc: kvm-devel
	<kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
	linux-kernel
	<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [RFC] Proposed new directory layout for kvm and virtualization
Date: Tue, 11 Dec 2007 19:42:28 +0200	[thread overview]
Message-ID: <475ECC04.8000609@qumranet.com> (raw)
In-Reply-To: <20071211173717.GA26368-QabhHTsIXMSnlFQ6Q1D1Y0B+6BGkLq7r@public.gmane.org>

Sam Ravnborg wrote:
>
>>> So use arch/*/virt/kvm/ if kvm really requires
>>> a subdirectory of it own. Preferably not.
>>> A handful of files named kvm* does not warrant their own
>>> subdirectory IMO.
>>>
>>>  
>>>       
>> We'll have 5-6 x86 specific files.
>>
>> Where do you suggest we place them?
>>     
> /arch/x86/virt/
>
>   

But, I want to place the arch independent files in virt/kvm/, so as to 
leave room for virt/lguest/.

> Seems logical and fit the way we handle mm/ versus arch/*/mm,
> kernel/ arch/*/kernel etc.
>   

Exactly, so virt/kvm/ -> arch/x86/virt/kvm/.

> 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.

-- 
error compiling committee.c: too many arguments to function


-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php

  reply	other threads:[~2007-12-11 17:42 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 [this message]
2007-12-11 17:42         ` Avi Kivity
2007-12-11 18:26         ` [kvm-devel] " Hollis Blanchard

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=475ECC04.8000609@qumranet.com \
    --to=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.