All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel@lists.xensource.com, suravee.suthikulpanit@amd.com,
	qing.he@intel.com, eddie.dong@intel.com,
	dietmar.hahn@ts.fujitsu.com, jun.nakajima@intel.com,
	jiongxi.li@intel.com,
	Boris Ostrovsky <boris.ostrovsky@oracle.com>
Subject: Re: vpmu=1 and running 'perf top' within a PVHVM guest eventually hangs dom0 and hypervisor has stuck vCPUS. Romley-EP (model=45, stepping=2)
Date: Wed, 13 Mar 2013 10:12:33 -0400	[thread overview]
Message-ID: <20130313141233.GC25782@phenom.dumpdata.com> (raw)
In-Reply-To: <514046D902000078000C53CE@nat28.tlf.novell.com>

On Wed, Mar 13, 2013 at 08:28:57AM +0000, Jan Beulich wrote:
> >>> On 12.03.13 at 19:50, Boris Ostrovsky <boris.ostrovsky@oracle.com> wrote:
> > On 03/12/2013 01:30 PM, Konrad Rzeszutek Wilk wrote:
> >> This issue I am encountering seems to only happen on multi-socket
> >> machines.
> > 
> > I believe I was able to reproduce this (once) on my laptop.
> > 
> >> It also does not help that the only multi-socket box I have is
> >> an Romley-EP (so two socket SandyBridge CPUs). The other
> >> SandyBridge boxes I've (one socket) are not showing this. Granted
> >> they are also a different model (42).
> >>
> >> The problem is that when I run 'perf top' within an SMP PVHVM
> >> guest, after a couple of seconds or minutes the guest hangs.
> >> Hypervisor ends up stuck too looping, and then the dom0 ends
> >> up hanging as well.
> >>
> >> Dumping the cpu registers (Ctrl-A x3, then 'd'
> >> shows that the guest is pretty firmly stuck in vmx_vmexit_handler:
> >>
> >> (XEN)    [<ffff82c4c01d386f>] vmx_vmexit_handler+0x22f/0x174
> > 
> > And in my case this address is the second instruction after STI, i.e. we
> > are right at the point where interrupts got enabled.
> 
> As I didn't notice anything regarding the top commit of the tree
> you used - was this with 7dd3b06 already included?

I did include Tim's patch in the tree (this was before it got committed
in). I had these right above
ba9ef879973f9bee4b72c8f1d3ef816bc58e5fdc (x86: minor fix for rdmsrl):

b77cd15 trace: Add reason for NMI exit TRAP
ad8523a trace: Add the other variant of do_block.
4fb1793 trace: Add trace events for IRQ activities.
e71031c trace: Use correct trace class for power management changes.
7b185ec vmx/nmi: Do not use self_nmi() in VMEXIT handler]
020ad4c vpmu intel: pass through cpuid bits when BTS is enabled
650f7f0 Always save/restore performance counters when HVM guest switching VCPU

and also without them.

> 
> Jan
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
> 

  reply	other threads:[~2013-03-13 14:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-12 17:30 vpmu=1 and running 'perf top' within a PVHVM guest eventually hangs dom0 and hypervisor has stuck vCPUS. Romley-EP (model=45, stepping=2) Konrad Rzeszutek Wilk
2013-03-12 18:50 ` Boris Ostrovsky
2013-03-12 20:31   ` Konrad Rzeszutek Wilk
2013-03-12 20:54     ` Boris Ostrovsky
2013-03-13  7:51       ` Dietmar Hahn
2013-03-13  8:02         ` Dietmar Hahn
2013-03-13 15:04           ` Konrad Rzeszutek Wilk
2013-03-29  1:14         ` Haitao Shan
2013-03-13  8:26       ` Jan Beulich
2013-03-13 19:59       ` Boris Ostrovsky
2013-03-13  8:28   ` Jan Beulich
2013-03-13 14:12     ` Konrad Rzeszutek Wilk [this message]
2013-03-13  8:33 ` Jan Beulich
2013-03-13 21:27   ` Konrad Rzeszutek Wilk
  -- strict thread matches above, loose matches on Subject: below --
2013-03-29 12:29 Boris Ostrovsky

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=20130313141233.GC25782@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=JBeulich@suse.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=dietmar.hahn@ts.fujitsu.com \
    --cc=eddie.dong@intel.com \
    --cc=jiongxi.li@intel.com \
    --cc=jun.nakajima@intel.com \
    --cc=qing.he@intel.com \
    --cc=suravee.suthikulpanit@amd.com \
    --cc=xen-devel@lists.xensource.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.