Andrea Arcangeli wrote:
> I thought some more about this.
>
> BTW, for completeness: normally (with exception of vm_destroy) the
> put_page run by rmap_remove won't be the last one, but still the page
> can go in the freelist a moment after put_page runs (leading to the
> same problem). The VM is p
>From 41d65b55580d3f07f9f1c50e89e3d64c5d10fbaf Mon Sep 17 00:00:00 2001
From: Feng (Eric) Liu <[EMAIL PROTECTED]>
Date: Tue, 1 Apr 2008 07:26:14 -0400
Subject: [PATCH] KVM: Add kvm trace support. when config KVM_TRACE, it
allows userspace app to read the trace of kvm_related
events through the rela
>From e0d0f33ce1a536d4f2c3a1763f23a89f0a726cd6 Mon Sep 17 00:00:00 2001
From: Feng (Eric) Liu <[EMAIL PROTECTED]>
Date: Mon, 31 Mar 2008 10:57:16 -0400
Subject: [PATCH] kvm: Add a tool kvmtrace for collecting binary data
from relayfs. The code is based on blktrace.
Signed-off-by: Feng (Eric) Liu <
>From d56731ffc6d5742a88a157dfe0e4344d35f7db58 Mon Sep 17 00:00:00 2001
From: Feng(Eric) Liu <[EMAIL PROTECTED]>
Date: Mon, 31 Mar 2008 10:08:55 -0400
Subject: [PATCH] KVM: Add some trace entries in current code and define
some interfaces for userspace app to contrl and use tracing data.
Signed-of
>From a18df6cb088a07ce34fb1981ca3077f5e6925ae2 Mon Sep 17 00:00:00 2001
From: Feng (Eric) Liu <[EMAIL PROTECTED]>
Date: Mon, 31 Mar 2008 10:35:59 -0400
Subject: [PATCH] kvm: Modify "Kbuild" for kvm trace and ensure
"kvm_stat"
work when kvm trace is enabled by userspace app.
Signed-off-by: Feng (E
>From 182054d6c1e6a6213f3fa56aab1ca56c39f9ba80 Mon Sep 17 00:00:00 2001
From: Feng(Eric) Liu <[EMAIL PROTECTED]>
Date: Mon, 31 Mar 2008 10:52:57 -0400
Subject: [PATCH] kvm: "kvmtrace_format" parses the binary trace data
outputted
by kvmtrace, and reformats it according to the rules in the
file "for
Hi,
The following patches add trace support in kvm using relay_fs
and trace_mark according to last comments. if we want to use it, we
should config kvm_trace firstly which depends on MARKERS and SYSFS, at
this case it will add a tiny time penalty to check whether we provide a
hook to call a
Avi Kivity wrote:
> Hollis Blanchard wrote:
>> I'm pleased to report that we now have working network support in the
>> guest, via the virtio-net driver. In fact, we can use NFS for the
>> guest's root filesystem. :) Boot log attached.
>>
>>
>
> Congrats!
>
>> The bad news is that it's very sl
On Tuesday 25 March 2008, Carsten Otte wrote:
> + case KVM_S390_SIGP_SET_PREFIX:
> + VCPU_EVENT(vcpu, 4, "interrupt: set prefix to %x",
> +inti->prefix.address);
> + vcpu->stat.deliver_prefix_signal++;
> + vcpu->arch.sie_block->prefix
On Tuesday 25 March 2008, Carsten Otte wrote:
> +
> +static inline void __user *__guestaddr_to_user(struct kvm_vcpu *vcpu,
> +u64 guestaddr)
> +{
> + u64 prefix = vcpu->arch.sie_block->prefix;
> + u64 origin = vcpu->kvm->arch.guest_origin;
> +
Avi Kivity wrote:
> Zhang, Xiantao wrote:
>>
>> diff --git a/include/linux/smp.h b/include/linux/smp.h
>> index 55232cc..b71820b 100644
>> --- a/include/linux/smp.h
>> +++ b/include/linux/smp.h
>> @@ -56,6 +56,9 @@ int smp_call_function(void(*func)(void *info),
>> void *info, int retry, int wait);
Dor Laor wrote:
> On Sat, 2008-03-29 at 16:55 -0500, Anthony Liguori wrote:
>
>> This patch introduces virtio support over PCI. virtio is a generic virtual
>> IO
>> framework for Linux first introduced in 2.6.23. Since 2.6.25, virtio has
>> supported a PCI transport which this patch implement
On Sat, 2008-03-29 at 16:55 -0500, Anthony Liguori wrote:
> This patch introduces virtio support over PCI. virtio is a generic virtual IO
> framework for Linux first introduced in 2.6.23. Since 2.6.25, virtio has
> supported a PCI transport which this patch implements.
>
> Since the last time t
Alexander Graf wrote:
>
> On Mar 30, 2008, at 9:44 PM, Anthony Liguori wrote:
>
>> Felix Leimbach wrote:
>>> While testing the new virtio drivers in linux-2.6.25 my test
>>> 2.6.25-rc7-git5 guest with paravirt support running in KVM-64 thinks it
>>> sits on cold and unfriendly bare metal instead of
On Mar 30, 2008, at 9:44 PM, Anthony Liguori wrote:
> Felix Leimbach wrote:
>> While testing the new virtio drivers in linux-2.6.25 my test
>> 2.6.25-rc7-git5 guest with paravirt support running in KVM-64
>> thinks it
>> sits on cold and unfriendly bare metal instead of a safe and cosy KVM
>> b
Felix Leimbach wrote:
> While testing the new virtio drivers in linux-2.6.25 my test
> 2.6.25-rc7-git5 guest with paravirt support running in KVM-64 thinks it
> sits on cold and unfriendly bare metal instead of a safe and cosy KVM
> bed ;-)
> Because it is very unhappy it emits the following mes
Paul Brook wrote:
> On Sunday 30 March 2008, Anthony Liguori wrote:
>
> The entity processing the data shouldn't need to know or care how the
> translation is done. PhysIOVector should describe everything it need to know.
>
Okay, I'll update.
>> What could work is if the DMA API functions
On Sunday 30 March 2008, Anthony Liguori wrote:
> Paul Brook wrote:
> > On Saturday 29 March 2008, Anthony Liguori wrote:
> >> This patch introduces a PCI DMA API and some generic code to support
> >> other DMA APIs. Two types are introduced: PhysIOVector and IOVector. A
> >> DMA API maps a PhysI
While testing the new virtio drivers in linux-2.6.25 my test
2.6.25-rc7-git5 guest with paravirt support running in KVM-64 thinks it
sits on cold and unfriendly bare metal instead of a safe and cosy KVM
bed ;-)
Because it is very unhappy it emits the following message during boot:
Booting paravi
Update:
The same mysterious 100% CPU Windows hangs occur with KVM-64 on a
2.6.24.3 kernel.
While I could not yet reproduce the hang on a cleanly installed Windows
Server 2003 STD guest, the same hang did occur on an idle Windows Vista
guest which was cleanly installed in the KVM environment.
So
Blue Swirl wrote:
> On 3/30/08, Anthony Liguori <[EMAIL PROTECTED]> wrote:
>
>> Blue Swirl wrote:
>> > On 3/30/08, Anthony Liguori <[EMAIL PROTECTED]> wrote:
>> >
>> >> This patch introduces a PCI DMA API and some generic code to support
>> other DMA
>> >> APIs. Two types are introduced:
Paul Brook wrote:
> On Saturday 29 March 2008, Anthony Liguori wrote:
>
>> +if ((elem = virtqueue_pop(n->rx_vq)) == NULL) {
>> + /* wait until the guest adds some rx bufs */
>> + n->can_receive = 0;
>> + return;
>> +}
>>
>
> Setting can_receive to zero *after* drop
On 3/30/08, Anthony Liguori <[EMAIL PROTECTED]> wrote:
> Blue Swirl wrote:
> > On 3/30/08, Anthony Liguori <[EMAIL PROTECTED]> wrote:
> >
> >> This patch introduces a PCI DMA API and some generic code to support
> other DMA
> >> APIs. Two types are introduced: PhysIOVector and IOVector. A D
Avi Kivity wrote:
> Anthony Liguori wrote:
>
>>> This looks like it wouldn't scale to handle the Sparc systems. There
>>> we want to make more translation steps from DVMA addresses to physical
>>> in DMA controller and IOMMU and only in the final stage to void *. To
>>> handle this, probably the
Anthony Liguori wrote:
>>
>> This looks like it wouldn't scale to handle the Sparc systems. There
>> we want to make more translation steps from DVMA addresses to physical
>> in DMA controller and IOMMU and only in the final stage to void *. To
>> handle this, probably there should be an opaque par
Avi Kivity wrote:
> Anthony Liguori wrote:
>> This patch introduces a PCI DMA API and some generic code to support
>> other DMA
>> APIs. Two types are introduced: PhysIOVector and IOVector. A DMA API
>> maps a PhysIOVector, which is composed of target_phys_addr_t, into an
>> IOVector,
>> which
Blue Swirl wrote:
> On 3/30/08, Anthony Liguori <[EMAIL PROTECTED]> wrote:
>
>> This patch introduces a PCI DMA API and some generic code to support other
>> DMA
>> APIs. Two types are introduced: PhysIOVector and IOVector. A DMA API
>> maps a PhysIOVector, which is composed of target_phys_
Paul Brook wrote:
> On Saturday 29 March 2008, Anthony Liguori wrote:
>
>> This patch introduces a PCI DMA API and some generic code to support other
>> DMA APIs. Two types are introduced: PhysIOVector and IOVector. A DMA API
>> maps a PhysIOVector, which is composed of target_phys_addr_t, int
Hi,
Selon "Zhang, Xiantao" <[EMAIL PROTECTED]>:
> >From 5f82ea88c095cf89cbae920944c05e578f35365f Mon Sep 17 00:00:00 2001
> From: Xiantao Zhang <[EMAIL PROTECTED]>
> Date: Wed, 12 Mar 2008 14:48:09 +0800
> Subject: [PATCH] kvm/ia64: Add mmio decoder for kvm/ia64.
[...]
> + pos
Izik Eidus wrote:
> ok, this should address all the issues.
>
> >From a4cd289ab2502172bde994612636f84bec5e7a60 Mon Sep 17 00:00:00 2001
> From: Izik Eidus <[EMAIL PROTECTED]>
> Date: Sun, 30 Mar 2008 15:13:47 +0300
> Subject: [PATCH] KVM: register the kvm mmu cache with the shrinker.
>
>
Applie
>From ebb9fe4765f1572314d2249e29a7ef4d0de07273 Mon Sep 17 00:00:00 2001
From: Izik Eidus <[EMAIL PROTECTED]>
Date: Sun, 30 Mar 2008 15:48:35 +0300
Subject: [PATCH] KVM: add kvm_get_kvm and kvm_put_kvm functions,
the main purpose of adding this functions is the abilaty to release the spinlock
that
Avi Kivity wrote:
> Izik Eidus wrote:
>> void kvm_mmu_module_exit(void)
>> {
>> if (pte_chain_cache)
>> @@ -1980,6 +2026,7 @@ void kvm_mmu_module_exit(void)
>> kmem_cache_destroy(rmap_desc_cache);
>> if (mmu_page_header_cache)
>> kmem_cache_destroy(mmu_page_header_cach
Zhang, Xiantao wrote:
>
> diff --git a/include/linux/smp.h b/include/linux/smp.h
> index 55232cc..b71820b 100644
> --- a/include/linux/smp.h
> +++ b/include/linux/smp.h
> @@ -56,6 +56,9 @@ int smp_call_function(void(*func)(void *info), void
> *info, int retry, int wait);
>
> int smp_call_funct
Hot diet solution for all weight watchers
Give her all the kicks she wants by driving a longer shaft into her
http://www.polinefe.com/
-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell servi
Bugs item #1929279, was opened at 2008-03-30 13:21
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1929279&group_id=180599
Please note that this message will contain a full copy
Anthony Liguori wrote:
> I converted everything to use offsetof but left the accessors. You need
> a fair number of macros to handle the various data sizes and even then,
> I think it ends up looking nicer with the macros. See my patch series
> on qemu-devel and let me know if you agree/disagr
Martin Maurer wrote:
>
> Hi all,
>
>
>
> I am running on kernel 2.6.24, KVM 63 – trying windows guests –
> working quite well.
>
>
>
> …but why tells the device manager that I have 15 CPU`s (QEMU Virtual
> CPU version 0.9.1)? The windows task manager is just showing one as
> expected.
>
>
Hollis Blanchard wrote:
> I'm pleased to report that we now have working network support in the
> guest, via the virtio-net driver. In fact, we can use NFS for the
> guest's root filesystem. :) Boot log attached.
>
>
Congrats!
> The bad news is that it's very slow, but the good news is that it
On Saturday 29 March 2008, Anthony Liguori wrote:
> + if ((elem = virtqueue_pop(n->rx_vq)) == NULL) {
> + /* wait until the guest adds some rx bufs */
> + n->can_receive = 0;
> + return;
> + }
Setting can_receive to zero *after* dropping a packet is a bit late.
Not a fatal
Anthony Liguori wrote:
> This patch introduces a PCI DMA API and some generic code to support other DMA
> APIs. Two types are introduced: PhysIOVector and IOVector. A DMA API
> maps a PhysIOVector, which is composed of target_phys_addr_t, into an
> IOVector,
> which is composed of void *.
>
> Th
On Saturday 29 March 2008, Anthony Liguori wrote:
> This patch introduces a PCI DMA API and some generic code to support other
> DMA APIs. Two types are introduced: PhysIOVector and IOVector. A DMA API
> maps a PhysIOVector, which is composed of target_phys_addr_t, into an
> IOVector, which is co
Marcelo Tosatti wrote:
> Unify slots_lock acquision around vcpu_run(). This is simpler and less
> error-prone.
>
> Also fix some callsites that were not grabbing the lock properly.
>
> Please review.
>
>
While I think we could simplify the locking even further (by locking at
the caller of __vc
Carlo Marcelo Arenas Belon wrote:
> remove dependency to the pci linux headers added since
> c10bf6159ff24501852c91a342c3077d5388b184 and that was generating the
> following conflict :
>
> qemu/hw/cirrus_vga.c:193:1: warning: "PCI_COMMAND_SERR" redefined
> In file included from /usr/include/l
Carlo Marcelo Arenas Belon wrote:
> included through "qemu-kvm.h" -> "cpu.h" -> "cpu-defs.h" for all architectures
> and resulting otherwise in :
>
> qemu/qemu-kvm-x86.c:23:1: warning: "ARRAY_SIZE" redefined In file included
> from ../cpu-defs.h:30,
> from qemu/target-i386/cpu.h:45,
> fr
Marcelo Tosatti wrote:
> - Fix reset, powerdown and shutdown.
> - Fix kvmctl.
>
>
Unfortunately, this is still broken:
- typing into a linux guest console, qemu locked up waiting for a signal
- the regression tests still fail due to guest slowdown. I haven't
isolated the cause yet (doesn't re
On 3/30/08, Anthony Liguori <[EMAIL PROTECTED]> wrote:
> This patch introduces a PCI DMA API and some generic code to support other DMA
> APIs. Two types are introduced: PhysIOVector and IOVector. A DMA API
> maps a PhysIOVector, which is composed of target_phys_addr_t, into an
> IOVector,
>
46 matches
Mail list logo
