All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Vrabel <david.vrabel@citrix.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: xen-devel@lists.xenproject.org,
	Boris Ostrovsky <boris.ostrovsky@oracle.com>
Subject: Re: [PATCH] xen/grant-table: fix suspend for non-PV guests
Date: Mon, 16 Jun 2014 15:32:40 +0100	[thread overview]
Message-ID: <539F0008.9070309@citrix.com> (raw)
In-Reply-To: <20140616142002.GD11200@laptop.dumpdata.com>

On 16/06/14 15:20, Konrad Rzeszutek Wilk wrote:
> On Mon, Jun 16, 2014 at 12:49:18PM +0100, David Vrabel wrote:
>> Commit aa8532c32216ae07c3813b9aeb774517878a7573 (xen: refactor suspend
>> pre/post hooks) broke resuming PVHVM (auto-translated physmap) guests.
>>
>> The gnttab_suspend() would clear the mapping for the grant table
>> frames, but the ->unmap_frames() call is only applicable to PV guests.
>>
>> Signed-off-by: David Vrabel <david.vrabel@citrix.com>
> 
> You forgot:
> 
> Reported-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>

I'm more interested in a Tested-by, any chance of one?

> However, if the code is structured like this, should we just
> make the 'unmap_frames' be a NOP for HVM and instead have:
> 
> if (gnttab_interface->unmap_frames)
> 	gnttab_interface->unmap_frames();
> 
> And the HVM path will make sure that 'unmap_frames' is
> set to NULL?
> 
> Maybe even change the name to 'unmap_frames_pv' ?

That may be useful as part of a wider refactor.  But the use of the
feature test mirrors the use in gnttab_setup() (as called by
gnttab_resume()) so I think it is clearer.

David

  reply	other threads:[~2014-06-16 14:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-16 11:49 [PATCH] xen/grant-table: fix suspend for non-PV guests David Vrabel
2014-06-16 14:20 ` Konrad Rzeszutek Wilk
2014-06-16 14:32   ` David Vrabel [this message]
2014-06-16 18:56 ` Konrad Rzeszutek Wilk

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=539F0008.9070309@citrix.com \
    --to=david.vrabel@citrix.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=konrad.wilk@oracle.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.