From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: Ian Jackson <ian.jackson@citrix.com>
Cc: Marcus of Wetware Labs <marcus@wetwa.re>,
Wei Liu <wei.liu2@citrix.com>,
xen-devel@lists.xen.org
Subject: Re: [PATCH v2] libxl: allow libxl_domain_suspend to simply suspend a domain, without saving it
Date: Wed, 4 Apr 2018 17:42:17 +0200 [thread overview]
Message-ID: <20180404154217.GC5817@mail-itl> (raw)
In-Reply-To: <23227.31353.516795.789410@mariner.uk.xensource.com>
[-- Attachment #1.1: Type: text/plain, Size: 1951 bytes --]
On Wed, Mar 28, 2018 at 12:20:25PM +0100, Ian Jackson wrote:
> Wei Liu writes ("Re: [PATCH v2] libxl: allow libxl_domain_suspend to simply suspend a domain, without saving it"):
> > On Wed, Mar 14, 2018 at 03:36:08PM +0100, Marek Marczykowski-Górecki wrote:
> > > When LIBXL_SUSPEND_NO_SAVE flag is set, no savefile will be written, but
> > > the domain will still be suspended (but not destroyed). The main reason
> > > for this functionality is to suspend the host while some domains are
> > > running, potentially holding PCI devices. This will give a chance to a
> > > driver in such a domain to properly suspend the device.
> > >
> ...
> > > Signed-off-by: Marek Marczykowski-Górecki <marmarek@invisiblethingslab.com>
> > > Signed-off-by: Marcus of Wetware Labs <marcus@wetwa.re>
> >
> > The code and idea look fine.
> >
> > I would like to give Ian a chance to voice his opinion (he's currently
> > away).
>
> The API does seem a bit odd. The intent is then that the domain will
> be un-suspended afterwards ? This doesn't seem to be documented
> AFAICT in your patch.
Yes, there is already libxl_domain_resume for that.
> I don't think I agree with this part of the reaoning:
>
> > > It would be better to have a separate function for this, but in fact it
> > > should be named libxl_domain_suspend, then the current one renamed to
> > > libxl_domain_save. Since that would break API compatibility, keep it in
> > > the same function.
>
> I agree that libxl_domain_suspend is an unfortunate name, but can't we
> come up with an alternative new name ? It does seem odd to bundle
> this into _save.
libxl_domain_just_suspend ?
It isn't bundling it into _save. There is no _save function - that's the
problem.
--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 157 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-04-04 15:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-14 14:36 [PATCH v2] libxl: allow libxl_domain_suspend to simply suspend a domain, without saving it Marek Marczykowski-Górecki
2018-03-21 16:08 ` Marek Marczykowski-Górecki
2018-03-21 16:52 ` Wei Liu
2018-03-28 11:20 ` Ian Jackson
2018-04-04 15:42 ` Marek Marczykowski-Górecki [this message]
2018-04-04 15:45 ` Ian Jackson
2018-04-04 15:53 ` Marek Marczykowski-Górecki
2018-04-04 15:57 ` Ian Jackson
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=20180404154217.GC5817@mail-itl \
--to=marmarek@invisiblethingslab.com \
--cc=ian.jackson@citrix.com \
--cc=marcus@wetwa.re \
--cc=wei.liu2@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 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.