xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Andre Przywara <andre.przywara@amd.com>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] x86/hvm: accelerate IO intercept handling
Date: Fri, 05 Mar 2010 15:55:17 +0000	[thread overview]
Message-ID: <C7B6D9E5.C58B%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <4B91281D.7010405@amd.com>

On 05/03/2010 15:49, "Andre Przywara" <andre.przywara@amd.com> wrote:

>> Unless the speedup on the only
>> possibly-interesting workload you mention is significant, this whole
>> optimisation seems unnecessary.
> Actually it is missing enablement.

Yes it's very important to use *every* CPU feature. ;-)

Well, the patch looks okay, and it may speed up things we care about a
percent or two I guess. I will look at it properly after 4.0 and I'm sure we
can get it in the tree.

 -- Keir

      reply	other threads:[~2010-03-05 15:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-05 14:36 [PATCH] x86/hvm: accelerate IO intercept handling Andre Przywara
2010-03-05 14:52 ` Keir Fraser
2010-03-05 15:49   ` Andre Przywara
2010-03-05 15:55     ` Keir Fraser [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=C7B6D9E5.C58B%keir.fraser@eu.citrix.com \
    --to=keir.fraser@eu.citrix.com \
    --cc=andre.przywara@amd.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 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).