From: Don Slutz <dslutz@verizon.com>
To: "Pasi Kärkkäinen" <pasik@iki.fi>,
"Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com>
Cc: xen-devel@lists.xenproject.org, Ian Jackson <Ian.Jackson@eu.citrix.com>
Subject: Re: [PATCH] README, xen/Makefile: Update to Xen 4.5.0
Date: Tue, 06 Jan 2015 14:30:18 -0500 [thread overview]
Message-ID: <54AC37CA.5060708@terremark.com> (raw)
In-Reply-To: <20150106191422.GY19091@reaktio.net>
On 01/06/15 14:14, Pasi Kärkkäinen wrote:
> On Tue, Jan 06, 2015 at 01:21:58PM -0500, Konrad Rzeszutek Wilk wrote:
>> On Tue, Jan 06, 2015 at 06:06:23PM +0000, Ian Jackson wrote:
>>> Konrad Rzeszutek Wilk writes ("[Xen-devel] [PATCH] README, xen/Makefile: Update to Xen 4.5.0"):
>>>> -The 4.3 release offers a number of improvements, including NUMA
>>>> -scheduling affinity, openvswitch integration, and defaulting to
>>>> -qemu-xen rather than qemu-traditional for non-stubdom guests.
>>>> -(qemu-xen is kept very close to the upstream project.) We also have a
>>>> -number of updates to vTPM, and improvements to XSM and Flask to allow
>>>> -greater disaggregation. Additionally, 4.3 contains a basic version of
>>>> -Xen for the new ARM server architecture, both 32- and 64-bit. And as
>>>> -always, there are a number of performance, stability, and security
>>>> +The 4.5 release offers a number of improvements: including shedding
>>>
>>> Should read
>>> +The 4.5 release offers a number of improvements, including: shedding
>>> (note two punctuation changes) and the list items should all be
>>> separated with semicolons IMO.
>>
>>
>> Thank you for your update.
>>
>> I've incorporated feedback from all folks I hope. Would this be satisfactory?
>>
>
> Do we want to mention things like HVM guest direct kernel boot,
> or HVM guests MMIO hole resize support?
>
It is not "resize" support, it is configure size support. And
yes it might be good to list it.
-Don Slutz
>
> And I think there was optimizations to oxenstored to support up to 1000 VMs per host..
>
>
> -- Pasi
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
>
next prev parent reply other threads:[~2015-01-06 19:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-06 17:17 (no subject) Konrad Rzeszutek Wilk
2015-01-06 17:17 ` [PATCH] README, xen/Makefile: Update to Xen 4.5.0 Konrad Rzeszutek Wilk
2015-01-06 17:40 ` Julien Grall
2015-01-06 17:51 ` Konrad Rzeszutek Wilk
2015-01-06 17:54 ` Sander Eikelenboom
2015-01-06 18:00 ` Konrad Rzeszutek Wilk
2015-01-06 17:59 ` Andrew Cooper
2015-01-06 18:00 ` Ian Campbell
2015-01-06 18:06 ` Ian Jackson
2015-01-06 18:21 ` Konrad Rzeszutek Wilk
2015-01-06 18:26 ` Andrew Cooper
2015-01-06 18:46 ` Sander Eikelenboom
2015-01-07 9:07 ` Ian Campbell
2015-01-06 19:14 ` Pasi Kärkkäinen
2015-01-06 19:30 ` Don Slutz [this message]
2015-01-07 15:27 ` Konrad Rzeszutek Wilk
2015-01-07 15:33 ` Pasi Kärkkäinen
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=54AC37CA.5060708@terremark.com \
--to=dslutz@verizon.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=konrad.wilk@oracle.com \
--cc=pasik@iki.fi \
--cc=xen-devel@lists.xenproject.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 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.