From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Keir Fraser <keir@xen.org>, Jan Beulich <JBeulich@suse.com>,
Xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH] tools/hvmloader: Don't perform AML hotplug debugging in production
Date: Mon, 30 Mar 2015 16:30:01 +0100 [thread overview]
Message-ID: <55196BF9.2090905@citrix.com> (raw)
In-Reply-To: <20150330152229.GD31851@l.oracle.com>
On 30/03/15 16:22, Konrad Rzeszutek Wilk wrote:
> On Mon, Mar 30, 2015 at 03:20:19PM +0100, Andrew Cooper wrote:
>> It is number of vmexits and a moderate quantity of qemu logging which can
>> safely be avoided when not specifically debugging a PCI hotplug issue.
> Could we just make qemu-X not include this data when the we
> run in production? And in the field if this needs to be diagnosed
> we can just pass in an extra flag to QEMU and it would do it?
What do we not include? This is data which gets bundled into hvmloader
itself.
A little while ago, I proposed a different solution:
http://lists.xen.org/archives/html/xen-devel/2014-01/msg01526.html
which allowed this to all be controlled at runtime. The important point
is to avoid the vmexits if not needed, rather than to simply ignore the
debugging they are giving.
~Andrew
next prev parent reply other threads:[~2015-03-30 15:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-30 14:20 [PATCH] tools/hvmloader: Don't perform AML hotplug debugging in production Andrew Cooper
2015-03-30 15:22 ` Konrad Rzeszutek Wilk
2015-03-30 15:30 ` Andrew Cooper [this message]
2015-03-30 15:47 ` Konrad Rzeszutek Wilk
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=55196BF9.2090905@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=keir@xen.org \
--cc=konrad.wilk@oracle.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.