All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Michael Abd-El-Malek <mabdelmalek@cmu.edu>
Cc: Mark McLoughlin <markmc@redhat.com>,
	xen-devel <xen-devel@lists.xensource.com>,
	Andrea Arcangeli <andrea@qumranet.com>,
	Eduardo Habkost <ehabkost@redhat.com>,
	Keir Fraser <keir.fraser@eu.citrix.com>,
	Christoph Lameter <clameter@sgi.com>
Subject: Re: Vanilla Linux and has_foreign_mapping
Date: Tue, 29 Apr 2008 10:32:22 -0700	[thread overview]
Message-ID: <48175BA6.1090700@goop.org> (raw)
In-Reply-To: <7EA259C2-60B9-46FF-AF13-BD52C2E071A2@cmu.edu>

Michael Abd-El-Malek wrote:
> Some drivers may need to do additional tasks besides just clearing the 
> PTE.   For example, when unzapping my kernel PTE, I need to restore 
> the physical mapping of the page.  (On the initial set_pte (which I've 
> overridden), I removed the physical backing of the page.)
>
> If we really want to avoid a zap_pte hook, I suppose we can add flags 
> to the page/PTE that indicate things like "this page needs to have its 
> physical backing restored".

Is that something that needs to happen synchronously with the unmap, or 
could the driver do it in its vma callback?  What do you mean by 
remove/restoring the physical backing?  Do any of the in-tree drivers do 
this?

In the PAE case, which I think we can regard as usual these days, we 
have 64-bits to store per-mapping info, so stashing a callback or 
callback index seems pretty straightforward if we need full generality.

    J

  reply	other threads:[~2008-04-29 17:32 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-20 21:19 Vanilla Linux and has_foreign_mapping Michael Abd-El-Malek
2008-04-21 11:46 ` Jeremy Fitzhardinge
2008-04-21 16:36   ` Mark McLoughlin
2008-04-21 18:00   ` Michael Abd-El-Malek
2008-04-21 17:52 ` Keir Fraser
2008-04-21 18:10   ` Michael Abd-El-Malek
2008-04-21 18:17     ` Michael Abd-El-Malek
2008-04-21 18:30       ` Keir Fraser
2008-04-25  0:18         ` Jeremy Fitzhardinge
2008-04-25  6:01           ` Keir Fraser
2008-04-25 17:11           ` Michael Abd-El-Malek
2008-04-25 18:22             ` Jeremy Fitzhardinge
2008-04-25 18:31               ` Michael Abd-El-Malek
2008-04-25 22:33                 ` Jeremy Fitzhardinge
2008-04-29 16:39                   ` Michael Abd-El-Malek
2008-04-29 17:32                     ` Jeremy Fitzhardinge [this message]
2008-04-30 16:31                       ` Michael Abd-El-Malek
     [not found]             ` <20080425172416.GC23300@duo.random>
2008-04-26  0:14               ` Jeremy Fitzhardinge

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=48175BA6.1090700@goop.org \
    --to=jeremy@goop.org \
    --cc=andrea@qumranet.com \
    --cc=clameter@sgi.com \
    --cc=ehabkost@redhat.com \
    --cc=keir.fraser@eu.citrix.com \
    --cc=mabdelmalek@cmu.edu \
    --cc=markmc@redhat.com \
    --cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.