From: Paul Durrant <Paul.Durrant@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH] docs/design: introduce HVMMEM_ioreq_serverX types
Date: Thu, 25 Feb 2016 16:55:31 +0000 [thread overview]
Message-ID: <e7790e3be11b4c389c32963baf008b81@AMSPEX02CL03.citrite.net> (raw)
In-Reply-To: <56CF3E4202000078000D6567@prv-mh.provo.novell.com>
> -----Original Message-----
> From: Xen-devel [mailto:xen-devel-bounces@lists.xen.org] On Behalf Of Jan
> Beulich
> Sent: 25 February 2016 16:48
> To: Paul Durrant
> Cc: xen-devel@lists.xenproject.org
> Subject: Re: [Xen-devel] [PATCH] docs/design: introduce
> HVMMEM_ioreq_serverX types
>
> >>> On 25.02.16 at 16:49, <paul.durrant@citrix.com> wrote:
> > +To allow an IOREQ server to claim or release a claim to a type a new pair
> > +of hypercalls will be introduced:
> > +
> > +- HVMOP\_map\_mem\_type\_to\_ioreq\_server
> > +- HVMOP\_unmap\_mem\_type\_from\_ioreq\_server
> > +
> > +and an associated argument structure:
> > +
> > + struct hvm_ioreq_mem_type {
> > + domid_t domid; /* IN - domain to be serviced */
> > + ioservid_t id; /* IN - server id */
> > + hvmmem_type_t type; /* IN - memory type */
> > + uint32_t flags; /* IN - types of access to be
> > + intercepted */
> > +
> > + #define _HVMOP_IOREQ_MEM_ACCESS_READ 0
> > + #define HVMOP_IOREQ_MEM_ACCESS_READ \
> > + (1 << _HVMOP_IOREQ_MEM_ACCESS_READ)
> > +
> > + #define _HVMOP_IOREQ_MEM_ACCESS_WRITE 1
> > + #define HVMOP_IOREQ_MEM_ACCESS_WRITE \
> > + (1 << _HVMOP_IOREQ_MEM_ACCESS_WRITE)
> > +
> > + };
>
> How about having just one new hypercall, with flags being zero
> meaning "unmap"?
Hmm, yes we could do it that way. I saves an op code so I'll re-spin the doc.
Thanks,
Paul
>
> Jan
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-02-25 16:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-25 15:49 [PATCH] docs/design: introduce HVMMEM_ioreq_serverX types Paul Durrant
2016-02-25 16:28 ` Andrew Cooper
2016-02-25 16:48 ` Paul Durrant
2016-02-25 16:47 ` Jan Beulich
2016-02-25 16:55 ` Paul Durrant [this message]
2016-02-26 4:24 ` Tian, Kevin
2016-02-26 9:14 ` Jan Beulich
2016-02-26 9:14 ` Paul Durrant
2016-02-26 6:59 ` Yu, Zhang
2016-02-26 9:18 ` Jan Beulich
2016-02-26 9:36 ` Yu, Zhang
2016-02-26 9:50 ` Paul Durrant
2016-02-26 9:58 ` Yu, Zhang
2016-02-26 9:21 ` Paul Durrant
2016-02-26 9:30 ` Yu, Zhang
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=e7790e3be11b4c389c32963baf008b81@AMSPEX02CL03.citrite.net \
--to=paul.durrant@citrix.com \
--cc=JBeulich@suse.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).