Andrea Arcangeli wrote:
> On Sun, Dec 23, 2007 at 07:37:40PM +0200, Avi Kivity wrote:
>
>> The sched_in notifier needs to enable interrupts (but it must disable
>> preemption to avoid recursion).
>>
>
> Ok this update fixes the smp_call_function deadlock.
>
>
I was able to boot a 4-way
On Sun, Dec 23, 2007 at 07:37:40PM +0200, Avi Kivity wrote:
> The sched_in notifier needs to enable interrupts (but it must disable
> preemption to avoid recursion).
Ok this update fixes the smp_call_function deadlock.
Signed-off-by: Andrea Arcangeli <[EMAIL PROTECTED]>
diff --git a/kernel/hack
Andrea Arcangeli wrote:
> On Sat, Dec 22, 2007 at 09:13:44PM +0200, Avi Kivity wrote:
>
>> Unfortunately, this fails badly on Intel i386:
>>
>
> Hmm ok there's a definitive bug that I forgot a int1 kernel->kernel
> switch on x86 has no special debug stack like on x86-64. This will
> have a
On Sat, Dec 22, 2007 at 09:13:44PM +0200, Avi Kivity wrote:
> Unfortunately, this fails badly on Intel i386:
Hmm ok there's a definitive bug that I forgot a int1 kernel->kernel
switch on x86 has no special debug stack like on x86-64. This will
have a better chance to work, hope I got all offsets r
Izik Eidus wrote:
>> This fixes my longstanding KVM instability and "-smp 2" now works
>> flawlessy with svm too! -smp 2 -snapshot crashes in qemu userland but
>> that's not kernel related, must be some thread mutex lock recursion or
>> lock inversion in the qcow cow code. Removing -snapshot make -
Andrea Arcangeli wrote:
[snip]
> So in short with the below fix applied, after a write_tsc(0,0), the
> UP guest never return any error anymore. Previously it would return
> frequent errors because sched_in wasn't properly invoked by svm.c and
> it would crash at boot every single time after a writ
On Fri, Dec 21, 2007 at 07:52:52PM +0200, Izik Eidus wrote:
> oh, it was sent to the list, dont trust (in case you did) the source forge
> site for the mails
But this time I received it in my kvm-devel folder... previously I
didn't, so it had to be blocked my some spamfilter in the other
account
Andrea Arcangeli wrote:
> Hello,
>
> [ I already sent it once as [EMAIL PROTECTED] but it didn't go through
> for whatever reason, trying again from private email, hope there
> won't be dups ]
>
oh, it was sent to the list, dont trust (in case you did) the source
forge site for the mails
in
Hello,
[ I already sent it once as [EMAIL PROTECTED] but it didn't go through
for whatever reason, trying again from private email, hope there
won't be dups ]
My worst longstanding problem with KVM is that as the uptime of my
host system increased, my opensuse guest images started to destabil
Hello,
My worst longstanding problem with KVM is that as the uptime of my
host system increased, my opensuse guest images started to destabilize
and lockup at boot. The weird thing was that fresh after boot
everything was always perfectly ok, so I thought it was rmmod/insmod
or some other sticky e
10 matches
Mail list logo
