All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Andrew Cooper <andrew.cooper3@citrix.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 11:47:47 -0400	[thread overview]
Message-ID: <20150330154747.GF31851@l.oracle.com> (raw)
In-Reply-To: <55196BF9.2090905@citrix.com>

On Mon, Mar 30, 2015 at 04:30:01PM +0100, Andrew Cooper wrote:
> 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

.. in which I proposed an path that you had choosen in this patch.
> 
> 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.

<nods>

I know I've been using this in the field (so no need to deploy a
new build) - but then eventually I had to build an custom Xen binary.

Anyhow thank you for refreshing my memory on this patchset.

and in regards to the patch:
Reviewed-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>

> 
> ~Andrew

      reply	other threads:[~2015-03-30 15:47 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
2015-03-30 15:47     ` Konrad Rzeszutek Wilk [this message]

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=20150330154747.GF31851@l.oracle.com \
    --to=konrad.wilk@oracle.com \
    --cc=JBeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=keir@xen.org \
    --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.