From: "Jan Beulich" <JBeulich@suse.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
Chao Peng <chao.p.peng@linux.intel.com>,
xen-devel@lists.xen.org
Cc: keir@xen.org, Ian.Campbell@citrix.com,
stefano.stabellini@eu.citrix.com, George.Dunlap@eu.citrix.com,
Ian.Jackson@eu.citrix.com, dgdegra@tycho.nsa.gov
Subject: Re: [PATCH v17 01/10] x86: add generic resource (e.g. MSR) access hypercall
Date: Mon, 29 Sep 2014 14:55:35 +0100 [thread overview]
Message-ID: <542980F7020000780003A8EE@mail.emea.novell.com> (raw)
In-Reply-To: <542962E2.9070902@citrix.com>
>>> On 29.09.14 at 15:47, <andrew.cooper3@citrix.com> wrote:
> On 29/09/14 11:40, Chao Peng wrote:
>> --- a/xen/include/public/platform.h
>> +++ b/xen/include/public/platform.h
>> @@ -528,6 +528,33 @@ typedef struct xenpf_core_parking xenpf_core_parking_t;
>> DEFINE_XEN_GUEST_HANDLE(xenpf_core_parking_t);
>>
>> /*
>> + * Access generic platform resources(e.g., accessing MSR, port I/O, etc)
>> + * in unified way. Batch resource operations in one call are supported and
>> + * thay are always non-preemptible and execute in their original order.
>> + */
>> +#define XENPF_resource_op 61
>> +
>> +#define XEN_RESOURCE_OP_MSR_READ 0
>> +#define XEN_RESOURCE_OP_MSR_WRITE 1
>> +
>> +struct xenpf_resource_entry {
>> + uint32_t cmd; /* IN: XEN_RESOURCE_OP_* */
>> + uint32_t rsvd; /* IN: padding and must be zero */
>
> This rsvd should be int32_t ret, and an out parameter.
I guess I'd prefer keeping the reserved field as is and
overloading the cmd field (i.e. making it a union). That way
we retain extensibility for something future use of which is
really rather vague at this point.
Jan
next prev parent reply other threads:[~2014-09-29 13:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-29 10:40 [PATCH v17 00/10] enable Cache Monitoring Technology (CMT) feature Chao Peng
2014-09-29 10:40 ` [PATCH v17 01/10] x86: add generic resource (e.g. MSR) access hypercall Chao Peng
2014-09-29 13:47 ` Andrew Cooper
2014-09-29 13:55 ` Jan Beulich [this message]
2014-09-29 10:40 ` [PATCH v17 02/10] xsm: add resource operation related xsm policy Chao Peng
2014-09-29 10:40 ` [PATCH v17 03/10] tools: provide interface for generic resource access Chao Peng
2014-09-29 10:40 ` [PATCH v17 04/10] x86: detect and initialize Cache Monitoring Technology feature Chao Peng
2014-09-29 14:03 ` Andrew Cooper
2014-09-29 10:40 ` [PATCH v17 05/10] x86: dynamically attach/detach CMT service for a guest Chao Peng
2014-09-29 14:05 ` Andrew Cooper
2014-09-29 10:40 ` [PATCH v17 06/10] x86: collect global CMT information Chao Peng
2014-09-29 14:07 ` Andrew Cooper
2014-09-29 10:40 ` [PATCH v17 07/10] x86: enable CMT for each domain RMID Chao Peng
2014-09-29 14:08 ` Andrew Cooper
2014-09-29 10:40 ` [PATCH v17 08/10] x86: add CMT related MSRs in allowed list Chao Peng
2014-09-29 14:09 ` Andrew Cooper
2014-09-29 10:40 ` [PATCH v17 09/10] xsm: add CMT related xsm policies Chao Peng
2014-09-29 10:40 ` [PATCH v17 10/10] tools: CMDs and APIs for Cache Monitoring Technology Chao Peng
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=542980F7020000780003A8EE@mail.emea.novell.com \
--to=jbeulich@suse.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=chao.p.peng@linux.intel.com \
--cc=dgdegra@tycho.nsa.gov \
--cc=keir@xen.org \
--cc=stefano.stabellini@eu.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 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).