xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Tim Deegan <tim@xen.org>
To: Robert Phillips <robert.phillips@citrix.com>
Cc: xen-devel@lists.xen.org
Subject: Re: [PATCH] Avoid race when guest switches between log dirty mode and dirty vram mode.
Date: Thu, 13 Dec 2012 12:11:55 +0000	[thread overview]
Message-ID: <20121213121155.GC75286@ocelot.phlegethon.org> (raw)
In-Reply-To: <1355166836-11338-1-git-send-email-robert.phillips@citrix.com>

At 14:13 -0500 on 10 Dec (1355148836), Robert Phillips wrote:
> The previous code assumed the guest would be in one of three mutually exclusive
> modes for bookkeeping dirty pages: (1) shadow, (2) hap utilizing the log dirty
> bitmap to support functionality such as live migrate, (3) hap utilizing the
> log dirty bitmap to track dirty vram pages.
> Races arose when a guest attempted to track dirty vram while performing live
> migrate.  (The dispatch table managed by paging_log_dirty_init() might change
> in the middle of a log dirty or a vram tracking function.)
> 
> This change allows hap log dirty and hap vram tracking to be concurrent.
> Vram tracking no longer uses the log dirty bitmap.  Instead it detects
> dirty vram pages by examining their p2m type.  The log dirty bitmap is only
> used by the log dirty code.  Because the two operations use different
> mechanisms, they are no longer mutually exclusive.
> 
> Signed-Off-By: Robert Phillips <robert.phillips@citrix.com>

Applied; thanks for that. 

Tim.

      reply	other threads:[~2012-12-13 12:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-10 19:13 [PATCH] Avoid race when guest switches between log dirty mode and dirty vram mode Robert Phillips
2012-12-13 12:11 ` Tim Deegan [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=20121213121155.GC75286@ocelot.phlegethon.org \
    --to=tim@xen.org \
    --cc=robert.phillips@citrix.com \
    --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 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).