Chris Wright wrote:
During hotadd of SCSI devices lsi_scsi_init() handles failed
pci_device_register(), but qemu_system_hot_add_storage() will try and
attach a drive any way. Handle this error case rather the generating
SEGV.
Cc: Marcelo Tosatti [EMAIL PROTECTED]
Signed-off-by: Chris
Am Dienstag, 22. April 2008 schrieb Rusty Russell:
[Christian, Hollis, how much is this ABI breakage going to hurt you?]
It is ok for s390 at the moment. We are still working on making userspace
ready and I plan to change the guest-host for s390 anyway. I try to make
these changes for
Jamie Lokier wrote:
Avi Kivity wrote:
At such a tiny difference, I'm wondering why Linux-AIO exists at all,
as it complicates the kernel rather a lot. I can see the theoretical
appeal, but if performance is so marginal, I'm surprised it's in
there.
Linux aio exists, but that's
[Note: KVM Forum registration is now open at
http://kforum.qumranet.com/KVMForum/about_kvmforum.php]
[The deadline for submitting presentations has been extended by two
weeks, until May 4th]
This is the Call for Presentations for the second annual KVM Developer's
Forum, to be held on June
Hi All,
This is today's KVM test result against kvm.git
6cf59734fc9bc89954d0157524eea156c2f9a5ab and kvm-userspace.git
5157358e1946770847271e3602f1adae85002871.
One Issue Fixed:
1. booting smp windows guests has 30% chance of hang
Hi,
I am thinking about comibing this ROM with the extboot. Both two ROM
are about booting, so I think that is reasonable. So we will have
only 1 ROM that supports both external boot and Linux boot.
Is that desirable or not?
Thanks,
Quynh
On 4/21/08, Nguyen Anh Quynh [EMAIL PROTECTED] wrote:
Yang, Sheng wrote:
From 73c33765f3d879001818cd0719038c78a0c65561 Mon Sep 17 00:00:00 2001
From: Sheng Yang [EMAIL PROTECTED]
Date: Fri, 18 Apr 2008 17:15:39 +0800
Subject: [PATCH] kvm: qemu: Enable EPT support for real mode
This patch build a identity page table on the last page of VGA bios,
I believe that's the way to go. If you have spare time on your hands,
feel free to integrate my multiboot patches as well.
Alex
On Apr 22, 2008, at 11:07 AM, Nguyen Anh Quynh wrote:
Hi,
I am thinking about comibing this ROM with the extboot. Both two ROM
are about booting, so I think that
Размeщeниe гoсудаpствeннoгo и муниципальнoгo заказа на тopгах: спopныe вoпpoсы
сoвpeмeннoй пpактики
25 апpeля 2008, г. Мoсква
Пpoгpамма сeминаpа
- Анализ кoнкpeтных аpбитpажных дeл, являющихся наибoлee pаспpoстpанeнными
(типичными) в судeбнo-аpбитpажнoй пpактикe oспаpивания pазмeщeния
Damjan wrote:
I have some questions for the FAQ, about the configuration of Linux guests:
a) is swap needed in the guest (I'd say no, but..)
b) what filesystem is best for a guest
c) what io scheduler in the guest (noop? or cfq)
d) are there any runtime kernel tweaks for the guest
Jerone Young wrote:
virtio net device does not appear to show itself in the guest. I'm
curious of what options I may be missing. Here is my config
CONFIG_VIRTIO_NET=y
[..]
CONFIG_VIRTUALIZATION=y
CONFIG_KVM=y
CONFIG_KVM_BOOKE_HOST=y
CONFIG_VIRTIO=y
CONFIG_VIRTIO_RING=y
Jerone Young wrote:
What I am asking is do I have all the proper options in my kernel config
set to use it?
I have:
[EMAIL PROTECTED] linux-2.6 (kvm-updates-2.6.26)]$ grep VIRTIO .config
CONFIG_VIRTIO_BLK=m
CONFIG_VIRTIO_NET=m
CONFIG_VIRTIO=m
CONFIG_VIRTIO_RING=m
CONFIG_VIRTIO_PCI=m
Jes Sorensen wrote:
Hi,
This one fixes a segfault problem I am seeing on ia64 due to the
malloc'ed address being truncated to 32 bit.
Applied, thanks.
--
error compiling committee.c: too many arguments to function
-
Chris Wright wrote:
The pci hotadd patches make it easy to trigger segfaults when adding more
devices than a single PCI bus can handle. The following 2 patches fix the
pci nic devices and virtio-blk device. Now the following the following:
OK bus 0, slot 31, function 0 (devfn 248)
Rusty Russell wrote:
[Christian, Hollis, how much is this ABI breakage going to hurt you?]
A recent proposed feature addition to the virtio block driver revealed
some flaws in the API, in particular how easy it is to break big
endian machines.
The virtio config space was originally chosen
On Tue, Apr 22, 2008 at 1:10 PM, Avi Kivity [EMAIL PROTECTED] wrote:
Damjan wrote:
I have some questions for the FAQ, about the configuration of Linux guests:
a) is swap needed in the guest (I'd say no, but..)
b) what filesystem is best for a guest
c) what io scheduler in the guest
Luca Tettamanti wrote:
Is cfq still fair in the guest? The VM re-dispatches the requests (at
least when using QEMU IDE) and the host can reschedule them at will.
The same problem occurs (to a lesser extent) in non-virtualized
environments; disks (and esp. array controllers) also have their
Jerone Young wrote:
Recent change now requires target-ppc/helper.c to now include qemu-kvm.h to
get the definition for kvm_enabled(). This fixes it so things now compile
again.
Applied, thanks.
--
error compiling committee.c: too many arguments to function
On Tue, Apr 22, 2008 at 09:20:26AM +0200, Andrea Arcangeli wrote:
invalidate_range_start {
spin_lock(kvm-mmu_lock);
kvm-invalidate_range_count++;
rmap-invalidate of sptes in range
write_seqlock; write_sequnlock;
spin_unlock(kvm-mmu_lock)
}
Liu, Eric E wrote:
From a1b062cfd4d1a91c447b680ac9a2250fe55119ec Mon Sep 17 00:00:00 2001
From: Feng (Eric) Liu [EMAIL PROTECTED]
Date: Wed, 16 Apr 2008 05:29:37 -0400
Subject: [PATCH] KVM: trace: Add event mask support.
Allow user space application to specify one or more
filter masks to
On Tue, Apr 22, 2008 at 02:00:56PM +0200, Andrea Arcangeli wrote:
On Tue, Apr 22, 2008 at 09:20:26AM +0200, Andrea Arcangeli wrote:
invalidate_range_start {
spin_lock(kvm-mmu_lock);
kvm-invalidate_range_count++;
rmap-invalidate of sptes in range
On Tue, Apr 22, 2008 at 08:01:20AM -0500, Robin Holt wrote:
On Tue, Apr 22, 2008 at 02:00:56PM +0200, Andrea Arcangeli wrote:
On Tue, Apr 22, 2008 at 09:20:26AM +0200, Andrea Arcangeli wrote:
invalidate_range_start {
spin_lock(kvm-mmu_lock);
kvm-invalidate_range_count++;
Jerone Young wrote:
What I am asking is do I have all the proper options in my kernel config
set to use it?
Yes. You just need CONFIG_VIRTIO_NET and CONFIG_VIRTIO_PCI. The
remaining options will be automatically selected.
Regards,
Anthony Liguori
On Mon, 2008-04-21 at 17:13 -0500,
On Tue, Apr 22, 2008 at 03:21:43PM +0200, Andrea Arcangeli wrote:
On Tue, Apr 22, 2008 at 08:01:20AM -0500, Robin Holt wrote:
On Tue, Apr 22, 2008 at 02:00:56PM +0200, Andrea Arcangeli wrote:
On Tue, Apr 22, 2008 at 09:20:26AM +0200, Andrea Arcangeli wrote:
invalidate_range_start {
Nguyen Anh Quynh wrote:
Hi,
I am thinking about comibing this ROM with the extboot. Both two ROM
are about booting, so I think that is reasonable. So we will have
only 1 ROM that supports both external boot and Linux boot.
Is that desirable or not?
I think so.
Regards,
Anthony
On Tue, Apr 22, 2008 at 08:36:04AM -0500, Robin Holt wrote:
I am a little confused about the value of the seq_lock versus a simple
atomic, but I assumed there is a reason and left it at that.
There's no value for anything but get_user_pages (get_user_pages takes
its own lock internally though).
# HG changeset patch
# User Andrea Arcangeli [EMAIL PROTECTED]
# Date 1208870142 -7200
# Node ID ea87c15371b1bd49380c40c3f15f1c7ca4438af5
# Parent fb3bc9942fb78629d096bd07564f435d51d86e5f
Core of mmu notifiers.
Signed-off-by: Andrea Arcangeli [EMAIL PROTECTED]
Signed-off-by: Nick Piggin [EMAIL
# HG changeset patch
# User Andrea Arcangeli [EMAIL PROTECTED]
# Date 1208872186 -7200
# Node ID 3c804dca25b15017b22008647783d6f5f3801fa9
# Parent ea87c15371b1bd49380c40c3f15f1c7ca4438af5
Fix ia64 compilation failure because of common code include bug.
Signed-off-by: Andrea Arcangeli [EMAIL
# HG changeset patch
# User Andrea Arcangeli [EMAIL PROTECTED]
# Date 1208872186 -7200
# Node ID ac9bb1fb3de2aa5d27210a28edf24f6577094076
# Parent a6672bdeead0d41b2ebd6846f731d43a611645b7
Moves all mmu notifier methods outside the PT lock (first and not last
step to make them sleep capable).
# HG changeset patch
# User Andrea Arcangeli [EMAIL PROTECTED]
# Date 1208872187 -7200
# Node ID f8210c45f1c6f8b38d15e5dfebbc5f7c1f890c93
# Parent bdb3d928a0ba91cdce2b61bd40a2f80bddbe4ff2
Convert mm_lock to use semaphores after i_mmap_lock and anon_vma_lock
conversion.
Signed-off-by: Andrea
# HG changeset patch
# User Andrea Arcangeli [EMAIL PROTECTED]
# Date 1208872186 -7200
# Node ID ee8c0644d5f67c1ef59142cce91b0bb6f34a53e0
# Parent ac9bb1fb3de2aa5d27210a28edf24f6577094076
Move the tlb flushing into free_pgtables. The conversion of the locks
taken for reverse map scanning would
# HG changeset patch
# User Andrea Arcangeli [EMAIL PROTECTED]
# Date 1208872187 -7200
# Node ID e847039ee2e815088661933b7195584847dc7540
# Parent 128d705f38c8a774ac11559db445787ce6e91c77
This patch adds a lock ordering rule to avoid a potential deadlock when
multiple mmap_sems need to be locked.
# HG changeset patch
# User Andrea Arcangeli [EMAIL PROTECTED]
# Date 1208872187 -7200
# Node ID 128d705f38c8a774ac11559db445787ce6e91c77
# Parent f8210c45f1c6f8b38d15e5dfebbc5f7c1f890c93
XPMEM would have used sys_madvise() except that madvise_dontneed()
returns an -EINVAL if VM_PFNMAP is set,
# HG changeset patch
# User Andrea Arcangeli [EMAIL PROTECTED]
# Date 1208872186 -7200
# Node ID fbce3fecb033eb3fba1d9c2398ac74401ce0ecb5
# Parent ee8c0644d5f67c1ef59142cce91b0bb6f34a53e0
Move the tlb flushing inside of unmap vmas. This saves us from passing
a pointer to the TLB structure around
Hello,
This is the latest and greatest version of the mmu notifier patch #v13.
Changes are mainly in the mm_lock that uses sort() suggested by Christoph.
This reduces the complexity from O(N**2) to O(N*log(N)).
I folded the mm_lock functionality together with the mmu-notifier-core 1/12
patch to
# HG changeset patch
# User Andrea Arcangeli [EMAIL PROTECTED]
# Date 1208872186 -7200
# Node ID a6672bdeead0d41b2ebd6846f731d43a611645b7
# Parent 3c804dca25b15017b22008647783d6f5f3801fa9
get_task_mm should not succeed if mmput() is running and has reduced
the mm_users count to zero. This can
# HG changeset patch
# User Andrea Arcangeli [EMAIL PROTECTED]
# Date 1208872187 -7200
# Node ID bdb3d928a0ba91cdce2b61bd40a2f80bddbe4ff2
# Parent 6e04df1f4284689b1c46e57a67559abe49ecf292
Convert the anon_vma spinlock to a rw semaphore. This allows concurrent
traversal of reverse maps for
# HG changeset patch
# User Andrea Arcangeli [EMAIL PROTECTED]
# Date 1208872187 -7200
# Node ID 6e04df1f4284689b1c46e57a67559abe49ecf292
# Parent 8965539f4d174c79bd37e58e8b037d5db906e219
The conversion to a rwsem allows notifier callbacks during rmap traversal
for files. A rw style lock also
This patch changes virtio devices to be multi-function devices whenever
possible. This increases the number of virtio devices we can support now by
a factor of 8.
With this patch, I've been able to launch a guest with either 220 disks or 220
network adapters.
I haven't tested the Windows virtio
Otherwise multiple guests use the same variable and boom.
Also use kvm_vcpu_kick() to make sure that if a timer triggers on
a different CPU the event won't be missed.
Signed-off-by: Marcelo Tosatti [EMAIL PROTECTED]
Tested-and-Acked-by: Alex Davis [EMAIL PROTECTED]
diff --git
Anthony Liguori wrote:
This patch changes virtio devices to be multi-function devices whenever
possible. This increases the number of virtio devices we can support now by
a factor of 8.
With this patch, I've been able to launch a guest with either 220 disks or 220
network adapters.
On Tuesday 22 April 2008 21:22:48 Avi Kivity wrote:
The virtio config space was originally chosen to be little-endian,
because we thought the config might be part of the PCI config space
for virtio_pci. It's actually a separate mmio region, so that
argument holds little water; as only x86
On Tuesday 22 April 2008 17:44:08 Christian Borntraeger wrote:
Am Dienstag, 22. April 2008 schrieb Rusty Russell:
[Christian, Hollis, how much is this ABI breakage going to hurt you?]
It is ok for s390 at the moment. We are still working on making userspace
ready and I plan to change the
Marcelo Tosatti wrote:
Otherwise multiple guests use the same variable and boom.
Also use kvm_vcpu_kick() to make sure that if a timer triggers on
a different CPU the event won't be missed.
Applied, thanks.
--
error compiling committee.c: too many arguments to function
Avi Kivity wrote:
Anthony Liguori wrote:
This patch changes virtio devices to be multi-function devices whenever
possible. This increases the number of virtio devices we can support now by
a factor of 8.
With this patch, I've been able to launch a guest with either 220 disks or
220
Anthony Liguori wrote:
Avi Kivity wrote:
Anthony Liguori wrote:
This patch changes virtio devices to be multi-function devices whenever
possible. This increases the number of virtio devices we can
support now by
a factor of 8.
With this patch, I've been able to launch a guest with
Jamie Lokier wrote:
Avi Kivity wrote:
And video streaming on some embedded devices with no MMU! (Due to the
page cache heuristics working poorly with no MMU, sustained reliable
streaming is managed with O_DIRECT and the app managing cache itself
(like a database), and that needs AIO to
Le mardi 22 avril 2008 à 08:50 -0500, Anthony Liguori a écrit :
Nguyen Anh Quynh wrote:
Hi,
This should be submitted to upstream (but not to kvm-devel list), but
this is only the test code that I want to quickly send out for
comments. In case it looks OK, I will send it to upstream
Jamie Lokier wrote:
Avi Kivity wrote:
And video streaming on some embedded devices with no MMU! (Due to the
page cache heuristics working poorly with no MMU, sustained reliable
streaming is managed with O_DIRECT and the app managing cache itself
(like a database), and that needs AIO to
Nguyen Anh Quynh wrote:
Hi,
This should be submitted to upstream (but not to kvm-devel list), but
this is only the test code that I want to quickly send out for
comments. In case it looks OK, I will send it to upstream later.
Inspired by extboot and conversations with Anthony and HPA, this
Anthony Liguori wrote:
If I submit sequential O_DIRECT reads with aio_read(), will they enter
the device read queue in the same order, and reach the disk in that
order (allowing for reordering when worthwhile by the elevator)?
There's no guarantee that any sort of order will be preserved
On Tue, Apr 22, 2008 at 4:15 PM, Anthony Liguori [EMAIL PROTECTED] wrote:
This patch changes virtio devices to be multi-function devices whenever
possible. This increases the number of virtio devices we can support now by
a factor of 8.
[...]
diff --git a/qemu/hw/virtio.c
Anthony Liguori wrote:
Perhaps. This raises another point about AIO vs. threads:
If I submit sequential O_DIRECT reads with aio_read(), will they enter
the device read queue in the same order, and reach the disk in that
order (allowing for reordering when worthwhile by the elevator)?
* Anthony Liguori [EMAIL PROTECTED] [2008-04-22 09:16]:
This patch changes virtio devices to be multi-function devices whenever
possible. This increases the number of virtio devices we can support now by
a factor of 8.
With this patch, I've been able to launch a guest with either 220 disks
On Tue, Apr 22, 2008 at 04:56:10PM +0200, Eric Dumazet wrote:
Andrea Arcangeli a écrit :
+
+static int mm_lock_cmp(const void *a, const void *b)
+{
+cond_resched();
+if ((unsigned long)*(spinlock_t **)a
+(unsigned long)*(spinlock_t **)b)
+return -1;
+else
Ryan Harper wrote:
* Anthony Liguori [EMAIL PROTECTED] [2008-04-22 09:16]:
This patch changes virtio devices to be multi-function devices whenever
possible. This increases the number of virtio devices we can support now by
a factor of 8.
With this patch, I've been able to launch a guest
On Tue, Apr 22, 2008 at 05:32:45PM +0300, Avi Kivity wrote:
Anthony Liguori wrote:
This patch changes virtio devices to be multi-function devices whenever
possible. This increases the number of virtio devices we can support now by
a factor of 8.
With this patch, I've been able to
Avi Kivity wrote:
Anthony Liguori wrote:
If I submit sequential O_DIRECT reads with aio_read(), will they enter
the device read queue in the same order, and reach the disk in that
order (allowing for reordering when worthwhile by the elevator)?
There's no guarantee that any sort of order
Andrea Arcangeli wrote:
On Tue, Apr 22, 2008 at 04:56:10PM +0200, Eric Dumazet wrote:
Andrea Arcangeli a écrit :
+
+static int mm_lock_cmp(const void *a, const void *b)
+{
+ cond_resched();
+ if ((unsigned long)*(spinlock_t **)a
+ (unsigned long)*(spinlock_t **)b)
+
Andrew, Could we get direction/guidance from you as regards
the invalidate_page() callout of Andrea's patch set versus the
invalidate_range_start/invalidate_range_end callout pairs of Christoph's
patchset? This is only in the context of the __xip_unmap, do_wp_page,
page_mkclean_one, and
Avi Kivity wrote:
Perhaps. This raises another point about AIO vs. threads:
If I submit sequential O_DIRECT reads with aio_read(), will they enter
the device read queue in the same order, and reach the disk in that
order (allowing for reordering when worthwhile by the elevator)?
Yes,
Avi Kivity wrote:
And video streaming on some embedded devices with no MMU! (Due to the
page cache heuristics working poorly with no MMU, sustained reliable
streaming is managed with O_DIRECT and the app managing cache itself
(like a database), and that needs AIO to keep the request queue
On Tue, Apr 22, 2008 at 3:10 AM, Avi Kivity [EMAIL PROTECTED] wrote:
I'm rooting for btrfs myself.
but could btrfs (when stable) work for migration? i'm curious about
OCFS2 performance on this kind of load...
when i manage to sell the idea of a KVM cluster i'd like to know if i
should try
Marcelo Tosatti wrote:
Maybe require explicit device/function assignment on the command line?
It will be managed anyway.
ACPI does support hotplugging of individual functions inside slots,
not sure how well does Linux (and other OSes) support that.. should be
transparent though.
On Tuesday 22 April 2008 06:22:48 Avi Kivity wrote:
Rusty Russell wrote:
[Christian, Hollis, how much is this ABI breakage going to hurt you?]
A recent proposed feature addition to the virtio block driver revealed
some flaws in the API, in particular how easy it is to break big
endian
Nguyen Anh Quynh wrote:
Hi,
I am thinking about comibing this ROM with the extboot. Both two ROM
are about booting, so I think that is reasonable. So we will have
only 1 ROM that supports both external boot and Linux boot.
Is that desirable or not?
Does it make the code simpler and
Anthony Liguori wrote:
I think we need to decide what we want to target in terms of upper
limits.
With a bridge or two, we can probably easily do 128.
If we really want to push things, I think we should do a PCI based
virtio controller. I doubt a large number of PCI devices is ever
Avi Kivity wrote:
Anthony Liguori wrote:
I think we need to decide what we want to target in terms of upper
limits.
With a bridge or two, we can probably easily do 128.
If we really want to push things, I think we should do a PCI based
virtio controller. I doubt a large number of PCI
Andrea Arcangeli a écrit :
On Tue, Apr 22, 2008 at 04:56:10PM +0200, Eric Dumazet wrote:
Andrea Arcangeli a écrit :
+
+static int mm_lock_cmp(const void *a, const void *b)
+{
+ cond_resched();
+ if ((unsigned long)*(spinlock_t **)a
+ (unsigned long)*(spinlock_t **)b)
On Tue, Apr 22, 2008 at 05:37:38PM +0200, Eric Dumazet wrote:
I am saying your intent was probably to test
else if ((unsigned long)*(spinlock_t **)a ==
(unsigned long)*(spinlock_t **)b)
return 0;
Indeed...
Hum, it's not a micro-optimization, but a bug fix. :)
The
Hi guys.
I'm trying to figure out what's going on with this bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/217815
The short version of the problem is that it seems that if the console is
left alone for an extended period of time, everything seems to stall
until something (moving
Andrea Arcangeli a écrit :
+
+static int mm_lock_cmp(const void *a, const void *b)
+{
+ cond_resched();
+ if ((unsigned long)*(spinlock_t **)a
+ (unsigned long)*(spinlock_t **)b)
+ return -1;
+ else if (a == b)
+ return 0;
+ else
+
On Tue, Apr 22, 2008 at 11:31:11AM -0500, Anthony Liguori wrote:
Avi Kivity wrote:
Anthony Liguori wrote:
I think we need to decide what we want to target in terms of upper
limits.
With a bridge or two, we can probably easily do 128.
If we really want to push things, I think we should
* On Sunday 13 Apr 2008 14:06:27 Avi Kivity wrote:
Amit Shah wrote:
Passthrough devices are host machine PCI devices which have
been handed off to the guest. Handle interrupts from these
devices and route them to the appropriate guest irq lines.
The userspace provides us with the
Gerd Hoffmann wrote:
Jeremy Fitzhardinge wrote:
Xen could change the parameters in the instant after get_time_values().
That change could be as a result of suspend-resume, so the parameters
and the tsc could be wildly different.
Ah, ok, forgot the rdtsc in the picture. With that in mind I
I believe the differences between your patch set and Christoph's need
to be understood and a compromise approach agreed upon.
Those differences, as I understand them, are:
1) invalidate_page: You retain an invalidate_page() callout. I believe
we have progressed that discussion to the point
Thanks for all those who work on KVM. It is a wonderful product and I
have been very impressed with its features, performance, and the level
of activity in this project.
Back in February a bug was filed. I've been hit by this bug as well,
but there hasn't been much activity with it in the
On Tue, Apr 22, 2008 at 01:22:13PM -0500, Robin Holt wrote:
1) invalidate_page: You retain an invalidate_page() callout. I believe
we have progressed that discussion to the point that it requires some
direction for Andrew, Linus, or somebody in authority. The basics
of the difference
For mass storage, we should follow the SCSI model with a single device
serving multiple disks, similar to what you suggest. Not sure if the
device should have a single queue or one queue per disk.
My latest thought it to do a virtio-based virtio controller.
Why do you
Avi Kivity wrote:
For mass storage, we should follow the SCSI model with a single device
serving multiple disks, similar to what you suggest. Not sure if the
device should have a single queue or one queue per disk.
Don't you just end up re-implementing SCSI then, at which point you might
as
Marcelo Tosatti wrote:
On Tue, Apr 22, 2008 at 05:32:45PM +0300, Avi Kivity wrote:
Anthony Liguori wrote:
This patch changes virtio devices to be multi-function devices whenever
possible. This increases the number of virtio devices we can support now by
a factor of 8.
With this
On Tue, Apr 22, 2008 at 02:26:45PM -0300, Marcelo Tosatti wrote:
On Tue, Apr 22, 2008 at 11:31:11AM -0500, Anthony Liguori wrote:
Avi Kivity wrote:
Anthony Liguori wrote:
I think we need to decide what we want to target in terms of upper
limits.
With a bridge or two, we can
On Tue, Apr 22, 2008 at 08:43:35PM +0200, Andrea Arcangeli wrote:
On Tue, Apr 22, 2008 at 01:22:13PM -0500, Robin Holt wrote:
1) invalidate_page: You retain an invalidate_page() callout. I believe
we have progressed that discussion to the point that it requires some
direction for Andrew,
Hello my good friend.
How are you today? Hope all is well with you and your family?, You may not
understand why this mail came to you.But if you do not remember me, you might
have receive an email from me in the past regarding a multi-million-dollar
business proposal which we never
Thanks for adding most of my enhancements. But
1. There is no real need for invalidate_page(). Can be done with
invalidate_start/end. Needlessly complicates the API. One
of the objections by Andrew was that there mere multiple
callbacks that perform similar functions.
2.
I was wondering if anyone could reproduce my problem. If it is
reproduceable, then I'll file a bug.
I am using e1000 ethernet adapters on Windows 2003 and Linux guests.
The line to set it up is something like this:
-net nic,vlan=1,macaddr=00:ff:21:cf:91:01,model=e1000 \
-net
Looks like this is not complete. There are numerous .h files missing which
means that various structs are undefined (fs.h and rmap.h are needed
f.e.) which leads to surprises when dereferencing fields of these struct.
It seems that mm_types.h is expected to be included only in certain
I added tracers to kvm_mmu_page_fault() that include collecting tsc cycles:
1. before vcpu-arch.mmu.page_fault()
2. after vcpu-arch.mmu.page_fault()
3. after mmu_topup_memory_caches()
4. after emulate_instruction()
So the delta in the trace reports show:
- cycles required for arch.mmu.page_fault
Missing signoff by you.
-
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
Reverts a part of an earlier patch. Why isnt this merged into 1 of 12?
-
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use
Why are the subjects all screwed up? They are the first line of the
description instead of the subject line of my patches.
-
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's
Doing the right patch ordering would have avoided this patch and allow
better review.
-
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save
On Tue, 22 Apr 2008, Andrea Arcangeli wrote:
My patch order and API backward compatible extension over the patchset
is done to allow 2.6.26 to fully support KVM/GRU and 2.6.27 to support
XPMEM as well. KVM/GRU won't notice any difference once the support
for XPMEM is added, but even if the
On Tue, 22 Apr 2008, Robin Holt wrote:
putting it back into your patch/agreeing to it remaining in Andrea's
patch? If not, I think we can put this issue aside until Andrew gets
out of the merge window and can decide it. Either way, the patches
become much more similar with this in.
One
On Tue, Apr 22, 2008 at 01:19:29PM -0700, Christoph Lameter wrote:
Thanks for adding most of my enhancements. But
1. There is no real need for invalidate_page(). Can be done with
invalidate_start/end. Needlessly complicates the API. One
of the objections by Andrew was that there
On Tuesday 22 April 2008 09:31:35 Rusty Russell wrote:
On Tuesday 22 April 2008 21:22:48 Avi Kivity wrote:
The virtio config space was originally chosen to be little-endian,
because we thought the config might be part of the PCI config space
for virtio_pci. It's actually a separate mmio
This patch changes virtio devices to be multi-function devices whenever
possible. This increases the number of virtio devices we can support now by
a factor of 8.
With this patch, I've been able to launch a guest with either 220 disks or 220
network adapters.
Since v1, I've changed the way
On Wednesday 23 April 2008 06:29:14 Hollis Blanchard wrote:
On Tuesday 22 April 2008 09:31:35 Rusty Russell wrote:
We may still regret not doing *everything* little-endian, but this
doesn't make it worse.
Hmm, why *don't* we just do everything LE, including the ring?
Mainly because when
On Tuesday 22 April 2008 16:05:38 Rusty Russell wrote:
On Wednesday 23 April 2008 06:29:14 Hollis Blanchard wrote:
On Tuesday 22 April 2008 09:31:35 Rusty Russell wrote:
We may still regret not doing *everything* little-endian, but this
doesn't make it worse.
Hmm, why *don't* we just
On Mon, Apr 21, 2008 at 9:57 PM, Thomas Cataldo
[EMAIL PROTECTED] wrote:
Hi,
I am running kvm-66 on top of a debian sid host with 2.6.24 (intel 32bit
host).
Got the following in my logs today :
Apr 21 17:55:01 buffy kernel: WARNING: at
/usr/src/modules/kvm/mmu.c:390
1 - 100 of 121 matches
Mail list logo