From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: 4.2 TODO update Date: Mon, 12 Mar 2012 16:42:56 +0000 Message-ID: <1331570576.23971.154.camel@zakaz.uk.xensource.com> References: <1331554278.23971.63.camel@zakaz.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: George Dunlap Cc: "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org On Mon, 2012-03-12 at 16:36 +0000, George Dunlap wrote: > On Mon, Mar 12, 2012 at 12:11 PM, Ian Campbell wrote: > > This update covers two weeks since I was away last week. > > > > As usual please ping me with any updates/corrections. There are several > > things below which are in need of a volunteer to take care of them... > > > > hypervisor, blockers: > > * domctls / sysctls set up to modify scheduler parameters, like > > the credit1 timeslice and schedule rate. (George Dunlap, DONE) > > I recently discovered a set of patches updating the PoD code in the > XenServer patchqueue which I was meant to have upstreamed but never > actually got to. Can I add this to the "blockers" list? If we've been living without them are they really blockers? Adding them to the nice to have list seems like a no brainer but a few words on why they are blockers could easily upgrade my assessment ;-) Ian.