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,
which
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
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,
from
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
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
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 *.
This
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 flaw,
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's
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.
kvm
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/disagree.
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=detailatid=893831aid=1929279group_id=180599
Please note that this message will contain a full copy of
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
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
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
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.
[...]
+ post_update =
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, into an
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_addr_t,
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 is composed
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 parameter
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 there should be
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 DMA API
maps
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* dropping a packet is
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: PhysIOVector and
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
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
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 PhysIOVector,
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 mapped
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 message
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
bed ;-)
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 a safe and
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 these
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 implements.
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 slow, but the
33 matches
Mail list logo
