From mboxrd@z Thu Jan 1 00:00:00 1970 From: George Dunlap Subject: Re: Xen 4.3 development update Date: Tue, 2 Apr 2013 16:51:22 +0100 Message-ID: <515AFE7A.7020701@eu.citrix.com> References: <515B186F02000078000CA1A7@nat28.tlf.novell.com> <515AFD37.7020609@amd.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <515AFD37.7020609@amd.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: Suravee Suthikulanit Cc: Jan Beulich , "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org On 02/04/13 16:45, Suravee Suthikulanit wrote: > On 4/2/2013 10:42 AM, Jan Beulich wrote: >>>>> On 02.04.13 at 16:07, George Dunlap wrote: >>> * AMD NPT performance regression after c/s 24770:7f79475d3de7 >>> owner: ? >>> Reference: http://marc.info/?l=xen-devel&m=135075376805215 >> This is supposedly fixed with the RTC changes Tim committed the >> other day. Suravee, is that correct? > Let me verify this again with the new changes. I was looking at the > clock drifting issue on the 64-bit XP which was running fine. Let me > check 32-bit and get back to you today. > >>> * Remove hardcoded mobprobe's in xencommons >>> owner: ? >>> status: ? >>> prognosis: Poor. >> So before 4.2 got released it was promised to get dealt with, and >> now it's "poor" with no owner and status? Disappointing. > I was not aware of this issue. Could you give me some context of this? Just to be clear, this doesn't have anything to do with AMD -- it's a separate subject Jan is complaining about. :-) Jan: "Poor" just means that it needs intervention; namely, we need someone to step up and volunteer to do it. I'll ask for volunteers sometime this week. -George