From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Chen, Tiejun" Subject: Re: [v6][PATCH 2/2] xen:vtd: missing RMRR mapping while share EPT Date: Fri, 12 Sep 2014 16:27:21 +0800 Message-ID: <5412AE69.6050300@intel.com> References: <1406684186-12788-1-git-send-email-tiejun.chen@intel.com> <1406684186-12788-2-git-send-email-tiejun.chen@intel.com> <53D8CAC402000078000278E9@mail.emea.novell.com> <53D8B408.1010409@intel.com> <53D8D5A0020000780002792A@mail.emea.novell.com> <53D8BD70.7040905@intel.com> <53D8E4370200007800027986@mail.emea.novell.com> <53D8CB80.1000606@intel.com> <53D8E95A02000078000279BD@mail.emea.novell.com> <53DA103B.4000308@intel.com> <53DB552C020000780002846D@mail.emea.novell.com> <53DB3D57.5010107@intel.com> <53DB5C3002000078000284A4@mail.emea.novell.com> <53DB62EA.4090502@intel.com> <53DBB691020000780002875B@mail.emea.novell.com> <53DDED01.7000607@intel.com> <53DF53070200007800028CF1@mail.emea.novell.com> <5406E23B.9020806@intel.com> <540701610200007800030254@mail.emea.novell.com> <541294FB.2020202@intel.com> <5412BAA9020000780003452D@mail.emea.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <5412BAA9020000780003452D@mail.emea.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 , "lars.kurth@xen.org" Cc: yang.z.zhang@intel.com, kevin.tian@intel.com, xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org On 2014/9/12 15:19, Jan Beulich wrote: >>>> On 12.09.14 at 08:38, wrote: >> On 2014/9/3 17:54, Jan Beulich wrote: >>>>>> On 03.09.14 at 11:41, wrote: >>>>> >>>>>> Additionally, I want to know if patch v6 is fine to be acked. >>>>> >>>>> My position hasn't changed: I view this as correct but incomplete, >>>>> and hence not ready for inclusion. With - iirc - Tim being of a >>>>> different opinion, if you want to push for a decision without >>>>> supplying the missing pieces, see the section "Conflict Resolution" >>>>> on http://www.xenproject.org/governance.html. But of course >>>>> I'd much prefer to avoid having to fall back to this, and instead >>>>> have a complete patch set to commit within reasonable time. >>>> >>>> Looks I can't make my RFC patches to implement a complete RMRR >>>> supporting better as you pointed while reviewing, so I have to go back >>>> looking at this. >>> >>> Please just give me a little time to hand you a replacement patch on >>> which you could then base the rest of your series. But please also >>> realize that this isn't my top priority. >>> >>> Jan >>> >>>> So how can I issue such a private vote on these two patches? I don't see >>>> How-to in the section "Conflict Resolution" on >>>> http://www.xenproject.org/governance.html. >>>> >> >> Jan, >> >> I have to admit its really hard to push this RMRR RFC with my >> experiences and skills. Currently every new revision doesn't minimize >> all previous comments. Instead, it always brings more comments or >> arguments. So I don't think myself can do this very well in Xen side. >> >> So I still hope we can issue such a vote on these two patches if possible. > > Lars, how would we go about this? > >> Once I have enough capability to cover this I can go back or other guys >> may do really better than me. > > I already helped you with the first patch. Did you ask the VT-d Yes, this already costs more our time as you said, and this is also one reason why I'm saying myself can't finish this series completely. Recently looks we have to re-concern this to cover more scenarios, hotplug, migration and so forth. I don't think I already have a clear design to address everything. Originally that series is just as RFC. And I believe you already don't hope I post too much more incomplete codes to you again. > maintainers for help with the rest? > Ditto. Thanks Tiejun