|
|
|
|
|
|
|
|
|
|
xen-devel
Re: [Xen-devel] Re: Next steps with pv_ops for Xen
To: |
"Jeremy Fitzhardinge" <jeremy@xxxxxxxx> |
Subject: |
Re: [Xen-devel] Re: Next steps with pv_ops for Xen |
From: |
"Geoffrey Lefebvre" <geoffrey@xxxxxxxxx> |
Date: |
Wed, 5 Dec 2007 12:35:36 -0800 |
Cc: |
Derek Murray <Derek.Murray@xxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Eduardo Habkost <ehabkost@xxxxxxxxxx>, Juan Quintela <quintela@xxxxxxxxxx>, Jan Beulich <jbeulich@xxxxxxxxxx>, Glauber de Oliveira Costa <gcosta@xxxxxxxxxx>, Chris Wright <chrisw@xxxxxxxxxxxx>, "virtualization@xxxxxxxxxxxxxx" <virtualization@xxxxxxxxxxxxxx>, Gerd Hoffmann <kraxel@xxxxxxxxxx> |
Delivery-date: |
Wed, 05 Dec 2007 12:36:15 -0800 |
Dkim-signature: |
v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; bh=Sfs37kQnTkcui7w0nVtvAzv5lsnZqw0z+x6nxvZjvsc=; b=taDTccHcjLXfTT6bPMSx/7qfD1Hl7LkkzhZKzWX0jHxFkqljdJYGRu8NBgrI5U0O/u5BRh3MexXASpBUMDpw+DnmILFjeAeelAIgGaLnwX1gPhEpVKRkVhy38O2pnC9xwft9bTHQOZBBIdsUOosEcvZR7tVX7QVGndDm2Q+uMTA= |
Domainkey-signature: |
a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=MYzYvVdXG8lFeffRUpbJX1aJAQ0U5Uh0jc5vq9Pcw30XeZoy2S3YajDNxea8tkJQPsolWvxe1EOdXM/nEv0UeyA5DuizSvv2QKxfw88oOJJ6sM+/7DgiaSHWfEURbJMhiXS8MT9pRAmKxAOJOMcGND4wMnAK18OE/MNGsSdCSis= |
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxx |
In-reply-to: |
<475706C5.1000608@xxxxxxxx> |
List-help: |
<mailto:xen-devel-request@lists.xensource.com?subject=help> |
List-id: |
Xen developer discussion <xen-devel.lists.xensource.com> |
List-post: |
<mailto:xen-devel@lists.xensource.com> |
List-subscribe: |
<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
List-unsubscribe: |
<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
References: |
<1195682725.6726.48.camel@xxxxxxxxxxxxxxxxxxxxx> <47546931.2090602@xxxxxxxxxx> <475520A1.6080909@xxxxxxxxxxxx> <475541A8.7030100@xxxxxxxxxx> <1196771999.10809.18.camel@xxxxxxxxxxxxxxxxxxxxx> <4755B158.3030008@xxxxxxxxxx> <47569014.8080008@xxxxxxxxxxxx> <4756E9F2.4050502@xxxxxxxx> <4756EDF3.30501@xxxxxxxxxxxx> <475706C5.1000608@xxxxxxxx> |
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
> Can we take a different approach from the zap_pte hook? Given that
> we're 1) planning on claiming a pte bit for grant mappings, and 2) need
> to hook ptep_get_and_clear anyway to solve the mprotect performance
> problems, couldn't we just special-case grant mapping pte_clears?
>
> In 2.6.18-xen the only two implementations of zap_pte are
> blktap_clear_pte and gntdev_clear_pte. Given a ptep with the
> grant-mapping bit set, could we determine which of these need calling
> and do the appropriate thing? Do we even need separate implementations
> of the core pte-clearing functionality? Could we just say something like:
>
> if (pte & _PAGE_XEN_FOREIGN)
> HYPERVISOR_grant_table_op(GNTTABOP_unmap_grant_ref, ...);
> else
> xen_set_pte_at(...);
>
Hi,
In order to unmap a grant, you need the grant handle obtained when the
grant is mapped. That handle needs to be stored somewhere for the
lifetime of the mapping. Where would the handle be stored (as Gerd
proposed) in order to be able to unmap from ptep_get_and_clear_full?
I haven't looked at the paravirt ops in details so I could be missing
something obvious here.
cheers,
geoffrey
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- Re: [Xen-devel] Re: Next steps with pv_ops for Xen, (continued)
- Re: [Xen-devel] Re: Next steps with pv_ops for Xen, Gerd Hoffmann
- Re: [Xen-devel] Re: Next steps with pv_ops for Xen, Jeremy Fitzhardinge
- Re: [Xen-devel] Re: Next steps with pv_ops for Xen, Derek Murray
- Re: [Xen-devel] Re: Next steps with pv_ops for Xen, Jeremy Fitzhardinge
- Re: [Xen-devel] Re: Next steps with pv_ops for Xen,
Geoffrey Lefebvre <=
- Re: [Xen-devel] Re: Next steps with pv_ops for Xen, Gerd Hoffmann
- Re: [Xen-devel] Re: Next steps with pv_ops for Xen, Keir Fraser
- Re: [Xen-devel] Re: Next steps with pv_ops for Xen, Derek Murray
- Re: [Xen-devel] Re: Next steps with pv_ops for Xen, Jeremy Fitzhardinge
- Re: [Xen-devel] Re: Next steps with pv_ops for Xen, Derek Murray
- Re: [Xen-devel] Re: Next steps with pv_ops for Xen, Ian Main
- Re: [Xen-devel] Re: Next steps with pv_ops for Xen, Gerd Hoffmann
- Re: [Xen-devel] Re: Next steps with pv_ops for Xen, Gerd Hoffmann
- Re: [Xen-devel] Re: Next steps with pv_ops for Xen, Derek Murray
- Re: [Xen-devel] Re: Next steps with pv_ops for Xen, Ian Main
|
|
|
|
|