From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: David Vrabel <david.vrabel@citrix.com>
Cc: xen-devel@lists.xensource.com, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 0/4] xen: map foreign pages for shared rings by updating the PTEs directly
Date: Thu, 20 Oct 2011 19:44:59 -0400 [thread overview]
Message-ID: <20111020234459.GF19558@phenom.dumpdata.com> (raw)
In-Reply-To: <1319107519-2253-1-git-send-email-david.vrabel@citrix.com>
On Thu, Oct 20, 2011 at 11:45:15AM +0100, David Vrabel wrote:
> This series of patches allows the vmalloc_sync_all() to be removed
> from alloc_vm_area() by getting the hypervisor to update the PTEs (in
> init_mm) directly rather than having the hypervisor look in the
> current page tables to find the PTEs.
>
> Once the hypervisor has updated the PTEs, the normal mechanism of
> syncing the page tables after a fault works as expected.
>
> This mechanism doesn't currently work on the ia64 port as that does
> not support the GNTMAP_contains_pte flag.
>
> Andrew, patch 4 (xen: map foreign pages for shared rings by updating
> the PTEs directly) depends on patch 1 so it's probably best to go via
> Konrad's Xen tree with your acked-by.
Or I can Ack patch 1 and Andrew can pick both of them. Either way - but let
mention the Ack on patch #1
>
> David
>
> David Vrabel (4):
> xen: use generic functions instead of xen_{alloc,free}_vm_area()
> block: xen-blkback: use API provided by xenbus module to map rings
> net: xen-netback: use API provided by xenbus module to map rings
> xen: map foreign pages for shared rings by updating the PTEs directly
>
> arch/ia64/include/asm/xen/grant_table.h | 29 -----------
> arch/ia64/xen/grant-table.c | 62 ------------------------
> arch/x86/include/asm/xen/grant_table.h | 7 ---
> arch/x86/xen/grant-table.c | 2 +-
> drivers/block/xen-blkback/common.h | 5 +--
> drivers/block/xen-blkback/xenbus.c | 54 +++------------------
> drivers/net/xen-netback/common.h | 11 ++--
> drivers/net/xen-netback/netback.c | 80 +++++++------------------------
> drivers/xen/xenbus/xenbus_client.c | 15 ++++--
> include/linux/vmalloc.h | 2 +-
> include/xen/grant_table.h | 1 -
> mm/vmalloc.c | 27 +++++-----
> 12 files changed, 55 insertions(+), 240 deletions(-)
> delete mode 100644 arch/ia64/include/asm/xen/grant_table.h
> delete mode 100644 arch/x86/include/asm/xen/grant_table.h
>
> --
> 1.7.2.5
prev parent reply other threads:[~2011-10-24 13:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-20 10:45 [PATCH 0/4] xen: map foreign pages for shared rings by updating the PTEs directly David Vrabel
2011-10-20 10:45 ` [PATCH 1/4] xen: use generic functions instead of xen_{alloc,free}_vm_area() David Vrabel
2011-10-20 23:45 ` Konrad Rzeszutek Wilk
2011-10-20 10:45 ` [PATCH 2/4] block: xen-blkback: use API provided by xenbus module to map rings David Vrabel
2011-10-26 13:47 ` [Xen-devel] " Konrad Rzeszutek Wilk
2011-10-26 13:55 ` Jens Axboe
2011-10-20 10:45 ` [PATCH 3/4] net: xen-netback: " David Vrabel
2011-10-20 21:00 ` Konrad Rzeszutek Wilk
2011-10-20 10:45 ` [PATCH 4/4] xen: map foreign pages for shared rings by updating the PTEs directly David Vrabel
2011-10-20 23:44 ` Konrad Rzeszutek Wilk [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=20111020234459.GF19558@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=david.vrabel@citrix.com \
--cc=linux-kernel@vger.kernel.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 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).