All of lore.kernel.org
 help / color / mirror / Atom feed
From: George Dunlap <george.dunlap@eu.citrix.com>
To: Keir Fraser <Keir.Fraser@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Kouya Shimura <kouya@jp.fujitsu.com>
Subject: Re: [PATCH] PoD: Check p2m assumption in debug builds
Date: Thu, 17 Sep 2009 10:43:09 +0100	[thread overview]
Message-ID: <4AB204AD.30201@eu.citrix.com> (raw)
In-Reply-To: <C6D79240.14F49%keir.fraser@eu.citrix.com>

Keir Fraser wrote:
> On 17/09/2009 02:26, "Kouya Shimura" <kouya@jp.fujitsu.com> wrote:
>
>   
>> real 0m2.343s
>> user 0m0.040s
>> sys 0m0.030s
>>
>> real 2m25.741s
>> user 0m0.090s
>> sys 0m0.020s
>>
>> I'm about to lose my patience with it. :-)
>> Can you control it by a boot parameter? (ex. "pod_debug=nnn")
>>     
>
> Yeah, that's too slow for our normal debug build. I think we'll revert the
> patch -- noone would ever enable it, unless maybe if helping George track
> down a PoD bug.
>   
Hmm... my only concern is that the assumption seems like something which 
might easily change, with no one realizing that they'd broken the 
assumption, and the codepath not being tested since most OSS users 
probably won't be using PoD.

Hmm, perhaps we could wrap it with an if() statement checking if there 
are any outstanding PoD entries?  The assumption only really matters 
when PoD is in use.

Alternately, a separate #define for PoD debug might be useful, so we can 
easily turn on all these options when we need to.

 -George

      reply	other threads:[~2009-09-17  9:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-11 10:40 [PATCH] PoD: Check p2m assumption in debug builds George Dunlap
2009-09-17  1:26 ` Kouya Shimura
2009-09-17  6:14   ` Keir Fraser
2009-09-17  9:43     ` George Dunlap [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=4AB204AD.30201@eu.citrix.com \
    --to=george.dunlap@eu.citrix.com \
    --cc=Keir.Fraser@eu.citrix.com \
    --cc=kouya@jp.fujitsu.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.