All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@citrix.com>
To: "Liu, SongtaoX" <songtaox.liu@intel.com>
Cc: "Tian, Kevin" <kevin.tian@intel.com>,
	"keir@xen.org" <keir@xen.org>,
	"Nakajima, Jun" <jun.nakajima@intel.com>,
	"tim@xen.org" <tim@xen.org>, "Dong, Eddie" <eddie.dong@intel.com>,
	Jan Beulich <jbeulich@suse.com>,
	"Hu, Robert" <robert.hu@intel.com>,
	"Zhang, Yang Z" <yang.z.zhang@intel.com>,
	"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
	"Pang, LongtaoX" <longtaox.pang@intel.com>
Subject: Re: [PATCH] x86/EPT: flush cache when (potentially) limiting cachability
Date: Thu, 12 Jun 2014 09:43:25 +0100	[thread overview]
Message-ID: <1402562605.4342.16.camel@kazak.uk.xensource.com> (raw)
In-Reply-To: <582FB90AB890394081254B69739046FC0EAD474D@SHSMSX101.ccr.corp.intel.com>

On Thu, 2014-06-12 at 01:28 +0000, Liu, SongtaoX wrote:
> 
> > -----Original Message-----
> > From: Jan Beulich [mailto:jbeulich@suse.com]
> > Sent: Friday, May 30, 2014 7:20 PM
> > To: Liu, SongtaoX; xen-devel@lists.xenproject.org
> > Cc: Dong, Eddie; Nakajima, Jun; Tian, Kevin; Pang, LongtaoX; Hu, Robert; Zhang,
> > Yang Z; keir@xen.org; tim@xen.org
> > Subject: Re: RE: [Xen-devel] [PATCH] x86/EPT: flush cache when (potentially)
> > limiting cachability
> > 
> > >>> "Liu, SongtaoX" <songtaox.liu@intel.com> 05/30/14 9:35 AM >>>
> > >Sorry to update.
> > >The bug refers to
> > http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1887.
> > >L2 guest vnc console hangs at black screen with cursor flashing at the top left
> > corner.
> > >After several minutes, the Seabios screen shows up, but the screen still flush
> > slowly, the guest could not boot up.
> > 
> > That would then indeed be an indication of excessive flushes. I.e. you may want
> > to simply track down which one (and why) gets triggered too often.
> > 
> How to get that information? It is hard for me to do it since I am not
> a Xen expert. But if you can provide a patch help to debug, I would
> happy to do it.

Is this the sort of thing for which xentrace and xenalyze could be
useful?

  reply	other threads:[~2014-06-12  8:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-25 12:13 [PATCH] x86/EPT: flush cache when (potentially) limiting cachability Jan Beulich
2014-05-01 13:39 ` Tim Deegan
2014-05-30  2:07 ` Liu, SongtaoX
2014-05-30  6:26   ` Jan Beulich
2014-05-30  7:02     ` Jan Beulich
2014-05-30  7:34       ` Liu, SongtaoX
2014-05-30 11:20         ` Jan Beulich
2014-06-12  1:28           ` Liu, SongtaoX
2014-06-12  8:43             ` Ian Campbell [this message]
2014-06-16 13:01             ` Jan Beulich
2014-06-17  2:19               ` Liu, SongtaoX
2014-06-17  7:11                 ` Jan Beulich
2014-06-17  8:33                   ` Liu, SongtaoX
2014-06-17 15:34                     ` Jan Beulich
2014-06-18  3:09                       ` Liu, SongtaoX
2014-06-18 10:02                         ` Jan Beulich

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=1402562605.4342.16.camel@kazak.uk.xensource.com \
    --to=ian.campbell@citrix.com \
    --cc=eddie.dong@intel.com \
    --cc=jbeulich@suse.com \
    --cc=jun.nakajima@intel.com \
    --cc=keir@xen.org \
    --cc=kevin.tian@intel.com \
    --cc=longtaox.pang@intel.com \
    --cc=robert.hu@intel.com \
    --cc=songtaox.liu@intel.com \
    --cc=tim@xen.org \
    --cc=xen-devel@lists.xenproject.org \
    --cc=yang.z.zhang@intel.com \
    /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.