All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir@xensource.com>
To: Derek Murray <Derek.Murray@cl.cam.ac.uk>, xen-devel@lists.xensource.com
Subject: Re: [PATCH 0/3] [RFC] User-space grant table device
Date: Mon, 19 Mar 2007 14:00:29 +0000	[thread overview]
Message-ID: <C22447FD.BCE1%keir@xensource.com> (raw)
In-Reply-To: <F17DBCEF-7C4A-488D-90B8-DC783DC465E7@cl.cam.ac.uk>

On 19/3/07 10:40, "Derek Murray" <Derek.Murray@cl.cam.ac.uk> wrote:

> 1. gntdev.patch: This is the main driver, and associated header file.
> 2. libxc-changes.patch: These are the libxc functions for accessing
> the driver.
> 3. linux-changes.patch: These contain the necessary changes to linux
> (in effect, adding a hook to the vm_operations_struct that is called
> by the unmap_page_range function) for unmapping grants before the
> page table is destroyed.

1. The patches are malformed (don't apply). It might be best to send the
patches at plain-text attachments to prevent mangling by your email client.
2. Dependencies should be listed in the right order. So your patch 3 should
be patch 1, since it is required by the grant-table device.
3. Just looking at linux-changes.patch, I think the new interface function's
semantics need to be clearer. Do you really mean for the hook function to be
called *and* for unmap_page_range() to do the usual zap_pud_range() work?
Should the hook function return anything? What about responsibility for
synchronising TLBs?

 -- Keir

  reply	other threads:[~2007-03-19 14:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-19 10:40 [PATCH 0/3] [RFC] User-space grant table device Derek Murray
2007-03-19 14:00 ` Keir Fraser [this message]
2007-03-19 14:31   ` Derek Murray
2007-03-19 15:11     ` Keir Fraser
2007-03-21  4:32 ` Isaku Yamahata
2007-03-21 11:29   ` Derek Murray
2007-03-21 14:16     ` Andrew Warfield
2007-03-23 15:25       ` Mark Williamson
2007-03-22  2:28     ` Isaku Yamahata
2007-03-23 14:50       ` Derek Murray

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=C22447FD.BCE1%keir@xensource.com \
    --to=keir@xensource.com \
    --cc=Derek.Murray@cl.cam.ac.uk \
    --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.