xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ben Guthro <ben.guthro@gmail.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Mark Roddy <mark.roddy@citrix.com>, Ben Guthro <ben@guthro.net>,
	xen-devel <xen-devel@lists.xen.org>
Subject: Re: XSAVE/XRSTOR crash resurgence in 4.3
Date: Fri, 5 Jul 2013 08:10:12 -0400	[thread overview]
Message-ID: <-6045434008888857231@unknownmsgid> (raw)
In-Reply-To: <51D6BC5E02000078000E2F24@nat28.tlf.novell.com>

On Jul 5, 2013, at 6:30 AM, Jan Beulich <JBeulich@suse.com> wrote:

>>>> On 04.07.13 at 20:19, Mark Roddy <mark.roddy@citrix.com> 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
>
> <x86-FPU-selector-loss.patch>

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.

  reply	other threads:[~2013-07-05 12:10 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-03 14:02 XSAVE/XRSTOR crash resurgence in 4.3 Ben Guthro
2013-07-04 13:21 ` Jan Beulich
2013-07-04 13:24   ` Ben Guthro
2013-07-04 18:19     ` Mark Roddy
2013-07-05  6:42       ` Jan Beulich
2013-07-05 10:30       ` Jan Beulich
2013-07-05 12:10         ` Ben Guthro [this message]
2013-07-05 12:15           ` Jan Beulich
2013-07-05 12:58             ` Ben Guthro
2013-07-08 14:13               ` Ben Guthro
2013-07-08 14:24                 ` Jan Beulich
2013-07-08 14:31                   ` Ben Guthro
2013-07-08 14:40                     ` Jan Beulich
2013-07-08 14:42                       ` Ben Guthro
2013-07-08 14:47                         ` Jan Beulich
2013-07-08 15:10                           ` Ben Guthro
2013-07-12 13:11                             ` Ben Guthro
2013-07-12 13:38                               ` Jan Beulich
2013-07-12 13:49                                 ` Ben Guthro
2013-07-12 14:34                                   ` Jan Beulich
2013-07-12 14:49                                     ` Ben Guthro
2013-07-12 14:55                                       ` Jan Beulich
2013-07-12 15:14                                         ` Ben Guthro
2013-07-15  6:41                                           ` Jan Beulich
2013-07-15 12:33                                           ` Jan Beulich
2013-07-15 12:43                                             ` Ben Guthro
2013-07-15 13:49                                               ` Ben Guthro
2013-07-15 14:06                                                 ` Jan Beulich
2013-07-16 16:23                                                 ` Jan Beulich
2013-07-16 16:57                                                   ` Ben Guthro
2013-07-17  6:38                                                     ` Jan Beulich
2013-07-17 13:07                                                       ` Ben Guthro
2013-07-22 12:25                                                         ` Ben Guthro
2013-08-05 13:05                                                           ` [PATCH] x86: refine FPU selector handling code for XSAVEOPT Jan Beulich
2013-08-05 16:03                                                             ` Keir Fraser
2013-07-08 14:44                       ` XSAVE/XRSTOR crash resurgence in 4.3 Andrew Cooper
2013-07-08 14:52                         ` Jan Beulich
2013-07-08 14:55                           ` Andrew Cooper

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=-6045434008888857231@unknownmsgid \
    --to=ben.guthro@gmail.com \
    --cc=JBeulich@suse.com \
    --cc=ben@guthro.net \
    --cc=mark.roddy@citrix.com \
    --cc=xen-devel@lists.xen.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).