From: Olaf Hering <olaf@aepfle.de>
To: Wei Liu <wei.liu2@citrix.com>
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
Ian Campbell <ian.campbell@citrix.com>,
xen-devel@lists.xen.org
Subject: Re: [PATCH 5/7] xenalyze: disable sched_switch_process
Date: Tue, 28 Apr 2015 07:58:44 +0200 [thread overview]
Message-ID: <20150428055844.GB19048@aepfle.de> (raw)
In-Reply-To: <20150428031616.GA23012@zion.uk.xensource.com>
On Tue, Apr 28, Wei Liu wrote:
> On Mon, Apr 27, 2015 at 01:22:14PM +0000, Olaf Hering wrote:
> > It causes a crash, dump data and return early
> This doesn't look right. You skip all things below.
Yes, to avoid the crash when booted with "tbuf_size=-1". When I noticed
that I did not have the energy to dig into how the vcpu machinery works.
Appearently it cant cope with bootup data.
Olaf
next prev parent reply other threads:[~2015-04-28 5:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-27 13:22 [PATCH 0/7] add xenalyze to staging Olaf Hering
2015-04-27 13:22 ` [PATCH 1/7] xenalyze: add to tools/misc Olaf Hering
2015-04-27 14:04 ` David Vrabel
2015-04-28 5:57 ` Olaf Hering
2015-05-06 13:35 ` George Dunlap
2015-04-28 3:21 ` Wei Liu
2015-04-27 13:22 ` [PATCH 2/7] xenalyze: print newline after unknown hvm events Olaf Hering
2015-04-27 13:22 ` [PATCH 3/7] xenalyze: include odd mmio states in default output Olaf Hering
2015-04-27 13:22 ` [PATCH 4/7] xenalyze: handle TRC_TRACE_WRAP_BUFFER Olaf Hering
2015-04-27 13:22 ` [PATCH 5/7] xenalyze: disable sched_switch_process Olaf Hering
2015-04-28 3:16 ` Wei Liu
2015-04-28 5:58 ` Olaf Hering [this message]
2015-05-02 16:51 ` Wei Liu
2015-05-04 5:52 ` Olaf Hering
2015-04-27 13:22 ` [PATCH 6/7] xenalyze: handle more events in sched_process Olaf Hering
2015-04-27 13:22 ` [PATCH 7/7] xenalyze: remove traling whitespaces Olaf Hering
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=20150428055844.GB19048@aepfle.de \
--to=olaf@aepfle.de \
--cc=george.dunlap@eu.citrix.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=wei.liu2@citrix.com \
--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.