All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@suse.com>
To: SongtaoX Liu <songtaox.liu@intel.com>
Cc: Kevin Tian <kevin.tian@intel.com>, "keir@xen.org" <keir@xen.org>,
	"tim@xen.org" <tim@xen.org>, Eddie Dong <eddie.dong@intel.com>,
	Jun Nakajima <jun.nakajima@intel.com>,
	"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
	Yang Z Zhang <yang.z.zhang@intel.com>,
	Robert Hu <robert.hu@intel.com>,
	LongtaoX Pang <longtaox.pang@intel.com>
Subject: Re: [PATCH] x86/EPT: flush cache when (potentially) limiting cachability
Date: Tue, 17 Jun 2014 08:11:35 +0100	[thread overview]
Message-ID: <53A00647020000780001ADD2@mail.emea.novell.com> (raw)
In-Reply-To: <582FB90AB890394081254B69739046FC0EAD8C9D@SHSMSX101.ccr.corp.intel.com>

>>> On 17.06.14 at 04:19, <songtaox.liu@intel.com> wrote:
>> >>> On 12.06.14 at 03:28, <songtaox.liu@intel.com> wrote:
>> >> From: Jan Beulich [mailto:jbeulich@suse.com]
>> >> >>> "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.
>> 
>> The original patch makes quite clear where to put the instrumentation; I'm
>> attaching a patch anyway for you to try. This (obviously) is against the 
> current
>> staging tree - while it ought to apply fine on master, it certainly won't 
> apply on
>> 4.4 or older without adjustments.
>> 
> Env: Xen.git, master, commit: 7f8d8abcf6dfb85fae591a547b24f9b27d92272c, with 
> your patch,
> L2 guest with "hap=1", after creating the L2, "xl dmesg" in L0 shows: 
> (XEN) chg[000020] d1 [hvm_set_guest_pat+0xad/0xb9]
> (XEN) chg[000040] d1 [hvm_set_guest_pat+0xad/0xb9]
> (XEN) chg[000080] d1 [hvm_set_guest_pat+0xad/0xb9]
> (XEN) chg[000100] d1 [hvm_set_guest_pat+0xad/0xb9]
> (XEN) chg[000200] d1 [hvm_set_guest_pat+0xad/0xb9]
> (XEN) chg[000400] d1 [hvm_set_guest_pat+0xad/0xb9]
> (XEN) chg[000800] d1 [hvm_set_guest_pat+0xad/0xb9]
> (XEN) chg[001000] d1 [hvm_set_guest_pat+0xad/0xb9]
> (XEN) chg[002000] d1 [hvm_set_guest_pat+0xad/0xb9]
> (XEN) chg[004000] d1 [hvm_set_guest_pat+0xad/0xb9]
> (XEN) chg[008000] d1 [hvm_set_guest_pat+0xad/0xb9]
> (XEN) chg[008000] d1 [hvm_set_guest_pat+0xad/0xb9]

This looks like it's not really a proper part of the log (the last two
lines being duplicated). Which underlines that you should supply
(attach!) full logs rather than decide on your own which part(s)
might be relevant.

_Assuming_ the tail above really is the tail of the log, I can't see
why the guest wouldn't come up: 32k cache flushes aren't the
end of the world. There ought to be something else...

Jan

  reply	other threads:[~2014-06-17  7:11 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
2014-06-16 13:01             ` Jan Beulich
2014-06-17  2:19               ` Liu, SongtaoX
2014-06-17  7:11                 ` Jan Beulich [this message]
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=53A00647020000780001ADD2@mail.emea.novell.com \
    --to=jbeulich@suse.com \
    --cc=eddie.dong@intel.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.