Avi Kivity wrote:
> In the case of x86, we'll have 16 arch dependent files (i8259.[ch],
> irq.[ch], lapic.c, mmu.c, paging_tmpl.[ch], svm.[ch], vmx.[ch],
> x86.[ch], x86_emulate.[ch]) which warrant a kvm/ subdirectory IMO.
I think a subdirectory makes sense too. We'll end up with more than a
sin
Arnd Bergmann wrote:
> On Tuesday 11 December 2007, Avi Kivity wrote:
>
>> Heiko Carstens wrote:
>>
>>> On Tue, Dec 11, 2007 at 11:47:39AM +0200, Avi Kivity wrote:
>>>
>>>
arch/*/kvm/ arch dependent kvm code
>>> Maybe arch/*/virt/ ? No need to add an o
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
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 th
On Tue, Dec 11, 2007 at 06:15:40PM +0200, Avi Kivity wrote:
> Sam Ravnborg wrote:
> >On Tue, Dec 11, 2007 at 11:47:39AM +0200, Avi Kivity wrote:
> >
> >>KVM is due to receive support for multiple architectures (ppc, ia64, and
> >>s390, in addition to the existing x86), hopefully in time for the
Sam Ravnborg wrote:
> On Tue, Dec 11, 2007 at 11:47:39AM +0200, Avi Kivity wrote:
>
>> KVM is due to receive support for multiple architectures (ppc, ia64, and
>> s390, in addition to the existing x86), hopefully in time for the 2.6.25
>> merge window. It is awkward to place the new arch supp
On Tue, Dec 11, 2007 at 11:47:39AM +0200, Avi Kivity wrote:
> KVM is due to receive support for multiple architectures (ppc, ia64, and
> s390, in addition to the existing x86), hopefully in time for the 2.6.25
> merge window. It is awkward to place the new arch support in
> drivers/kvm/, so I'd
Heiko Carstens wrote:
> On Tue, Dec 11, 2007 at 11:47:39AM +0200, Avi Kivity wrote:
>
>> KVM is due to receive support for multiple architectures (ppc, ia64, and
>> s390, in addition to the existing x86), hopefully in time for the 2.6.25
>> merge window. It is awkward to place the new arch su
On Tue, Dec 11, 2007 at 11:47:39AM +0200, Avi Kivity wrote:
> KVM is due to receive support for multiple architectures (ppc, ia64, and
> s390, in addition to the existing x86), hopefully in time for the 2.6.25
> merge window. It is awkward to place the new arch support in drivers/kvm/,
> so I'd
Christian Borntraeger wrote:
> Am Dienstag, 11. Dezember 2007 schrieb Avi Kivity:
>
>> KVM is due to receive support for multiple architectures (ppc, ia64, and
>> s390, in addition to the existing x86), hopefully in time for the 2.6.25
>> merge window. It is awkward to place the new arch supp
Am Dienstag, 11. Dezember 2007 schrieb Avi Kivity:
> KVM is due to receive support for multiple architectures (ppc, ia64, and
> s390, in addition to the existing x86), hopefully in time for the 2.6.25
> merge window. It is awkward to place the new arch support in
> drivers/kvm/, so I'd like to
KVM is due to receive support for multiple architectures (ppc, ia64, and
s390, in addition to the existing x86), hopefully in time for the 2.6.25
merge window. It is awkward to place the new arch support in
drivers/kvm/, so I'd like to propose the following new layout:
virt/ top-leve
12 matches
Mail list logo
