xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Tamas K Lengyel <tamas@tklengyel.com>
Cc: Xen-devel <xen-devel@lists.xenproject.org>,
	Ian Jackson <ian.jackson@eu.citrix.com>,
	Wei Liu <wei.liu2@citrix.com>,
	Razvan Cojocaru <rcojocaru@bitdefender.com>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [PATCH 1/2] vm_event: sync domctl
Date: Thu, 7 Jan 2016 09:58:05 +0000	[thread overview]
Message-ID: <1452160685.21055.149.camel@citrix.com> (raw)
In-Reply-To: <CABfawhny==Ev_uxX2pQ6f4L+Ktkb_3HbxGBdVDRvYE0E0DpuAQ@mail.gmail.com>

On Wed, 2016-01-06 at 19:29 +0100, Tamas K Lengyel wrote:
> 
> 
> On Wed, Jan 6, 2016 at 4:48 PM, Ian Campbell <ian.campbell@citrix.com>
> wrote:
> > On Wed, 2015-12-23 at 15:53 +0100, Tamas K Lengyel wrote:
> > > Introduce new vm_event domctl option which allows an event subscriber
> > > to request all vCPUs not currently pending a vm_event request to be
> > > paused,
> > > thus allowing the subscriber to sync up on the state of the domain.
> > This
> > > is especially useful when the subscribed wants to disable certain
> > events
> > > from being delivered and wants to ensure no more requests are pending
> > on
> > > the
> > > ring before doing so.
> > >
> > > Cc: Ian Jackson <ian.jackson@eu.citrix.com>
> > > Cc: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
> > > Cc: Ian Campbell <ian.campbell@citrix.com>
> > > Cc: Wei Liu <wei.liu2@citrix.com>
> > > Cc: Razvan Cojocaru <rcojocaru@bitdefender.com>
> > > Signed-off-by: Tamas K Lengyel <tamas@tklengyel.com>
> > > ---
> > >  tools/libxc/include/xenctrl.h | 11 +++++++++++
> > >  tools/libxc/xc_vm_event.c     | 16 ++++++++++++++++
> > 
> > Tools side is pretty trivial, assuming there is agreement on the
> > underlying
> > hypercall interface:
> > 
> > Acked-by: Ian Campbell <ian.campbell@citrix.com>
> Thanks, we've decided that this patch is actually not needed as the pause
> reference count is already good enough.

OK, thanks.

> > > +/***
> > >   * Memory sharing operations.
> > 
> > Do you also maintain this? If so do you fancy sending a patch to fix:
> > 
> > >   *
> > >   * Unles otherwise noted, these calls return 0 on succes, -1 and
> > errno on
> > 
> > "Unless" and "success" ?
> > 
> Sure, that could be done in a separate patch.

Yes, that's what I intended.

>  IMHO the whole sharing subsystem could use a cleanup series of its own
> to fix things like this, style issues and whatnot.

Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

      reply	other threads:[~2016-01-07 10:00 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-23 14:53 [PATCH 1/2] vm_event: sync domctl Tamas K Lengyel
2015-12-23 14:53 ` [PATCH 2/2] vm_event: Add altp2m info to HVM events as well Tamas K Lengyel
2015-12-23 15:42   ` Razvan Cojocaru
2015-12-23 17:18     ` Andrew Cooper
2016-01-06 11:32   ` Jan Beulich
2016-01-06 11:42     ` Tamas K Lengyel
2016-01-06 11:48       ` Andrew Cooper
2016-01-06 11:50         ` Tamas K Lengyel
2016-01-12 10:21           ` Jan Beulich
2016-01-12 12:13             ` Tamas K Lengyel
2015-12-23 15:41 ` [PATCH 1/2] vm_event: sync domctl Razvan Cojocaru
2015-12-23 17:17   ` Andrew Cooper
2015-12-23 18:11     ` Tamas K Lengyel
2015-12-23 19:11       ` Razvan Cojocaru
2015-12-23 19:14       ` Andrew Cooper
2015-12-23 20:55         ` Tamas K Lengyel
2015-12-23 21:06           ` Tamas K Lengyel
2015-12-23 21:13             ` Andrew Cooper
2016-01-06 15:48 ` Ian Campbell
2016-01-06 18:29   ` Tamas K Lengyel
2016-01-07  9:58     ` Ian Campbell [this message]

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=1452160685.21055.149.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=rcojocaru@bitdefender.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=tamas@tklengyel.com \
    --cc=wei.liu2@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 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).