From xen-devel-bounces@lists.xen.org Fri May 23 07:49:05 2014 Received: (at maildrop) by bugs.xenproject.org; 23 May 2014 06:49:05 +0000 Received: from lists.xen.org ([50.57.142.19]) by bugs.xenproject.org with esmtp (Exim 4.80) (envelope-from ) id 1WnjHt-0001Ck-AL for xen-devel-maildrop-Eithu9ie@bugs.xenproject.org; Fri, 23 May 2014 07:49:05 +0100 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WnjBP-0002eG-2v; Fri, 23 May 2014 06:42:23 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WnjBN-0002e3-JQ for xen-devel@lists.xen.org; Fri, 23 May 2014 06:42:21 +0000 Received: from [85.158.139.211:53548] by server-7.bemta-5.messagelabs.com id 04/19-20531-CCDEE735; Fri, 23 May 2014 06:42:20 +0000 X-Env-Sender: JBeulich@suse.com X-Msg-Ref: server-9.tower-206.messagelabs.com!1400827339!5910525!1 X-Originating-IP: [130.57.118.101] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4272 invoked from network); 23 May 2014 06:42:20 -0000 Received: from mail.emea.novell.com (HELO mail.emea.novell.com) (130.57.118.101) by server-9.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 23 May 2014 06:42:20 -0000 Received: from EMEA1-MTA by mail.emea.novell.com with Novell_GroupWise; Fri, 23 May 2014 07:42:18 +0100 Message-Id: <537F09EC020000780001530D@mail.emea.novell.com> X-Mailer: Novell GroupWise Internet Agent 14.0.0 Date: Fri, 23 May 2014 07:42:20 +0100 From: "Jan Beulich" To: "Yang Z Zhang" References: <20140210080314.GA758@deinos.phlegethon.org> <20140211090202.GC92054@deinos.phlegethon.org> <20140211115553.GB97288@deinos.phlegethon.org> <52FA2C63020000780011B201@nat28.tlf.novell.com> <52FA480D.9040707@eu.citrix.com> <52FCE8BE.8050105@eu.citrix.com> <52FCF90F020000780011C29A@nat28.tlf.novell.com> <20140213162022.GE82703@deinos.phlegethon.org> <537B1E520200007800013EB7@mail.emea.novell.com> <537B4EA70200007800014085@mail.emea.novell.com> <537C769B02000078000145C2@mail.emea.novell.com> In-Reply-To: Mime-Version: 1.0 Content-Disposition: inline Cc: George Dunlap , "andrew.cooper3@citrix.com" , Tim Deegan , "xen-devel@lists.xen.org" , "KeirFraser\(keir.xen@gmail.com\)" , Jun Nakajima , Xiantao Zhang Subject: Re: [Xen-devel] [PATCH] Don't track all memory when enabling log dirty to track vram X-BeenThere: xen-devel@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen developer discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org >>> On 21.05.14 at 10:37, wrote: > Jan Beulich wrote on 2014-05-21: >> You didn't in any way negate the condition of superpage support to be >> added post-4.4 in order for your other change to go in: Neither >> http://lists.xenproject.org/archives/html/xen-devel/2014-02/msg01230.html >> nor >> http://lists.xenproject.org/archives/html/xen-devel/2014-02/msg01236.html >> have been responded to by you. By not doing so, to me at least you >> implicitly accepted the condition. And by now refusing to meet it, you >> basically tell us that we shouldn't be doing compromises like this with >> you in the future. > > I have said before I am totally unware of it. And I know it only two days > ago after someone told me. So please do not confuse this with the thing what > we are discussing now. If you think I gave a promise implicitly at that time, > I am sorry to let you think so. > > As I said in previous thread, if we can prove that add hugepage for the > separate VT-d page table is the only choice to solve problem, then now I am > promising that I will do it ASAP. But till now, I didn't see any point that > we must to have it. To me, it is still a nice to have feature. Btw., I think I just spotted a second thing not working without split page tables: mem-access (which doesn't and imo shouldn't depend on !need_iommu(), other than mem-sharing and mem-paging) likewise has the potential of creating entries resulting in IOMMU faults. Jan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel