xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: "Yang, Xiaowei" <xiaowei.yang@intel.com>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Root cause of the issue that HVM guest boots slowly with pvops dom0
Date: Thu, 21 Jan 2010 08:44:33 +0000	[thread overview]
Message-ID: <C77DC471.6ED6%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <4B580D6A.4030802@intel.com>

On 21/01/2010 08:16, "Yang, Xiaowei" <xiaowei.yang@intel.com> wrote:

> - Limiting vCPU# of dom0 is always an easiest one - you may call it workaround
> rather than a solution:) It not only reduces the total # of resched IPI ( =
> mlock# * (vCPU#-1)), but reduces the cost of each handler - because of
> spinlock. 
> But the impact is still there, more or less, when vCPU# > 1.
> 
> - To remove mlock, another sharing method is needed between dom0 user space
> app
> and Xen HV.

A pre-mlock()ed memory page for small (sub-page) hypercalls? Protected with
a semaphore: failure to acquire semaphore means take slow path. Have all
hypercallers in libxc launder their data buffers through a new interface
that tries to grab and copy into the pre-allocated buffer.

 -- Keir

  reply	other threads:[~2010-01-21  8:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-21  8:16 Root cause of the issue that HVM guest boots slowly with pvops dom0 Yang, Xiaowei
2010-01-21  8:44 ` Keir Fraser [this message]
2010-01-21  9:27   ` Keir Fraser
2010-01-21 11:23     ` Keir Fraser
2010-01-22  8:07       ` Yang, Xiaowei
2010-01-22  8:31         ` Keir Fraser
2010-01-22  8:48           ` Yang, Xiaowei

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=C77DC471.6ED6%keir.fraser@eu.citrix.com \
    --to=keir.fraser@eu.citrix.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=xiaowei.yang@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).