All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: "Yang, Xiaowei" <xiaowei.yang@intel.com>
Cc: "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: Fri, 22 Jan 2010 08:31:56 +0000	[thread overview]
Message-ID: <C77F12FC.718C%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <4B595CCD.3070509@intel.com>

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

>> How does the attached patch work for you? It ought to get you the same
>> speedup as your hack.
> 
> The speed should be almost the same, regardless of twice memcpy.

Did you actually try it out and confirm that?

> Some comments to your trial patch:
> 1.
> diff -r 6b61ef936e69 tools/libxc/xc_private.c
> --- a/tools/libxc/xc_private.c Fri Jan 22 14:50:30 2010 +0800
> +++ b/tools/libxc/xc_private.c Fri Jan 22 15:32:48 2010 +0800

Yes, missed that all-important bit!

> 2. _xc_clean_hcall_buf needs a more careful NULL pointer check.

Not really: free() accepts NULL. But I suppose it would be clearer to put
the free(hcall_buf) inside the if(hcall_buf) block.

> 3. It does modification to 5 out of 73 hypercalls invoking mlock. Other
> problem 
> hypercalls could turn out to be the bottleneck later?:)

The point of a new interface was to be able to do the callers incrementally.
A bit of care is needed on each one, and most are not and probably never
will be bottlenecks.

 -- Keir

  reply	other threads:[~2010-01-22  8:31 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
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 [this message]
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=C77F12FC.718C%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 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.