From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ben Guthro Subject: Re: XSAVE/XRSTOR crash resurgence in 4.3 Date: Fri, 5 Jul 2013 08:10:12 -0400 Message-ID: <-6045434008888857231@unknownmsgid> References: <51D592E502000078000E2C7D@nat28.tlf.novell.com> <930123250021152322@unknownmsgid> <51D6BC5E02000078000E2F24@nat28.tlf.novell.com> Mime-Version: 1.0 (1.0) Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <51D6BC5E02000078000E2F24@nat28.tlf.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Jan Beulich Cc: Mark Roddy , Ben Guthro , xen-devel List-Id: xen-devel@lists.xenproject.org On Jul 5, 2013, at 6:30 AM, Jan Beulich wrote: >>>> On 04.07.13 at 20:19, Mark Roddy wrote: >> -----Original Message----- >> From: Ben Guthro [mailto:ben.guthro@gmail.com] >> >> Happy to test a debug patch, as well. > > Here you go. The logging is done using thresholds (so you wouldn't > get your log flooded), but of course this has the risk of not seeing > anything useful in case the problem happens not on every run > through these functions. Also the patch instruments on the xsave/ > xrstor paths, not the fxsave/fxrstor ones, so is assumed to be used > on an xsave-capable and -enabled system. Ideally - if reproducible > this way - you'd use a single-vCPU guest (easing later log analysis). > > Jan > > Thanks. Since I am not in the office today, nor near a machine that I can access this, I asked someone else to apply and check in this patch, in the hope that we could get some useful debug info from the weekend test run. However, when he went to test booting a VM with this patch, the host machine rebooted - presumably a Xen crash. I'll have a closer look on Mon.