This works better. Not sure why but when I had fake-exec in target-ppc,
the build system was complaining that it could not find fake-exec.d. So
then I just decided to move it to fake-exec-ppc.c.
This patch works fine for powerpc.
On Wed, 2008-02-13 at 12:55 -0600, Anthony Liguori wrote:
> Jerone
Hi Kanoj,
On Wed, Feb 13, 2008 at 03:43:17PM -0800, Kanoj Sarcar wrote:
> Oh ok, yes, I did see the discussion on this; sorry I
> missed it. I do see what notifiers bring to the table
> now (without endorsing it :-)).
I'm not really livelocks are really the big issue here.
I'm running N 1G VM on
On Wednesday, February 13, 2008 3:43 pm Kanoj Sarcar wrote:
> Oh ok, yes, I did see the discussion on this; sorry I
> missed it. I do see what notifiers bring to the table
> now (without endorsing it :-)).
>
> An orthogonal question is this: is IB/rdma the only
> "culprit" that elevates page refcou
On Wed, Feb 13, 2008 at 06:23:08PM -0500, Pete Wyckoff wrote:
> [EMAIL PROTECTED] wrote on Tue, 12 Feb 2008 20:09 -0800:
> > One other area that has not been brought up yet (I think) is the
> > applicability of notifiers in letting users know when pinned memory
> > is reclaimed by the kernel. This
--- Christoph Lameter <[EMAIL PROTECTED]> wrote:
> On Wed, 13 Feb 2008, Kanoj Sarcar wrote:
>
> > It seems that the need is to solve potential
> memory
> > shortage and overcommit issues by being able to
> > reclaim pages pinned by rdma driver/hardware. Is
> my
> > understanding correct?
>
> Co
[EMAIL PROTECTED] wrote on Tue, 12 Feb 2008 20:09 -0800:
> One other area that has not been brought up yet (I think) is the
> applicability of notifiers in letting users know when pinned memory
> is reclaimed by the kernel. This is useful when a lower-level
> library employs lazy deregistration st
On Wed, 13 Feb 2008, Kanoj Sarcar wrote:
> It seems that the need is to solve potential memory
> shortage and overcommit issues by being able to
> reclaim pages pinned by rdma driver/hardware. Is my
> understanding correct?
Correct.
> If I do understand correctly, then why is rdma page
> pinning
--- Christoph Lameter <[EMAIL PROTECTED]> wrote:
> On Wed, 13 Feb 2008, Christian Bell wrote:
>
> > not always be in the thousands but you're still
> claiming scalability
> > for a mechanism that essentially logs who accesses
> the regions. Then
> > there's the fact that reclaim becomes a colle
Avi Kivity wrote:
> Glauber de Oliveira Costa wrote:
>> This is the host part of kvm clocksource implementation. As it does
>> not include clockevents, it is a fairly simple implementation. We
>> only have to register a per-vcpu area, and start writting to it
>> periodically.
>>
>> The area is bin
Ok taking everybodys suggestions. This patch adds a
--disable-cpu-emulation option to qemu. This way powerpc has the
ability to compile, and also gives other archs the ability to easily add
the ability to compile without the tcg code.
Signed-off-by: Jerone Young <[EMAIL PROTECTED]>
diff --git a/
On Wed, 13 Feb 2008, Jason Gunthorpe wrote:
> Unfortunately it really has little to do with the drivers - changes,
> for instance, need to be made to support this in the user space MPI
> libraries. The RDMA ops do not pass through the kernel, userspace
> talks directly to the hardware which compli
On Wed, 13 Feb 2008, Christian Bell wrote:
> not always be in the thousands but you're still claiming scalability
> for a mechanism that essentially logs who accesses the regions. Then
> there's the fact that reclaim becomes a collective communication
> operation over all region accessors. Makes
Hi Jerone,
Jerone Young wrote:
Ok taking everybodys suggestions. This patch adds a
--disable-cpu-emulation option to qemu. This way powerpc has the
ability to compile, and also gives other archs the ability to easily add
the ability to compile without the tcg code.
Signed-off-by: Jerone Young
On Wed, Feb 13, 2008 at 10:51:58AM -0800, Christoph Lameter wrote:
> On Tue, 12 Feb 2008, Jason Gunthorpe wrote:
>
> > But this isn't how IB or iwarp work at all. What you describe is a
> > significant change to the general RDMA operation and requires changes to
> > both sides of the connection an
On Wed, 13 Feb 2008, Christoph Lameter wrote:
> Right. We (SGI) have done something like this for a long time with XPmem
> and it scales ok.
I'd dispute this based on experience developing PGAS language support
on the Altix but more importantly (and less subjectively), I think
that "scales ok" r
On Wed, 13 Feb 2008, Christoph Raisch wrote:
> For ehca we currently can't modify a large MR when it has been allocated.
> EHCA Hardware expects the pages to be there (MRs must not have "holes").
> This is also true for the global MR covering all kernel space.
> Therefore we still need the memory
On Tue, 12 Feb 2008, Christian Bell wrote:
> You're arguing that a HW page table is not needed by describing a use
> case that is essentially what all RDMA solutions already do above the
> wire protocols (all solutions except Quadrics, of course).
The HW page table is not essential to the notific
Jerone Young wrote:
> On Wed, 2008-02-13 at 09:29 +0200, Avi Kivity wrote:
>
>> Jerone Young wrote:
>>
>>> So the recent code in qemu cvs has problem powerpc. So what I have done
>>> is mainly work around this in the build system, by creating
>>> ppcemb_kvm-sofmmu target. Along with this is
* [EMAIL PROTECTED] <[EMAIL PROTECTED]> [2008-02-13 12:18]:
> Greetings,
>
> I'm using vanilla sources 2.6.24.2 and KVM-60. I'm trying to install a
> corporate rollout WinXP image which utilizes WinPE in an attempt to be
> clever. Unfortunately, this seems to fail because dmidecode and vpddecode
>
On Tue, 12 Feb 2008, Jason Gunthorpe wrote:
> But this isn't how IB or iwarp work at all. What you describe is a
> significant change to the general RDMA operation and requires changes to
> both sides of the connection and the wire protocol.
Yes it may require a separate connection between both s
Greetings,
I'm using vanilla sources 2.6.24.2 and KVM-60. I'm trying to install a
corporate rollout WinXP image which utilizes WinPE in an attempt to be
clever. Unfortunately, this seems to fail because dmidecode and vpddecode
produce no usable results. Is there any chance that kvm/qemu will see
s
On Wed, Feb 13, 2008 at 06:07:36PM +0100, Koen Vermeer wrote:
> On Wed, 2008-02-13 at 17:55 +0200, Dan Kenigsberg wrote:
> > On Wed, Feb 13, 2008 at 02:00:38PM +0100, [EMAIL PROTECTED] wrote:
> > However, as Uri mentioned earlier, this is useful only with newer KVMs.
> > I assume that your host run
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Wed 13/02/2008 14:52
To: Uri Lublin
Cc: kvm-devel@lists.sourceforge.net
Subject: RE: [kvm-devel] Clock off in guest
>> This would not work if you are using an old version of kvm ( with no
>> in-kernel-apic )
>> I recommend upgrading to kvm-6
This patch implements the Last Branch Record Virtualization (LBRV) feature of
the AMD Barcelona and Phenom processors into the kvm-amd module. It will only
be enabled if the guest enables last branch recording in the DEBUG_CTL MSR. So
there is no increased world switch overhead when the guest doesn
This patch changes the kvm-amd module to allocate the SVM MSR permission map
per VCPU instead of a global map for all VCPUs. With this we have more
flexibility allowing specific guests to access virtualized MSRs. This is
required for LBR virtualization.
Signed-off-by: Joerg Roedel <[EMAIL PROTECTE
This patch set enables the virtualization of the last branch record in SVM if
this feature is supported by the hardware. To the previous post the fix for the
XP 64 bit install crash has been removed from this series and was posted
seperatly to keep it small enough for 2.6.25. This patch set applies
Change the parameter of the init_vmcb() function in the kvm-amd module from
struct vmcb to struct vcpu_svm.
Signed-off-by: Joerg Roedel <[EMAIL PROTECTED]>
Signed-off-by: Markus Rechberger <[EMAIL PROTECTED]>
---
arch/x86/kvm/svm.c | 12 ++--
1 files changed, 6 insertions(+), 6 deletion
On Wed, 2008-02-13 at 09:29 +0200, Avi Kivity wrote:
> Jerone Young wrote:
> > So the recent code in qemu cvs has problem powerpc. So what I have done
> > is mainly work around this in the build system, by creating
> > ppcemb_kvm-sofmmu target. Along with this is a fake-exec.c that stubs
> > out t
On Wed, 2008-02-13 at 17:55 +0200, Dan Kenigsberg wrote:
> On Wed, Feb 13, 2008 at 02:00:38PM +0100, [EMAIL PROTECTED] wrote:
> However, as Uri mentioned earlier, this is useful only with newer KVMs.
> I assume that your host runs the kvm from 2.6.23 which is pretty old in
> kvm timescale. Try down
> On Wed, Feb 13, 2008 at 02:00:38PM +0100, [EMAIL PROTECTED] wrote:
>> > What is the clock source of your guest? If it is the traditional PIT,
>> > you describe a known problem in busy hosts. You may try to set
>> > clocksource=tsc in the guest kerenl parameters.
>> Thanks for your reply. I tried
> > > Chelsio's T3 HW doesn't support this.
For ehca we currently can't modify a large MR when it has been allocated.
EHCA Hardware expects the pages to be there (MRs must not have "holes").
This is also true for the global MR covering all kernel space.
Therefore we still need the memory to be
On Wed, Feb 13, 2008 at 02:00:38PM +0100, [EMAIL PROTECTED] wrote:
> Hi Dan,
>
> > On Wed, Feb 13, 2008 at 10:41:44AM +0100, Koen Vermeer wrote:
> >> I'm running an Linux AMD64 guest on an AMD64 host. The host is running a
> >> 2.6.23 kernel (self compiled), the guest is running a stock
> >> linux
While installing Windows XP 64 bit wants to access the DEBUGCTL and the last
branch record (LBR) MSRs. Don't allowing this in KVM causes the installation to
crash. This patch allow the access to these MSRs and fixes the issue.
Signed-off-by: Joerg Roedel <[EMAIL PROTECTED]>
Signed-off-by: Markus R
> GRU
> - Simple additional hardware TLB (possibly covering multiple instances of
> Linux)
> - Needs TLB shootdown when the VM unmaps pages.
> - Determines page address via follow_page (from interrupt context) but can
> fall back to get_user_pages().
> - No page reference possible since no page
Hi Dan,
> On Wed, Feb 13, 2008 at 10:41:44AM +0100, Koen Vermeer wrote:
>> I'm running an Linux AMD64 guest on an AMD64 host. The host is running a
>> 2.6.23 kernel (self compiled), the guest is running a stock
>> linux-image-2.6.22-3-amd64 Debian kernel.
>> My problem is that the clock on the gue
> This would not work if you are using an old version of kvm ( with no
> in-kernel-apic )
> I recommend upgrading to kvm-60 (or latest linux kernel).
Should I upgrade the guest kernel or the host kernel? My bet is the host
kernel, but the clocksource=tsc applies to the guest, so I'm not really
sur
Avi Kivity <[EMAIL PROTECTED]> writes:
> In practice it doesn't matter, but yes, any fd which we will
> select() needs to have a signal attached.
It matters to me, because I am removing periodic timers, and so I
ended up where I could not attach with VNC at all (well, strace would
break the loop)
Anders Melchiorsen wrote:
> I am wondering about this commit,
>
> http://git.kernel.org/?p=virt/kvm/kvm-userspace.git;a=commit;h=b4e392c21c4b98c1c13af353caa3d6e6bcb6b8af
>
> which adds signals on tap I/O. It seems a bit half-done to me. For one
> thing, it is mixing timers with I/O.
>
>
The sig
From: [EMAIL PROTECTED] on behalf of Dan Kenigsberg
Sent: Wed 13/02/2008 13:25
To: Koen Vermeer
Cc: kvm-devel@lists.sourceforge.net
Subject: Re: [kvm-devel] Clock off in guest
>On Wed, Feb 13, 2008 at 10:41:44AM +0100, Koen Vermeer wrote:
>> Hi,
>>
>> I'm running an Linux AMD64 guest on an AMD64
I am wondering about this commit,
http://git.kernel.org/?p=virt/kvm/kvm-userspace.git;a=commit;h=b4e392c21c4b98c1c13af353caa3d6e6bcb6b8af
which adds signals on tap I/O. It seems a bit half-done to me. For one
thing, it is mixing timers with I/O.
Anyway, my question is about the remaining file de
On Wed, Feb 13, 2008 at 10:41:44AM +0100, Koen Vermeer wrote:
> Hi,
>
> I'm running an Linux AMD64 guest on an AMD64 host. The host is running a
> 2.6.23 kernel (self compiled), the guest is running a stock
> linux-image-2.6.22-3-amd64 Debian kernel.
>
> My problem is that the clock on the guest
Glauber de Oliveira Costa wrote:
> This is the host part of kvm clocksource implementation. As it does
> not include clockevents, it is a fairly simple implementation. We
> only have to register a per-vcpu area, and start writting to it periodically.
>
> The area is binary compatible with xen, as w
Joerg Roedel wrote:
>>>
>>>
>> This still has the same issue as the previous patchset: if the guest
>> enables some other bit
>> in MSR_IA32_DEBUCTLMSR, we silently ignore it. We should either pr_unimpl()
>> on such bits or
>> not handle them (ultimately injecting a #GP).
>>
>
>
On Wed, Feb 13, 2008 at 11:50:58AM +0200, Avi Kivity wrote:
> Joerg Roedel wrote:
> >@@ -1224,6 +1261,15 @@ static int svm_set_msr(struct kvm_vcpu *vcpu,
> >unsigned ecx, u64 data)
> > if (data != 0)
> > goto unhandled;
> > break;
> >+case MSR_IA32_D
Joerg Roedel wrote:
> @@ -1224,6 +1261,15 @@ static int svm_set_msr(struct kvm_vcpu *vcpu, unsigned
> ecx, u64 data)
> if (data != 0)
> goto unhandled;
> break;
> + case MSR_IA32_DEBUGCTLMSR:
> + svm->vmcb->save.dbgctl = data;
> +
Hi,
I'm running an Linux AMD64 guest on an AMD64 host. The host is running a
2.6.23 kernel (self compiled), the guest is running a stock
linux-image-2.6.22-3-amd64 Debian kernel.
My problem is that the clock on the guest is off (slow), while the clock
on the host seems to be OK. When doing 'time
-Original Message-
From: [EMAIL PROTECTED] on behalf of Andrey Dmitriev
Sent: Tue 2/12/2008 11:20 PM
To: kvm-devel@lists.sourceforge.net
Subject: [kvm-devel] stable distro for kvm?
>Any recommendations or link to plans for a stable KVM with any major distro?
Latest KVM (KVM-60) is stable
47 matches
Mail list logo
