xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Dave McCracken <dcm@mccr.org>
To: Tim Deegan <Tim.Deegan@citrix.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
	Xen Developers List <xen-devel@lists.xensource.com>,
	Keir Fraser <Keir.Fraser@eu.citrix.com>
Subject: Re: [PATCH] Allow PV superpages to work with live migration
Date: Tue, 18 May 2010 09:20:18 -0500	[thread overview]
Message-ID: <201005180920.18349.dcm@mccr.org> (raw)
In-Reply-To: <20100518123553.GG4164@whitby.uk.xensource.com>

On Tuesday, May 18, 2010, Tim Deegan wrote:
> > PV superpages currently do not work with live migration.  They fall over
> > dead  when the shadow page table is enabled for dirty tracking.  The HVM
> > support for superpages in this code has been tested and found to work
> > just fine for PV superpages.  This patch modifies the test macro to
> > allow the code to work with PV superpages.
> 
> It rather overshoots. :)  This enables PSE even for HVM guests which
> have explicitly disabled it.   I think you want
> 
>     return (is_hvm_vcpu(v) ? (GUEST_PAGING_LEVELS != 2
>                               || !hvm_paging_enabled(v)
>                               || (v->arch.hvm_vcpu.guest_cr[4] &
> X86_CR4_PSE)) : opt_allow_hugepage);

I'm confused.  As far as I know, opt_allow_hugeage only affects PV guests.  All 
I did in the macro was add a test for it.  I didn't touch any of the HVM 
logic.  Are you saying the HVM logic is wrong or that opt_allow_hugepage 
affects HVM guests in some fashion?

Dave McCracken
Oracle Corp.

  reply	other threads:[~2010-05-18 14:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-17 19:10 [PATCH] Allow PV superpages to work with live migration Dave McCracken
2010-05-18 12:35 ` Tim Deegan
2010-05-18 14:20   ` Dave McCracken [this message]
2010-05-18 14:32     ` Tim Deegan
2010-05-18 14:33       ` Keir Fraser
2010-05-18 16:21       ` Dave McCracken

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=201005180920.18349.dcm@mccr.org \
    --to=dcm@mccr.org \
    --cc=Keir.Fraser@eu.citrix.com \
    --cc=Tim.Deegan@citrix.com \
    --cc=jeremy@goop.org \
    --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 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).