On Sat, 2009-10-10 at 16:48 +0800, Yolkfull Chow wrote:
On Sat, Oct 10, 2009 at 04:24:45PM +0800, Yolkfull Chow wrote:
On Mon, Oct 05, 2009 at 04:03:22PM -0300, Lucas Meneghel Rodrigues wrote:
Hi Yolkfull! I've checked your patch, but it turns out that the comma
is valid syntax for the
This (broken) check dates back to the days when this code was shared
across architectures. x86 has IOMEM, so drop it.
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
---
arch/x86/kvm/x86.c |2 --
1 files changed, 0 insertions(+), 2 deletions(-)
diff --git a/arch/x86/kvm/x86.c
Hi, Michael,
I found that if the sessions initialized using kvm_subprcoess are not closed,
the processes will never exit, and /tmp/kvm_spawn will be filled with the
temporary files.
And we can find in the code,
# kvm_subprocess.py
...
# Read from child and write to files/pipes
Hi all,
I am a KVM newbie and I picked up the following task from the TODO of the KVM
wiki.
Add a qemu interface for sharing memory between guests. Using a pci device to
expose the shared memory is probably a good starting point. (this should use
virtio and probably depends on
Hi,
I was starring at the IRQ delivery path of assigned devices for a while,
wondering why we have a work queue there. Now, after looking at some
prehistoric versions, I think the reason is that there once was a mutex
involved while we now use RCU. Am I right that we could actually drop
this
On Mon, Oct 12, 2009 at 09:03:18AM +0200, Jan Kiszka wrote:
Hi,
I was starring at the IRQ delivery path of assigned devices for a while,
wondering why we have a work queue there. Now, after looking at some
prehistoric versions, I think the reason is that there once was a mutex
involved
Gleb Natapov wrote:
On Mon, Oct 12, 2009 at 09:03:18AM +0200, Jan Kiszka wrote:
Hi,
I was starring at the IRQ delivery path of assigned devices for a while,
wondering why we have a work queue there. Now, after looking at some
prehistoric versions, I think the reason is that there once was a
On Mon, Oct 12, 2009 at 09:27:19AM +0200, Jan Kiszka wrote:
Gleb Natapov wrote:
On Mon, Oct 12, 2009 at 09:03:18AM +0200, Jan Kiszka wrote:
Hi,
I was starring at the IRQ delivery path of assigned devices for a while,
wondering why we have a work queue there. Now, after looking at some
On Mon, Oct 12, 2009 at 09:50:58AM +0200, Jan Kiszka wrote:
Gleb Natapov wrote:
On Mon, Oct 12, 2009 at 09:27:19AM +0200, Jan Kiszka wrote:
Gleb Natapov wrote:
On Mon, Oct 12, 2009 at 09:03:18AM +0200, Jan Kiszka wrote:
Hi,
I was starring at the IRQ delivery path of assigned devices
Gleb Natapov wrote:
On Mon, Oct 12, 2009 at 09:27:19AM +0200, Jan Kiszka wrote:
Gleb Natapov wrote:
On Mon, Oct 12, 2009 at 09:03:18AM +0200, Jan Kiszka wrote:
Hi,
I was starring at the IRQ delivery path of assigned devices for a while,
wondering why we have a work queue there. Now, after
Gleb Natapov wrote:
On Mon, Oct 12, 2009 at 09:50:58AM +0200, Jan Kiszka wrote:
Gleb Natapov wrote:
On Mon, Oct 12, 2009 at 09:27:19AM +0200, Jan Kiszka wrote:
Gleb Natapov wrote:
On Mon, Oct 12, 2009 at 09:03:18AM +0200, Jan Kiszka wrote:
Hi,
I was starring at the IRQ delivery path of
On 10/12/2009 09:50 AM, Jan Kiszka wrote:
Apic is lockless. For ioapic/pic I used spinlocks initially, but Avi
prefers mutexes. Theoretically it is possible to make them lockless,
but code will be complex and eventually more slow, since more then two
atomic operation will be used on irq
On Mon, Oct 12, 2009 at 10:16:56AM +0200, Jan Kiszka wrote:
Apic is lockless. For ioapic/pic I used spinlocks initially, but Avi
prefers mutexes. Theoretically it is possible to make them lockless,
but code will be complex and eventually more slow, since more then two
atomic operation will
On 10/06/2009 07:24 PM, Glauber Costa wrote:
When we migrate a kvm guest that uses pvclock between two hosts, we may
suffer a large skew. This is because there can be significant differences
between the monotonic clock of the hosts involved. When a new host with
a much larger monotonic time
On 10/12/2009 08:53 AM, Sivaram Kannan wrote:
Hi all,
I am a KVM newbie and I picked up the following task from the TODO of the KVM
wiki.
Add a qemu interface for sharing memory between guests. Using a pci device to
expose the shared memory is probably a good starting point. (this should use
kmap_atomic_to_page was not exported before 2.6.32, and adding a compat
wrapper for it is impossible due to further missing exports. This breaks
x86-32 modules under CONFIG_HIGHMEM.
So avoid its use via a crude hack: nested_svm_map callers receive the
mapped page and have to pass it back to
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
---
linux-2.6 |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/linux-2.6 b/linux-2.6
index abb015a..8fdcaf6 16
--- a/linux-2.6
+++ b/linux-2.6
@@ -1 +1 @@
-Subproject commit abb015ac65852287c7a7c243c8cdee966a38854d
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
---
sync |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/sync b/sync
index 0bbd488..4821b84 100755
--- a/sync
+++ b/sync
@@ -119,6 +119,8 @@ def __hack(data):
line = sub(r'flags', r'kvm_pt_regs_flags', line)
The following changes since commit e19bf3254985d9b8b6b916acc82fc398595cff95:
Jan Kiszka (1):
x86: Remove zombie kvm_trace from build
are available in the git repository at:
git://git.kiszka.org/kvm-kmod.git queue
Jan Kiszka (4):
Remove const from vm_ops to avoid warnings on
On 10/12/2009 11:05 AM, Gleb Natapov wrote:
I'm worried about disabling irqs for non-device-assignment cases.
It would be more palatable if ioapic was completely O(1) (there are
some per-vcpu loops in there, shouldn't be too bad for 16 vcpus, but
we want to scale).
We can change it to
Gleb Natapov wrote:
On Mon, Oct 12, 2009 at 10:16:56AM +0200, Jan Kiszka wrote:
Apic is lockless. For ioapic/pic I used spinlocks initially, but Avi
prefers mutexes. Theoretically it is possible to make them lockless,
but code will be complex and eventually more slow, since more then two
Avi Kivity wrote:
On 10/12/2009 09:50 AM, Jan Kiszka wrote:
Apic is lockless. For ioapic/pic I used spinlocks initially, but Avi
prefers mutexes. Theoretically it is possible to make them lockless,
but code will be complex and eventually more slow, since more then two
atomic operation will be
On 10/12/2009 11:04 AM, Jan Kiszka wrote:
I'd rather remove dev-passthrough completely than continue adding hack upon hack
upon hack to make is some times kinda sorta work :)
Hmm, is this code not needed for the VT-d Co. case?
It is needed.
Or what is the
alternative?
irqfd
On Mon, Oct 12, 2009 at 11:04:23AM +0200, Jan Kiszka wrote:
Gleb Natapov wrote:
On Mon, Oct 12, 2009 at 10:16:56AM +0200, Jan Kiszka wrote:
Apic is lockless. For ioapic/pic I used spinlocks initially, but Avi
prefers mutexes. Theoretically it is possible to make them lockless,
but code
On 10/12/2009 11:07 AM, Jan Kiszka wrote:
I'm worried about disabling irqs for non-device-assignment cases. It
would be more palatable if ioapic was completely O(1) (there are some
per-vcpu loops in there, shouldn't be too bad for 16 vcpus, but we want
to scale).
Yeah, what a pity.
On 10/09/2009 08:03 PM, Glauber Costa wrote:
This series aims at cleanin up vcpu_context structure. I am not removing yet
the fd field, because it is used in the ioctls, and I want to do it separadedly.
But after this series, this structure exists only as a way to hold the file
descriptor,
and
Avi Kivity wrote:
On 10/12/2009 11:04 AM, Jan Kiszka wrote:
I'd rather remove dev-passthrough completely than continue adding
hack upon hack
upon hack to make is some times kinda sorta work :)
Hmm, is this code not needed for the VT-d Co. case?
It is needed.
Or what is the
On 10/09/2009 04:08 PM, Joerg Roedel wrote:
Hi Avi, Marcelo,
this series of patches contains bugfixes for the Nested SVM code and the
conversion of Nested SVM debugging to tracepoints. The fixes are:
1) A patch Alex already sent (1/9) but which was not yet
applied. It fixes
On 10/12/2009 11:25 AM, Jan Kiszka wrote:
Or what is the
alternative?
irqfd (which only supports edge-triggered interrupts now). Note irqfd
needs the same love, it uses a workqueue as well.
The theory is:
fd1 = eventfd()
give fd1 to kvm as irqfd, vhost-net as trigger fd
fd2 =
On 10/08/2009 06:46 PM, Alexander Graf wrote:
Am 08.10.2009 um 18:38 schrieb Avi Kivity a...@redhat.com:
On 10/08/2009 06:32 PM, Joerg Roedel wrote:
No. The L1 guest needs to execute VMRUN with an interrupt to inject to
the L2 guest with event_inj. On that VMRUN instruction emulation an
On 10/12/2009 11:38 AM, Gleb Natapov wrote:
irqfd can work from interrupt context, so if we only use the
workqueue for the many-vcpu cases, we should be fine.
I think we can do it cleanly, too: in ioapic code, if we're talking
to one vcpu, wake it immediately; otherwise schedule work to
On Mon, Oct 12, 2009 at 11:40:59AM +0200, Avi Kivity wrote:
On 10/12/2009 11:38 AM, Gleb Natapov wrote:
irqfd can work from interrupt context, so if we only use the
workqueue for the many-vcpu cases, we should be fine.
I think we can do it cleanly, too: in ioapic code, if we're talking
to
Instead of carrying pcbios as a subtree in kvm/bios/, switch to a
submodule in roms/pcbios/. The submodule contains all of the subtree
history and is merge-compatible with qemu.git's pcbios submodule.
Avi Kivity (2):
Switch roms/pcbios submodule to qemu-kvm branch
Drop kvm/bios/ tree
Signed-off-by: Avi Kivity a...@redhat.com
---
roms/pcbios |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/roms/pcbios b/roms/pcbios
index da5ff65..e5c3144 16
--- a/roms/pcbios
+++ b/roms/pcbios
@@ -1 +1 @@
-Subproject commit da5ff65dc9473e3f069736d38b9a189ea14a67eb
javier martinez canillas schrieb:
I got this compile warning with today linux-next:
arch/x86/kvm/mmu.c: In function ‘kvm_set_pte_rmapp’:
arch/x86/kvm/mmu.c:770: warning: cast to pointer from integer of different
size
arch/x86/kvm/mmu.c: In function ‘kvm_set_spte_hva’:
You're right, currently the sessions must be closed explicitly.
This is due to the fact that both qemu and ssh/telnet are handled by the
same code, and qemu has to keep running in the background if we want to
pass it from one test to another.
To deal with this, first, we should use try..finally
Juan Quintela wrote:
I notice that discussion is going nowhere, basically we are in the
state:
- people that want one device
* they emulate the same hardware
* lots of code is shared
* they should be interchageable
* if they are not interchageable, it is a bug
* once that they are
Avi Kivity wrote:
On 10/09/2009 09:49 PM, Anthony Liguori wrote:
If I've just been sent an image produced by someone running KVM, and
my machine is not KVM-capable, or I cannot upgrade the KVM kernel
module because it's in use by other VMs (had this problem a few
times), there's no choice but
Gleb Natapov wrote
BTW, I don't think it's write-protected and it probably should be?
AFAIR it is not writable on plain qemu.
KVM wants it to be writable for the TPR optimization. Historically, it
was read-only in QEMU but it changed to read-write in order to fake
coreboot into
We should fix qemu to re-read bios from flash.
Makes sense?
We have option_rom_setup_reset() already.
We don't, anymore :)
We are fast! Well, we surely have something similar instead.
Sure. Try 'info roms'. Everything listed there will be reloaded on
reset (unless mem=rom, in which case
On Mon, Oct 12, 2009 at 03:45:47PM +0200, Gerd Hoffmann wrote:
We should fix qemu to re-read bios from flash.
Makes sense?
We have option_rom_setup_reset() already.
We don't, anymore :)
We are fast! Well, we surely have something similar instead.
Sure. Try 'info roms'. Everything
Bugs item #2874699, was opened at 2009-10-08 08:18
Message generated for change (Settings changed) made by dondster
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=2874699group_id=180599
Please note that this message will contain a full copy of the comment
Bugs item #2874689, was opened at 2009-10-08 07:54
Message generated for change (Comment added) made by dondster
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=2874689group_id=180599
Please note that this message will contain a full copy of the comment
Anthony Liguori wrote:
We already have the single device model implementation and the
limitations are well known. The best way to move forward is for someone
to send out patches implementing separate device models.
At that point, it becomes a discussion of two concrete pieces of code
On Mon, Oct 12, 2009 at 08:44:56AM -0500, Anthony Liguori wrote:
Gleb Natapov wrote
BTW, I don't think it's write-protected and it probably should be?
AFAIR it is not writable on plain qemu.
KVM wants it to be writable for the TPR optimization. Historically,
I don't think so. TPR will
Gleb Natapov wrote:
On Mon, Oct 12, 2009 at 08:44:56AM -0500, Anthony Liguori wrote:
Gleb Natapov wrote
BTW, I don't think it's write-protected and it probably should be?
AFAIR it is not writable on plain qemu.
KVM wants it to be writable for the TPR optimization.
On Mon, Oct 12, 2009 at 11:59:29AM +0200, Michael S. Tsirkin wrote:
VGA adapters need to claim memory and i/o
transactions even if they do not have any
i/o or memory bars. E.g. PCI spec, page 297,
gives an example of such a device:
I've modified your patch slightly (to use new
On Mon, Oct 12, 2009 at 10:38:06AM -0400, Kevin O'Connor wrote:
On Mon, Oct 12, 2009 at 11:59:29AM +0200, Michael S. Tsirkin wrote:
VGA adapters need to claim memory and i/o
transactions even if they do not have any
i/o or memory bars. E.g. PCI spec, page 297,
gives an example of such a
On 10/12/09 15:53, Gleb Natapov wrote:
On Mon, Oct 12, 2009 at 03:45:47PM +0200, Gerd Hoffmann wrote:
We should fix qemu to re-read bios from flash.
Makes sense?
We have option_rom_setup_reset() already.
We don't, anymore :)
We are fast! Well, we surely have something similar instead.
On Mon, Oct 12, 2009 at 04:50:35PM +0200, Gerd Hoffmann wrote:
On 10/12/09 15:53, Gleb Natapov wrote:
On Mon, Oct 12, 2009 at 03:45:47PM +0200, Gerd Hoffmann wrote:
We should fix qemu to re-read bios from flash.
Makes sense?
We have option_rom_setup_reset() already.
We don't, anymore :)
Jamie Lokier wrote:
Anthony Liguori wrote:
We already have the single device model implementation and the
limitations are well known. The best way to move forward is for someone
to send out patches implementing separate device models.
At that point, it becomes a discussion of two
On Mon, Oct 12, 2009 at 08:44:56AM -0500, Anthony Liguori wrote:
Gleb Natapov wrote
BTW, I don't think it's write-protected and it probably should be?
AFAIR it is not writable on plain qemu.
KVM wants it to be writable for the TPR optimization. Historically, it
was read-only in
Gleb Natapov wrote:
But KVM doesn't support it (memory is always writable).
That seems like something which could be fixed.
-- Jamie
--
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
Hi Michael, I am reviewing your patchset and have just a minor remark
to make here:
On Wed, Oct 7, 2009 at 2:54 PM, Michael Goldish mgold...@redhat.com wrote:
This patch adds a new test that checks the timedrift introduced by migrations.
It uses the same parameters used by the timedrift test to
On 10/12/09 16:52, Gleb Natapov wrote:
On Mon, Oct 12, 2009 at 04:50:35PM +0200, Gerd Hoffmann wrote:
pc.c does some magic here to map the complete bios into high memory
and the legacy part at 0xe, thats why it is loaded in a
different way. It gets loaded to IO_MEM_ROM memory though, so the
- Lucas Meneghel Rodrigues l...@redhat.com wrote:
Hi Michael, I am reviewing your patchset and have just a minor remark
to make here:
On Wed, Oct 7, 2009 at 2:54 PM, Michael Goldish mgold...@redhat.com
wrote:
This patch adds a new test that checks the timedrift introduced by
On Mon, Oct 12, 2009 at 05:43:39PM +0200, Gerd Hoffmann wrote:
On 10/12/09 16:52, Gleb Natapov wrote:
On Mon, Oct 12, 2009 at 04:50:35PM +0200, Gerd Hoffmann wrote:
pc.c does some magic here to map the complete bios into high memory
and the legacy part at 0xe, thats why it is loaded in a
On Mon, Oct 12, 2009 at 11:07:28AM +0200, Jan Kiszka wrote:
Avi Kivity wrote:
On 10/12/2009 09:50 AM, Jan Kiszka wrote:
Apic is lockless. For ioapic/pic I used spinlocks initially, but Avi
prefers mutexes. Theoretically it is possible to make them lockless,
but code will be complex and
On Tue, Oct 06, 2009 at 01:24:50PM -0400, Glauber Costa wrote:
For a while now, we are issuing a rdmsr instruction to find out which msrs in
our
save list are really supported by the underlying machine. However, it fails
to account
for kvm-specific msrs, such as the pvclock ones.
This
On Sun, 2009-10-11 at 07:19 +0200, Avi Kivity wrote:
On 10/09/2009 10:04 PM, Andrew Theurer wrote:
This is on latest master branch on kvm.git and qemu-kvm.git, running
12 Windows Server2008 VMs, and using oprofile. I ran again without
oprofile and did not get the BUG. I am wondering if
On Fri, Oct 09, 2009 at 04:08:24PM +0200, Joerg Roedel wrote:
Hi Avi, Marcelo,
this series of patches contains bugfixes for the Nested SVM code and the
conversion of Nested SVM debugging to tracepoints. The fixes are:
1) A patch Alex already sent (1/9) but which was not yet
On Tue, Oct 06, 2009 at 02:25:02PM -0500, Mark Langsdorf wrote:
From 8ec340648103510095ff339b914706c81e9d815d Mon Sep 17 00:00:00 2001
From: Mark Langsdorf mark.langsd...@amd.com
Date: Wed, 9 Sep 2009 22:12:51 -0500
Subject: [PATCH] [PATCH] Support Pause Filter in AMD processors
New AMD
On Fri, Oct 09, 2009 at 04:26:08PM -1000, Zachary Amsden wrote:
If cpufreq can't determine the CPU khz, or cpufreq is not compiled in,
we should fallback to the measured TSC khz.
Signed-off-by: Zachary Amsden zams...@redhat.com
Applied, thanks.
--
To unsubscribe from this list: send the
Marcelo Tosatti wrote:
On Mon, Oct 12, 2009 at 11:07:28AM +0200, Jan Kiszka wrote:
Avi Kivity wrote:
On 10/12/2009 09:50 AM, Jan Kiszka wrote:
Apic is lockless. For ioapic/pic I used spinlocks initially, but Avi
prefers mutexes. Theoretically it is possible to make them lockless,
but code
Hello!
I just tested qemu-kvm-0.11.0 with the KVM module of kernel 2.6.31.1. I
noticed that the I/O performance of an unattended stock Debian Lenny
install dropped somehow. The test machines ran with kvm-88 and 2.6.30.x
before. The difference is very noticeable (went from about 5 minutes up
to
René Pfeiffer wrote:
Hello!
I just tested qemu-kvm-0.11.0 with the KVM module of kernel 2.6.31.1. I
noticed that the I/O performance of an unattended stock Debian Lenny
install dropped somehow. The test machines ran with kvm-88 and 2.6.30.x
before. The difference is very noticeable (went from
On Oct 13, 2009 at 0145 +0400, Michael Tokarev appeared and said:
René Pfeiffer wrote:
Hello!
I just tested qemu-kvm-0.11.0 with the KVM module of kernel 2.6.31.1. I
noticed that the I/O performance of an unattended stock Debian Lenny
install dropped somehow. The test machines ran with
The recent change to QemuOpts for the -net nic option breaks specifying -net
nic,... more than once. The net_init_nic function's return value in net.c is
a table index, which is non-zero after the first time it is called. The
qemu_opts_foreach function in qemu-option.c receives the non-zero
On Mon, Oct 12, 2009 at 10:54:54AM +0200, Jan Kiszka wrote:
The following changes since commit e19bf3254985d9b8b6b916acc82fc398595cff95:
Jan Kiszka (1):
x86: Remove zombie kvm_trace from build
are available in the git repository at:
git://git.kiszka.org/kvm-kmod.git queue
On Mon, Oct 12, 2009 at 09:07:45AM -0400, Michael Goldish wrote:
You're right, currently the sessions must be closed explicitly.
This is due to the fact that both qemu and ssh/telnet are handled by the
same code, and qemu has to keep running in the background if we want to
pass it from one
Since os.rename requires that the file is in the same partition with
the dest directory, we would get a python OSError if the result
directory is mounted to a nfs server (or different partition or
something else alike).
the traceback would be like:
Traceback (most recent call last):
File
71 matches
Mail list logo
