xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Paul Durrant <Paul.Durrant@citrix.com>
To: Andrew Cooper <Andrew.Cooper3@citrix.com>,
	"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Cc: Ian Jackson <Ian.Jackson@citrix.com>,
	Jennifer Herbert <jennifer.herbert@citrix.com>,
	Jan Beulich <jbeulich@suse.com>
Subject: Re: [PATCH v6 1/8] public / x86: Introduce __HYPERCALL_dm_op...
Date: Mon, 23 Jan 2017 12:03:09 +0000	[thread overview]
Message-ID: <7f78913d4d8347aeadba54603e08a9ee@AMSPEX02CL03.citrite.net> (raw)
In-Reply-To: <5776be4b-a544-4fda-8844-71768066077a@citrix.com>

> -----Original Message-----
> From: Andrew Cooper
> Sent: 23 January 2017 11:06
> To: Paul Durrant <Paul.Durrant@citrix.com>; xen-devel@lists.xenproject.org
> Cc: Ian Jackson <Ian.Jackson@citrix.com>; Jennifer Herbert
> <jennifer.herbert@citrix.com>; Jan Beulich <jbeulich@suse.com>
> Subject: Re: [PATCH v6 1/8] public / x86: Introduce __HYPERCALL_dm_op...
> 
> On 23/01/17 10:00, Paul Durrant wrote:
> > diff --git a/xen/include/public/hvm/dm_op.h
> b/xen/include/public/hvm/dm_op.h
> > new file mode 100644
> > index 0000000..9f3e9ee
> > --- /dev/null
> > +++ b/xen/include/public/hvm/dm_op.h
> > @@ -0,0 +1,69 @@
> > +/*
> > + * Copyright (c) 2016, Citrix Systems Inc
> > + *
> > + * Permission is hereby granted, free of charge, to any person obtaining a
> copy
> > + * of this software and associated documentation files (the "Software"),
> to
> > + * deal in the Software without restriction, including without limitation the
> > + * rights to use, copy, modify, merge, publish, distribute, sublicense,
> and/or
> > + * sell copies of the Software, and to permit persons to whom the
> Software is
> > + * furnished to do so, subject to the following conditions:
> > + *
> > + * The above copyright notice and this permission notice shall be included
> in
> > + * all copies or substantial portions of the Software.
> > + *
> > + * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY
> KIND, EXPRESS OR
> > + * IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
> MERCHANTABILITY,
> > + * FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO
> EVENT SHALL THE
> > + * AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,
> DAMAGES OR OTHER
> > + * LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR
> OTHERWISE, ARISING
> > + * FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE
> OR OTHER
> > + * DEALINGS IN THE SOFTWARE.
> > + *
> > + */
> > +
> > +#ifndef __XEN_PUBLIC_HVM_DM_OP_H__
> > +#define __XEN_PUBLIC_HVM_DM_OP_H__
> > +
> > +#if defined(__XEN__) || defined(__XEN_TOOLS__)
> > +
> > +#include "../xen.h"
> > +
> > +struct xen_dm_op {
> > +    uint32_t op;
> > +};
> > +
> > +struct xen_dm_op_buf {
> > +    XEN_GUEST_HANDLE(void) h;
> > +    xen_ulong_t size;
> > +};
> > +typedef struct xen_dm_op_buf xen_dm_op_buf_t;
> > +DEFINE_XEN_GUEST_HANDLE(xen_dm_op_buf_t);
> > +
> > +/* ` enum neg_errnoval
> > + * ` HYPERVISOR_dm_op(domid_t domid,
> > + * `                  xen_dm_op_buf_t bufs[],
> > + * `                  unsigned int nr_bufs)
> > + * `
> > + *
> > + * @domid is the domain the hypercall operates on.
> > + * @bufs points to an array of buffers where @bufs[0] contains a struct
> > + * xen_dm_op, describing the specific device model operation and its
> > + * parameters.
> > + * @bufs[1..] may be referenced in the parameters for the purposes of
> > + * passing extra information to or from the domain.
> > + * @nr_bufs is the number of buffers in the @bufs array.
> > + */
> 
> Sorry.  One last issue.  xen_dm_op_buf and the hypercall documentation
> need to be outside the __XEN_TOOL__ define, as they to be used by the
> kernel.
> 
> xen_dm_op can stay restricted to tools, as it is only needed by a device
> model.
> 
> With this fixed, Reviewed-by: Andrew Cooper
> <andrew.cooper3@citrix.com>.  This can be fixed on commit if there are
> no issues from others.
> 

I'm going to need to send v7. The name change in patch #7 broke the user-space parts so I need to fix.

  Paul

> ~Andrew

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

  reply	other threads:[~2017-01-23 12:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-23 10:00 [PATCH v6 0/8] New hypercall for device models Paul Durrant
2017-01-23 10:00 ` [PATCH v6 1/8] public / x86: Introduce __HYPERCALL_dm_op Paul Durrant
2017-01-23 11:06   ` Andrew Cooper
2017-01-23 12:03     ` Paul Durrant [this message]
2017-01-23 10:00 ` [PATCH v6 2/8] dm_op: convert HVMOP_*ioreq_server* Paul Durrant
2017-01-23 10:00 ` [PATCH v6 3/8] dm_op: convert HVMOP_track_dirty_vram Paul Durrant
2017-01-23 10:01 ` [PATCH v6 4/8] dm_op: convert HVMOP_set_pci_intx_level, HVMOP_set_isa_irq_level, and Paul Durrant
2017-01-23 10:01 ` [PATCH v6 5/8] dm_op: convert HVMOP_modified_memory Paul Durrant
2017-01-23 10:01 ` [PATCH v6 6/8] dm_op: convert HVMOP_set_mem_type Paul Durrant
2017-01-23 10:01 ` [PATCH v6 7/8] dm_op: convert HVMOP_inject_trap and HVMOP_inject_msi Paul Durrant
2017-01-23 10:01 ` [PATCH v6 8/8] x86/hvm: serialize trap injecting producer and consumer 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=7f78913d4d8347aeadba54603e08a9ee@AMSPEX02CL03.citrite.net \
    --to=paul.durrant@citrix.com \
    --cc=Andrew.Cooper3@citrix.com \
    --cc=Ian.Jackson@citrix.com \
    --cc=jbeulich@suse.com \
    --cc=jennifer.herbert@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).