From mboxrd@z Thu Jan 1 00:00:00 1970 From: George Dunlap Subject: Re: Xen 4.4 development update Date: Wed, 14 Aug 2013 11:35:25 +0100 Message-ID: <520B5D6D.1090907@eu.citrix.com> References: <5204BF3402000078000EA952@nat28.tlf.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <5204BF3402000078000EA952@nat28.tlf.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Jan Beulich Cc: "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org On 09/08/13 09:06, Jan Beulich wrote: >>>> On 08.08.13 at 18:09, George Dunlap wrote: >> === clean-ups === >> >> * Implement Xen hypervisor dmesg log entry timestamps > Isn't that what the "console_timestamps" command line option > already does? Or if not, what is this about? It comes from this uservoice suggestion by Pasi: https://xenorg.uservoice.com/forums/172169-xen-development/suggestions/3924048-implement-xen-hypervisor-dmesg-log-entry-timestamp Andy C. commented, saying that "console_timestamps" was a bit heavyweight, and that this (which only has seconds since boot) was more useful. I'll update this to reflect that. >> * Multi-vector PCI MSI (support at least for Dom0) >> owner: jan@suse >> status: Patches posted for Intel; AMD not yet done > Oh, this was listed under cleanups. Anyway - it's done (also for > AMD). Yes, sorry -- the list is getting awfully long, and I was under some pressure to get the list out, particularly as it had been over a month since the 4.3 release. I've re-organized stuff now and will post it to the wiki in the better-organized format. -George