All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Vrabel <david.vrabel@citrix.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: xen-devel@lists.xensource.com, keir@xen.org,
	Ian.Campbell@citrix.com, JBeulich@suse.com
Subject: Re: [PATCH RFC] xen/grant_table: deprecate	GNTTABOP_unmap_and_replace
Date: Mon, 22 Jul 2013 12:40:50 +0100	[thread overview]
Message-ID: <51ED1A42.6050107@citrix.com> (raw)
In-Reply-To: <1374428099-24328-1-git-send-email-stefano.stabellini@eu.citrix.com>

On 21/07/13 18:34, Stefano Stabellini wrote:
> GNTTABOP_unmap_and_replace has two issues:
> - it unconditionally replaces the mapping passed in new_addr with 0;
> - it doesn't support GNTMAP_contains_pte mappings on x86, returning a
> general error instead of some forms of ENOSYS.

I don't think you can change the behavior of the existing sub-op in this
way.  XenServer's current netback driver relies on the current
behaviour, for example.

I think this will also mess up the ref counting on the frame that is at
the new_addr virtual address.  It will be mapped twice but with no
additional ref count.

I think the you can fix the problem in Linux without any hypervisor side
changes, but adding a new sub-op for GNTTABOP_unmap_and_duplicate (unmap
and replace with mapping with a duplicate of an existing mapping) will
allow for batching.

David

  parent reply	other threads:[~2013-07-22 11:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-21 17:34 [PATCH RFC] xen/grant_table: deprecate GNTTABOP_unmap_and_replace Stefano Stabellini
2013-07-21 17:52 ` Ian Campbell
2013-07-22 10:15   ` Stefano Stabellini
2013-07-22 10:22     ` Stefano Stabellini
2013-08-05 12:06       ` Jan Beulich
2013-08-05 13:00         ` Stefano Stabellini
2013-08-05 12:07     ` Jan Beulich
2013-07-22 11:40 ` David Vrabel [this message]
2013-07-22 19:45 ` Konrad Rzeszutek Wilk
2013-07-23 11:52   ` Stefano Stabellini

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=51ED1A42.6050107@citrix.com \
    --to=david.vrabel@citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=keir@xen.org \
    --cc=stefano.stabellini@eu.citrix.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.