On 07/29/11 06:53, Amos Kong wrote:
This test adds a usb storage for the guest, and do some check from monitor and
inside the guest.
It's not very stable, could you help to review if something is wrong?
"Not stable" means what exactly?
+output = session.get_command_output("lsusb")
+#n
On 2011-07-31 21:47, Avi Kivity wrote:
> When a range is being unmapped, ask accelerators (e.g. kvm) to synchronize the
> dirty bitmap to avoid losing information forever.
>
> Fixes grub2 screen update.
I does.
But something is still broken. As I reported before, the performance of
grub2 startup
get_system_io() returns the root I/O memory region.
Signed-off-by: Avi Kivity
---
Replaces v1 patches 9 and 10.
exec-memory.h |2 ++
exec.c| 10 ++
2 files changed, 12 insertions(+), 0 deletions(-)
diff --git a/exec-memory.h b/exec-memory.h
index c439aba..999fd69 100644
On 2011-08-01 09:34, Jan Kiszka wrote:
> On 2011-07-31 21:47, Avi Kivity wrote:
>> When a range is being unmapped, ask accelerators (e.g. kvm) to synchronize
>> the
>> dirty bitmap to avoid losing information forever.
>>
>> Fixes grub2 screen update.
>
> I does.
>
> But something is still broken
On Mon, Aug 01, 2011 at 02:25:36PM +0800, Liu Yuan wrote:
> On 07/28/2011 11:22 PM, Michael S. Tsirkin wrote:
> >
> >It would be nicer to reuse the worker infrastructure
> >from vhost.c. In particular this one ignores cgroups that
> >the owner belongs to if any.
> >Does this one do anything that vh
On Mon, Aug 01, 2011 at 01:46:33PM +0800, Liu Yuan wrote:
> >- I focused on using vfs interfaces in the kernel, so that I can
> >use it for file-backed devices.
> >Our use-case scenario is mostly file-backed images.
> >
> vhost-blk's that uses Linux AIO also support file-backed images.
> Actually,
On 08/01/2011 10:52 AM, Jan Kiszka wrote:
On 2011-08-01 09:34, Jan Kiszka wrote:
> On 2011-07-31 21:47, Avi Kivity wrote:
>> When a range is being unmapped, ask accelerators (e.g. kvm) to synchronize
the
>> dirty bitmap to avoid losing information forever.
>>
>> Fixes grub2 screen update.
>
On 07/29/2011 06:25 PM, Sasha Levin wrote:
On Fri, 2011-07-29 at 20:01 +0800, Liu Yuan wrote:
> Looking at this long list,most are function pointers that can not be
> inlined, and the internal data structures used by these functions are
> dozons. Leave aside code complexity, this long code pat
On Sun, Jul 31, 2011 at 08:57:43PM +0300, Avi Kivity wrote:
> @@ -491,30 +473,26 @@ static void virtio_pci_config_writel(void *opaque,
> uint32_t addr, uint32_t val)
> virtio_config_writel(proxy->vdev, addr, val);
> }
>
> -static void virtio_map(PCIDevice *pci_dev, int region_num,
> -
On 08/01/2011 04:12 PM, Michael S. Tsirkin wrote:
On Mon, Aug 01, 2011 at 02:25:36PM +0800, Liu Yuan wrote:
On 07/28/2011 11:22 PM, Michael S. Tsirkin wrote:
It would be nicer to reuse the worker infrastructure
>from vhost.c. In particular this one ignores cgroups that
the owner belongs to if
On 2011-08-01 10:16, Avi Kivity wrote:
> On 08/01/2011 10:52 AM, Jan Kiszka wrote:
>> On 2011-08-01 09:34, Jan Kiszka wrote:
>> > On 2011-07-31 21:47, Avi Kivity wrote:
>> >> When a range is being unmapped, ask accelerators (e.g. kvm) to
>> synchronize the
>> >> dirty bitmap to avoid losing info
On 08/01/2011 04:17 PM, Avi Kivity wrote:
On 07/29/2011 06:25 PM, Sasha Levin wrote:
On Fri, 2011-07-29 at 20:01 +0800, Liu Yuan wrote:
> Looking at this long list,most are function pointers that can not be
> inlined, and the internal data structures used by these functions are
> dozons. Leav
On 08/01/2011 12:05 PM, Jan Kiszka wrote:
On 2011-08-01 10:16, Avi Kivity wrote:
> On 08/01/2011 10:52 AM, Jan Kiszka wrote:
>> On 2011-08-01 09:34, Jan Kiszka wrote:
>> > On 2011-07-31 21:47, Avi Kivity wrote:
>> >> When a range is being unmapped, ask accelerators (e.g. kvm) to
>> synch
On 08/01/2011 12:30 PM, Avi Kivity wrote:
It does not link here due to forgotten rwhandler in Makefile.target.
I probably still have it in my tree, will update and re-push.
done now.
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the
On 08/01/2011 11:26 AM, Michael S. Tsirkin wrote:
>
> static void virtio_write_config(PCIDevice *pci_dev, uint32_t address,
> uint32_t val, int len)
> {
> VirtIOPCIProxy *proxy = DO_UPCAST(VirtIOPCIProxy, pci_dev, pci_dev);
> +VirtIODevice *vdev =
On 07/29/2011 10:57 PM, Umesh Deshpande wrote:
This patch creates a separate thread for the guest migration on the source side.
Signed-off-by: Umesh Deshpande
Looks pretty good!
One thing that shows, is that the interface separation between
buffered_file.c is migration.c is pretty weird. Yo
On 08/01/2011 12:18 PM, Liu Yuan wrote:
Agree. vhost-net works around the lack of async zero copy networking
interface. Block I/O on the other hand does have such an interface,
and in addition transaction rates are usually lower. All we're
saving is the syscall overhead.
Personally I too
On 07/29/2011 10:57 PM, Umesh Deshpande wrote:
+qemu_mutex_unlock_iothread();
while (s->state == MIG_STATE_ACTIVE) {
if (migrate_fd_check_expire()) {
+qemu_mutex_lock_iothread();
buffered_rate_tick(s->file);
+qemu_mutex_unlock_iothread();
Hi ,
I am studying KVM, but I have a question to ask.I wish someone can spare
time to help me.
What does the file "Assigned-dev.c" use for? I add some printk in the
funcitons in this file,but it seldom work.
Is it used for VT-d or others? can you give me some suggestions?
Thank you so much for y
On 08/01/2011 12:05 PM, Jan Kiszka wrote:
On 2011-08-01 10:16, Avi Kivity wrote:
> On 08/01/2011 10:52 AM, Jan Kiszka wrote:
>> On 2011-08-01 09:34, Jan Kiszka wrote:
>> > On 2011-07-31 21:47, Avi Kivity wrote:
>> >> When a range is being unmapped, ask accelerators (e.g. kvm) to
>> synch
On 2011-08-01 11:45, Avi Kivity wrote:
> On 08/01/2011 12:05 PM, Jan Kiszka wrote:
>> On 2011-08-01 10:16, Avi Kivity wrote:
>>> On 08/01/2011 10:52 AM, Jan Kiszka wrote:
On 2011-08-01 09:34, Jan Kiszka wrote:
> On 2011-07-31 21:47, Avi Kivity wrote:
>> When a range is being
On Mon, Aug 01, 2011 at 12:35:44PM +0300, Avi Kivity wrote:
> On 08/01/2011 11:26 AM, Michael S. Tsirkin wrote:
> >>
> >> static void virtio_write_config(PCIDevice *pci_dev, uint32_t address,
> >> uint32_t val, int len)
> >> {
> >> VirtIOPCIProxy *proxy =
On Mon, Aug 01, 2011 at 04:55:54PM +0800, Liu Yuan wrote:
> Nope, V1 completion thread doesn't has any mutex, thus can run
> parallel with the vhost worker.
It's true, it doesn't, but I think it's a bug :)
It calls vhost_add_used which definitely needs the
vq mutex.
--
To unsubscribe from this lis
On 08/01/2011 01:21 PM, Jan Kiszka wrote:
>
> Note that drop/add is always paired (i.e. the guest never sees an
> unmapped area), and we always map the full 64k even though cirrus code
> manages each 32k bank individually. It looks optimal... we're probably
> not testing the same thing (eith
On Mon, Jul 25, 2011 at 11:51:12AM +0300, Avi Kivity wrote:
> qemu_malloc() is type-unsafe as it returns a void pointer. Introduce
> QEMU_NEW() (and QEMU_NEWZ()), which return the correct type.
>
> Signed-off-by: Avi Kivity
> ---
>
> This is part of my memory API patchset, but doesn't really be
Hi
Please send in any agenda items you are interested in covering.
Later, Juan.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
This patch adds support for the UNIX extensions to 9p2000.
Supporting thses extensions allow us to transperantly mount UNIX directories
without missing features such as symlinks.
Signed-off-by: Sasha Levin
---
tools/kvm/include/kvm/virtio-9p.h |4 +-
tools/kvm/virtio/9p-pdu.c |6
This patch adds 2 new flags:
--rootfs [path] - Specifies a path to use as rootfs. The path will be mounted
using virtio-9p and booted from.
Easiest way to test it is to mount the sample image we recommend with kvm tool
(http://wiki.qemu.org/download/linux-0.2.img.bz2) and mounting it somewhere.
*
On Mon, 1 Aug 2011 17:08:22 +0300, Sasha Levin wrote:
> This patch adds support for the UNIX extensions to 9p2000.
>
> Supporting thses extensions allow us to transperantly mount UNIX directories
> without missing features such as symlinks.
>
> Signed-off-by: Sasha Levin
> ---
> tools/kvm/inc
On Mon, 2011-08-01 at 20:42 +0530, Aneesh Kumar K.V wrote:
> On Mon, 1 Aug 2011 17:08:22 +0300, Sasha Levin
> wrote:
> > This patch adds support for the UNIX extensions to 9p2000.
> >
> > Supporting thses extensions allow us to transperantly mount UNIX directories
> > without missing features s
Signed-off-by: Marcelo Tosatti
Index: qemu-kvm/sysemu.h
===
--- qemu-kvm.orig/sysemu.h
+++ qemu-kvm/sysemu.h
@@ -123,7 +123,6 @@ extern int semihosting_enabled;
extern int old_param;
extern int boot_menu;
extern QEMUClock *rtc_clo
Signed-off-by: Marcelo Tosatti
Index: qemu-kvm/qemu-kvm.c
===
--- qemu-kvm.orig/qemu-kvm.c
+++ qemu-kvm/qemu-kvm.c
@@ -31,7 +31,6 @@
int kvm_irqchip = 1;
int kvm_pit = 1;
int kvm_pit_reinject = 1;
-int kvm_nested = 0;
#define A
Signed-off-by: Marcelo Tosatti
Index: qemu-kvm/hw/piix_pci.c
===
--- qemu-kvm.orig/hw/piix_pci.c
+++ qemu-kvm/hw/piix_pci.c
@@ -30,7 +30,6 @@
#include "sysbus.h"
#include "range.h"
#include "xen.h"
-#include "kvm.h"
/*
* I440
See individual patches for details.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
As noted by the original commit. Probably kept in qemu-kvm
due to a mismerge.
commit 7d0adcd6d57149d4e9ec66f3a1c171df2bea2775
Author: aurel32
Date: Fri Oct 24 13:12:42 2008 +
hw/pc: don't register the memory hole as unassigned twice
Since revision 5228, we don't register the m
The information can be inferred from CPU_PUT_FULL_STATE and
bios_enabled.
Signed-off-by: Marcelo Tosatti
Index: qemu-kvm/kvm-tpr-opt.c
===
--- qemu-kvm.orig/kvm-tpr-opt.c
+++ qemu-kvm/kvm-tpr-opt.c
@@ -218,7 +218,7 @@ static int get
On Tue, Jul 26, 2011 at 06:08:09PM -0400, Donald Dutile wrote:
> The bcm5761 provides a PCIe Cap structure (capid=0x10)
> that is invalid, providing one that is 8 bytes shorter
> than the v2 PCIe spec defines.
> This leads to a memory corruption when mapped for device-assigment.
>
> Add a check in
On Mon, Jul 25, 2011 at 09:13:41AM +0200, Jan Kiszka wrote:
> From: Jan Kiszka
>
> kvm_add/remove_ioport_region need to know if the change is done during
> init or while the system is running. We added qemu_system_is_ready for
> this purpose which exported qemu_system_ready. The latter will be go
On 08/01/2011 06:50 PM, Marcelo Tosatti wrote:
On Tue, Jul 26, 2011 at 06:08:09PM -0400, Donald Dutile wrote:
> The bcm5761 provides a PCIe Cap structure (capid=0x10)
> that is invalid, providing one that is 8 bytes shorter
> than the v2 PCIe spec defines.
> This leads to a memory corruption
On 07/31/2011 10:57 AM, Avi Kivity wrote:
> This is a mostly mindless conversion of all QEMU PCI devices to the memory
> API.
> After this patchset is applied, it is no longer possible to create a PCI
> device
> using the old API.
>
> An immediate benefit is that PCI BARs that overlap each other
On Mon, Aug 01, 2011 at 06:53:49PM +0300, Avi Kivity wrote:
> On 08/01/2011 06:50 PM, Marcelo Tosatti wrote:
> >On Tue, Jul 26, 2011 at 06:08:09PM -0400, Donald Dutile wrote:
> >> The bcm5761 provides a PCIe Cap structure (capid=0x10)
> >> that is invalid, providing one that is 8 bytes shorter
>
qemu-kvm.git as of:
commit dacdc4b10bafbb21120e1c24a9665444768ef999
Merge: 7b69d4f 0af4922
Author: Avi Kivity
Date: Sun Jul 31 11:42:26 2011 +0300
Merge branch 'upstream-merge' into next
is aborting with the error:
qemu-kvm: qemu-kvm.git/hw/vhost.c:123: vhost_dev_unassign_memory:
Asserti
On 08/01/2011 06:56 PM, Marcelo Tosatti wrote:
OK. Its not lost:
commit f9c29774d2174df6ffc20becec20928948198914
Author: Donald Dutile
Date: Tue Jul 26 18:08:09 2011 -0400
device-assignment: handle device with incorrect PCIe Cap structure size
Ah, I looked for it in the kernel tree in
On Sun, 2011-07-31 at 08:21 +1000, Benjamin Herrenschmidt wrote:
> On Sat, 2011-07-30 at 09:58 +1000, Benjamin Herrenschmidt wrote:
> > Hi folks !
> >
> > So I promised Anthony I would try to summarize some of the comments &
> > issues we have vs. VFIO after we've tried to use it for PCI pass-thro
On 08/01/2011 11:44 AM, David Ahern wrote:
> qemu-kvm.git as of:
>
> commit dacdc4b10bafbb21120e1c24a9665444768ef999
> Merge: 7b69d4f 0af4922
> Author: Avi Kivity
> Date: Sun Jul 31 11:42:26 2011 +0300
>
> Merge branch 'upstream-merge' into next
>
> is aborting with the error:
>
> qemu-k
On Sun, 2011-07-31 at 09:54 +1000, Benjamin Herrenschmidt wrote:
> On Sat, 2011-07-30 at 12:20 -0600, Alex Williamson wrote:
>
> > On x86, the USB controllers don't typically live behind a PCIe-to-PCI
> > bridge, so don't suffer the source identifier problem, but they do often
> > share an interru
On 07/31/2011 10:57 AM, Avi Kivity wrote:
> +pci_register_bar_region(dev, 3, PCI_BASE_ADDRESS_SPACE_IO,
> +&d->cmd646_bar[2].cmd);
Typo: cmd646_bar[1].
r~
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger
On Mon, Aug 01, 2011 at 12:35:44PM +0300, Avi Kivity wrote:
> On 08/01/2011 11:26 AM, Michael S. Tsirkin wrote:
> >>
> >> static void virtio_write_config(PCIDevice *pci_dev, uint32_t address,
> >> uint32_t val, int len)
> >> {
> >> VirtIOPCIProxy *proxy =
* Zhi Yong Wu [2011-08-01 01:30]:
> The main goal of the patch is to effectively cap the disk I/O speed or counts
> of one single VM.It is only one draft, so it unavoidably has some drawbacks,
> if you catch them, please let me know.
>
> The patch will mainly introduce one block I/O throttling
* Zhi Yong Wu [2011-08-01 01:30]:
> +static AIOPool block_queue_pool = {
> +.aiocb_size = sizeof(struct BlockDriverAIOCB),
> +.cancel = qemu_block_queue_cancel,
> +};
> +
> +static void qemu_block_queue_callback(void *opaque, int ret)
> +{
> +BlockDriverAIOCB *acb
On 08/01/2011 03:26 AM, Michael S. Tsirkin wrote:
On Sun, Jul 31, 2011 at 08:57:43PM +0300, Avi Kivity wrote:
@@ -491,30 +473,26 @@ static void virtio_pci_config_writel(void *opaque,
uint32_t addr, uint32_t val)
virtio_config_writel(proxy->vdev, addr, val);
}
-static void virtio_map(PC
On 08/01/2011 05:23 AM, Michael S. Tsirkin wrote:
On Mon, Aug 01, 2011 at 12:35:44PM +0300, Avi Kivity wrote:
On 08/01/2011 11:26 AM, Michael S. Tsirkin wrote:
static void virtio_write_config(PCIDevice *pci_dev, uint32_t address,
uint32_t val, int len)
On Sun, 2011-07-31 at 17:09 +0300, Avi Kivity wrote:
> On 07/30/2011 02:58 AM, Benjamin Herrenschmidt wrote:
> > Due to our paravirt nature, we don't need to masquerade the MSI-X table
> > for example. At all. If the guest configures crap into it, too bad, it
> > can only shoot itself in the foot s
* Zhi Yong Wu [2011-08-01 01:32]:
> Note:
> 1.) When bps/iops limits are specified to a small value such as 511
> bytes/s, this VM will hang up. We are considering how to handle this senario.
> 2.) When "dd" command is issued in guest, if its option bs is set to a
> large value such
On 08/01/2011 05:37 AM, Paolo Bonzini wrote:
On 07/29/2011 10:57 PM, Umesh Deshpande wrote:
This patch creates a separate thread for the guest migration on the
source side.
Signed-off-by: Umesh Deshpande
Looks pretty good!
One thing that shows, is that the interface separation between
buff
On Sun, 2011-07-31 at 17:09 +0300, Avi Kivity wrote:
> On 07/30/2011 02:58 AM, Benjamin Herrenschmidt wrote:
> > - Having a magic heuristic in libvirt to figure out those constraints is
> > WRONG. This reeks of XFree 4 PCI layer trying to duplicate the kernel
> > knowledge of PCI resource managemen
On Mon, 2011-08-01 at 10:40 -0600, Alex Williamson wrote:
> On Sun, 2011-07-31 at 08:21 +1000, Benjamin Herrenschmidt wrote:
> > On Sat, 2011-07-30 at 09:58 +1000, Benjamin Herrenschmidt wrote:
> > > Hi folks !
> > >
> > > So I promised Anthony I would try to summarize some of the comments &
> > >
On Mon, 2011-08-01 at 12:59 -0600, Alex Williamson wrote:
> >
> > .../...
>
> I'll try to consolidate my reply to all the above here because there are
> too many places above to interject and make this thread even more
> difficult to respond to.
True, I should try to do the same :-)
> Much
This test uses 'hdparm' to set disk device to low/high
performance status, and compare the reading speed.
The emulated device should pass all the tests.
Signed-off-by: Feng Yang
Signed-off-by: Amos Kong
---
client/tests/kvm/tests/hdparm.py | 84
client/t
59 matches
Mail list logo
