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 wrote:
> What is the problem with
> embed
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 wrote:
> >>
> >>> What is the problem with
> >>> embedding an architecture-specific sub-structure, i.e.
> >>> s
On Oct 18, 2007, at 3:11 PM, Jerone Young wrote:
> This patch contains a small set of simple tests for testing guest
> functionality for powerpc.
>
>
> Signed-off-by: Jerone Young <[EMAIL PROTECTED]>
some of these tests should be marked a 44x specific (any tlb related
ones)
- k
-
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 arch_k
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 arch_kvm_vcpu arch_vcpu;
> > };
> >
Hollis Blanchard wrote:
> On Thu, 2007-10-18 at 15:34 +0800, Zhang, Xiantao wrote:
>
>> Hi Avi,
>> According to your and community's suggestions, I changed the kvm_vcpu
>> structure to two parts. To avoid the much intrusive into current code,
>> one is common part which is defined as a macro, an
On Thu, 2007-10-18 at 22:47 +0200, Izik Eidus wrote:
> Jerone Young wrote:
> > diff --git a/user/kvmctl-powerpc.c b/user/kvmctl-powerpc.c
> > new file mode 100644
> > --- /dev/null
> > +++ b/user/kvmctl-powerpc.c
> > @@ -0,0 +1,351 @@
> > +/*
> > + * This program is free software; you can redistri
Jerone Young wrote:
> diff --git a/user/kvmctl-powerpc.c b/user/kvmctl-powerpc.c
> new file mode 100644
> --- /dev/null
> +++ b/user/kvmctl-powerpc.c
> @@ -0,0 +1,351 @@
> +/*
> + * This program is free software; you can redistribute it and/or modify
> + * it under the terms of the GNU General Publ
On Tuesday 16 October 2007, Avi Kivity wrote:
> Jan Frey wrote:
> >> Can you set up netconsole or serial console on that machine and grab
> >> the kernel output?
> >
> > Currently I don't have really much time.. could you point me to some
> > guide or manual about what to do exactly? I'll try to do
Ok, so some useful feedback :-). I'm going to rework these patches
completely. Have them share a LOT more then these now. Which is
basically a total spilt.
On Thu, 2007-10-18 at 15:40 -0500, Hollis Blanchard wrote:
> On Thu, 2007-10-18 at 15:37 -0500, Jerone Young wrote:
> > On Thu, 2007-10-18 at
On Thu, 2007-10-18 at 15:37 -0500, Jerone Young wrote:
> On Thu, 2007-10-18 at 15:28 -0500, Anthony Liguori wrote:
> >
> > 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?
>
> I do ha
On Thu, 2007-10-18 at 15:28 -0500, Anthony Liguori wrote:
> Jerone Young wrote:
> > This patch splits kvmctl architecture specific declarations &
> > implementations into their own files & headers. Common interfaces are
> > kept in kvmctl.h, as well as the arch specific headers are included from
>
Jerone Young wrote:
> This patch splits kvmctl architecture specific declarations &
> implementations into their own files & headers. Common interfaces are
> kept in kvmctl.h, as well as the arch specific headers are included from
> within kvmctl.h. This may or may not want to be changed.
>
> Also
This patch contains a small set of simple tests for testing guest
functionality for powerpc.
Signed-off-by: Jerone Young <[EMAIL PROTECTED]>
diff --git a/user/test/powerpc/io.S b/user/test/powerpc/io.S
new file mode 100644
--- /dev/null
+++ b/user/test/powerpc/io.S
@@ -0,0 +1,32 @@
+#def
This patch moves make rules around to accommodate for powerpc or any
none x86 architecture. This patch also adds file
user/config-powerpc.mak. Also added $CROSS_COMPILE variable is added to
the config.mak generated to configure script.
Signed-off-by: Jerone Young <[EMAIL PROTECTED]>
diff --git a
On Thu, 2007-10-18 at 15:34 +0800, Zhang, Xiantao wrote:
> Hi Avi,
> According to your and community's suggestions, I changed the kvm_vcpu
> structure to two parts. To avoid the much intrusive into current code,
> one is common part which is defined as a macro, and the other one is
> arch-specific
Acked-by: Laurent Vivier <[EMAIL PROTECTED]>
Christian Borntraeger a écrit :
> Seems I overlooked this type while reviewing Laurents patch.
> cputime_add already adds, dont do it twice.
>
> Avi. This should go to Linus before 2.6.24.
>
> Signed-off-by: Christian Borntraeger <[EMAIL PROTECTED]>
>
On Wed, Oct 17, 2007 at 06:55:02PM +0200, Avi Kivity wrote:
> Carlo Marcelo Arenas Belon wrote:
> > This series adds options to kvm's configure that match the ones used by qemu
> > to conditionally enable or disable options that alter its runtime
> > dependencies
> > and functionality, like for ex
That was quick! Don't have this problem with kvm48 anymore.
On 10/18/07, Haydn Solomon <[EMAIL PROTECTED]> wrote:
>
> Good day. First thanks for release 47. This is to report a problem with
> kvm-47 where my host locked up upon shutdown of windows 32 bit xp guest.
> Guest was running for about 1
Seems I overlooked this type while reviewing Laurents patch.
cputime_add already adds, dont do it twice.
Avi. This should go to Linus before 2.6.24.
Signed-off-by: Christian Borntraeger <[EMAIL PROTECTED]>
---
fs/proc/array.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: linu
kvm-47 had a host memory corruption bug when setting the guest pte dirty
bit, so here's kvm-48 with a fix.
Note that guest time accounting, below, will only work with Linux 2.6.24+.
Changes from kvm-47:
- use precise cpu accounting on ppc and s390 (Christian Borntraeger)
- make guest time accoun
Gerd Hoffmann wrote:
>
>>> Should I send an updated patch or do you just drop these lines when
>>> merging?
>>>
>> Please send a rebased and retested patch.
>>
>
> Oh, -47 is there. Updated patch attached.
>
>
Applied. But please:
- always supply the changelog comment so I don't
Good day. First thanks for release 47. This is to report a problem with
kvm-47 where my host locked up upon shutdown of windows 32 bit xp guest.
Guest was running for about 15 min before shutdown. Host locked up when
guest was at "you may now turn off your machine" screen.
Host Details:
=
Anthony Liguori wrote:
> Allocate a userspace buffer for older userspaces. Also eliminate phys_mem
> buffer. The memset() in kvmctl really kills initial memory usage but swapping
> does even with old userspaces.
>
Applied, thanks.
--
error compiling committee.c: too many arguments to functi
Anthony Liguori wrote:
>>
>>
>> This is really nice, especially the diffstat.
>>
>
> Time to update patchbomb script...
>
I meant I like the number of lines deleted by the patch, not a subtle
hint that I want diffstats. Diffstats are for people who don't read
patches.
--
error compiling c
Avi Kivity wrote:
> Gerd Hoffmann wrote:
>> No, I'm hacking up one more user ;)
>
> Nice. What will it do?
Run xenified guest kernels without Xen.
>> Should I send an updated patch or do you just drop these lines when
>> merging?
>
> Please send a rebased and retested patch.
Oh, -47 is there.
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 for older
Avi Kivity wrote:
> dAnthony Liguori wrote:
>
>> Allocate a userspace buffer for older userspaces. Also eliminate phys_mem
>> buffer. The memset() in kvmctl really kills initial memory usage but
>> swapping
>> does even with old userspaces.
>>
>> Since v1, fixed a bug in slot creation.
>>
>>
On Thu, 2007-10-18 at 09:05 -0500, Anthony Liguori wrote:
> Allocate a userspace buffer for older userspaces. Also eliminate phys_mem
> buffer. The memset() in kvmctl really kills initial memory usage but swapping
> does even with old userspaces.
>
> Since v1, fixed a bug in slot creation.
>
>
Allocate a userspace buffer for older userspaces. Also eliminate phys_mem
buffer. The memset() in kvmctl really kills initial memory usage but swapping
does even with old userspaces.
Since v1, fixed a bug in slot creation.
Since v2, changed the error checking to use IS_ERR().
Signed-off-by: An
dAnthony Liguori wrote:
> Allocate a userspace buffer for older userspaces. Also eliminate phys_mem
> buffer. The memset() in kvmctl really kills initial memory usage but swapping
> does even with old userspaces.
>
> Since v1, fixed a bug in slot creation.
>
> I send the previous patch in respons
Allocate a userspace buffer for older userspaces. Also eliminate phys_mem
buffer. The memset() in kvmctl really kills initial memory usage but swapping
does even with old userspaces.
Since v1, fixed a bug in slot creation.
I send the previous patch in response to a mail instead of top level so
Zhang, Xiantao wrote:
> Hi Avi,
> According to your and community's suggestions, I changed the kvm_vcpu
> structure to two parts. To avoid the much intrusive into current code,
> one is common part which is defined as a macro, and the other one is
> arch-specific part.
> In addition, I have a sug
Anthony Liguori wrote:
> 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)
>
>
If I commit through git-am, it doesn't show up. If I start a rebase,
l
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
-
This SF.ne
On Thu, 2007-10-18 at 18:07 +0200, Oliver Kowalke wrote:
> Hello,
> I'm using the newest linux kernel (2.6.23.1) but as I could read in some
> emials - I should use the newest kvm modules.
> (Because kvm crashes if I install OpenSolaris Express as guest on Linux -
> with -no-kvm installation work
Hello,
I'm using the newest linux kernel (2.6.23.1) but as I could read in some
emials - I should use the newest kvm modules.
(Because kvm crashes if I install OpenSolaris Express as guest on Linux -
with -no-kvm installation works).
Could you tell me where can I download the newst one?
regards,
Bugs item #1815804, was opened at 2007-10-18 15:55
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1815804&group_id=180599
Please note that this message will contain a full copy
Avi Kivity a écrit :
> Laurent Vivier wrote:
>> According comments from Avi, we can clear PF_VCPU in kvm_guest_exit if we
>> move
>> it after local_irq_enable().
>>
>> http://lkml.org/lkml/2007/10/15/114
>>
>> To simplify s390 port, we don't clear it in account_system_time().
>>
>> http://lkml.org
Laurent Vivier wrote:
> According comments from Avi, we can clear PF_VCPU in kvm_guest_exit if we move
> it after local_irq_enable().
>
> http://lkml.org/lkml/2007/10/15/114
>
> To simplify s390 port, we don't clear it in account_system_time().
>
> http://lkml.org/lkml/2007/10/15/183
>
Applied
According comments from Avi, we can clear PF_VCPU in kvm_guest_exit if we move
it after local_irq_enable().
http://lkml.org/lkml/2007/10/15/114
To simplify s390 port, we don't clear it in account_system_time().
http://lkml.org/lkml/2007/10/15/183
---
drivers/kvm/kvm_main.c |5 -
kernel
Dong, Eddie wrote:
>
>> benefit is
>> removing the lapic calculations from the critical section.
>>
>> But I still don't understand your object. The interrupt has to be
>> committed sometime. We move the commit point earlier by the time it
>> takes to ->prepare_guest_switch() (normally zero, but
Christian Borntraeger wrote:
> ppc and s390 offer the possibility to track process times precisely
> by looking at cpu timer on every context switch, irq, softirq etc.
> We can use that infrastructure as well for guest time accounting.
> We need to account the used time before we change the state.
Avi,
ppc and s390 offer the possibility to track process times precisely
by looking at cpu timer on every context switch, irq, softirq etc.
We can use that infrastructure as well for guest time accounting.
We need to account the used time before we change the state.
This patch adds a call to acco
Gerd Hoffmann wrote:
> Hi,
>
>
>> Break it. It has just one user, our qemu, which is included in the same
>> package.
>>
>
> No, I'm hacking up one more user ;)
>
>
Nice. What will it do?
> But maybe I'm better off shipping a private copy of kvmctl.c as long as
> the library interf
Hi,
> Break it. It has just one user, our qemu, which is included in the same
> package.
No, I'm hacking up one more user ;)
But maybe I'm better off shipping a private copy of kvmctl.c as long as
the library interface isn't finalized yet and subject to change.
>> Thats why I went the route
Today's news includes partial support for swapping. You can now run
guests with more memory than you have on the host, and Linux will page
them out to the swap file. The support is partial in that the guest
will still pin a substantial amount of memory.
Changes from kvm-46:
- Reset fixes (Edd
Bugs item #1815704, was opened at 2007-10-18 13:24
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1815704&group_id=180599
Please note that this message will contain a full copy
Gerd Hoffmann wrote:
>
>>> anyone who use kvmctl, should not call kvm_create_userspace_memory
>>> directly, instead should call kvm_create()...
>>>
>
> I'm talking about the kvm_create() interface, dammit. Sure I can modify
> kvm_create_userspace_memory() without breaking anyone as this is
Avi Kivity wrote:
> Izik Eidus wrote:
>> On Thu, 2007-10-18 at 12:18 +0200, Gerd Hoffmann wrote:
>>
> I don't see how I can pass a pointer to
> kvm_create_userspace_memory() via kvm_create() without
> breaking the libkvm interface. There is no flags field or
> similar which could
Izik Eidus wrote:
> On Thu, 2007-10-18 at 12:18 +0200, Gerd Hoffmann wrote:
>
>> Dor Laor wrote:
>>
>>> Gerd Hoffmann wrote:
>>>
I don't see how I can pass a pointer to kvm_create_userspace_memory()
via kvm_create() without breaking the libkvm interface. There is no
f
On Sat, Oct 13, 2007 at 09:30:54PM -0300, Emmanuel Nicolas Millan wrote:
> >Hi,
> >
> >is there any option to reenable virtualisation support (AMD-CPU) if it
> >is disabled by bios (and Bios does not show an option to enable
> >virtualisation support)?
>
> >Elmar
>
> Hi, i'm having the same probl
On Thu, 2007-10-18 at 12:18 +0200, Gerd Hoffmann wrote:
> Dor Laor wrote:
> > Gerd Hoffmann wrote:
> >> I don't see how I can pass a pointer to kvm_create_userspace_memory()
> >> via kvm_create() without breaking the libkvm interface. There is no
> >> flags field or similar which could be used to
Dor Laor wrote:
> Gerd Hoffmann wrote:
>> I don't see how I can pass a pointer to kvm_create_userspace_memory()
>> via kvm_create() without breaking the libkvm interface. There is no
>> flags field or similar which could be used to signal "vm_mem is a valid
>> pointer, please use that instead of m
Avi Kivity wrote:
>> I will argue the necessaity of this code movement. A VM
>> Exit/Resume itself probably will block system responsibility
>> (can't deliver irq) in the level of 1K cycles, interrupt injection is
>> clearly far less than this granularity. Probably less than 100cycles.
>>
>>
>
>
Aurelien Jarno wrote:
> Ok, next try. This time I have opened the IA32 manual (I should have
> done that before), so I hope it is correct.
>
>
> KVM: Access registers for instructions with ModR/M byte and Mod = 3
>
> The patch belows changes the access type to register from memory for
> instructio
Jerone Young wrote:
> Qemu is interpreting --cross-prefix & cpu as one argument. This of
> course yeilds an error. This fixes the error.
>
>
Applied, thanks.
--
error compiling committee.c: too many arguments to function
-
Dong, Eddie wrote:
previous irq injection, next injection will be refused with IRQ
window enabled. This is because current implementation will inject
exception earlier than irq injection and vmx_intr_assist doesn;t
know if previous injected event is external irq (and thus
o
Zhang, Xiantao wrote:
> >From c5c9ec8d090d553b4d5d00e7ba7fc2daddfb3d00 Mon Sep 17 00:00:00 2001
> From: Zhang Xiantao <[EMAIL PROTECTED]>
> Date: Thu, 18 Oct 2007 10:31:07 +0800
> Subject: [PATCH] Fix compile error on latest commit
> Signed-off-by: Zhang Xiantao <[EMAIL PROTECTED]>
> ---
> drivers
Gerd Hoffmann wrote:
>
> Izik Eidus wrote:
> > hi,
> > why not making kvm_create_userspace_memory() recive a pointer to a
> > userspace allocated memory (that was allocated from file or from normal
> > malloc)
> > and make all the changes before kvm_create_userspace_memory() get
> called?
>
> I do
Izik Eidus wrote:
> hi,
> why not making kvm_create_userspace_memory() recive a pointer to a
> userspace allocated memory (that was allocated from file or from normal
> malloc)
> and make all the changes before kvm_create_userspace_memory() get called?
I don't see how I can pass a pointer to kvm_c
Hi Avi,
According to your and community's suggestions, I changed the kvm_vcpu
structure to two parts. To avoid the much intrusive into current code,
one is common part which is defined as a macro, and the other one is
arch-specific part.
In addition, I have a suggestion to re-organize the head fi
62 matches
Mail list logo
