Dor Laor wrote:
> Anthony Liguori wrote:
>> This is a PCI device that implements a transport for virtio. It
>> allows virtio
>> devices to be used by QEMU based VMMs like KVM or Xen.
>>
>>
>>
> While it's a little premature, we can st
Chen Xi wrote:
> Hi everybody,
>
> I'm trying to clone the repository:
>
> git-clone http://www.kernel.org/pub/scm/linux/kernel/git/avi/kvm.git kvm
>
You should clone with the git URL.
Regards,
Anthony Liguori
> Fail on this:
> error: Couldn't get
>
Dor Laor wrote:
> Anthony Liguori wrote:
>> This still needs quite a lot of work but I wanted to post it for
>> reference.
>>
>> Regards,
>>
>> Anthony Liguori
>>
>> diff --git a/qemu/Makefile.target b/qemu/Makefile.target
>>
> ...
Avi Kivity wrote:
> Anthony Liguori wrote:
>>>>>
>>>>>> +case VIRTIO_PCI_QUEUE_NOTIFY:
>>>>>> +if (val < VIRTIO_PCI_QUEUE_MAX)
>>>>>> +virtio_ring_kick(vdev, &vdev->vq[val]);
>>>>>&
Arnd Bergmann wrote:
> On Thursday 08 November 2007, Anthony Liguori wrote:
>
>> +/* A PCI device has it's own struct device and so does a virtio device so
>> + * we create a place for the virtio devices to show up in sysfs. I think it
>> + * would make more sens
add quite a lot of complexity. Just the
mechanism to setup the device is complicated enough. I suspect that
it'll be necessary down the road for performance but I certainly don't
think it's a simplification.
Regards,
Anthony Liguori
-
Avi Kivity wrote:
> Anthony Liguori wrote:
>> Avi Kivity wrote:
>>> Anthony Liguori wrote:
>>>
>>>> +case VIRTIO_PCI_QUEUE_NOTIFY:
>>>> +if (val < VIRTIO_PCI_QUEUE_MAX)
>>>> +virtio_ring_kick(vdev, &vdev-
rtio device showed up like a normal PCI device.
Am I misunderstanding what you're asking about?
Regards,
Anthony Liguori
>
>>> I think that with Amit's pvdma patches you
>>> can support dma-capable devices as well without too much fuss.
>>>
>>
>
Avi Kivity wrote:
> Anthony Liguori wrote:
>
>> +case VIRTIO_PCI_QUEUE_NOTIFY:
>> +if (val < VIRTIO_PCI_QUEUE_MAX)
>> +virtio_ring_kick(vdev, &vdev->vq[val]);
>> +break;
>>
>>
>
> I see you're not using h
Avi Kivity wrote:
> Anthony Liguori wrote:
>
>> This is a PCI device that implements a transport for virtio. It allows
>> virtio
>> devices to be used by QEMU based VMMs like KVM or Xen.
>>
>>
>>
>
> Didn't see support for dma.
No
This still needs quite a lot of work but I wanted to post it for reference.
Regards,
Anthony Liguori
diff --git a/qemu/Makefile.target b/qemu/Makefile.target
index 65f449e..3032337 100644
--- a/qemu/Makefile.target
+++ b/qemu/Makefile.target
@@ -448,6 +448,8 @@ VL_OBJS += rtl8139.o
# PCI
This patch moves virtio under the virtualization menu and changes virtio
devices to not claim to only be for lguest.
Signed-off-by: Anthony Liguori <[EMAIL PROTECTED]>
diff --git a/drivers/Kconfig b/drivers/Kconfig
index f4076d9..d945ffc 100644
--- a/drivers/Kconfig
+++ b/drivers/K
This patch series implements a PCI driver for virtio. This allows virtio
devices (like block and network) to be used in QEMU/KVM. I'll post a very
early KVM userspace backend in kvm-devel for those that are interested.
This series depends on the two virtio fixes I've posted and Rusty's config_op
This is a PCI device that implements a transport for virtio. It allows virtio
devices to be used by QEMU based VMMs like KVM or Xen.
Signed-off-by: Anthony Liguori <[EMAIL PROTECTED]>
diff --git a/drivers/virtio/Kconfig b/drivers/virtio/Kconfig
index 9e33fc4..c81e0f3 100644
--- a/drivers/
This is needed for the virtio PCI device to be compiled as a module.
Signed-off-by: Anthony Liguori <[EMAIL PROTECTED]>
diff --git a/drivers/virtio/virtio_ring.c b/drivers/virtio/virtio_ring.c
index 0e1bf05..3f28b47 100644
--- a/drivers/virtio/virtio_ring.c
+++ b/drivers/virtio/virtio_
I'm assuming this should be very easy to replicate for anyone running kvm-50
> or older with the tpr patch and an acpi hal windows.
>
Are you using the TPR patch and if so, which one are you using?
Regards,
Anthony Liguori
> -
Alexey Eremenko wrote:
>
> It seems nice !
>
> But is there any documentation ? I don't know how-to start it.
>
http://kvm.qumranet.com/kvmwiki/KVMTest
Let me know if that's not sufficient to get you going.
Regards,
Ant
Avi Kivity wrote:
> Anthony Liguori wrote:
>> Dong, Eddie wrote:
>>> Anthony Liguori wrote:
>>>
>>>> Dong, Eddie wrote:
>>>>
>>>>>> BTW, is it wise to enable this by default for all guests?
>>>>>> I
n.
>>
>>
>>
>
> A bug was fixed in mainline for this issue, so it is not related to the
> optimization. I still need to make sure it doesn't harm 64-bit Windows.
>
Does 64-bit Windows ever access
Avi Kivity wrote:
> Anthony Liguori wrote:
>
>> Hi,
>>
>> I've finally gotten around to incorporating the feedback from KVM Forum
>> into kvm-test. I think it's ready for more people to use now. kvm-test
>> allows the user to record a KVM sessio
ed by tglx.
Signed-off-by: Anthony Liguori <[EMAIL PROTECTED]>
diff --git a/drivers/kvm/kvm_main.c b/drivers/kvm/kvm_main.c
index 9a3d663..5ce0754 100644
--- a/drivers/kvm/kvm_main.c
+++ b/drivers/kvm/kvm_main.c
@@ -1028,7 +1028,10 @@ int kvm_is_visible_gfn(struct kvm *kvm
er is also developing an autotest harness to allow kvm-test to
be run nightly.
Feedback is, as always, appreciated.
http://kvm.qumranet.com/kvmwiki/KVMTest
Regards,
Anthony Liguori
-
This SF.net email is sponsored by:
Anthony Liguori wrote:
> Luca Tettamanti wrote:
>> On 10/29/07, Denys Duchier <[EMAIL PROTECTED]> wrote:
>>
>>> qemu doesn't quit (no poweroff?) on halt for linux 2.6.23 x86 guests
>>> (confirmed
>>> by danieldg on irc), but it works for 64
BIOSes shipped before 2001 are
> blacklisted because they tend to be very broken).
>
This would require CONFIG_ACPI_BLACKLIST_YEAR=2001. In my kernel
config, it's set to 0 and my guests still don't shut off so I think
there's more to it than just this.
Regards,
Anthony Liguor
Hollis Blanchard wrote:
> On Sun, 2007-10-28 at 22:50 -0500, Anthony Liguori wrote:
>
>> You could certainly get even more clever and have the arch backend
>> register the appropriate tables based on the as type but that's merely
>> an implementation detail.
Dong, Eddie wrote:
> Anthony Liguori wrote:
>
>> Dong, Eddie wrote:
>>
>>>> BTW, is it wise to enable this by default for all guests?
>>>> Ignoring the
>>>> fact that we're modifying guest's memory without its knowledge, if a
Hollis Blanchard wrote:
> On Mon, 2007-10-29 at 10:41 +0800, Zhang, Xiantao wrote:
>
>> Anthony Liguori wrote:
>>
>>> Hollis Blanchard wrote:
>>>
>>>>> I don't know the privious story about this thread, but now I can't
&
Hollis Blanchard wrote:
> On Sun, 2007-10-28 at 21:11 -0500, Anthony Liguori wrote:
>
>> int (*io_write)(void *opaque, int as, uint64_t addr, uint64_t data,
>> int size);
>>
>> Where as is a #define representing the address space (on x86, there is
>> the
probably be the same too. That pretty much covers the
majority of the callbacks structure :-)
Regards,
Anthony Liguori
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
y (For MMIO devices)
> -int (*writeq)(void *opaque, uint64_t addr, uint64_t data);
>
With a little refactoring, this can be made into something sharable for
all architectures. I'd recommend converting to something like:
int (*io_write)(void *opaque, int as, uint64_t addr,
a part of the architecture
specific structure (just like is done in the kernel code).
Regards,
Anthony Liguori
> Signed-off-by: Jerone Young <[EMAIL PROTECTED]>
>
> diff --git a/user/kvmctl-x86.h b/user/kvmctl-x86.h
> --- a/user/kvmctl-x86.h
> +++ b/user/kvmctl-x86.
good
idea to upgrade to a newer version of KVM. If you can't find an option
for enabling virtualization in your BIOS, you may need to update the
BIOS or contact your manufacture.
Regards,
Anthony Liguori
> -
&g
dows XP with -smp 2.
Regards,
Anthony Liguori
> On 10/26/07, * Anthony Liguori* <[EMAIL PROTECTED]
> <mailto:[EMAIL PROTECTED]>> wrote:
>
> Haydn Solomon wrote:
> > Were you able to do this with -smp 2 or more?
>
> I get a BSOD with -smp 2. But I
Haydn Solomon wrote:
> Were you able to do this with -smp 2 or more?
I get a BSOD with -smp 2. But I haven't yet been able to confirm that
this is a regression.
Since the TPR optimization makes the install go over 2x as fast, it's
throwing off my automated tests.
Regards,
An
Haydn Solomon wrote:
> Were you able to do this with -smp 2 or more?
I haven't tried doing smp testing yet. But I can do that now.
Regards,
Anthony Liguori
> On 10/26/07, *Anthony Liguori* <[EMAIL PROTECTED]
> <mailto:[EMAIL PROTECTED]>> wrote:
>
> With t
(i386)
Ubuntu 7.04 desktop (x86_64)
Ubuntu 7.10 desktop (i386)
It's looking pretty good to me.
Regards,
Anthony Liguori
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?
ur.
>>
>>
> Good movement!
>
> But, Vista won't work with patching. The memory guard in vista
> will make the system refuse to service. Maybe we need a option
> to check if it is vista.
>
FWIW, I successfully installed and booted Vista Enterprise Ed
Avi Kivity wrote:
> Anthony Liguori wrote:
>> Avi Kivity wrote:
>>
>>> Anthony Liguori wrote:
>>>
>>>>>> static int mmu_topup_memory_caches(struct kvm_vcpu *vcpu)
>>>>>> {
>>>>>> int r;
>&
Avi Kivity wrote:
> Anthony Liguori wrote:
>> Avi Kivity wrote:
>>> Anthony Liguori wrote:
>>>>>
>>>>> Good movement!
>>>>>
>>>>> But, Vista won't work with patching. The memory guard in vista
>>>>
Avi Kivity wrote:
> Anthony Liguori wrote:
>>>
>>> Good movement!
>>>
>>> But, Vista won't work with patching. The memory guard in vista will
>>> make the system refuse to service. Maybe we need a option
>>> to check if it is vista.
p/driver load? Seems odd to periodically scan memory.
In the recently released Windows Hypervisor specification, in section
13.2.2 (Local APIC Memory-mapped Accesses), it's dictated that the APIC
can only be accessed through 6 instructions. They are all >= 5 byte
instructions. When
Avi Kivity wrote:
Anthony Liguori wrote:
static int mmu_topup_memory_caches(struct kvm_vcpu *vcpu)
{
int r;
kvm_mmu_free_some_pages(vcpu);
r = mmu_topup_memory_cache(&vcpu->mmu_pte_chain_cache,
pte_chain_cache, 4);
if (r)
goto out
Avi Kivity wrote:
> Anthony Liguori wrote:
>>>
>>>> static int mmu_topup_memory_caches(struct kvm_vcpu *vcpu)
>>>> {
>>>> int r;
>>>>
>>>> kvm_mmu_free_some_pages(vcpu);
>>>> r = mmu_topup_memory_cache(
Avi Kivity wrote:
> Anthony Liguori wrote:
>> Avi Kivity wrote:
>>> Haydn Solomon wrote:
>>>
>>>> I also had a problem installing windows xp. Got the following error
>>>>
>>>
>>>
>>> I guess I'll have to test
last time it was almost immediately). This is
with your updated tree. I'll next try to reproduce with the latest git.
Regards,
Anthony Liguori
[ 1577.621100] [ cut here ]
[ 1577.621106] kernel BUG at /home/anthony/tmp/2/tpr-opt-1/kernel/mmu.c:308!
[ 1
BTW, is it wise to enable this by default for all guests? Ignoring the
fact that we're modifying guest's memory without its knowledge, if a
guest unmaps the VA mappings for the BIOS then all sorts of problems
could occur.
Regards,
Anthony Liguori
-
Avi Kivity wrote:
> Anthony Liguori wrote:
>> Avi Kivity wrote:
>>> This is a request for testing of an experimental kvm feature that
>>> dramatically accelerates some Windows releases (when running with
>>> the ACPI HAL, and especially with guest SMP). The
ting
goes.
Regards,
Anthony Liguori
diff -ur a/qemu/qemu-kvm.h b/qemu/qemu-kvm.h
--- a/qemu/qemu-kvm.h 2007-10-25 11:55:25.0 -0500
+++ b/qemu/qemu-kvm.h 2007-10-25 12:48:38.0 -0500
@@ -30,7 +30,6 @@
#define ALIGN(x, y) (((x)+(y)-1) & ~((y)-1))
#define BITMAP_SIZE
Avi Kivity wrote:
> Anthony Liguori wrote:
>> I'm building some kvm-test harnesses and noticed an issue when
>> installing Windows on my Core 2 Duo laptop. After the first reboot
>> during the installation, after the prompt to press any key to boot
>> from CD,
known issue? I know there were some issues with reboot in VT
but I thought they were resolved. I vaguely remember running into this
before and just restarting KVM to work around it but that's not an
option here. Has this worked for others in the past?
Regards,
Antho
gards,
Anthony Liguori
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of S
The recent paravirt refactoring broke external modules. This patch fixes that.
Signed-off-by: Anthony Liguori <[EMAIL PROTECTED]>
diff --git a/kernel/Makefile b/kernel/Makefile
index ebb2903..b78c81a 100644
--- a/kernel/Makefile
+++ b/kernel/Makefile
@@ -26,6 +26,8 @@ sync:
lag, on s390 it won't help.
>
While both PPC and x86 may be able to use it, I doubt there will
actually be common code that ever touches it.
Regards,
Anthony Liguori
> Arnd <><
>
> -
>
Hollis Blanchard wrote:
> On Thu, 2007-10-18 at 16:31 -0500, Anthony Liguori wrote:
>
>> Hollis Blanchard wrote:
>>
>>> On Thu, 2007-10-18 at 16:04 -0500, Anthony Liguori wrote:
>>>
>>>
>>>> Hollis Blanchard wrot
Hollis Blanchard wrote:
> On Thu, 2007-10-18 at 16:04 -0500, Anthony Liguori wrote:
>
>> Hollis Blanchard wrote:
>>
>>> What is the problem with
>>> embedding an architecture-specific sub-structure, i.e.
>>> struct kvm_vcpu {
>&
*/
};
struct vcpu_svm {
struct kvm_vcpu vcpu;
/* svm specific stuff */
};
But we should move to:
struct kvm_vcpu {
/* stuff common to x86/ppc/ia64 */
};
struct vcpu_x86 {
struct kvm_vcpu vcpu;
/* stuff common to vt/svm */
}
struct vcpu_svm {
struct vcpu_x86 vcpu;
/* svm specifi
retty hard to reasonably review since diff is so large.
A quick glance suggests that there's a lot of code duplication between
things like main-x86.c and main-ppc.c. Perhaps the common code could be
unified?
Regards,
Anthony Liguori
Weird... guilt stripped the diffstat. It should be:
kvm.h |2 -
kvm_main.c | 83
++---
2 files changed, 30 insertions(+), 55 deletions(-)
Regards,
Anthony Liguori
Anthony Liguori wrote:
> Allocate a userspace buffer
gt; Since v1, fixed a bug in slot creation.
>>
>> I send the previous patch in response to a mail instead of top level so I'm
>> resending properly.
>>
>>
>>
>
>
> This is really nice, especially the diffstat.
>
Time to update patchbomb scrip
: Anthony Liguori <[EMAIL PROTECTED]>
diff --git a/drivers/kvm/kvm.h b/drivers/kvm/kvm.h
index 53b2d58..eb086e9 100644
--- a/drivers/kvm/kvm.h
+++ b/drivers/kvm/kvm.h
@@ -407,10 +407,8 @@ struct kvm_memory_slot {
gfn_t base_gfn;
unsigned long npages;
unsigned long
I'm
resending properly.
Signed-off-by: Anthony Liguori <[EMAIL PROTECTED]>
diff --git a/drivers/kvm/kvm.h b/drivers/kvm/kvm.h
index 53b2d58..eb086e9 100644
--- a/drivers/kvm/kvm.h
+++ b/drivers/kvm/kvm.h
@@ -407,10 +407,8 @@ struct kvm_memory_slot {
gfn_t base_gfn;
un
It appears that a good number of KVM commits never make their way to
kvm-commits.
For instance, I don't see Izik's recent overcommit patches
(1253f76f37189f0bfda7e4a46bfe537f329dc0db)
Regards,
Anthony Liguori
. While preserving behavior.
>
This one looks a lot better to me.
Thanks,
Anthony Liguori
> Signed-off-by: Jerone Young <[EMAIL PROTECTED]>
>
> diff --git a/configure b/configure
> --- a/configure
> +++ b/configure
> @@ -3,32 +3,32 @@ prefix=/usr/local
> prefix
Jerone Young wrote:
> On Tue, 2007-10-16 at 09:59 -0500, Anthony Liguori wrote:
>
>> Jerone Young wrote:
>>
>>> On Mon, 2007-10-15 at 15:13 -0500, Anthony Liguori wrote:
>>>
>>>
>>>
>>>>> +fi
>>>>
Avi Kivity wrote:
> Anthony Liguori wrote:
>> Izik Eidus wrote:
>>
>>>> That's not quite what I was wondering.
>>>>
>>>> When you do an madvise() in userspace, the result is that when that
>>>> memory is accessed again, linux
s on what the configuration is. IMHO, just relying on SDL to pick
the Right Thing is best because that's a choice that was made by the
distribution so presumably it's whatever works the best on the given system.
Regards,
Anthony Liguori
> to :
>
> QEMU_AUDIO_DRV=sdl
> S
Jerone Young wrote:
> On Mon, 2007-10-15 at 15:13 -0500, Anthony Liguori wrote:
>
>
>>> +fi
>>> +
>>> +qemudir=`pwd`/qemu
>>> +
>>> +#configure user dir
>>> +(cd user; ./configure --prefix="$prefix" --kerneldir=&quo
>>
>>
>
> If audio output is going to sdl anyway, then this has no effect on most
> users, right?
>
Yes.
> If so I prefer being closer to qemu as you suggest.
>
Me too.
Regards,
Anthony Liguori
--
Izik Eidus wrote:
> Anthony Liguori wrote:
>> Very nice!
>>
>> This series seems to have solved the problem for me.
>>
>> Izik Eidus wrote:
>>> this patch remove all the ugly messages from the dmesg,
>>> now i think my patch together with Antho
mb for one final review? Right now I'm using patches from a few
different sets. I'll also run some tests on it.
Also, did your updated 3/4 patch fix the Fedora rmap problem?
Regards,
Anthony Liguori
> thanks to Anthony with his he
Jerone Young wrote:
> On Mon, 2007-10-15 at 15:13 -0500, Anthony Liguori wrote:
>
>> Jerone Young wrote:
>>
>>> This patch is an improved version of patches sent last week to enable
>>> the top level configuration file for cross compile. This curren
> +# look for gcc version 3.x
> +if [[ -z "$qemu_cc" ]] && [[ -z "$cross_prefix" ]]; then
> +#check for a gcc 3.x version on the system
> +cc_check=$(ls /usr/bin/gcc3* /usr/bin/gcc-3* 2>/dev/null | tail -n1)
> +#prefer gcc if its version is 3.*
p() is initiated from
userspace. We could just add an ioctl() to do it from userspace but I
think it would be nicer if it Just Worked.
Regards,
Anthony Liguori
>
>
>
>
-
This SF.net email is sponsored by:
Izik Eidus wrote:
> Anthony Liguori wrote:
>> Izik Eidus wrote:
>>> Anthony Liguori wrote:
>>>> I've been playing around with these patches. If I do an
>>>> madvise(MADV_DONTNEED) in userspace, when I close the VM, I get the
>>>>
Anthony Liguori wrote:
Izik Eidus wrote:
Anthony Liguori wrote:
I think it's just a matter of calling do_mmap() with the appropriate
parameters. It looks likes there's some drivers call do_mmap()
directly.
yea, i think you right, this is excellent idea!, when we will merge
th
Izik Eidus wrote:
> Anthony Liguori wrote:
>> I've been playing around with these patches. If I do an
>> madvise(MADV_DONTNEED) in userspace, when I close the VM, I get the
>> following bug. My knowledge of the mm is limited but since
>> madvise(M
y callback to also remove any potential GPA
covered by that range from shadow page cache.
Regards,
Anthony Liguori
[ 860.724555] rmap_remove: 81004c48cf00 506d1025 0->BUG
[ 860.724603] [ cut here ]
[ 860.724606] kernel BUG at
/home/anthony/git/fresh/kvm-userspace
Avi Kivity wrote:
> Anthony Liguori wrote:
>> Avi Kivity wrote:
>>> Anthony Liguori wrote:
>>>
>>>> I think it's just a matter of calling do_mmap() with the
>>>> appropriate parameters. It looks likes there's some drivers call
>
Avi Kivity wrote:
> Anthony Liguori wrote:
>
>> I think it's just a matter of calling do_mmap() with the appropriate
>> parameters. It looks likes there's some drivers call do_mmap() directly.
>>
>>
>>
>
> This will halve the maximu
Izik Eidus wrote:
Anthony Liguori wrote:
I think it's just a matter of calling do_mmap() with the appropriate
parameters. It looks likes there's some drivers call do_mmap()
directly.
yea, i think you right, this is excellent idea!, when we will merge
the swapping to kvm, w
Anthony Liguori wrote:
> Very nice!
>
> I've tested this series (with your new 3/4) with win2k, winxp, ubuntu
> 7.10, and opensuse. Everything seemed to work just fine.
Spoke too soon, found the following in dmesg:
[35078.913071] BUG: scheduling while atomic:
qemu-system-x86
Very nice!
I've tested this series (with your new 3/4) with win2k, winxp, ubuntu
7.10, and opensuse. Everything seemed to work just fine.
I also was able to create four 1G VMs on my 2G laptop :-) That was very
neat.
Regards,
Anthony Liguori
Izik Eidus wrote:
> this patchs allow t
Izik Eidus wrote:
> Anthony Liguori wrote:
>> Izik Eidus wrote:
>>> Izik Eidus wrote:
>>>> Anthony Liguori wrote:
>>>>> Izik Eidus wrote:
>>>>>>
>>>>>> @@ -1058,8 +1038,27 @@ struct page *gfn_to_page(st
Izik Eidus wrote:
> Izik Eidus wrote:
>> Anthony Liguori wrote:
>>> Izik Eidus wrote:
>>>> this patchs allow the guest not shadowed memory to be swapped out.
>>>>
>>>> to make it the must effective you should run -kvm-shadow-memory 1
>>
Izik Eidus wrote:
> Izik Eidus wrote:
>> Anthony Liguori wrote:
>>> Izik Eidus wrote:
>>>>
>>>> @@ -1058,8 +1038,27 @@ struct page *gfn_to_page(struct kvm *kvm,
>>>> gfn_t gfn)
>>>>
>>>> gfn = unalias_g
r
> + + (gfn - slot->base_gfn) * PAGE_SIZE, 1,
> + 1, 0, page, NULL);
> + up_read(¤t->mm->mmap_sem);
> + if (npages != 1) {
> + get_page(bad_page);
> +
orth exposing it as
an option if it slows down guests so much?
At least, a better name for the option would be nice.
Regards,
Anthony Liguori
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log f
Hollis Blanchard wrote:
> On Fri, 2007-10-12 at 15:02 -0500, Anthony Liguori wrote:
>
>> Hollis Blanchard wrote:
>>
>>> On Fri, 2007-10-12 at 13:08 -0300, Glauber de Oliveira Costa wrote:
>>>
>>>
>>>> +conf
TSC that changes frequencies. A PV time source gives you more
stable clocksource (although as in glommer's patch, when the TSC can be
used, it's better to use it).
3) a PV clock can support stolen time calculation which there really
isn't a concept of with emulation.
Regards,
t; +#ifdef CONFIG_KVM_CLOCK
>> +kvmclock_init();
>> +#endif
>>
>>
>
> Why is this necessary? Can't you hook one of the existing pvops?
>
Something needs to install the pvops in the first place. Inste
Avi Kivity wrote:
> Anthony Liguori wrote:
>
>> Now that we have userspace memory allocation, I wanted to play with
>> ballooning.
>> The idea is that when a guest "balloons" down, we simply unpin the underlying
>> physical memory and the host ke
@@ -51,7 +59,9 @@ int kvm_cpu_get_interrupt(struct kvm_vcpu *v)
> struct kvm_pic *s;
> int vector;
>
> - vector = kvm_get_apic_interrupt(v); /* APIC */
> + vector = kvm_get_pvclock_interrupt(v);
> + if (vector == -1)
> +
othing wrong with s390 not supporting multiple memory slots, but
there's no reason the ioctl interface can't be the same.
Regards,
Anthony Liguori
> Looks to me like the s390 might have a lot in common with a future AMD
> nested page table implementation. If AMD choose to reuse th
me would be to not use
get_user_pages() on all memory to start with and instead, allow pages to
be faulted in on use. This is particularly useful for creating a VM
with a very large amount of memory, and immediately ballooni
Now that we have userspace memory allocation, I wanted to play with ballooning.
The idea is that when a guest "balloons" down, we simply unpin the underlying
physical memory and the host kernel may or may not swap it. To reclaim
ballooned memory, the guest can just start using it and we'll pin it
tested and works on my machine):
>
This patch works for me under KVM. Thanks!
Regards,
Anthony Liguori
> --- bincode.asm (revision 650)
> +++ bincode.asm (working copy)
> @@ -15546,7 +15546,11 @@
> mov ax,pm_seg.prog_d16
> mov ds,ax
>
Christian Borntraeger wrote:
>
> I agree. It seems I can simply remove the kvm_hypercall macro.
>
> Here is the updated patch (without the s390 parts. Will send them later
> when ready) and the changes mentioned above.
>
> Avi, Anthony, comments?
>
It looks good t
LL_FOO);
Is a lot more understandable than:
kvm_hypercall(0, KVM_HYPERCALL_FOO);
It's much harder to guess with the later what the significance of the
first parameter is.
Regards,
Anthony Liguori
> +#endif
> #endif
> Index: kvm/include/asm-s390/kvm_para.h
> ==
s are visible immediately.
>>
>>
>
> OK, that is about sharing memory file. How about a shared file in
> which a file is a real physical file on the host?
>
> As far as I remember, there is a caution about sharing a file using
> mmap() between 2 processes, that is: if
This time, the biggest change is gpa_to_hpa. The translation of GPA to HPA does
not depend on the VCPU state unlike GVA to GPA so there's no need to pass in
the kvm_vcpu.
Signed-off-by: Anthony Liguori <[EMAIL PROTECTED]>
diff --git a/drivers/kvm/kvm.h b/drivers/kvm/kvm.h
index 4ab48
501 - 600 of 1040 matches
Mail list logo
