On Thu, Jul 16, 2009 at 03:09:30PM -0300, Marcelo Tosatti wrote:
On Thu, Jul 16, 2009 at 10:51:16AM +0300, Gleb Natapov wrote:
On Wed, Jul 15, 2009 at 06:38:48PM -0300, Marcelo Tosatti wrote:
On Wed, Jul 15, 2009 at 11:48:17PM +0300, Gleb Natapov wrote:
+
Amit Shah 提到:
Is the host a 64-bit host and are you running a 64 bit kernel on the
host?
Yes, the host is Debian/64-bit/kernel-2.6.30.
John Wong 提到:
My host system is(uname -a): Linux Debian 2.6.30-1-amd64 #1 SMP Wed
Jul 8 12:20:34 UTC 2009 x86_64 GNU/Linux
My cpu is Intel core2duo
It replaces the previous fix of using select.
From ab5ae4bb69f8ab6c9a476f7823cb8d6729d31594 Mon Sep 17 00:00:00 2001
From: Dor Laor d...@redhat.com
Date: Wed, 15 Jul 2009 17:53:16 +0300
Subject: [PATCH] Set the iothread's eventfd/pipe descriptors to non-blocking.
It fixes migration issue when
Fischer, Anna wrote:
Hi, I am trying to compile the kvm-87 module for Linux 2.6.16. I thought that
it has been back-ported to such an old kernel. However, I don't seem to be able
to compile the module on my kernel. I get the following error:
CCtsc2005.o
CCscsi-disk.o
CC
So I propose this as a universal quoting scheme:
\char where char is not ASCII alphanumeric.
No thank you. This sounds dangerously like the windows command shell quoting
rules. At first clance they appear to just work, however when you actually
try to figure out what's going on it gets
Arnd Bergmann wrote:
On Thursday 16 July 2009, Gregory Haskins wrote:
Arnd Bergmann wrote:
Your approach allows passing the vmid from a process that does
not own the kvm context. This looks like an intentional feature,
but I can't see what this gains us.
This work is
On Friday 17 July 2009 03:14:54 Marcelo Tosatti wrote:
On Thu, Jul 16, 2009 at 11:48:46AM -0700, Jordan Justen wrote:
On Thu, 2009-07-16 at 11:18 -0700, Marcelo Tosatti wrote:
On Thu, Jul 16, 2009 at 11:02:22AM -0700, Jordan Justen wrote:
Although VMX_EPT_IDENTITY_PAGETABLE_ADDR does not
Hi,
I am trying to compile kvm-88, like followings:
./configure --disable-xen
make
Then I get following errors. Why do I have such a problem, if I
already disalbe Xen support, like above? How to fix this problem?
Thanks lot,
J
CC x86_64-softmmu/disas.o
CC
On Friday 17 July 2009 11:34:03 Jun Koi wrote:
Hi,
I am trying to compile kvm-88, like followings:
./configure --disable-xen
make
Then I get following errors. Why do I have such a problem, if I
already disalbe Xen support, like above? How to fix this problem?
Comment out all XEN related
Hi,
I have a KVM box which has 4GB physical memory totally, I'd like to
know how much I can use to run my domains, and how much will be
reserved by hypervisor(KVM) itself?
Thanks!
Regards,
Qian
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to
On Fri, Jul 17, 2009 at 2:45 PM, Sheng Yangsh...@linux.intel.com wrote:
On Friday 17 July 2009 11:34:03 Jun Koi wrote:
Hi,
I am trying to compile kvm-88, like followings:
./configure --disable-xen
make
Then I get following errors. Why do I have such a problem, if I
already disalbe Xen
This adds the book3s specific header file that contains structs that
are only valid on book3s specific code.
Signed-off-by: Alexander Graf ag...@suse.de
---
arch/powerpc/include/asm/kvm_book3s.h | 131 +
1 files changed, 131 insertions(+), 0 deletions(-)
create
We need to intercept interrupt vectors. To do that, let's add a file
we can always include which only activates the intercepts when we have
then configured.
Signed-off-by: Alexander Graf ag...@suse.de
---
arch/powerpc/include/asm/kvm_book3s_64_asm.h | 58 ++
1 files
This is the really low level of guest entry/exit code.
Usually the Linux kernel resides in virtual memory 0xc000 to
0x. These addresses are mapped into every userspace
application.
When going into a 32 bit guest, this is perfectly fine. That one can't
access memory
Getting from host state to the guest is only half the story. We also need
to return to our host context and handle whatever happened to get us out of
the guest.
On PowerPC every guest exit is an interrupt. So all we need to do is trap
the host's interrupt handlers and get into our #VMEXIT code to
We designed the Book3S port of KVM as modular as possible. Most
of the code could be easily used on a Book3S_32 host as well.
The main difference between 32 and 64 bit cores is the MMU. To keep
things well separated, we treat the book3s_64 MMU as one possible compile
option.
This patch adds all
To be able to run a guest, we also need to implement a guest MMU.
This patch adds MMU handling for Book3s_64 guests.
Signed-off-by: Alexander Graf ag...@suse.de
---
arch/powerpc/kvm/book3s_64_mmu.c | 466 ++
1 files changed, 466 insertions(+), 0 deletions(-)
This patch adds an implementation for a G3/G4 MMU, so we can run G3 and
G4 guests in KVM on Book3s_64.
Signed-off-by: Alexander Graf ag...@suse.de
---
arch/powerpc/kvm/book3s_32_mmu.c | 357 ++
1 files changed, 357 insertions(+), 0 deletions(-)
create mode
There are generic parts of PowerPC that can be shared across all
implementations and specific parts that only apply to BookE or desktop PPCs.
This patch adds emulation for desktop specific opcodes that don't apply
to BookE CPUs.
Signed-off-by: Alexander Graf ag...@suse.de
---
We support setting the DEC to a certain value right now. Doing that basically
triggers the CPU local timer.
But there's also an mfdec command that enabled the OS to read the decrementor.
This is required at least by all desktop and server PowerPC Linux kernels. It
can't really hurt to allow
Little opcodes behave differently on desktop and embedded PowerPC cores.
In order to reflect those differences, let's add some #ifdef code to emulate.c.
We could probably also handle them in the core specific emulation files, but I
would prefer to reuse as much code as possible.
Signed-off-by:
We need to loop through the SLB several times when switching from guest to host
or vice versa.
We only really know the SLB size of the system we're running on on bootup.
Linux patches its own assembly code on bootup to know how big its SLB is.
Let's just take that code and patch our own assembly
We need to access some VCPU fields from assembly code. In order to get
the proper offsets, we have to define them in asm-offsets.c.
Signed-off-by: Alexander Graf ag...@suse.de
---
arch/powerpc/kernel/asm-offsets.c | 13 +
1 files changed, 13 insertions(+), 0 deletions(-)
diff
We want to be able to build KVM as a module. To enable us doing so, we
need some more exports from core Linux parts.
This patch exports all functions and variables that are required for KVM.
Signed-off-by: Alexander Graf ag...@suse.de
---
arch/powerpc/kernel/ppc_ksyms.c |3 ++-
It looks like the variable pc is defined. At least the current code always
failed on me stating that pc is already defined somewhere else.
Let's use _pc instead, because that doesn't collide.
Is this the right approach? Does it break on 440 too? If not, why not?
Signed-off-by: Alexander Graf
I haven't implemented dirty logging yet, but without things are just way too
slow. So for the time being I hacked in a dummy function that always tells
userspace we're dirty in VGA regions.
Please don't apply this. This patch is for reference only.
Signed-off-by: Alexander Graf ag...@suse.de
---
Now we have everything in place to be able to build KVM, so let's add it
as config option and in the Makefile.
Signed-off-by: Alexander Graf ag...@suse.de
---
arch/powerpc/kvm/Kconfig | 17 +
arch/powerpc/kvm/Makefile | 27 +++
2 files changed, 40
101 - 127 of 127 matches
Mail list logo
