xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@suse.com>
To: Yang Z Zhang <yang.z.zhang@intel.com>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
	"andrew.cooper3@citrix.com" <andrew.cooper3@citrix.com>,
	Tim Deegan <tim@xen.org>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	"KeirFraser(keir.xen@gmail.com)" <keir.xen@gmail.com>,
	Jun Nakajima <jun.nakajima@intel.com>,
	Xiantao Zhang <xiantao.zhang@intel.com>
Subject: Re: [PATCH] Don't track all memory when enabling log dirty to track vram
Date: Fri, 23 May 2014 07:42:20 +0100	[thread overview]
Message-ID: <537F09EC020000780001530D@mail.emea.novell.com> (raw)
In-Reply-To: <A9667DDFB95DB7438FA9D7D576C3D87E0AACF97A@SHSMSX104.ccr.corp.intel.com>

>>> On 21.05.14 at 10:37, <yang.z.zhang@intel.com> 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

  parent reply	other threads:[~2014-05-23  6:42 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-10  6:14 [PATCH] Don't track all memory when enabling log dirty to track vram Yang Zhang
2014-02-10  8:03 ` Tim Deegan
2014-02-10  8:15   ` Zhang, Yang Z
2014-02-11  9:02     ` Tim Deegan
2014-02-11 10:59       ` George Dunlap
2014-02-11 11:55         ` Tim Deegan
2014-02-11 12:57           ` Jan Beulich
2014-02-11 15:55             ` George Dunlap
2014-02-12  0:53               ` Zhang, Yang Z
2014-02-13 15:46                 ` George Dunlap
2014-02-13 15:55                   ` Jan Beulich
2014-02-13 16:20                     ` Tim Deegan
2014-02-13 16:25                       ` George Dunlap
2014-02-13 16:45                         ` Processed: " xen
2014-02-17 10:18                       ` Jan Beulich
2014-02-17 12:23                         ` George Dunlap
2014-02-17 12:37                           ` Jan Beulich
2014-02-17 14:51                         ` George Dunlap
2014-02-17 15:05                           ` Jan Beulich
2014-02-18  3:14                             ` Zhang, Yang Z
2014-02-18 10:26                               ` George Dunlap
2014-02-19  1:28                                 ` Zhang, Yang Z
2014-02-19  8:55                                   ` Jan Beulich
2014-02-19 11:03                                     ` George Dunlap
2014-02-19 11:13                                       ` Jan Beulich
2014-02-19 11:17                                         ` George Dunlap
2014-02-17 15:00                         ` Jan Beulich
2014-02-18  3:25                           ` Zhang, Yang Z
2014-02-18  8:45                             ` Jan Beulich
2014-02-18 11:46                             ` Jan Beulich
2014-02-18 15:28                               ` Jan Beulich
2014-02-19  6:40                                 ` Xu, Dongxiao
2014-02-19  1:17                               ` Zhang, Yang Z
2014-02-19  8:50                                 ` Jan Beulich
2014-02-18  8:30                           ` Jan Beulich
2014-05-19  7:48                       ` Zhang, Yang Z
2014-05-19  9:03                         ` Jan Beulich
2014-05-20  3:09                           ` Zhang, Yang Z
2014-05-20  7:17                             ` Jan Beulich
2014-05-19 13:27                         ` George Dunlap
2014-05-19 13:50                           ` Jan Beulich
2014-05-19 13:59                             ` George Dunlap
2014-05-19 14:19                               ` Jan Beulich
2014-05-20  3:13                           ` Zhang, Yang Z
2014-05-20  7:20                             ` Jan Beulich
2014-05-20 10:12                               ` George Dunlap
2014-05-20 10:46                                 ` Jan Beulich
2014-05-21  1:02                                   ` Zhang, Yang Z
2014-05-21  7:49                                     ` Jan Beulich
2014-05-21  8:37                                       ` Zhang, Yang Z
2014-05-21  9:58                                         ` Jan Beulich
2014-05-23  6:42                                         ` Jan Beulich [this message]
2014-05-26  8:16                                           ` Zhang, Yang Z
2014-05-26  9:04                                             ` Jan Beulich
2014-05-31  1:26                                               ` Nakajima, Jun
2014-06-02  6:55                                                 ` Jan Beulich
2014-06-02 14:06                                                   ` George Dunlap
2014-06-02 14:27                                                     ` Jan Beulich
2014-06-02 15:03                                                       ` George Dunlap
2014-02-10 10:42   ` Andrew Cooper
2014-02-10 16:13 ` George Dunlap
2014-02-10 16:30   ` Processed: " xen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=537F09EC020000780001530D@mail.emea.novell.com \
    --to=jbeulich@suse.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=jun.nakajima@intel.com \
    --cc=keir.xen@gmail.com \
    --cc=tim@xen.org \
    --cc=xen-devel@lists.xen.org \
    --cc=xiantao.zhang@intel.com \
    --cc=yang.z.zhang@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).