All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juergen Gross <jgross@suse.com>
To: xen-devel@lists.xenproject.org
Cc: George.Dunlap@eu.citrix.com, wei.liu2@citrix.com,
	ian.jackson@eu.citrix.com, Juergen Gross <jgross@suse.com>
Subject: [PATCH v2 0/2] xentrace: fix xentrace for smt=0
Date: Thu,  4 Oct 2018 12:51:48 +0200	[thread overview]
Message-ID: <20181004105150.27923-1-jgross@suse.com> (raw)

When hyperthreads are disabled via smt=0 Xen boot parameter xentrace
is no longer working, but crashing the system.

Patch 1 makes the xentrace user tool work on systems when not all
possible cpu ids have an associated trace buffer allocated.

Patch 2 corrects xentrace handling by sizing the control structures
according to the physical cpus instead of taking online cpus into
account only.

Juergen Gross (2):
  xentrace: allow sparse cpu list
  xentrace: handle sparse cpu ids correctly in xen trace buffer handling

 tools/xentrace/xentrace.c | 18 ++++++++++++------
 xen/common/trace.c        |  6 +++---
 2 files changed, 15 insertions(+), 9 deletions(-)

-- 
2.16.4


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

             reply	other threads:[~2018-10-04 10:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-04 10:51 Juergen Gross [this message]
2018-10-04 10:51 ` [PATCH v2 1/2] xentrace: allow sparse cpu list Juergen Gross
2018-10-04 11:22   ` George Dunlap
2018-10-04 11:25     ` Juergen Gross
2018-10-04 10:51 ` [PATCH v2 2/2] xentrace: handle sparse cpu ids correctly in xen trace buffer handling Juergen Gross
2018-10-04 11:39   ` George Dunlap

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=20181004105150.27923-1-jgross@suse.com \
    --to=jgross@suse.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=wei.liu2@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.