All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Andrew Cooper <Andrew.Cooper3@citrix.com>,
	ian.jackson@eu.citrix.com,
	xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [xen-unstable test] 57852: regressions - FAIL
Date: Wed, 10 Jun 2015 15:08:14 +0100	[thread overview]
Message-ID: <1433945294.30003.83.camel@citrix.com> (raw)
In-Reply-To: <55785B9F020000780008316C@mail.emea.novell.com>

On Wed, 2015-06-10 at 14:45 +0100, Jan Beulich wrote:
> >>> On 10.06.15 at 14:56, <ian.campbell@citrix.com> wrote:
> > On Wed, 2015-06-10 at 12:48 +0100, Jan Beulich wrote:
> >> Sure we can; I just generally prefer not to bother people with
> >> problems they already solved, but maybe that's the wrong approach
> >> a case like this.
> > 
> > Is the list of errata fixed by a given ucode update public? If not then
> > I think we've done sufficient due diligence that we should feel ok to
> > ask, even if the answer turns out to be fixed in microcode.
> 
> So I went though the errata list for that specific model; the only
> one really concerning seems to be CA135 ("A MOV to CR3 When
> EPT is Enabled May Lead to an Unexpected Page Fault or an
> Incorrect Page Translation"). But while it would affect us, it would
> quite likely make the guest crash instead of idling or being hung.

Yes, sounds like it.

> So if we're going to approach Intel with this - will you or should I?

I think it'd be best coming from you.

Ian.

  reply	other threads:[~2015-06-10 14:21 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-04 12:01 [xen-unstable test] 57852: regressions - FAIL osstest service user
2015-06-05  8:45 ` Ian Campbell
2015-06-05  9:00   ` Jan Beulich
2015-06-05  9:07     ` Ian Campbell
2015-06-05  9:18       ` Jan Beulich
2015-06-05 10:48         ` Ian Campbell
2015-06-05 16:46           ` Ian Campbell
2015-06-08  8:07           ` Jan Beulich
2015-06-08  8:53             ` Ian Campbell
2015-06-08  9:15               ` Jan Beulich
2015-06-08  9:27                 ` Ian Campbell
2015-06-08 10:17                   ` Jan Beulich
2015-06-08 14:43                     ` Ian Jackson
2015-06-08 12:16                   ` Ian Campbell
2015-06-08 12:19                     ` Andrew Cooper
2015-06-08 12:24                     ` Jan Beulich
2015-06-09  8:26                     ` Ian Campbell
2015-06-09  9:29                       ` Jan Beulich
2015-06-10  8:50                         ` Ian Campbell
2015-06-10  9:36                           ` Jan Beulich
2015-06-10 11:01                             ` Ian Campbell
2015-06-10 11:48                               ` Jan Beulich
2015-06-10 12:56                                 ` Ian Campbell
2015-06-10 13:23                                   ` Jan Beulich
2015-06-10 13:45                                   ` Jan Beulich
2015-06-10 14:08                                     ` Ian Campbell [this message]
2015-06-11  7:02                                       ` Jan Beulich
2015-06-11  8:45                                         ` Ian Campbell
2015-06-15  8:57                                           ` Ian Campbell
2015-06-15  9:03                                             ` Jan Beulich
2015-06-10 14:34                                   ` Ian Campbell
2015-06-10 15:59                                     ` Jan Beulich
2015-06-10 16:18                                       ` Don Slutz
2015-06-10 18:00                                       ` Ian Campbell
2015-06-08 13:50                   ` Konrad Rzeszutek Wilk
2015-06-08 14:02                     ` Ian Campbell
2015-06-08 14:47                     ` Ian Jackson
2015-06-08 15:21                       ` Konrad Rzeszutek Wilk
2015-06-08 15:29                         ` Ian Campbell
2015-06-08 10:10                 ` Ian Campbell

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=1433945294.30003.83.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=Andrew.Cooper3@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.