From: Gerd Hoffmann <kraxel@redhat.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Xen Development Mailing List <xen-devel@lists.xensource.com>
Subject: Re: pv_ops & gntdev?
Date: Wed, 25 Feb 2009 22:43:26 +0100 [thread overview]
Message-ID: <49A5BB7E.8030503@redhat.com> (raw)
In-Reply-To: <49A5B9AA.7010709@goop.org>
Jeremy Fitzhardinge wrote:
> Gerd Hoffmann wrote:
>> Jeremy Fitzhardinge wrote:
>>
>>> Hm, I hope not. Doesn't it always end up using set_pte*?
>>>
>>
>> ptep_get_and_clear_full();
>>
>> See zap_pte_range() in mm/memory.c
>
> Ah, right. It could be changed to use ptep_modify_prot_start/commit.
> That would make it batchable too. Slightly less good for native.
Hmm. One more Q: How is pinning used? Is a process pinned all the
time? Or can it happen that the pages are unpinned in case it does hang
around idle for a while? Is there some way to prevent a process from
being unpinned?
I somehow feel like checking out mmu notifiers first ...
thanks,
Gerd
next prev parent reply other threads:[~2009-02-25 21:43 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-24 18:45 pv_ops & gntdev? Gerd Hoffmann
2009-02-24 21:18 ` Jeremy Fitzhardinge
2009-02-24 22:12 ` Gerd Hoffmann
2009-02-25 10:05 ` Gerd Hoffmann
2009-02-25 17:51 ` Jeremy Fitzhardinge
2009-02-25 18:37 ` Gerd Hoffmann
2009-02-25 20:06 ` Jeremy Fitzhardinge
2009-02-25 21:19 ` Gerd Hoffmann
2009-02-25 21:35 ` Jeremy Fitzhardinge
2009-02-25 21:43 ` Gerd Hoffmann [this message]
2009-02-25 21:48 ` Jeremy Fitzhardinge
2009-02-25 22:11 ` Gerd Hoffmann
2009-02-25 22:28 ` Jeremy Fitzhardinge
2009-02-25 22:42 ` Gerd Hoffmann
2009-02-25 22:59 ` Jeremy Fitzhardinge
2009-03-02 22:53 ` Gerd Hoffmann
2009-03-03 1:05 ` Jeremy Fitzhardinge
2009-03-03 22:59 ` Jeremy Fitzhardinge
2009-03-04 8:18 ` Gerd Hoffmann
2009-03-04 14:52 ` Gerd Hoffmann
2009-03-04 15:16 ` Jeremy Fitzhardinge
2009-03-04 15:32 ` Gerd Hoffmann
2009-02-25 18:56 ` Gerd Hoffmann
2009-02-25 20:10 ` Jeremy Fitzhardinge
2009-02-25 21:45 ` Gerd Hoffmann
2009-02-25 22:16 ` Gerd Hoffmann
2009-02-25 22:30 ` 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=49A5BB7E.8030503@redhat.com \
--to=kraxel@redhat.com \
--cc=jeremy@goop.org \
--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.