Wink Saville wrote:
> Hello,
>
> Based on the initial feed back I'm going to start trying to implement
> a PV block device that will use kshmem/ACE. What is the best
> way to track KVM development.
>
>
See http://kvm.qumranet.com/kvmwiki/Code.
--
error compiling committee.c: too many argumen
Wink Saville wrote:
>>
>> Most paravirtual devices use atomic operations (or even just raw memory
>> accesses and memory barriers), which don't need any special
>> infrastructure. This effectively makes them message-passing protocols
>> rather than shared memory protocol. I can't see offhand why
Gregory Haskins wrote:
>>
>>>
>>> vcpu- >cpu = - 1;
>>> vcpu- >kvm = kvm;
>>> @@ - 366,13 +370,20 @@ static void free_pio_guest_pages(struct kvm_vcpu
>>> *vcpu)
>>>
>>> static void kvm_free_vcpu(struct kvm_vcpu *vcpu)
>>> {
>>> + unsigned long irqsave;
>>> +
>>
Gregory Haskins wrote:
>
>>> +
>>> +static struct kvm_irqdevice *get_irq_dev(struct kvm_kernint *s)
>>> +{
>>> + struct kvm_irqdevice *dev;
>>> +
>>> + if (kvm_lapic_enabled(s- >vcpu))
>>> + dev = &s- >apic_irq;
>>> + else
>>> + dev = s- >ext_irq;
>>> +
>>> + if (!dev
Gregory Haskins wrote:
>
>> Hopefully not by setting the
>> signal number, bit by making the vcpu fd writable (userspace can attach
>> a signal to the fd if it wishes).
>>
>
> Can you provide an example of what you would like here? I am not quite sure
> what you mean by making the fd wr
Nguyen Anh Quynh wrote:
> This patch clarifies some "old version" error message, and deletes
> some unused functions in userspace code.
>
> Signed-off-by: Nguyen Anh Quynh <[EMAIL PROTECTED]>
>
Applied. Please send unrelated changes in different patches in the future.
--
error compiling committ
Nguyen Anh Quynh wrote:
> This patch installs kvm modules into drivers/kvm directory rather than
> in extra/
>
> Without this patch, I got a problem: after installing kvm (got from
> git repo), modprobe always found and picked kvm modules in drivers/kvm
> (ie old modules) instead the new ones (in
Jeff Chua wrote:
> Avi,
>
> Here's a little patch to silent ...
> - sdl-config when SDK is compiled without static library
> - texi2html when not found
>
>
As this is just a cleanup, and not strictly necessary, please post it to
qemu-devel so that we diverge as little as possible f
Michael Ivanov wrote:
> Avi Kivity пишет:
>
>
>> Well, it's supposed to be fixed in kvm-22. Are you 100% certain you
>> don't have leftover modules somewhere? Please load them with insmod
>> instead of modprobe.
>>
> I loaded modules using insmod directly from kvm-22/kernel and retested
[EMAIL PROTECTED] wrote:
> BTW, I have another patch in hand to further reduce MSR
> save/restore and
> thus
> improve performance more for lightweight VM Exit. Base on my
> observation for FC5 32 bits
> guest, 93% VM Exit will fall into the lightweight path.
>
This patch reduce the VM Exit handli
Dong, Eddie wrote:
> [EMAIL PROTECTED] wrote:
>
>> BTW, I have another patch in hand to further reduce MSR
>> save/restore and
>> thus
>> improve performance more for lightweight VM Exit. Base on my
>> observation for FC5 32 bits
>> guest, 93% VM Exit will fall into the lightweight path.
>>
>>
The recent performance enhancements caused another serious regression,
namely an oops while loading kvm-intel.ko on i386.
Changes from kvm-23:
- fix oops loading kvm-intel module on i386 with highmem
I will be traveling for the rest of this week and unable to introduce
new regressions, so kvm-2
>>> On Tue, May 8, 2007 at 4:13 AM, in message <[EMAIL PROTECTED]>,
Avi Kivity <[EMAIL PROTECTED]> wrote:
> Gregory Haskins wrote:
>>
>> I am perhaps being a bit overzealous here. What I found in practice is that
> the LVTT can screw things up on shutdown, so I was being pretty conservative
>
Avi Kivity wrote:
> Dong, Eddie wrote:
>> This patch reduce the VM Exit handling cost continuously
>> for those lightweight VM Exit which occupies 93% of VM Exit in
>> KB case if 64 bits OS has similar situation with 32 bits. In my old
>> machine, I saw 20% performance increasement of KB within 64
Gregory Haskins wrote:
On Tue, May 8, 2007 at 4:13 AM, in message <[EMAIL PROTECTED]>,
> Avi Kivity <[EMAIL PROTECTED]> wrote:
>
>> Gregory Haskins wrote:
>>
>>> I am perhaps being a bit overzealous here. What I found in practice is
>>> that
>>>
>> the LVTT ca
>>> On Tue, May 8, 2007 at 4:19 AM, in message <[EMAIL PROTECTED]>,
Avi Kivity <[EMAIL PROTECTED]> wrote:
> Gregory Haskins wrote:
>
>> By "drop it", I assume you mean drop the abstraction and just use native
> HRTIMER directly for now?
>>
>>
>
> Yes, we can worry about compatibility when
>>> On Tue, May 8, 2007 at 4:26 AM, in message <[EMAIL PROTECTED]>,
Avi Kivity <[EMAIL PROTECTED]> wrote:
> Gregory Haskins wrote:
>>
>>> Hopefully not by setting the
>>> signal number, bit by making the vcpu fd writable (userspace can attach
>>> a signal to the fd if it wishes).
>>>
>>
Avi Kivity пишет:
>> * ctrl alt does NOT release the pointer
>
> This is strange.
Just tested it again with kvm-24
The pointer is not released on ctrl del.
When the guest system reboots the system does not hang anymore though.
Is it possible to turn on some kind of trace/debug output to figure
hi,
What is the status of paravirtualization? Also when Ingo released his
paravirtualization patch and some results Avi noted that :
"Very impressive! The gain probably comes not only from avoiding the
vmentry/vmexit, but also from avoiding the flushing of the global page
tlb entries." [htt
Here is my latest series incorporating the feedback and numerous bugfixes. I
did not keep an official change-log, so its difficult to say what changed off
the top of my head without an interdiff. I will keep a changelog from here on
out. Lets call this drop officially "v1". I will start trackin
Signed-off-by: Gregory Haskins <[EMAIL PROTECTED]>
---
drivers/kvm/kvm.h | 60 +++
drivers/kvm/kvm_main.c | 94 ++--
2 files changed, 142 insertions(+), 12 deletions(-)
diff --git a/drivers/kvm/kvm.h b/drivers/kvm/k
The current code is geared towards using a user-mode (A)PIC. This patch adds
an "irqdevice" abstraction, and implements a "userint" model to handle the
duties of the original code. Later, we can develop other irqdevice models
to handle objects like LAPIC, IOAPIC, i8259, etc, as appropriate
Signe
The VCPU executes synchronously w.r.t. userspace today, and therefore
interrupt injection is pretty straight forward. However, we will soon need
to be able to inject interrupts asynchronous to the execution of the VCPU
due to the introduction of SMP, paravirtualized drivers, and asynchronous
hyper
Signed-off-by: Gregory Haskins <[EMAIL PROTECTED]>
---
drivers/kvm/kvm.h |2 +
drivers/kvm/kvm_main.c | 82
2 files changed, 84 insertions(+), 0 deletions(-)
diff --git a/drivers/kvm/kvm.h b/drivers/kvm/kvm.h
index 0f6cc32..b5bfc91 1006
Signed-off-by: Gregory Haskins <[EMAIL PROTECTED]>
---
drivers/kvm/Makefile |2
drivers/kvm/kernint.c | 149 +
drivers/kvm/kvm.h | 35 +
drivers/kvm/kvm_main.c | 179 +-
drivers/kvm/lapic.c| 1412
drivers/kvm/svm.c
Signed-off-by: Gregory Haskins <[EMAIL PROTECTED]>
---
drivers/kvm/irqdevice.h |3 +++
drivers/kvm/kvm.h |1 +
drivers/kvm/lapic.c | 15 +++
3 files changed, 19 insertions(+), 0 deletions(-)
diff --git a/drivers/kvm/irqdevice.h b/drivers/kvm/irqdevice.h
index 097d
Signed-off-by: Gregory Haskins <[EMAIL PROTECTED]>
---
drivers/kvm/vmx.c | 63 +
drivers/kvm/vmx.h |3 +++
2 files changed, 61 insertions(+), 5 deletions(-)
diff --git a/drivers/kvm/vmx.c b/drivers/kvm/vmx.c
index bee4831..1c99bc9 100644
Signed-off-by: Gregory Haskins <[EMAIL PROTECTED]>
---
drivers/kvm/vmx.c | 32 ++--
1 files changed, 26 insertions(+), 6 deletions(-)
diff --git a/drivers/kvm/vmx.c b/drivers/kvm/vmx.c
index 1c99bc9..7745bb9 100644
--- a/drivers/kvm/vmx.c
+++ b/drivers/kvm/vmx.c
@@
28 matches
Mail list logo
