LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Zachary Amsden <zach@vmware.com>
To: David Rientjes <rientjes@google.com>
Cc: Hugh Dickins <hugh@veritas.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Ingo Molnar <mingo@redhat.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [patch -mm 1/2] i386: add ptep_test_and_clear_{dirty,young}
Date: Mon, 26 Mar 2007 12:22:03 -0800	[thread overview]
Message-ID: <46082B6B.8010707@vmware.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0703252334110.4535@chino.kir.corp.google.com>

David Rientjes wrote:
> On Sun, 25 Mar 2007, Zachary Amsden wrote:
>
>   
>> If you actually clear the bit, you need to:
>>
>> +         pte_update_defer(vma->vm_mm, addr, ptep);
>>
>> The reason is, when updating PTEs, the hypervisor must be notified.  Using
>> atomic operations to do this is fine for all hypervisors I am aware of.
>> However, for hypervisors which shadow page tables, if these PTE modifications
>> are not trapped, you need a post-modification call to fulfill the update of
>> the shadow page table.
>>
>>     
>
> Then why was ptep_test_and_clear_{dirty,young} ever removed in the first 
> place??  To gain the optimization of one fewer branch and introduce a hack 
> to advertise it's existance so the generic header file doesn't include its 
> own version?
>   

Yes, pretty much.

Zach

      reply	other threads:[~2007-03-26 19:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-26  0:35 [patch -mm 1/2] i386: add ptep_test_and_clear_{dirty,young} David Rientjes
2007-03-26  0:35 ` [patch -mm 2/2] smaps: use ptep_test_and_clear_young David Rientjes
2007-03-26  5:53 ` [patch -mm 1/2] i386: add ptep_test_and_clear_{dirty,young} Hugh Dickins
2007-03-26  7:07   ` Zachary Amsden
2007-03-26  6:27     ` Hugh Dickins
2007-03-26 20:20       ` Zachary Amsden
2007-03-26  6:35     ` David Rientjes
2007-03-26 20:22       ` Zachary Amsden [this message]

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=46082B6B.8010707@vmware.com \
    --to=zach@vmware.com \
    --cc=akpm@linux-foundation.org \
    --cc=hugh@veritas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=rientjes@google.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).