All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Vrabel <david.vrabel@citrix.com>
To: Andres Lagar-Cavilla <andreslc@gridcentric.ca>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	Andres Lagar-Cavilla <andres@lagarcavilla.com>,
	<boris.ostrovsky@oracle.com>
Subject: Re: [PATCH] Xen: Fix retry calls into PRIVCMD_MMAPBATCH*.
Date: Thu, 1 Aug 2013 12:23:51 +0100	[thread overview]
Message-ID: <51FA4547.7080408@citrix.com> (raw)
In-Reply-To: <2BE2F119-7375-4C8D-933D-9BCD5A9B7552@gridcentric.ca>

On 01/08/13 04:30, Andres Lagar-Cavilla wrote:
> -- Resend as I haven't seen this hit the lists. Maybe some smtp misconfig. Apologies. Also expanded cc --
> 
> When a foreign mapper attempts to map guest frames that are paged out,
> the mapper receives an ENOENT response and will have to try again
> while a helper process pages the target frame back in.
> 
> Gating checks on PRIVCMD_MMAPBATCH* ioctl args were preventing retries
> of mapping calls.

This breaks the auto_translated_physmap case as will allocate another
set of empty pages and leak the previous set.

This privcmd_enforce_singleshot_mapping() stuff seems very odd anyway.
Does anyone know what it was for originally?  It would be preferrable if
we could update the mappings with a new set of foreign MFNs without
having to tear down the VMA and recreate a new VMA.

> --- a/drivers/xen/privcmd.c
> +++ b/drivers/xen/privcmd.c
[...]
> +/* For MMAPBATCH*. This allows asserting the singleshot mapping
> + * on a per pfn/pte basis. Mapping calls that fail with ENOENT
> + * can be then retried until success. */

Comment coding style.

David

  reply	other threads:[~2013-08-01 11:24 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1375203632-23854-1-git-send-email-andres@lagarcavilla.org>
2013-08-01  3:30 ` [PATCH] Xen: Fix retry calls into PRIVCMD_MMAPBATCH* Andres Lagar-Cavilla
2013-08-01 11:23   ` David Vrabel [this message]
2013-08-01 11:49     ` Andres Lagar-Cavilla
2013-08-01 12:04       ` David Vrabel
2013-08-01 12:04       ` David Vrabel
2013-08-01 13:30         ` Andres Lagar-Cavilla
2013-08-01 13:30         ` Andres Lagar-Cavilla
2013-08-01 11:49     ` Andres Lagar-Cavilla
2013-08-01 11:23   ` David Vrabel
2013-08-01  3:30 ` Andres Lagar-Cavilla
2013-08-01 14:26 Andres Lagar-Cavilla
2013-08-09 10:30 ` David Vrabel
2013-08-09 10:30 ` David Vrabel
  -- strict thread matches above, loose matches on Subject: below --
2013-08-01 14:26 Andres Lagar-Cavilla
2013-08-09 14:11 Andres Lagar-Cavilla
2013-08-12 15:58 ` David Vrabel
2013-08-12 15:58 ` David Vrabel

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=51FA4547.7080408@citrix.com \
    --to=david.vrabel@citrix.com \
    --cc=andres@lagarcavilla.com \
    --cc=andreslc@gridcentric.ca \
    --cc=boris.ostrovsky@oracle.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xen-devel@lists.xen.org \
    /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.