From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: pvops upstream status Date: Tue, 17 Jun 2014 06:25:32 -0400 Message-ID: <20140617102532.GA20722@laptop.dumpdata.com> References: <53A00FE5.3050709@suse.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WwqaC-0005zE-VE for xen-devel@lists.xenproject.org; Tue, 17 Jun 2014 10:25:41 +0000 Content-Disposition: inline In-Reply-To: <53A00FE5.3050709@suse.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: Juergen Gross Cc: xen-devel@lists.xenproject.org List-Id: xen-devel@lists.xenproject.org On Tue, Jun 17, 2014 at 11:52:37AM +0200, Juergen Gross wrote: > Hi, > > I'd like to update the wiki page > > http://wiki.xenproject.org/wiki/XenParavirtOps > > regarding the current status of the pvops kernel. I've just started to > collect the missing bits and who is working on them. Up to now I have a > SUSE internal list, some data from Konrad, and, of course, the EFI > patches sent by Daniel last week: > > - EFI support (patches posted by Daniel Kiper on 13.06.2014) > - use of PAT (i.e. WC memory type) not possible > - microcode loader (runtime) > - 500Gb+ support > - expected to be dead (under Xen) code cannot be easily verified to > indeed be dead (e.g. IOMMU, PCI ATS, PRI, and PASID), leaving the > risk of bad interaction between hypervisor and Dom0 if a new, active > user of that code appears and goes unnoticed > - user mode pvclock that would something I had been looking at and hope to have some patches soon out. > - possibly not suitable for pre-4.0.1 hypervisor (definitely not as > Dom0) > - blktap (blktap3 replacement stalled) > - pvSCSI > - pvUSB > - oprofile (perf implementation having got started by Boris) > - some SUSE internal enhancement patches > > Done: > - memory hotplug (available 3.9) > - ACPI Sx handling (3.11) > - not using ticket locks (3.12) > - NMI injection/delivery (3.12) > - kexec (implementation not requiring a kernel layer in place) > - MSI-X possibly broken (fixed in 3.14) > - multi-vector MSI (3.15) > > I'll add above stuff to the wiki. Any further information is appreciated > especially regarding who is currently working on any of the above or not > mentioned topics. Missing topics not mentioned here with nobody working > on them are welcomed, too. > > > Juergen > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel