WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Re: [PATCH][SVM] fix spinlock panic

To: Christoph Egger <Christoph.Egger@xxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] Re: [PATCH][SVM] fix spinlock panic
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Thu, 18 Jun 2009 09:51:17 +0100
Cc:
Delivery-date: Thu, 18 Jun 2009 01:52:15 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <200906171620.49105.Christoph.Egger@xxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcnvV0iMn8gIfqQNTJeWsyzGnlH3kgAmqitn
Thread-topic: [PATCH][SVM] fix spinlock panic
User-agent: Microsoft-Entourage/12.19.0.090515
On 17/06/2009 15:20, "Christoph Egger" <Christoph.Egger@xxxxxxx> wrote:

> Attached patch enables irq when initializing SVM so it's safe to take locks.
> This fixes a panic like this:

The bug is related to the fact you leak memory on every S3 resume, by
reallocating hsa[cpu] and root_vmcb[cpu] which were never freed. Please see
c/s 19784 in the staging tree which does a general cleanup and fix of
start_svm(). It should fix your crash.

It does change behaviour a bit -- primarily: It does not reset the ASID
logic completely (I'm not certain there couldn't be VCPUs hanging around
pointing at earlier generations on this CPU, in which case it would be
dangerous to reset the ASID generation back to zero); Also, as well as not
reallocating hsa and root_vmcb, we don't re-init them either. I don't know
ehether that strictly matters but obviously we could easily re-jig the code
to always clear_page() those pages unconditionally.

 -- Keir



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>