All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Zhang, Yang Z" <yang.z.zhang@intel.com>
To: Matthias <matthias.kannenberg@googlemail.com>,
	Jan Beulich <JBeulich@suse.com>
Cc: "tim@xen.org" <tim@xen.org>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Please revert / review 077fc1c04d70ef1748ac2daa6622b3320a1a004c
Date: Fri, 20 Jun 2014 11:24:01 +0000	[thread overview]
Message-ID: <A9667DDFB95DB7438FA9D7D576C3D87E0AB00415@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <CABoYbGp-C7_6GW67W84QCc==iZzOG5vOPbq--MqZkiZ3S8+n4A@mail.gmail.com>

Matthias wrote on 2014-06-20:
> Just for me for clarification: So is it reasonable that my server
> crashed with th
> #3 patch used, or is this something I should investigate furthor /
> maybe do another xen build.?

As Jan pointed out that the patch should not work on AMD platform and cause the Xen crash. I will work out a NPT patch for you to have a try.

> 
> 
> Also, I don't have a serial port, but i got a netconsole setup
> running. Is there any way to pipe the xl dmesg output into the normal
> dmesg output so it would be caught by netconsole?
> 
> 
> 
> 2014-06-20 10:22 GMT+02:00 Jan Beulich <JBeulich@suse.com>:
> 
> 
> 	>>> On 19.06.14 at 18:22, <matthias.kannenberg@googlemail.com> wrote:
> 	> Test 2: 	> 	> Xen-Version: Compiled a normal 077 commit version
> without any of your 	> patches 	> Xen cmd line: added immo=no-sharept as
> suggested 	> Passed-through devices: vga, 2 usb controller (ohci+ehci),
> sound card 	> Result: works fine. domU boots, no BSOD, no other
> problems, server seems to 	> be stable. So not sharing the VT-d page
> tables seems to do the trick / the 	> problem is in the page table
> sharing.
> 
> 
> 	Just to clarify - page table sharing is intended to get disabled in
> 	-unstable on the AMD side ( 	
> http://lists.xenproject.org/archives/html/xen-devel/2014-06/msg00416.h t
> ml, 	still awaiting an AMD IOMMU maintainer ack). But as that's not
> 	immediately a backporting candidate, understanding the problem 	to find
> a solution also for 4.4.x would still be necessary.
> 
> 	Jan
> 
> 
>


Best regards,
Yang

  parent reply	other threads:[~2014-06-20 11:24 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-11 15:44 Please revert / review 077fc1c04d70ef1748ac2daa6622b3320a1a004c Matthias
2014-06-12  1:02 ` Zhang, Yang Z
2014-06-12  9:35   ` Jan Beulich
2014-06-12 13:49     ` Matthias
2014-06-16  7:47       ` Zhang, Yang Z
2014-06-16  8:08         ` Jan Beulich
2014-06-16 13:42           ` Matthias
2014-06-16 14:52             ` Jan Beulich
2014-06-16 15:07               ` Matthias
2014-06-18  7:25             ` Zhang, Yang Z
2014-06-18 22:21               ` Matthias
2014-06-19  1:07                 ` Matthias
2014-06-19  1:29                   ` Matthias
2014-06-19 12:25                 ` Zhang, Yang Z
2014-06-19 16:22                   ` Matthias
2014-06-20  0:20                     ` Zhang, Yang Z
2014-06-20  8:22                     ` Jan Beulich
2014-06-20 10:07                       ` Matthias
2014-06-20 11:18                         ` Jan Beulich
2014-06-20 11:27                           ` Zhang, Yang Z
2014-06-20 11:24                         ` Zhang, Yang Z [this message]
2014-06-20 11:28                       ` Zhang, Yang Z
2014-06-20  8:17                   ` Jan Beulich
2014-06-20 11:26                     ` Zhang, Yang Z

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=A9667DDFB95DB7438FA9D7D576C3D87E0AB00415@SHSMSX104.ccr.corp.intel.com \
    --to=yang.z.zhang@intel.com \
    --cc=JBeulich@suse.com \
    --cc=matthias.kannenberg@googlemail.com \
    --cc=tim@xen.org \
    --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 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.