Ni hao,
+---+
Warning! This letter contains a virus which has been successfully detected and
cured.
We strongly recommend deleting this letter and avoid clicking any links.
+---+
[RBN Networks Antivirus]
david ahern wrote:
Attaching gdb to qemu you work with addresses as seen by the qemu process; the
idea is to work with addresses as seen inside the guest.
For example, in the qemu console you can examine guest kernel memory such as
task structs using guest kernel based addresses:
(qemu) x
Marcelo Tosatti wrote:
On Mon, Mar 17, 2008 at 04:41:18PM +0200, Avi Kivity wrote:
Marcelo Tosatti wrote:
While aging is not too hard to do, I don't think it would add much in
practice; we rarely observe mmu shadow pages being recycled due to
memory pressure. So this is mostly
Marcelo Tosatti wrote:
Otherwise the guest will miscalculate the region size.
Applied all, thanks.
--
Do not meddle in the internals of kernels, for they are subtle and quick to
panic.
-
This SF.net email is
Glauber Costa wrote:
As Marcelo pointed out, we need slots_lock to protect
against slots changing under our nose during wall clock
writing.
This patch address this issue.
Applied, thanks.
This lock is fairly annoying. What do you think about taking it in
vcpu_run unconditionally and
Glauber Costa wrote:
Avi,
This series now apply ontop of kvm.git.
Only the needed function from machine_ops is made non-static.
Applied, thanks.
Ingo, can you carry the first two patches as well? They are
602ac559a208ba44d5879a8e6381a379b376a8b7 and
Christian Borntraeger wrote:
include/linux/kvm.h defines struct kvm_dirty_log to
[...]
union {
void __user *dirty_bitmap; /* one bit per page */
__u64 padding;
};
__user requires compiler.h to compile. Currently, this works on x86
only
Trying to merge qemu-cvs, there's a conflict in vmwarevga between two
changes that appear to be identical in purpose, only implemented
differently: 6d262b07a2046ed1fa0ec3fd61f00efbfcd5a9ef (master) and
5aa90452c52e3a914e1f6bbf34331507fd7c5d52 (qemu-cvs).
I think the correct action is to drop
Avi Kivity wrote:
Glauber Costa wrote:
Avi,
This series now apply ontop of kvm.git.
Only the needed function from machine_ops is made non-static.
Applied, thanks.
Er, compilation breaks if CONFIG_KEXEC is not set (i386).
--
Do not meddle in the internals of kernels, for they are
Avi Kivity wrote:
Yunfeng Zhao wrote:
Hi All,
This is today's KVM test result against kvm.git
a16664b59065b8ae877b213e68a6f962ac359ca4 and kvm-userspace.git
3017d054a6a9f37bfffee4ebf0bf52a51c9860b5.
One new issue:
1. booting smp windows guests has 30% chance of hang
Aктуальные вопросы правового регулирования
коммерческой деятельности в 2008г.
31 марта - 02 апреля 2008, Санкт-Петербург
Программа включает следующие пункты:
1. Применение ФЗ Об акционерных обществах, ФЗ Об обществах с ограниченной
ответственностью. Комментарии к последним изменениям
Avi Kivity wrote:
Glauber Costa wrote:
This lock is fairly annoying. What do you think about taking it in
vcpu_run unconditionally and only dropping it while in guest mode?
Most exits are mmu (or with npt, mmio) so they need to take it anyway.
Can't see the point. This is taken before
Glauber Costa wrote:
This lock is fairly annoying. What do you think about taking it in
vcpu_run unconditionally and only dropping it while in guest mode?
Most exits are mmu (or with npt, mmio) so they need to take it anyway.
Can't see the point. This is taken before updates to the wall
Avi Kivity wrote:
david ahern wrote:
Attaching gdb to qemu you work with addresses as seen by the qemu process;
the
idea is to work with addresses as seen inside the guest.
Now, if you attach gdb to the qemu process,
gdb /usr/local/bin/qemu-system-x86_64 2346
I meant
Avi Kivity wrote:
Glauber Costa wrote:
As Marcelo pointed out, we need slots_lock to protect
against slots changing under our nose during wall clock
writing.
This patch address this issue.
Applied, thanks.
This lock is fairly annoying. What do you think about taking it in
Glauber Costa wrote:
[EMAIL PROTECTED] linux-2.6 (master)]$ git grep down_read.*slots_lock
arch/x86/kvm/ | wc -l
16
We take the lock for read 16 times, could be narrowed down to
probably once (with a drop and re-take around guest mode).
Since it will be written to so rarely, that's
Avi,
Hope this series is okay now.
Thanks for the testing
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
it will allow external users to call it. It is mainly
useful for routines that will override its machine_ops
field for its own special purposes, but want to call the
normal shutdown routine after they're done
Signed-off-by: Glauber Costa [EMAIL PROTECTED]
---
arch/x86/kernel/reboot.c |2 +-
This patch writes 0 (actually, what really matters is that the
LSB is cleared) to the system time msr before shutting down
the machine for kexec.
Without it, we can have a random memory location being written
when the guest comes back
It overrides the functions shutdown, used in the path of
Glauber Costa wrote:
Avi,
Hope this series is okay now.
Thanks for the testing
Applied, thanks.
[Once a patchset has been applied and pushed (as seen on kvm-commits), I
prefer incremental patches]
--
Do not meddle in the internals of kernels, for they are subtle and quick to
Avi Kivity wrote:
Glauber Costa wrote:
Avi,
Hope this series is okay now.
Thanks for the testing
Applied, thanks.
[Once a patchset has been applied and pushed (as seen on kvm-commits), I
prefer incremental patches]
But I think this is a very good case of an exception, since
Glauber Costa wrote:
[Once a patchset has been applied and pushed (as seen on
kvm-commits), I prefer incremental patches]
But I think this is a very good case of an exception, since the
applied patches would break bisect. I prefer to hear damn glommer!
because of that than damn glommer!!
Avi Kivity wrote:
Glauber Costa wrote:
[Once a patchset has been applied and pushed (as seen on
kvm-commits), I prefer incremental patches]
But I think this is a very good case of an exception, since the
applied patches would break bisect. I prefer to hear damn glommer!
because of that
This patch broke -no-kvm-irqchip:
* On Wednesday 12 March 2008 01:42:08 Marcelo Tosatti wrote:
So drivers can clear their mem io table entries on exit back to unassigned
state.
Also make the io mem index allocation dynamic.
Signed-off-by: Marcelo Tosatti [EMAIL PROTECTED]
Index:
On Tue, Mar 18, 2008 at 06:02:10PM +0530, Amit Shah wrote:
This patch broke -no-kvm-irqchip:
* On Wednesday 12 March 2008 01:42:08 Marcelo Tosatti wrote:
So drivers can clear their mem io table entries on exit back to unassigned
state.
Also make the io mem index allocation dynamic.
* Marcelo Tosatti wrote:
On Tue, Mar 18, 2008 at 06:02:10PM +0530, Amit Shah wrote:
This patch broke -no-kvm-irqchip:
...
Hi Amit,
There is no need to zero io_mem_used since its in the BSS. The loop in
io_mem_init() was meant to allocate the slots from 0 to 4, not free
them.
Of
This is the first release of network drivers for Windows guests running
on a kvm host. The drivers are intended for Windows 2000 and Windows XP
32-bit. kvm-61 or later is needed in the host. At the moment only
binaries are available.
The drivers are available from the download page of the
On Tue, Mar 18, 2008 at 05:01:09PM +0200, Avi Kivity wrote:
This is the first release of network drivers for Windows guests running
on a kvm host. The drivers are intended for Windows 2000 and Windows XP
32-bit. kvm-61 or later is needed in the host. At the moment only
binaries are
Daniel P. Berrange wrote:
On Tue, Mar 18, 2008 at 05:01:09PM +0200, Avi Kivity wrote:
This is the first release of network drivers for Windows guests running
on a kvm host. The drivers are intended for Windows 2000 and Windows XP
32-bit. kvm-61 or later is needed in the host. At the
Avi Kivity wrote:
This is the first release of network drivers for Windows guests running
on a kvm host.
Any plans for Windows Server and block support?
-
This SF.net email is sponsored by: Microsoft
Defy all challenges.
Amit Shah wrote:
So does the following fix the problem?
Yes, it does. Thanks.
Okay, applied.
--
Do not meddle in the internals of kernels, for they are subtle and quick to
panic.
-
This SF.net email is sponsored
This is the first release of the kvm drivers disc -- a collection of kvm
guest drivers packaged as an ISO 9660 CD-ROM for easy installation.
The driver disc can be obtained from the kvm download page, below.
Initial release:
- kvm-guest-drivers-linux-1
- kvm-guest-drivers-windows-1
Ian,
XP drivers are also supported on Win2003 server.
Best regards,
Yan Vugenfirer.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ian Kirk
Sent: ג 18 מרץ 2008 17:19
To: Avi Kivity
Cc: KVM
Subject: Re: [kvm-devel] [ANNOUNCE]
Ian Kirk wrote:
Avi Kivity wrote:
This is the first release of network drivers for Windows guests running
on a kvm host.
Any plans for Windows Server
IIUC the XP drivers should also work for Windows 2003 Server. Windows
2008 Server and x64 variants are planned.
and block
On Sun, 2008-03-16 at 19:08 +0200, Avi Kivity wrote:
Dor Laor wrote:
From 498f162fc9d9fb897c756273c481101a44a220de Mon Sep 17 00:00:00 2001
From: Dor Laor [EMAIL PROTECTED]
Date: Thu, 13 Mar 2008 00:11:41 +0200
Subject: [PATCH] Fix sci irq set when acpi timer about to wrap.
The acpi
Avi Kivity wrote:
Trying to merge qemu-cvs, there's a conflict in vmwarevga between two
changes that appear to be identical in purpose, only implemented
differently: 6d262b07a2046ed1fa0ec3fd61f00efbfcd5a9ef (master) and
5aa90452c52e3a914e1f6bbf34331507fd7c5d52 (qemu-cvs).
I think the
Are you interested in collecting ports of the drivers for various distributions?
I have the virtio drivers working with RHEL4. The virtio_net appears to be
working better than e1000 for the workload I am testing with (though I still the
need the noapic boot option). The virtio_blk driver mostly
david ahern wrote:
Are you interested in collecting ports of the drivers for various
distributions?
What we would like to do, is have the kvm-guest-drivers-linux.git tree
autogenerate backports for as far back as we need them. Posting what
you needed to do for RHEL4 would be helpful.
# HG changeset patch
# User Jerone Young [EMAIL PROTECTED]
# Date 1205870472 18000
# Branch merge
# Node ID 4f90f7d25186f55bfb1503764af5264201df067f
# Parent ac0fc9dfd78d2eddd083326e9b635a9286fc3b19
Add ability to specify ram on command line for bamboo board model
This patch adds the ability to
# HG changeset patch
# User Jerone Young [EMAIL PROTECTED]
# Date 1205870472 18000
# Branch merge
# Node ID 3e87db599895937824b9bf3369eb67ea7f5a7595
# Parent ba2876c3e8916ba9c19b75c4464cbb8dc6858fbd
Add dynamic device tree manipulation change uboot loader for PPC bamboo board
model
This patch
# HG changeset patch
# User Jerone Young [EMAIL PROTECTED]
# Date 1205870472 18000
# Branch merge
# Node ID 25515e6983ba1e070cbdcb7be1527426a097048b
# Parent aa10b5ca2f11cd571ae8a06c1e92425b7f7407ca
Create new load_uimage() gunzip support to uboot loader in Qemu
This patch adds the ability for
# HG changeset patch
# User Jerone Young [EMAIL PROTECTED]
# Date 1205870472 18000
# Branch merge
# Node ID aa10b5ca2f11cd571ae8a06c1e92425b7f7407ca
# Parent 499d36637c8b4fcc0cd0008186d7974bb28369ab
Add libfdt support to qemu
This patch adds needed configuration options to compile in libfdt
# HG changeset patch
# User Jerone Young [EMAIL PROTECTED]
# Date 1205870472 18000
# Branch merge
# Node ID ac0fc9dfd78d2eddd083326e9b635a9286fc3b19
# Parent 3e87db599895937824b9bf3369eb67ea7f5a7595
Modify PPC bamboo ppc440 board models
This patch renames pp440_init to ppc440ep_init, as ppc440
init_rmode_tss was forgotten during the conversion from mmap_sem to
slots_lock.
There are several sites reading the slots data without taking
slots_lock, including tdp_page_fault. I'll be sending a patch
to move acquision to vcpu_run as suggested by Avi later today.
INFO: task
# HG changeset patch
# User Jerone Young [EMAIL PROTECTED]
# Date 1205870472 18000
# Branch merge
# Node ID ba2876c3e8916ba9c19b75c4464cbb8dc6858fbd
# Parent 25515e6983ba1e070cbdcb7be1527426a097048b
Add PPC 440EP bamboo board device tree source binary into qemu
This patch places the bamboo
On Tue, 2008-03-18 at 15:06 -0500, Jerone Young wrote:
# HG changeset patch
# User Jerone Young [EMAIL PROTECTED]
# Date 1205870472 18000
# Branch merge
# Node ID 4f90f7d25186f55bfb1503764af5264201df067f
# Parent ac0fc9dfd78d2eddd083326e9b635a9286fc3b19
Add ability to specify ram on
On Tue, 2008-03-18 at 15:06 -0500, Jerone Young wrote:
+tmp_loaded_image_size = hdr-ih_size;
+
+if (hdr-ih_comp == IH_COMP_GZIP) {
+ uncompressed_data = qemu_malloc(MAX_KERNEL_SIZE);
+ ret = gunzip(uncompressed_data, MAX_KERNEL_SIZE,
+(unsigned
On Tue, 2008-03-18 at 15:06 -0500, Jerone Young wrote:
+##
+# libfdt probe
+#
+if test -z $device_tree_support -a \
+ $cpu = powerpc; then
+ device_tree_support=no
+ cat $TMPC EOF
+#include libfdt.h
+/* XXX uncomment later when libfdt is built
On Tue, 2008-03-18 at 16:03 -0500, Hollis Blanchard wrote:
On Tue, 2008-03-18 at 15:06 -0500, Jerone Young wrote:
# HG changeset patch
# User Jerone Young [EMAIL PROTECTED]
# Date 1205870472 18000
# Branch merge
# Node ID 4f90f7d25186f55bfb1503764af5264201df067f
# Parent
So this is the code Anthony asked for for probing libfdt. The problem is
that if you do ./configure params at kvm-userpace top directory for
the first time or after a clean you do not have libfdt.a. When qemu
configure is run this probe would allways fail. So to check we just
check for the header.
On Tue, 2008-03-18 at 15:06 -0500, Jerone Young wrote:
# HG changeset patch
# User Jerone Young [EMAIL PROTECTED]
# Date 1205870472 18000
# Branch merge
# Node ID 3e87db599895937824b9bf3369eb67ea7f5a7595
# Parent ba2876c3e8916ba9c19b75c4464cbb8dc6858fbd
Add dynamic device tree manipulation
OK, if that's acceptable to the qemu folks, could you put that in the
patch description?
--
Hollis Blanchard
IBM Linux Technology Center
On Tue, 2008-03-18 at 16:22 -0500, Jerone Young wrote:
So this is the code Anthony asked for for probing libfdt. The problem is
that if you do ./configure
On Tue, 2008-03-18 at 16:25 -0500, Hollis Blanchard wrote:
On Tue, 2008-03-18 at 15:06 -0500, Jerone Young wrote:
# HG changeset patch
# User Jerone Young [EMAIL PROTECTED]
# Date 1205870472 18000
# Branch merge
# Node ID 3e87db599895937824b9bf3369eb67ea7f5a7595
# Parent
On Tue, 2008-03-18 at 16:14 -0500, Hollis Blanchard wrote:
On Tue, 2008-03-18 at 15:06 -0500, Jerone Young wrote:
+tmp_loaded_image_size = hdr-ih_size;
+
+if (hdr-ih_comp == IH_COMP_GZIP) {
+ uncompressed_data = qemu_malloc(MAX_KERNEL_SIZE);
+ ret =
Well this can not go upstream. If it were to go into upstream qemu we
would need for them to take in libfdt (which they most likely will have
big issue with). Also we wouldn't do the probing if they did take it in.
But for the forseable future we are not getting stuff into qemu yet. If
we do then
I can only assume that you will actually make the corrections that you
didn't respond to in this mail.
On Tue, 2008-03-18 at 16:35 -0500, Jerone Young wrote:
On Tue, 2008-03-18 at 16:25 -0500, Hollis Blanchard wrote:
+#define DT_PROC_INTERFACE_PATH /proc/device-tree
+
+/* FUNCTIONS
On Tue, 2008-03-18 at 16:46 -0500, Jerone Young wrote:
On Tue, 2008-03-18 at 16:14 -0500, Hollis Blanchard wrote:
On Tue, 2008-03-18 at 15:06 -0500, Jerone Young wrote:
+tmp_loaded_image_size = hdr-ih_size;
+
+if (hdr-ih_comp == IH_COMP_GZIP) {
+ uncompressed_data
After some research of time drift while using window windows acpi hal I
discovered it uses the ... rtc timer as a source clock.
Not the apic, acpi nor the pit. The acpi timer is not used by the time
keeping clock, the apic pit timer irqs are masked.
In order to fix the time drift we need to fix
On Wed, 2008-03-19 at 01:09 +0200, Dor Laor wrote:
After some research of time drift while using window windows acpi hal I
discovered it uses the ... rtc timer as a source clock.
Not the apic, acpi nor the pit. The acpi timer is not used by the time
keeping clock, the apic pit timer irqs
Dor Laor wrote:
After some research of time drift while using window windows acpi hal I
discovered it uses the ... rtc timer as a source clock.
Not the apic, acpi nor the pit. The acpi timer is not used by the time
keeping clock, the apic pit timer irqs are masked.
In order to fix the time
Dor Laor wrote:
On Wed, 2008-03-19 at 01:09 +0200, Dor Laor wrote:
After some research of time drift while using window windows acpi hal I
discovered it uses the ... rtc timer as a source clock.
Not the apic, acpi nor the pit. The acpi timer is not used by the time
keeping clock, the
Dor Laor wrote:
2. The other option is to have an accurate userspace timer (userspace
hrtimer exist = 2.6.24) and to add interface to pic/apic to queue
pending irqs by the pit/rtc.
The pending queue can be a simple atomic counter per irq.
So this may explain why I see no appreciable
That's what I was looking for.
thanks,
david
Uri Lublin wrote:
Avi Kivity wrote:
david ahern wrote:
Attaching gdb to qemu you work with addresses as seen by the qemu
process; the
idea is to work with addresses as seen inside the guest.
Now, if you attach gdb to the qemu process,
Упpощeнная систeма налoгooблoжeния
Oднoднeвный сeминаp пpoйдёт 21 маpта 2008г. (Мoсква)
В пpoгpамма:
1. Сущнoсть УСН, oсвoбoждeниe oт уплаты pяда налoгoв.
Пopядoк и услoвия начала и пpeкpащeния пpимeнeния упpoщeннoй систeмы
налoгooблoжeния с учeтoм нoвшeств 2008 г.
Тpeбoвания к pазмepу
Marcelo Tosatti wrote:
init_rmode_tss was forgotten during the conversion from mmap_sem to
slots_lock.
yup, good catch.
There are several sites reading the slots data without taking
slots_lock, including tdp_page_fault. I'll be sending a patch
to move acquision to vcpu_run
65 matches
Mail list logo
