From: Avi Kivity a...@redhat.com
Unneeded.
Signed-off-by: Avi Kivity a...@redhat.com
diff --git a/hw/e1000.c b/hw/e1000.c
index 1de133b..b0fe917 100644
--- a/hw/e1000.c
+++ b/hw/e1000.c
@@ -26,7 +26,6 @@
#include hw.h
#include pci.h
#include net.h
-#include qemu-kvm.h
#include e1000_hw.h
From: Avi Kivity a...@redhat.com
Too many to list independently.
Signed-off-by: Avi Kivity a...@redhat.com
diff --git a/Makefile.target b/Makefile.target
index d890220..f90b714 100644
--- a/Makefile.target
+++ b/Makefile.target
@@ -134,8 +134,7 @@ endif
kvm.o: CFLAGS+=$(KVM_CFLAGS)
kvm-all.o:
Cam Macdonell wrote:
Configure spits out an error about include/asm not existing. I think
that make sync has to be run before configure to create the include
directory and copy asm-x86 inside so that ln -sf asm-$karch
include/asm will work.
I changed configure to create include/ if it
Michael S. Tsirkin wrote:
That saves us the new API (at the expense of a lot more code, but with
added flexibility).
So we'll probably need to rename request_vqs to request_vectors,
but we probably still need the driver to pass the number of
vectors it wants to the transport. Right?
David S. Ahern wrote:
Anthony Liguori wrote:
Jan Kiszka wrote:
Anthony Liguori wrote:
Marcelo Tosatti wrote:
Jan,
While the patch itself looks fine, IMO it would be better to move all
of the timer handling to userspace, except the performance critical
parts,
Ack all. This also solved one bug by my hand. Thanks!
I observe one point: the performance of high workload interrupt(e.g. 10
gigabyte oplin card) dropped dramatically with smp_send_reschedule() method...
In one environment(the speed of oplin card also limited by cpu performance),
Using
Cornelius Wefelscheid wrote:
Hi,
i have the following problem:
I got a amd opteron server with 32 (4*8) cpus.
Since kvm is only able to created a virtual machine with 16 cpus, i
changed KVM_MAX_VCPUS, MAX_VCPUS and MAX_CPUS
as suggested in
A recent merge broke tap networking because qemu_send_packet()
now always returns -EAGAIN causing tap to try and resend the
same packet forever.
Fix by having qemu_send_packet() return the status from the
qemu_deliver_packet() of the packet in question, rather than
any packets which happened to
Mark McLoughlin wrote:
A recent merge broke tap networking because qemu_send_packet()
now always returns -EAGAIN causing tap to try and resend the
same packet forever.
Fix by having qemu_send_packet() return the status from the
qemu_deliver_packet() of the packet in question, rather than
any
From 5858c329a426dc1450bad038e7506b17faa4910c Mon Sep 17 00:00:00 2001
From: Michael S. Tsirkin m...@redhat.com
Date: Tue, 28 Apr 2009 12:07:35 +0300
Subject: [PATCH] kvm-kmod: create include directory
include directory is not in git, so configure must create it before
creating include/asm link
Mark McLoughlin wrote:
Include qemu-kvm.h for non-KVM_UPSTREAM building and surround the
kvm code with USE_KVM guards.
Fixes target-arm:
qemu/hw/framebuffer.c: In function 'framebuffer_update_display':
qemu/hw/framebuffer.c:53: warning: implicit declaration of function
'kvm_enabled'
Zhang, Xiantao wrote:
From d184d9b0a91ca674961000ed3d35b7fc25d29e03 Mon Sep 17 00:00:00 2001
From: Xiantao Zhang xiantao.zh...@intel.com
Date: Tue, 28 Apr 2009 16:59:36 +0800
Subject: [PATCH] qemu-kvm: other archs should maintain memory mapping also.
Currently, use TARGET_I386 to comment out
Gregory Haskins wrote:
Sure, the interface remains the same (write 8 bytes), but the
implementation can change. For example, we can implement it to work
from interrupt context, once we hack the locking appropriately.
I was thinking more along the lines of eventfd_signal(). AIO and
Attached.
-Original Message-
From: Avi Kivity [mailto:a...@redhat.com]
Sent: Tuesday, April 28, 2009 5:40 PM
To: Zhang, Xiantao
Cc: kvm-i...@vger.kernel.org; kvm@vger.kernel.org
Subject: Re: [PATCH 00/04] Enable qemu-kvm for ia64.
Zhang, Xiantao wrote:
Patches for enabing qemu-kvm
Joerg Roedel wrote:
If userspace knows that the kernel part supports 1GB pages it can enable
the corresponding cpuid bit so that guests actually use GB pages.
Why not do everything via KVM_GET_SUPPORTED_CPUID2 and virtualized
cpuid? We can enable it in the kernel unconditionally.
--
Do
On Tue, 2009-04-28 at 11:58 +0300, Avi Kivity wrote:
Mark McLoughlin wrote:
A recent merge broke tap networking because qemu_send_packet()
now always returns -EAGAIN causing tap to try and resend the
same packet forever.
Fix by having qemu_send_packet() return the status from the
Joerg Roedel wrote:
Hi,
this is the second version of the patches implementing support for 1GB
pages in KVM. There are too many changes to the first version to mention
them all here. The core support was rewritten to work with mapping
levels instead of page sizes. This was the main part of the
Hi Marcello,
On Mon, Apr 27, 2009 at 02:12:45PM -0300, Marcelo Tosatti wrote:
On Fri, Apr 24, 2009 at 01:58:43PM +0200, Joerg Roedel wrote:
With the new name and the corresponding backend changes this function
can now support multiple hugepage sizes.
Signed-off-by: Joerg Roedel
On Mon, Apr 27, 2009 at 03:32:29PM +0300, Avi Kivity wrote:
This is a small git repository for the kvm external module kit.
So, I am building on a host with CONFIG_KVM_TRACE set in its
kernel, but I run configure without enabling kvm trace.
As a result the module fails to link:
WARNING:
Michael S. Tsirkin wrote:
On Mon, Apr 27, 2009 at 03:32:29PM +0300, Avi Kivity wrote:
This is a small git repository for the kvm external module kit.
So, I am building on a host with CONFIG_KVM_TRACE set in its
kernel, but I run configure without enabling kvm trace.
As a result the
AMDs VMCB does not have an explicit unusable segment descriptor field,
so we emulate it by using not present. This has to be setup before
the fixups, because this field is used there.
Signed-off-by: Andre Przywara andre.przyw...@amd.com
---
arch/x86/kvm/svm.c |7 +--
1 files changed, 5
include directory is not in git, so configure must create it before
creating include/asm link
Signed-off-by: Michael S. Tsirkin m...@redhat.com
---
resending with a sane subject, sorry about multiple messages.
configure |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git
From 98c3d2efeddae9e050455ae06f5214ba2bdc4ec3 Mon Sep 17 00:00:00 2001
From: Xiantao Zhang xiantao.zh...@intel.com
Date: Tue, 28 Apr 2009 15:03:05 +0800
Subject: [PATCH] qemu-kvm: Set default configure option for ia64
1.Disable xen config support for ia64.
2.Only configure ia64-softmmu for ia64.
Michael S. Tsirkin wrote:
Or maybe, add a s/CONFIG_KVM_TRACE/CONFIG_KMOD_KVM_TRACE/ to make the
two options independent.
You decide.
Well, I think it's less confusing.
I also wonder what happens if one tries to build on
a machine with kvm built into kernel. Ideally one would get
a
On Tue, Apr 28, 2009 at 01:53:26PM +0300, Avi Kivity wrote:
Michael S. Tsirkin wrote:
Or maybe, add a s/CONFIG_KVM_TRACE/CONFIG_KMOD_KVM_TRACE/ to make the
two options independent.
You decide.
Well, I think it's less confusing.
Fine. Patch?
--
MST
--
To unsubscribe from this
Gregory Haskins wrote:
But eventfd_signal basically marries us to eventfd.
Well, only if we expect the fd to have eventfd semantics. There are
advantages to doing so, as we have discussed, because things like AIO
can polymorhpically signal an interrupt without even knowing whats
Michael S. Tsirkin wrote:
On Tue, Apr 28, 2009 at 01:53:26PM +0300, Avi Kivity wrote:
Michael S. Tsirkin wrote:
Or maybe, add a s/CONFIG_KVM_TRACE/CONFIG_KMOD_KVM_TRACE/ to make the
two options independent.
You decide.
Well, I think it's less confusing.
Avi Kivity wrote:
Gregory Haskins wrote:
But eventfd_signal basically marries us to eventfd.
Well, only if we expect the fd to have eventfd semantics. There are
advantages to doing so, as we have discussed, because things like AIO
can polymorhpically signal an interrupt without
Zhang, Xiantao wrote:
qemu_get_ram_ptr() returns a pointer. Don't cast it to a ram_addr_t,
leave it a pointer.
But why not use cpu_physical_memory_write() (or
cpu_physical_memory_write_rom())? It's much simpler and cleaner.
Good suggestion! I just followed the original logic. Updated
Avi Kivity wrote:
So what is your proposal for such interface?
-write().
Alternatively, a new fileop -signal_event(), which would map to
eventfd_signal() or irqfd_signal(). This would be defined to work in
irq contexts. It may also be useful for uio interrupts.
--
Do not meddle
Michael S. Tsirkin wrote:
include directory is not in git, so configure must create it before
creating include/asm link
This is already in, 24877cbe.
--
Do not meddle in the internals of kernels, for they are subtle and quick to
panic.
--
To unsubscribe from this list: send the line
Patches for enabing qemu-kvm for ia64.
[PATCH 01/04] qemu-kvm: Set default configure option for ia64.
[PATCH 02/04] qemu-kvm: Add header files for ia64.
[PATCH 03/04] qemu-kvm: Remove the dependency for phys_ram_base for ipf.c
[PATCH 04/04] qemu-kvm: other archs should maintain memory mapping
Sheng Yang wrote:
msix_table_page is a page, and mmap allocate memory on page boundary. So
I use it.
Just wondering, would e.g. posix_memalign work here as well?
Um, I think it should work too.
I think qemu_malloc() would work just as well. The hardware never sees
the page,
Avi Kivity wrote:
Zhang, Xiantao wrote:
From aaf97331da3d6cd34522441218c8c9ab3c1067f6 Mon Sep 17 00:00:00
2001
From: Xiantao Zhang xiantao.zh...@intel.com
Date: Tue, 28 Apr 2009 16:55:47 +0800
Subject: [PATCH] qemu-kvm: Remove the dependency for phys_ram_base
for ipf.c
Upstream has
Avi Kivity wrote:
Avi Kivity wrote:
So what is your proposal for such interface?
-write().
Alternatively, a new fileop -signal_event(), which would map to
eventfd_signal() or irqfd_signal(). This would be defined to work in
irq contexts. It may also be useful for uio interrupts.
On 27/04/09 at 19:40 -0400, john cooper wrote:
Lucas Nussbaum wrote:
On 27/04/09 at 13:36 -0400, john cooper wrote:
Lucas Nussbaum wrote:
non-virtio:
kvm -drive file=/tmp/debian-amd64.img,if=scsi,cache=writethrough -net
nic,macaddr=00:16:3e:5a:28:1,model=e1000 -net tap -nographic -kernel
Gregory Haskins wrote:
Avi Kivity wrote:
Avi Kivity wrote:
So what is your proposal for such interface?
-write().
Alternatively, a new fileop -signal_event(), which would map to
eventfd_signal() or irqfd_signal(). This would be defined to work in
irq contexts.
On 28/04/09 at 12:56 +0200, Lucas Nussbaum wrote:
I then upgraded to kvm-85 (both the host kernel modules and the
userspace), and re-ran the tests. Performance is better (about 85 MB/s),
but still very far from the non-virtio case.
I forgot to mention that the strangest result I got was the
Hi Avi - Probably you can answer this question?
Thx,
Venkat
-Original Message-
From: kvm-ow...@vger.kernel.org [mailto:kvm-ow...@vger.kernel.org] On Behalf Of
Kumar, Venkat
Sent: Tuesday, April 28, 2009 4:16 PM
To: kvm@vger.kernel.org
Subject: Notification from Qemu to Guest
I have
Lucas Nussbaum wrote:
On 28/04/09 at 12:56 +0200, Lucas Nussbaum wrote:
I then upgraded to kvm-85 (both the host kernel modules and the
userspace), and re-ran the tests. Performance is better (about 85 MB/s),
but still very far from the non-virtio case.
I forgot to mention that the
Kumar, Venkat wrote:
Hi Avi - Probably you can answer this question?
I'm no virtio expert; copying someone who is.
I have emulated a PCI device on Qemu and hooked my sample/simple driver to that
virtio device on the guest.
I am testing the notification from Guest-Qemu and vice-versa.
On Mon, Apr 27, 2009 at 12:15:31PM +0300, Avi Kivity wrote:
I think that's worthwhile. The extra bloat is trivial (especially as
the number of inflight virtio requests is tightly bounded), and stalling
the vcpu for requests is a pain.
Ok, new patch will follow ASAP.
--
To unsubscribe from
CONFIG_KVM_TRACE in kernel conflicts with the definition
in external module. external-module-compat-comm.h tried
to work around this, but this didn't work as some
code still does #include linux/autoconf.h
directly.
Solve this differently by s/CONFIG_KVM_TRACE/CONFIG_KMOD_KVM_TRACE/
in awk. Had to
Zhang, Xiantao wrote:
Patches for enabing qemu-kvm for ia64.
[PATCH 01/04] qemu-kvm: Set default configure option for ia64.
[PATCH 02/04] qemu-kvm: Add header files for ia64.
[PATCH 03/04] qemu-kvm: Remove the dependency for phys_ram_base for ipf.c
[PATCH 04/04] qemu-kvm: other archs should
Zhang, Xiantao wrote:
Patches for enabing qemu-kvm for ia64.
[PATCH 01/04] qemu-kvm: Set default configure option for ia64.
[PATCH 02/04] qemu-kvm: Add header files for ia64.
Applied 1 and 2.
--
Do not meddle in the internals of kernels, for they are subtle and quick to
panic.
--
To
On Tue, Apr 28, 2009 at 01:24:44PM +0300, Avi Kivity wrote:
Michael S. Tsirkin wrote:
On Mon, Apr 27, 2009 at 03:32:29PM +0300, Avi Kivity wrote:
This is a small git repository for the kvm external module kit.
So, I am building on a host with CONFIG_KVM_TRACE set in its
kernel, but
Avi Kivity wrote:
Gregory Haskins wrote:
Sure, the interface remains the same (write 8 bytes), but the
implementation can change. For example, we can implement it to work
from interrupt context, once we hack the locking appropriately.
I was thinking more along the lines of
From aaf97331da3d6cd34522441218c8c9ab3c1067f6 Mon Sep 17 00:00:00 2001
From: Xiantao Zhang xiantao.zh...@intel.com
Date: Tue, 28 Apr 2009 16:55:47 +0800
Subject: [PATCH] qemu-kvm: Remove the dependency for phys_ram_base for ipf.c
Upstream has dropped phys_ram_base, so ia64 also remove
the
I have emulated a PCI device on Qemu and hooked my sample/simple driver to that
virtio device on the guest.
I am testing the notification from Guest-Qemu and vice-versa.
I am able to notify from Guest to Qemu but Qemu-Guest notification is not
happening.
As a part of Kick routine in my guest
From d184d9b0a91ca674961000ed3d35b7fc25d29e03 Mon Sep 17 00:00:00 2001
From: Xiantao Zhang xiantao.zh...@intel.com
Date: Tue, 28 Apr 2009 16:59:36 +0800
Subject: [PATCH] qemu-kvm: other archs should maintain memory mapping also.
Currently, use TARGET_I386 to comment out the mapping machanism
for
Avi Kivity wrote:
Gregory Haskins wrote:
Avi Kivity wrote:
Avi Kivity wrote:
So what is your proposal for such interface?
-write().
Alternatively, a new fileop -signal_event(), which would map to
eventfd_signal() or irqfd_signal(). This would be defined to
Add support for SG_IO passthru (packet commands) to the virtio-blk
backend. Conceptually based on an older patch from Hannes Reinecke
but largely rewritten to match the code structure and layering in
virtio-blk aswell as doing asynchronous I/O.
Signed-off-by: Christoph Hellwig h...@lst.de
Jes Sorensen wrote:
Avi == Avi Kivity a...@redhat.com writes:
Avi Zhang, Xiantao wrote:
qemu_get_ram_ptr() returns a pointer. Don't cast it to a
ram_addr_t, leave it a pointer.
But why not use cpu_physical_memory_write() (or
cpu_physical_memory_write_rom())? It's much
Zhang, Xiantao wrote:
From aaf97331da3d6cd34522441218c8c9ab3c1067f6 Mon Sep 17 00:00:00 2001
From: Xiantao Zhang xiantao.zh...@intel.com
Date: Tue, 28 Apr 2009 16:55:47 +0800
Subject: [PATCH] qemu-kvm: Remove the dependency for phys_ram_base for ipf.c
Upstream has dropped phys_ram_base, so
On Mon, Apr 27, 2009 at 09:36:51AM -0500, Anthony Liguori wrote:
So practically speaking, what can you do with this?
It's interesting if your underlying device is a real scsi disk and you
want virtio for efficiency but also allow to issue scsi commands on
the underlying device, e.g. for finding
Avi == Avi Kivity a...@redhat.com writes:
Avi Zhang, Xiantao wrote:
qemu_get_ram_ptr() returns a pointer. Don't cast it to a
ram_addr_t, leave it a pointer.
But why not use cpu_physical_memory_write() (or
cpu_physical_memory_write_rom())? It's much simpler and cleaner.
Good
Marc Bevand wrote:
Arnd Bergmann arnd at arndb.de writes:
http://en.wikipedia.org/wiki/List_of_Intel_Core_2_microprocessors is quite
good here. As a rule of thumb, anything higher than 6000 will have VT,
anything below 6000 will not. Interesting exceptions are
Doesn't have VT: E7300, Q8200,
Hello Andrea,
I have applied the patch to kvm and userland, but, when I tried to port the
host kernel patch I noticed that the changes were over the file e820.c.
However, on kernel 2.6.26 there are two e820 files, e820_32.c and e820_64.c and
most of the changes maps on the e820_64.c file. So,
I'm trying to clone this new repository using the http protocol because I'm
behind a proxy. I get the following error. For kvm.git and qemu-kvm.git this
works well.
$ git clone http://www.kernel.org/pub/scm/virt/kvm/kvm-kmod.git
Initialized empty Git repository in /home/bernd/src/kvm-kmod/.git/
On Tuesday 28 April 2009, Marc Bevand wrote:
As a rule of thumb, anything higher than 6000 will have VT,
anything below 6000 will not. Interesting exceptions are
Doesn't have VT: E7300, Q8200, Q8400, E8190
Does have VT: T5600, U2xxx, SU3xxx, Celeron 900 (?)
May have VT[1]: T5500,
we currently unblock shadow interrupt state when we skip an instruction,
but failing to do so when we actually emulate one. This blocks interrupts
in key instruction blocks, in particular sti; hlt; sequences
If the instruction emulated is an sti, we have to block shadow interrupts.
The same goes
On 28/04/09 at 14:55 +0300, Avi Kivity wrote:
Lucas Nussbaum wrote:
On 28/04/09 at 12:56 +0200, Lucas Nussbaum wrote:
I then upgraded to kvm-85 (both the host kernel modules and the
userspace), and re-ran the tests. Performance is better (about 85 MB/s),
but still very far from the
On Mon, Apr 27, 2009 at 2:56 PM, Avi Kivity a...@redhat.com wrote:
Pantelis Koukousoulas wrote:
Or maybe
modprobe virtio-pci claim=0x10f2 claim=0x10f7
How about claim=0x10f2,0x10f7 instead so that it can be implemented as
a standard module array parameter?
Even better.
Ok, since a
Avi Kivity wrote:
Jes Sorensen wrote:
Hi,
I am not crazy about this patch. You need to use cpy_physical_memory_rw()
in the hob and nvram code too, not just in the ipf.c code.
What about the flush_icache_range() call you removed - is it safe to
just discard that?
I was in the process of
On Tue, Apr 28, 2009 at 6:07 AM, Avi Kivity a...@redhat.com wrote:
Marc Bevand wrote:
This is very wrong:
- none of the Pentium, Celeron, Atom processors, even the latest ones,
come with VT
According to processorfinder, 3 out of the 8 Atoms come with VT. Some
Pentium Ds also do. Maybe
Avi Kivity wrote:
I have emulated a PCI device on Qemu and hooked my sample/simple
driver to that virtio device on the guest.
This is independent of the existing virtio PCI device?
As a part of Kick routine in my guest driver I could see the
notification happening from Guest-Qemu and In the
Hi,
Ok, since a day has passed with no further comments, I 'll dare to
assume everyone is happy with this solution. So, here is an
implementation. I 've tested locally with my driver that uses 0x10f5
and it seems to work.
Patch looks fine to me.
cheers,
Gerd
--
To unsubscribe from this
The irq handler changes (introduced in 2.6.19, not 2.6.20) dropped
struct pt_regs from the handler prototype, they are found globally now.
This introduces the back compat for older kernels. The handler is just
a thin layer which calls the real registered handler (all this to work
around a minor
Christoph Hellwig wrote:
Should we be
handling some SCSI cmds internally to QEMU (like eject operations) and
supporting media=cdrom in -drive for if=virtio?
Not quite yet. Eventually I want to support a virtio-scsi kind of
transport which would use the same virtio-blk protocol but only
I came across this thread looking for an efficient event channel mechanism
between two guests (running on different cpu cores).
While I can use available emulated IO mechanism (guest1-host kernel
driver-Qemu1-Qemu2) in conjunction with interrupt mechanism (Qemu2-host
kernel driver-guest2) in
Am Tuesday 28 April 2009 18:37:01 schrieb Anthony Liguori:
Christoph Hellwig wrote:
Should we be
handling some SCSI cmds internally to QEMU (like eject operations) and
supporting media=cdrom in -drive for if=virtio?
Not quite yet. Eventually I want to support a virtio-scsi
Kapadia, Vivek wrote:
I came across this thread looking for an efficient event channel mechanism
between two guests (running on different cpu cores).
While I can use available emulated IO mechanism (guest1-host kernel
driver-Qemu1-Qemu2) in conjunction with interrupt mechanism (Qemu2-host
Hi Anthony - My questions and Comments are in line.
Thx,
Venkat
-Original Message-
From: Anthony Liguori [mailto:anth...@codemonkey.ws]
Sent: Tuesday, April 28, 2009 8:41 PM
To: Avi Kivity
Cc: Kumar, Venkat; kvm@vger.kernel.org
Subject: Re: FW: Notification from Qemu to Guest
Avi
On Tue, Apr 28, 2009 at 09:47:14AM +0300, Avi Kivity wrote:
Michael S. Tsirkin wrote:
That saves us the new API (at the expense of a lot more code, but
with added flexibility).
So we'll probably need to rename request_vqs to request_vectors,
but we probably still need the driver to
Michael S. Tsirkin wrote:
This does not work for MSIX - in linux, you must map all MSI-X entries
to interrupt vectors upfront.
What? that's very inflexible.
Can you point me at the code?
So what I see is transports providing something like:
struct virtio_interrupt_mapping {
int
On Tue, Apr 28, 2009 at 07:35:26AM -0600, Passera, Pablo R wrote:
- Against which kernel version was this patch generated?
I don't remember exactly (I was just using an upstream hg checkout and
I didn't record its hash value) but I think you can go back to when
e820.c was still shared and it'll
On Tue, Apr 28, 2009 at 08:51:08PM +0300, Avi Kivity wrote:
Michael S. Tsirkin wrote:
This does not work for MSIX - in linux, you must map all MSI-X entries
to interrupt vectors upfront.
What? that's very inflexible.
Can you point me at the code?
See pci_enable_msix in
Hi
Still getting (some but less) network issues with a 2.6.28.9 host.
Found quite a few of these call traces in the 2.6.29.1 guests:
Guest has 512MB of memory and was not all that busy (just network
traffic), so I don't understand why it would fail to allocate a page...
[701453.834571]
Am Tuesday 28 April 2009 11:51:54 schrieb Christoph Hellwig:
Not quite yet. Eventually I want to support a virtio-scsi kind of
transport which would use the same virtio-blk protocol but only send
scsi commands. We'd need a different driver on the Linux side for
it that registers to the scsi
Michael S. Tsirkin wrote:
So to map vq 0 to vector 0, vq 1 to vector 1 and vq 2 to vector 2 the driver
would do:
struct virtio_interrupt_mapping mapping[3] = { {0, 0}, {1, 1}, {2, 2} };
vec = map_vqs_to_interrupt(dev, mapping, 3);
if (vec) {
error handling
}
and then find_vq as usual.
On Tue, Apr 28, 2009 at 02:56:15PM -0500, Anthony Liguori wrote:
Michael S. Tsirkin wrote:
So to map vq 0 to vector 0, vq 1 to vector 1 and vq 2 to vector 2 the driver
would do:
struct virtio_interrupt_mapping mapping[3] = { {0, 0}, {1, 1}, {2, 2} };
vec = map_vqs_to_interrupt(dev, mapping,
looking for comments/feedback
These relatively simple changes to kvm_runtest_2 will allow for the addition of
new tests without having modifying kvm_runtest code.
One would just add a newtest.py file and update the config file. This will
simplify test development and make it easier to
This will allow for adding of additional tests with out modifying the code.
One would just add the testname.py file to the test_dir and edit the comfig
file.
---
client/tests/kvm_runtest_2/kvm_runtest_2.py | 32 +++---
1 files changed, 23 insertions(+), 9 deletions(-)
---
client/tests/kvm_runtest_2/kvm_tests.py | 396 ---
1 files changed, 0 insertions(+), 396 deletions(-)
delete mode 100644 client/tests/kvm_runtest_2/kvm_tests.py
diff --git a/client/tests/kvm_runtest_2/kvm_tests.py
b/client/tests/kvm_runtest_2/kvm_tests.py
autotest.py, boot.py, linux_s3.py, migration.py, yum_update.py
---
client/tests/kvm_runtest_2/kvm_tests/autotest.py | 145
client/tests/kvm_runtest_2/kvm_tests/boot.py | 45 ++
client/tests/kvm_runtest_2/kvm_tests/linux_s3.py | 53 +++
Hollis Blanchard wrote:
On Thu, 2009-04-23 at 18:40 +0300, Avi Kivity wrote:
Still missing:
- I have not tested powerpc or ia64. Patches welcome!
This repository seems pretty messed up; I'm not even sure what you want
from me.
Since PPC is now supported in upstream QEMU, does it
On Tue, Apr 28, 2009 at 7:20 PM, Anthony Liguori anth...@codemonkey.ws wrote:
Hollis Blanchard wrote:
On Thu, 2009-04-23 at 18:40 +0300, Avi Kivity wrote:
Still missing:
- I have not tested powerpc or ia64. Patches welcome!
This repository seems pretty messed up; I'm not even sure what
Glauber Costa wrote:
Yes. There are people (me) who still rely on building everything from
the same source.
It can only be done by the superset (qemu-kvm.git)
Fedora doesn't package a KVM enabled qemu-system-ppcemb, do they?
Regards,
Anthony Liguori
--
To unsubscribe from this list:
On Tue, 2009-04-28 at 17:20 -0500, Anthony Liguori wrote:
Hollis Blanchard wrote:
On Thu, 2009-04-23 at 18:40 +0300, Avi Kivity wrote:
Still missing:
- I have not tested powerpc or ia64. Patches welcome!
This repository seems pretty messed up; I'm not even sure what you
On Tue, 2009-04-28 at 17:28 -0500, Anthony Liguori wrote:
Glauber Costa wrote:
Yes. There are people (me) who still rely on building everything from
the same source.
It can only be done by the superset (qemu-kvm.git)
Fedora doesn't package a KVM enabled qemu-system-ppcemb, do they?
Jes Sorensen wrote:
Avi == Avi Kivity a...@redhat.com writes:
Avi Zhang, Xiantao wrote:
qemu_get_ram_ptr() returns a pointer. Don't cast it to a
ram_addr_t, leave it a pointer.
But why not use cpu_physical_memory_write() (or
cpu_physical_memory_write_rom())? It's much simpler and
Avi Kivity wrote:
Jes Sorensen wrote:
Avi == Avi Kivity a...@redhat.com writes:
Avi Zhang, Xiantao wrote:
qemu_get_ram_ptr() returns a pointer. Don't cast it to a
ram_addr_t, leave it a pointer.
But why not use cpu_physical_memory_write() (or
cpu_physical_memory_write_rom())?
Intel TXT(Trusted Execution Technology) required VMX off for all cpu to work
when system shutdown.
CC: Joseph Cihula joseph.cih...@intel.com
Signed-off-by: Sheng Yang sh...@linux.intel.com
---
virt/kvm/kvm_main.c | 18 +-
1 files changed, 9 insertions(+), 9 deletions(-)
diff
On Tuesday, April 28, 2009 7:11 AM kvm-ow...@vger.kernel.org wrote:
Cam Macdonell wrote:
Hi,
I've tried booting two VMs (Ubuntu and Fedora 11) that previously
worked with the latest kvm-userspace. At start, I get the following
warning:
Could not open '/dev/kqemu' - QEMU acceleration
Anthony Liguori anthony at codemonkey.ws writes:
Kapadia, Vivek wrote:
I came across this thread looking for an efficient event channel
mechanism between two guests (running on different cpu cores).
While I can use available emulated IO mechanism (guest1-host kernel
Hi guys,
As you know kvmppc uses shadow_ref to record connections between gtlbes and
pages.
44x implement it as kvmppc_44x_shadow_ref, and e500 implement it as
kvmppc_e500_shadow_ref in recent patches.
The problem for e500 now is that, the shadow_ref for TLB0 doesn't reflect the
hardware
On Thu, 2009-04-23 at 18:40 +0300, Avi Kivity wrote:
Still missing:
- I have not tested powerpc or ia64. Patches welcome!
This repository seems pretty messed up; I'm not even sure what you want
from me. Some of the bigger problems:
* configure completely ignores --kerneldir and only
Hollis Blanchard wrote:
On Thu, 2009-04-23 at 18:40 +0300, Avi Kivity wrote:
Still missing:
- I have not tested powerpc or ia64. Patches welcome!
This repository seems pretty messed up; I'm not even sure what you want
from me.
Since PPC is now supported in upstream QEMU, does it
On Tue, Apr 28, 2009 at 7:20 PM, Anthony Liguori anth...@codemonkey.ws wrote:
Hollis Blanchard wrote:
On Thu, 2009-04-23 at 18:40 +0300, Avi Kivity wrote:
Still missing:
- I have not tested powerpc or ia64. Patches welcome!
This repository seems pretty messed up; I'm not even sure what
Glauber Costa wrote:
Yes. There are people (me) who still rely on building everything from
the same source.
It can only be done by the superset (qemu-kvm.git)
Fedora doesn't package a KVM enabled qemu-system-ppcemb, do they?
Regards,
Anthony Liguori
--
To unsubscribe from this list:
1 - 100 of 103 matches
Mail list logo
