linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: david.vrabel@citrix.com (David Vrabel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] xen/grant-table: Refactor gnttab_[un]map_refs to avoid m2p_override
Date: Mon, 10 Mar 2014 17:35:58 +0000	[thread overview]
Message-ID: <531DF7FE.1000708@citrix.com> (raw)
In-Reply-To: <1393516530-9145-1-git-send-email-zoltan.kiss@citrix.com>

On 27/02/14 15:55, Zoltan Kiss wrote:
> (This is a continuation of "[PATCH v9] xen/grant-table: Avoid m2p_override
> during mapping")
> 
> The grant mapping API does m2p_override unnecessarily: only gntdev needs it,
> for blkback and future netback patches it just cause a lock contention, as
> those pages never go to userspace. Therefore this series does the following:
> - the bulk of the original function (everything after the mapping hypercall)
>   is moved to arch-dependent set/clear_foreign_p2m_mapping
> - the "if (xen_feature(XENFEAT_auto_translated_physmap))" brach goes to ARM
> - therefore the ARM function could be much smaller, the m2p_override stubs
>   could be also removed
> - on x86 the set_phys_to_machine calls were moved up to this new funcion
>   from m2p_override functions
> - and m2p_override functions are only called when there is a kmap_ops param
> 
> It also removes a stray space from arch/x86/include/asm/xen/page.h.

Applied to devel/for-linus-3.15.

Thanks.

David

  parent reply	other threads:[~2014-03-10 17:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-27 15:55 [PATCH] xen/grant-table: Refactor gnttab_[un]map_refs to avoid m2p_override Zoltan Kiss
2014-03-10 17:14 ` Zoltan Kiss
2014-03-10 17:35 ` David Vrabel [this message]
2014-03-16 16:32   ` 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=531DF7FE.1000708@citrix.com \
    --to=david.vrabel@citrix.com \
    --cc=linux-arm-kernel@lists.infradead.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 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).