From: Yi Sun <yi.y.sun@linux.intel.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: wei.liu2@citrix.com, he.chen@linux.intel.com,
andrew.cooper3@citrix.com, ian.jackson@eu.citrix.com,
chao.p.peng@linux.intel.com, xen-devel@lists.xenproject.org
Subject: Re: [PATCH 2/3] x86: add support for L2 CAT in hypervisor.
Date: Wed, 7 Sep 2016 15:13:06 +0800 [thread overview]
Message-ID: <20160907071306.GD30513@yi.y.sun> (raw)
In-Reply-To: <57CE8FBA020000780010BEF0@prv-mh.provo.novell.com>
On 16-09-06 01:43:22, Jan Beulich wrote:
> >>> On 25.08.16 at 07:22, <yi.y.sun@linux.intel.com> wrote:
>
> Please extend the comments given for patch 1 to this one. Just one
> extra thing:
>
> > @@ -743,7 +744,7 @@ struct xen_sysctl_psr_cat_op {
> > uint32_t cos_max; /* OUT: Maximum COS */
> > #define XEN_SYSCTL_PSR_CAT_L3_CDP (1u << 0)
> > uint32_t flags; /* OUT: CAT flags */
> > - } l3_info;
> > + } info;
>
> Such an adjustment breaks the tools build, i.e. can't come without
> also minimally adjusting libxc.
>
> Jan
I thought 4.8 will also make tools version upgrade but not considered
to be compatible with old tools. Sorry for that.
Considering the compatibility and to support future feature, I want to
add a general structure in union, like below. How do you think? Thanks!
union {
struct {
uint32_t cbm_len; /* OUT: CBM length */
uint32_t cos_max; /* OUT: Maximum COS */
#define XEN_SYSCTL_PSR_CAT_L3_CDP (1u << 0)
uint32_t flags; /* OUT: CAT flags */
} l3_info;
struct {
uint32_t cbm_len;
uint32_t cos_max;
uint32_t data; /* Specific data of feature */
} psr_info;
} u;
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-09-07 7:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-25 5:22 [PATCH 2/3] x86: add support for L2 CAT in hypervisor Yi Sun
2016-09-06 7:43 ` Jan Beulich
2016-09-07 7:13 ` Yi Sun [this message]
2016-09-07 9:03 ` Jan Beulich
2016-09-08 7:30 ` Yi Sun
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=20160907071306.GD30513@yi.y.sun \
--to=yi.y.sun@linux.intel.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=chao.p.peng@linux.intel.com \
--cc=he.chen@linux.intel.com \
--cc=ian.jackson@eu.citrix.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).