All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tim Deegan <tim@xen.org>
To: Paul Durrant <Paul.Durrant@citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] Fix save/restore for HVM domains with viridian=1
Date: Fri, 25 Nov 2011 15:25:06 +0000	[thread overview]
Message-ID: <20111125152506.GC6475@ocelot.phlegethon.org> (raw)
In-Reply-To: <291EDFCB1E9E224A99088639C4762022B5988E4CE3@LONPMAILBOX01.citrite.net>

At 15:14 +0000 on 25 Nov (1322234058), Paul Durrant wrote:
> > > @@ -411,6 +417,8 @@ static int viridian_load_domain_ctxt(str
> > >      if ( hvm_load_entry(VIRIDIAN_DOMAIN, h, &ctxt) != 0 )
> > >          return -EINVAL;
> > >
> > > +    ASSERT(is_viridian_domain(d));
> > > +
> > 
> > I don't think it's appropriate to crash Xen if the save file is
> > bogus.
> > 
> 
> There's a similar ASSERT in the hypercall function anyway; would you rather I turned that into a rate limited warning too?
> 

If you mean the one in viridian_hypercall(), no - if that function is
called for a non-viridian VM that's a bug in Xen so the ASSERT() is
correct.   

The viridian_load_*_ctxt() functions are called based on the HVM save
record the tools gave us, so we should at most return an error if they
lead us astray.  And I think it should be OK to load the HVM state and then
set the HVM params, so the current (lack of) response is correct. 

Cheers,

Tim.

  reply	other threads:[~2011-11-25 15:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-25 15:14 [PATCH] Fix save/restore for HVM domains with viridian=1 Paul Durrant
2011-11-25 15:25 ` Tim Deegan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-11-25 15:30 Paul Durrant
2011-11-25 15:39 ` Keir Fraser
2011-11-25 15:42   ` Paul Durrant
2011-11-25 15:29 Paul Durrant
2011-11-25 15:30 ` Paul Durrant
2011-11-25 15:28 Paul Durrant
2011-11-25 14:50 Paul Durrant
2011-11-25 14:58 ` Jan Beulich
2011-11-25 15:16   ` Keir Fraser
2011-11-25 15:00 ` Tim Deegan
2011-11-25 15:18   ` Keir Fraser
2011-11-25 15:26     ` Paul Durrant

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=20111125152506.GC6475@ocelot.phlegethon.org \
    --to=tim@xen.org \
    --cc=Paul.Durrant@citrix.com \
    --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 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.