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] [PATCH] Print a message if no vpmu support for Intel cpu

To: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] [PATCH] Print a message if no vpmu support for Intel cpu
From: Dietmar Hahn <dietmar.hahn@xxxxxxxxxxxxxx>
Date: Tue, 16 Nov 2010 11:33:26 +0100
Delivery-date: Tue, 16 Nov 2010 02:34:15 -0800
Dkim-signature: v=1; a=rsa-sha256; c=simple/simple; d=ts.fujitsu.com; i=dietmar.hahn@xxxxxxxxxxxxxx; q=dns/txt; s=s1536b; t=1289903611; x=1321439611; h=from:to:subject:date:mime-version:message-id; z=From:=20Dietmar=20Hahn=20<dietmar.hahn@xxxxxxxxxxxxxx> |To:=20"xen-devel@xxxxxxxxxxxxxxxxxxx"=20<xen-devel@lists .xensource.com>|Subject:=20[PATCH]=20Print=20a=20message =20if=20no=20vpmu=20support=20for=20Intel=20cpu|Date:=20T ue,=2016=20Nov=202010=2011:33:26=20+0100|MIME-Version:=20 1.0|Message-Id:=20<201011161133.27131.dietmar.hahn@xxxxxx itsu.com>; bh=mW0+C0mSyiuBQ3ZYwHMXuMzFbcKZccBrbDF5GLk3wf4=; b=rFx6Twk5Y/AC3yZ5OIEOlUhLXju0ZwLk+3HcDy7c17iHru6ls9+hXwA3 GlpEoXMxxhvi1tUNMjDvnkUIhPBSFNoeeu2NYPPxZIdP7bFlqrj95hdNR L3jlncezNoufJb+kjN4/wOpeb4U1gv4PKmvOYCx7r8Mes0fiDIBiJU1+C OWnm0umdAvlvkRzsvE7XCm7jJj6OsBo203qEN9OzBpehog7zzb9Hx8/dO Pa7rMxFnBz+mFLtVbEe9VNf9h9MbK;
Domainkey-signature: s=s1536a; d=ts.fujitsu.com; c=nofws; q=dns; h=X-SBRSScore:X-IronPort-AV:Received:X-IronPort-AV: Received:Received:From:To:Subject:Date:User-Agent: X-KMail-Markup:MIME-Version:Content-Type:Message-Id; b=otsvX/C20hnLeq7os2y1piPVIZZ412HNCMI43rd8m+AAvC3DPnSH7Tg0 kkV5L5VJYcbkuSxh9KKEEt2aNJtZ9mas+C1OBT1lU7obXT7PQYjt25u1D 15KUmYPSzfj/O/8qpmrLM0zJ18Wv4HnKj4wQUIoZwP1Lv92i+IvPK0Nq4 Hb0mYgjZ95r8ri10652rcHRfcYrKZmVs2Uwxbdtt/z5OUIu/fMZEymocN pc4Ptg7o5sSzr6Hfx4zX3Adj5TkxU;
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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
User-agent: KMail/1.13.5 (Linux/2.6.34.7-0.5-xen; KDE/4.5.3; x86_64; ; )

Print a message if there is no vpmu support for this Intel cpu.

Signed-off-by: Dietmar Hahn <dietmar.hahn@xxxxxxxxxxxxxx>

diff -r 87f248de5230 -r 8902695abe34 xen/arch/x86/hvm/vpmu.c

--- a/xen/arch/x86/hvm/vpmu.c Mon Nov 15 09:31:38 2010 +0000

+++ b/xen/arch/x86/hvm/vpmu.c Tue Nov 16 11:22:39 2010 +0100

@@ -115,6 +115,7 @@

case X86_VENDOR_INTEL:

{

+ int supported = 1;

if ( family == 6 )

{

switch ( cpu_model )

@@ -125,8 +126,20 @@

case 29:

vpmu->arch_vpmu_ops = &core2_vpmu_ops;

break;

+ default:

+ supported = 0;

}

}

+ else

+ supported = 0;

+

+ if ( !supported )

+ {

+ printk("VMPU: Initialization failed. "

+ "Intel processor family %d model %d has not "

+ "been supported\n", family, cpu_model);

+ return;

+ }

}

break;

--

Company details: http://ts.fujitsu.com/imprint.html

Attachment: vpmu_support.patch
Description: Text Data

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] [PATCH] Print a message if no vpmu support for Intel cpu, Dietmar Hahn <=