xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir.xen@gmail.com>
To: Jan Beulich <JBeulich@suse.com>,
	xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH] x86: add locking to map_pages_to_xen()
Date: Mon, 15 Jul 2013 13:12:16 +0100	[thread overview]
Message-ID: <CE09A5B0.2D724%keir.xen@gmail.com> (raw)
In-Reply-To: <51E3E64002000078000E4E08@nat28.tlf.novell.com>

On 15/07/2013 11:08, "Jan Beulich" <JBeulich@suse.com> wrote:

> While boot time calls don't need this, run time uses of the function
> which may result in L2 page tables getting populated need to be
> serialized to avoid two CPUs populating the same L2 (or L3) entry,
> overwriting each other's results.
> 
> This is expected to fix what would seem to be a regression from commit
> b0581b92 ("x86: make map_domain_page_global() a simple wrapper around
> vmap()"), albeit that change only made more readily visible the already
> existing issue.
> 
> This patch intentionally does not
> - add locking to the page table de-allocation logic in
>   destroy_xen_mappings() (the only user having potential races here,
>   msix_put_fixmap(), gets converted to use __set_fixmap() instead)
> - avoid races between super page splitting and reconstruction in
>   map_pages_to_xen() (no such uses exist; races between multiple
>   splitting attempts or between multiple reconstruction attempts are
>   being taken care of)
> If we wanted to take care of these, we'd need to alter the behavior
> of virt_to_xen_l?e() - they would need to return with the lock held
> then.
> 
> Signed-off-by: Jan Beulich <jbeulich@suse.com>

Acked-by: Keir Fraser <keir@xen.org>

      reply	other threads:[~2013-07-15 12:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-15 10:08 [PATCH] x86: add locking to map_pages_to_xen() Jan Beulich
2013-07-15 12:12 ` Keir Fraser [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=CE09A5B0.2D724%keir.xen@gmail.com \
    --to=keir.xen@gmail.com \
    --cc=JBeulich@suse.com \
    --cc=xen-devel@lists.xenproject.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).