All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Xen Development Mailing List <xen-devel@lists.xensource.com>
Subject: Re: pv_ops & gntdev?
Date: Wed, 25 Feb 2009 12:06:21 -0800	[thread overview]
Message-ID: <49A5A4BD.7080207@goop.org> (raw)
In-Reply-To: <49A58FFF.3050604@redhat.com>

Gerd Hoffmann wrote:
>> Yes, my plan is:
>>
>>   1. when installing a grant in a pte page, allocate a shadow page and
>>      hang it off page->private; also set a page flag on the pgd page
>>      flags (steal something spare)
>>     
>
> pgd or pte page flags?  or both?
>   

Just pgd, so that the unpinner can see it needs to make a second pass.  
At the pte level, looking for a non-NULL page->private should be enough.

>>   3. when clearing the pte, check to see if there's a grant handle and
>>      zap it
>>     
>
> That needs a new paravirt hook I think ...
>   

Hm, I hope not.  Doesn't it always end up using set_pte*?

>>   4. when unpinning the pagetable, check to see if there's the "grant
>>      mapping" flag in the pgd, and do a grant-zap pass before unpinning
>>     
>
> ok.
>
> Prelimary patches by chance?
>   

No, I haven't got around to implementing this at all.

Thanks,
    J

  reply	other threads:[~2009-02-25 20:06 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 [this message]
2009-02-25 21:19             ` Gerd Hoffmann
2009-02-25 21:35               ` Jeremy Fitzhardinge
2009-02-25 21:43                 ` Gerd Hoffmann
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=49A5A4BD.7080207@goop.org \
    --to=jeremy@goop.org \
    --cc=kraxel@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.