xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: George Dunlap <George.Dunlap@eu.citrix.com>
Cc: Keir Fraser <keir@xen.org>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH 0 of 5] HVM performance improvements
Date: Tue, 6 Aug 2013 10:59:21 +0100	[thread overview]
Message-ID: <5200C8F9.8020204@citrix.com> (raw)
In-Reply-To: <CAFLBxZYs2_3je=UCcqQSLXpYW+8MniLaAqpk3HCRCpj-W1eOLQ@mail.gmail.com>

On 06/08/13 10:57, George Dunlap wrote:
> On Mon, Aug 5, 2013 at 6:10 PM, Andrew Cooper <andrew.cooper3@citrix.com> wrote:
>> On 05/08/13 17:31, Pasi Kärkkäinen wrote:
>>> On Thu, May 09, 2013 at 05:07:36PM +0300, Pasi Kärkkäinen wrote:
>>>> On Mon, Nov 26, 2012 at 04:41:31PM +0000, Andrew Cooper wrote:
>>>>> This patch series contains the results of an investigation by XenServer
>>>>> to try and reduce dom0 load during a VDI bootstorm.
>>>>>
>>>>> All patches reduce the number of polled IO traps to qemu that a booting
>>>>> HVM domain uses.
>>>>>
>>>>> The patches are unmodified from the last time I posted them to the list,
>>>>> but are presented now outside of a feature freeze.
>>>>>
>>>> It's feature freeze time again :)
>>>>
>>>> Are these patches still necessary? for Xen 4.4?
>>>>
>>> Xen 4.3 is now out of the door, so should these patches be considered for Xen 4.4 ?
>>>
>>> Thanks,
>>>
>>> -- Pasi
>>>
>> I would dearly love for these patches to finally go in.  The patches
>> likely apply as-are.
> Any chance you could re-post them?
>
>  -George

Sure - coming up

~Andrew

      reply	other threads:[~2013-08-06  9:59 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-26 16:41 [PATCH 0 of 5] HVM performance improvements Andrew Cooper
2012-11-26 16:41 ` [PATCH 1 of 5] rombios/keyboard: Don't needlessly poll the status register Andrew Cooper
2012-11-26 16:48   ` Ian Campbell
2012-11-26 16:53     ` Andrew Cooper
2012-11-27 16:33   ` Tim Deegan
2012-11-27 17:08     ` Andrew Cooper
2012-11-26 16:41 ` [PATCH 2 of 5] rombios/ata: Do not wait for BSY to be set Andrew Cooper
2012-11-27 16:46   ` Tim Deegan
2012-11-27 17:02     ` Mats Petersson
2012-11-27 17:08     ` Alan Cox
2012-11-27 17:22       ` Andrew Cooper
2012-11-27 17:49         ` Alan Cox
2012-11-27 18:24           ` Andrew Cooper
2012-11-26 16:41 ` [PATCH 3 of 5] rombios/ata: Reading this status register has no relevant side effects Andrew Cooper
2012-11-26 16:51   ` Ian Campbell
2012-11-26 16:56     ` Andrew Cooper
2012-11-26 17:01       ` Ian Campbell
2012-11-26 16:41 ` [PATCH 4 of 5] rombios/ata Remove more needless traps from the int 0x13 path Andrew Cooper
2012-11-26 16:41 ` [PATCH 5 of 5] rombios/debug: Reduce verbosity of rombios Andrew Cooper
2012-11-27 17:07   ` Tim Deegan
2013-05-09 14:07 ` [PATCH 0 of 5] HVM performance improvements Pasi Kärkkäinen
2013-08-05 16:31   ` Pasi Kärkkäinen
2013-08-05 17:10     ` Andrew Cooper
2013-08-06  9:57       ` George Dunlap
2013-08-06  9:59         ` Andrew Cooper [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=5200C8F9.8020204@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=keir@xen.org \
    --cc=xen-devel@lists.xen.org \
    /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).