xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: "Jiang, Yunhong" <yunhong.jiang@intel.com>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] Allocate vmcs pages when system booting
Date: Thu, 12 Nov 2009 15:04:02 +0000	[thread overview]
Message-ID: <C721D462.BE92%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <E2263E4A5B2284449EEBD0AAB751098418E55575CE@PDSMSX501.ccr.corp.intel.com>

On 12/11/2009 14:58, "Jiang, Yunhong" <yunhong.jiang@intel.com> wrote:

>> Can you try this alternative fix please?
> 
> Yes, spin_debug_disable() is the first idea come into my mind, I change my
> mind because the spin_debug is a global variable.  disable spin_debug() before
> start_secondary means maybe we can't catch error happens at that window, so I
> choose this method. Previously I thought high-end system support cpu hotplug
> may not care about the 64 pages :$

CONFIG_HOTPLUG_CPU is not a user-accessible build option. In fact manually
disabling it in config.h resulted in a broken build, and now I basically
stripped out the non-HOTPLUG_CPU code (in c/s 20431). So this would be an
overhead for absolutely everyone.

> Or you assume this window is quite small, and we can assume safely if a error
> happening at this window, it will happen in other timeslot in the end,
> sepecially this function itself don't need the check?

Exactly. The spinlock debug checking can be best effort. I did think about
allowing the checks to be disabled per-cpu, but I don't think it's worth it.

I will check in my suggested fix, then.

 -- Keir

  reply	other threads:[~2009-11-12 15:04 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-12 10:52 [PATCH] Allocate vmcs pages when system booting Jiang, Yunhong
2009-11-12 11:22 ` Keir Fraser
2009-11-12 14:58   ` Jiang, Yunhong
2009-11-12 15:04     ` Keir Fraser [this message]
2009-11-12 15:15       ` Jiang, Yunhong
2010-01-15  9:06   ` Jiang, Yunhong
2010-01-15  9:30     ` Jan Beulich
2010-01-15 10:31       ` Keir Fraser
2010-01-17  2:02         ` Jiang, Yunhong
2010-01-17 21:35           ` Keir Fraser
2010-01-18  8:11             ` Keir Fraser
2010-01-18  8:22               ` Jiang, Yunhong
2010-03-18 10:45         ` Jan Beulich
2010-03-18 10:51           ` Keir Fraser
2010-03-19  2:17           ` Jiang, Yunhong
2010-01-15 10:28     ` Keir Fraser

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=C721D462.BE92%keir.fraser@eu.citrix.com \
    --to=keir.fraser@eu.citrix.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=yunhong.jiang@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).