All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tim Deegan <tim@xen.org>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: xen-devel@lists.xenproject.org, "Jan Beulich" <JBeulich@suse.com>,
	"Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: [PATCH v3 1/3] xen/pvh: enable mmu_update hypercall
Date: Thu, 16 Apr 2015 10:04:53 +0100	[thread overview]
Message-ID: <20150416090453.GB13443@deinos.phlegethon.org> (raw)
In-Reply-To: <552D11AB.9040408@citrix.com>

At 14:10 +0100 on 14 Apr (1429020603), Andrew Cooper wrote:
> On 14/04/15 13:03, Roger Pau Monné wrote:
> > El 14/04/15 a les 13.55, Jan Beulich ha escrit:
> >>>>> On 10.04.15 at 19:29, <roger.pau@citrix.com> wrote:
> >>> This is needed for performing save/restore of PV guests.
> >>>
> >>> Signed-off-by: Roger Pau Monné <roger.pau@citrix.com>
> >>> Cc: Tim Deegan <tim@xen.org>
> >>> Cc: Jan Beulich <jbeulich@suse.com>
> >>> Cc: Andrew Cooper <andrew.cooper3@citrix.com>
> >>> ---
> >>> Once migration v2 has been merged this patch can be reverted, since it
> >>> removes the need to use the MMU_MACHPHYS_UPDATE hypercall.
> >> Didn't earlier discussion end with the request to limit PVH access to
> >> just this one sub-op?
> > My bad, from the last conversation I got the feeling that the other
> > sub-ops already had the needed checks so it was fine to enable them. I
> > know the checks are there, and using the other sub-ops from a PVH guest
> > should be fine, but I guess it's better to just enable what we really need.
> 
> I would be in favour of dropping this patch entirely, as there is
> agreement in principle from the toolstack maintainers to include
> migration v2 in its current state.

+1.

Tim.

  reply	other threads:[~2015-04-16  9:05 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-10 17:29 [PATCH v3 0/3] xen/pvh: enable migration on PVH Dom0 Roger Pau Monne
2015-04-10 17:29 ` [PATCH v3 1/3] xen/pvh: enable mmu_update hypercall Roger Pau Monne
2015-04-14 11:55   ` Jan Beulich
2015-04-14 12:03     ` Roger Pau Monné
2015-04-14 13:10       ` Andrew Cooper
2015-04-16  9:04         ` Tim Deegan [this message]
2015-04-10 17:29 ` [PATCH v3 2/3] xen/shadow: fix shadow_track_dirty_vram to work on hvm guests Roger Pau Monne
2015-04-14 12:22   ` Jan Beulich
2015-05-06 15:12     ` Roger Pau Monné
2015-05-06 15:41       ` Jan Beulich
2015-04-10 17:29 ` [PATCH v3 3/3] xen: rework paging_log_dirty_op to work with " Roger Pau Monne
2015-04-11  9:27   ` Roger Pau Monné
2015-04-14 12:14   ` Jan Beulich
2015-04-16  9:11     ` Tim Deegan
2015-04-16  9:49       ` Jan Beulich
2015-05-06 11:55     ` Roger Pau Monné
2015-05-06 12:10       ` Jan Beulich
2015-05-06 12:32         ` Roger Pau Monné
2015-05-06 12:39           ` Jan Beulich

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=20150416090453.GB13443@deinos.phlegethon.org \
    --to=tim@xen.org \
    --cc=JBeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=roger.pau@citrix.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 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.