From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Jan Beulich" Subject: Re: [v6][PATCH 2/2] xen:vtd: missing RMRR mapping while share EPT Date: Thu, 25 Sep 2014 16:14:28 +0100 Message-ID: <54244D7402000078000390F2@mail.emea.novell.com> References: <541FB087.4080008@intel.com> <541FB7C3.9080608@intel.com> <541FFFC50200007800036C28@mail.emea.novell.com> <541FE65A.8070803@intel.com> <542017E80200007800036D1E@mail.emea.novell.com> <5420D357.1060202@intel.com> <5422A08C020000780003814F@mail.emea.novell.com> <5423E98E0200007800038C27@mail.emea.novell.com> <20140925141215.GC20089@laptop.dumpdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20140925141215.GC20089@laptop.dumpdata.com> Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Konrad Rzeszutek Wilk Cc: Yang Z Zhang , Tiejun Chen , Kevin Tian , "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org >>> On 25.09.14 at 16:12, wrote: > On Thu, Sep 25, 2014 at 09:08:14AM +0100, Jan Beulich wrote: >> Considering it's a bug that gets fixed, I would think so. But as for >> anything more involved, Konrad as the release manager will have >> the final say. > > What are the non-bugs (features) that we speak of? There are no non-bug changes here. It's just that the issue has always been there, so is also not a regression. > Are the the ones that had > been posted (and then one written by Jan and then reworked)? Yes, and which need further reworking. > Please do be aware that the feature freeze window time has just elapsed > (yesterday) > so anything to be considered a feature should have been posted before or on > that date. > > Please keep in mind that bug-fixes can be posted and checked in _after_ the > feature freeze. But as the RCs numbers increases the likehood of bugs being > checked in goes down (to reduce the risk of further regressions instroduced > by bug-fixes). That's the main reason why I pointed at you as the release manager - together with this not being a new bug our willingness to add a fix for this will presumably decrease as time goes on. Jan