On Fri, 2007-07-27 at 16:56 +1000, Rusty Russell wrote:
> This patch converts the vcpus array in "struct kvm" to a linked list
> of VCPUs
... and here's the version which leaves it as an array (of pointers).
Oops.
==
Dynamically allocate vcpus
This patch converts the vcpus array in "struct kvm"
Hi Rusty,
So with this patch, we no longer have limitation on the number of
vcpus running in a VM?
Thanks,
Jun
On 7/27/07, Rusty Russell <[EMAIL PROTECTED]> wrote:
> On Fri, 2007-07-27 at 16:56 +1000, Rusty Russell wrote:
> > This patch converts the vcpus array in "struct kvm" to a linked list
>
On Fri, 2007-07-27 at 16:39 +0900, Jun Koi wrote:
> Hi Rusty,
>
> So with this patch, we no longer have limitation on the number of
> vcpus running in a VM?
Well, the #define needs to be changed, but that's a trivial matter.
If we want it really big, we should look at dynamic reallocation of the
On Fri, 2007-07-27 at 16:53 +1000, Rusty Russell wrote:
> On Thu, 2007-07-26 at 14:45 -0400, Gregory Haskins wrote:
> > Signed-off-by: Gregory Haskins <[EMAIL PROTECTED]>
>
> OK, in anticipation that you would do it, I've done a trivial
> s/svm()/to-svm()/ and s/vmx()/to_vmx()/ patch and put my pa
On Fri, 2007-07-27 at 07:58 +0300, Avi Kivity wrote:
> Gregory Haskins wrote:
> > We need to provide locking around the current_vmcs/VMCS interactions to
> > protect against race conditions.
> >
> >
>
> We agreed the race was benign? Do you no longer think so?
No, I agree (see "0/3" note). I
<>-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> htt
Signed-off-by: Gregory Haskins <[EMAIL PROTECTED]>
---
drivers/kvm/vmx.c | 71 +++--
1 files changed, 58 insertions(+), 13 deletions(-)
diff --git a/drivers/kvm/vmx.c b/drivers/kvm/vmx.c
index 96837d6..86f1eea 100644
--- a/drivers/kvm/vmx.c
+++ b
On Fri, 2007-07-27 at 07:56 +0300, Avi Kivity wrote:
> Gregory Haskins wrote:
> > Hi guys,
> > While working with the -rt kernel, I have noticed a problem in KVM.
> > Specifically, when you stop a VM you sometimes get a "sleep while
> > atomic" oopses. It turns out that the issue is related to a
(Note the last "v3" I sent out was a duplicate v3...it should have been v4)
This series includes the following changes from v4(v3)
Patch #1: I have folded Rusty's cleanup in (thanks Rusty!)
Patch #2: Rebased on Rusty's changes
Patch #3: Dropped
Signed-off-by: Gregory Haskins <[EMAIL PROTECTED]>
Signed-off-by: Gregory Haskins <[EMAIL PROTECTED]>
---
drivers/kvm/kvm.h | 31
drivers/kvm/kvm_main.c | 26 +--
drivers/kvm/kvm_svm.h |3
drivers/kvm/svm.c | 394
drivers/kvm/vmx.c | 249 +++--
Put cpu feature detecting part in hardware_setup, and stored the vmcs
condition in global variable for further check.
Signed-off-by: Sheng Yang <[EMAIL PROTECTED]>
---
drivers/kvm/vmx.c | 145
1 files changed, 100 insertions(+), 45 deletions(-
Hi,
I've installed the latest version kvm-33 on my PC. All guests (tested
with several knoppix version and SuSE 10.1 install dvd image) hanging on
reboot. In the host syslog I found a lot of messages (>1000): "kernel:
kvm: unhandled wrmsr: 0xc083"
I've tested with the original kernel kvm modu
Gregory Haskins wrote:
> Signed-off-by: Gregory Haskins <[EMAIL PROTECTED]>
> ---
>
> drivers/kvm/vmx.c | 71
> +++-- 1 files
changed, 58
> insertions(+), 13 deletions(-)
>
> diff --git a/drivers/kvm/vmx.c b/drivers/kvm/vmx.c
> index 96837d6..86
On Fri, 2007-07-27 at 17:09 -0700, Nakajima, Jun wrote:
> Gregory Haskins wrote:
> > Signed-off-by: Gregory Haskins <[EMAIL PROTECTED]>
> > ---
> >
> > drivers/kvm/vmx.c | 71
> > +++-- 1 files
> changed, 58
> > insertions(+), 13 deletions(-)
> >
On Wednesday 25 July 2007, Avi Kivity wrote:
> Chris Clayton wrote:
> > Forgot to cc this to the list, sorry
> > -- Forwarded Message --
> >
> > Subject: Re: [kvm-devel] kvm-31 seg fault
> > Date: Tuesday 24 July 2007
> > From: Chris Clayton <[EMAIL PROTECTED]>
> > To: Avi Kivity
15 matches
Mail list logo
