From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tim Deegan Subject: Re: [PATCH 20 of 20] n2 MSR handling and capability exposure Date: Tue, 26 Jul 2011 11:00:18 +0100 Message-ID: <20110726100018.GH8970@whitby.uk.xensource.com> References: <4E0D9D48.20308@grosc.com> <20110704085810.GZ17634@whitby.uk.xensource.com> <4E16ADD9.4060304@grosc.com> <1A42CE6F5F474C41B63392A5F80372B212DAB9DD82@shsmsx501.ccr.corp.intel.com> <4E258DC4.4050106@grosc.com> <1A42CE6F5F474C41B63392A5F80372B212DAC025EB@shsmsx501.ccr.corp.intel.com> <4E26E23D.4030000@grosc.com> <20110725140843.GC8970@whitby.uk.xensource.com> <20110725161657.GF8970@whitby.uk.xensource.com> <4E2E6992.9030407@grosc.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Return-path: Content-Disposition: inline In-Reply-To: <4E2E6992.9030407@grosc.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jeroen Groenewegen van der Weyden Cc: "Christoph.Egger@amd.com" , "xen-devel@lists.xensource.com" , "Dong, Eddie" List-Id: xen-devel@lists.xenproject.org Hi, At 09:15 +0200 on 26 Jul (1311671730), Jeroen Groenewegen van der Weyden wrote: > I think the behaviour is still the same, > > 1) cs23726 > 2) vvmc.c patched with attachment. > 3) new compile > > after a little while the domu becomes ir-responsive. Dang. :( > with xm dmesg I see a lot of these: > (XEN) vvmx.c:1182:d3 vmclear gpa 1f5a89000 not the same as current > vmcs 00000001f448f000 > (XEN) vvmx.c:1182:d3 vmclear gpa 1f5a89000 not the same as current > vmcs 00000001f448f000 Yeah; with the patch applied, those should be harmlesss. If you give your first-level guest only one vcpu, does the problem go away? > Note: I have to say, patching this on this level is not common > practice for me. although I think I did it the right way. please > keep in mind I can make mistakes on this level. If you want to double-check that you've done the patch right, edit xen/arch/x86/hvm/vmx/vvmx.c, and at line 1185, just under the line ` /* Even if this VMCS isn't the current one, we must clear it. */ ' add a line ` printk("boo!\n"); '. Then when you recompile and test you should see "boo!" printed just after each "vvmx.c:1182:d3" line on the console. Cheers, Tim. -- Tim Deegan Principal Software Engineer, Xen Platform Team Citrix Systems UK Ltd. (Company #02937203, SL9 0BG)