Avi Kivity wrote:
Zhang, Xiantao wrote:
Avi Kivity wrote:
Zhang, Xiantao wrote:
Zhang, Xiantao wrote:
Hi Avi,
So you mean IA64 can adopt the similar method as well?
What method do you mean exactly?
Put all arch-specific files into arch/ia64/kvm as you described in
On Mon, 2007-10-08 at 10:36 +0800, Zhang, Xiantao wrote:
Avi Kivity wrote:
Zhang, Xiantao wrote:
Avi Kivity wrote:
Zhang, Xiantao wrote:
Zhang, Xiantao wrote:
Hi Avi,
So you mean IA64 can adopt the similar method as well?
What method do you mean exactly?
On Tue, 2007-10-02 at 14:11 +1000, Rusty Russell wrote:
On Tue, 2007-10-02 at 01:19 +, Hollis Blanchard wrote:
On Sun, 30 Sep 2007 15:56:16 +0200, Avi Kivity wrote:
Eventually I'd like to see the code in arch/*/kvm. That's probably not
easily doable right now because modules
On Tue, 2007-10-02 at 01:01 -0500, Hollis Blanchard wrote:
On Tue, 2007-10-02 at 14:11 +1000, Rusty Russell wrote:
On Tue, 2007-10-02 at 01:19 +, Hollis Blanchard wrote:
On Sun, 30 Sep 2007 15:56:16 +0200, Avi Kivity wrote:
Eventually I'd like to see the code in arch/*/kvm.
Rusty Russell wrote:
Whatever way we go, grouping both host and guest support in the same dir
seems confusing (which is why lguest is moving to arch/i386/lguest/ for
guest and drivers/lguest/i386/ for host).
That really is funny. Our s39host is just the other way round:
arch/s390/sie for the
On Sun, 30 Sep 2007 15:56:16 +0200, Avi Kivity wrote:
Eventually I'd like to see the code in arch/*/kvm. That's probably not
easily doable right now because modules cannot span directories, but
once that's solved, we'll do that as this is most consistent with the
rest of the kernel.
On Tue, 2007-10-02 at 01:19 +, Hollis Blanchard wrote:
On Sun, 30 Sep 2007 15:56:16 +0200, Avi Kivity wrote:
Eventually I'd like to see the code in arch/*/kvm. That's probably not
easily doable right now because modules cannot span directories, but
once that's solved, we'll do
Zhang, Xiantao wrote:
Zhang, Xiantao wrote:
Hi Avi,
So you mean IA64 can adopt the similar method as well?
What method do you mean exactly?
Put all arch-specific files into arch/ia64/kvm as you described in
future KVM infrastructure.
The powerpc people had
Avi Kivity wrote:
Zhang, Xiantao wrote:
Zhang, Xiantao wrote:
Hi Avi,
So you mean IA64 can adopt the similar method as well?
What method do you mean exactly?
Put all arch-specific files into arch/ia64/kvm as you described in
future KVM infrastructure.
The powerpc people had
Zhang, Xiantao wrote:
Avi Kivity wrote:
Zhang, Xiantao wrote:
Zhang, Xiantao wrote:
Hi Avi,
So you mean IA64 can adopt the similar method as well?
What method do you mean exactly?
Put all arch-specific files into arch/ia64/kvm as you
Avi Kivity wrote:
Zhang, Xiantao wrote:
Avi Kivity wrote:
Zhang, Xiantao wrote:
Zhang, Xiantao wrote:
Hi Avi,
So you mean IA64 can adopt the similar method as well?
What method do you mean exactly?
Put all arch-specific files into arch/ia64/kvm as you described in
On Thu, 2007-09-27 at 11:18 +0200, Avi Kivity wrote:
The whole drivers/kvm/ thing was just a trick to get merged quickly. I
think the new layout should be something like
virt/kvm/, include/linux/kvm*.h - common code
virt/lguest/ - the other hypervisor
virt/virtio/ - shared I/O
Hi Rusty.
On Sat, Sep 29, 2007 at 11:06:51PM +1000, Rusty Russell wrote:
On Thu, 2007-09-27 at 11:18 +0200, Avi Kivity wrote:
The whole drivers/kvm/ thing was just a trick to get merged quickly. I
think the new layout should be something like
virt/kvm/, include/linux/kvm*.h - common
Carsten Otte wrote:
Zhang, Xiantao wrote:
We are working on enabling KVM support on IA64 platform, and now
Linux, Windows guests get stable run and achieve reasonable
performance on KVM with Open GFW. But you know, the current KVM only
considers x86 platform, and is short of
Hi Avi,
So you mean IA64 can adopt the similar method as well? But even so, I
am still thinking we have to come out a solution for checking IA64 code into
existing KVM upstream tree , because KVM infrastructure in mainline Linux may
been a long way to go. Moreover, we also have no
Zhang, Xiantao wrote:
Hi Avi,
Sound good! But what can we do before the merge? You know, we have to
spend much effort maintaining our patches with sync with upstream tree. Do
you have an interim solution or proposal for merging IA64 code? Thanks.
Xiantao
The merge is due in a
Zhang, Xiantao wrote:
We are working on enabling KVM support on IA64 platform, and now
Linux, Windows guests get stable run and achieve reasonable performance
on KVM with Open GFW. But you know, the current KVM only considers x86
platform, and is short of cross-architecture framework.
Zhang, Xiantao wrote:
Hi Avi,
So you mean IA64 can adopt the similar method as well?
What method do you mean exactly?
But even so, I am still thinking we have to come out a solution for checking
IA64 code into existing KVM upstream tree , because KVM infrastructure in
mainline
Hi Avi,
Sound good! But what can we do before the merge? You know, we have to
spend much effort maintaining our patches with sync with upstream tree. Do you
have an interim solution or proposal for merging IA64 code? Thanks.
Xiantao
-Original Message-
From: Avi Kivity
Hi,
is this the same layout introduced for the powerpc port ?
Perhaps you should work together ?
Laurent
Zhang, Xiantao wrote:
Hi Folks,
We are working on enabling KVM support on IA64 platform, and now
Linux, Windows guests get stable run and achieve reasonable performance
on KVM with
20 matches
Mail list logo
