From: Chao Peng <chao.p.peng@linux.intel.com>
To: Yi Sun <yi.y.sun@linux.intel.com>, xen-devel@lists.xenproject.org
Cc: kevin.tian@intel.com, wei.liu2@citrix.com,
andrew.cooper3@citrix.com, dario.faggioli@citrix.com,
ian.jackson@eu.citrix.com, julien.grall@arm.com,
mengxu@cis.upenn.edu, jbeulich@suse.com, roger.pau@citrix.com
Subject: Re: [RFC v2 07/12] x86: implement set value flow for MBA.
Date: Wed, 09 Aug 2017 09:33:05 +0800 [thread overview]
Message-ID: <1502242385.3636.25.camel@linux.intel.com> (raw)
In-Reply-To: <1500540553-29199-8-git-send-email-yi.y.sun@linux.intel.com>
> /* write_msr is used to write out feature MSR register. */
> void (*write_msr)(unsigned int cos, uint32_t val, enum
> psr_val_type type);
> +
> + /*
> + * check_change_val is used to check if input val fulfills SDM
> requirement.
> + * Change it to valid value if SDM allows.
> + */
> + bool (*check_change_val)(const struct feat_node *feat, unsigned
> long *val);
I understand you need check the value and also potentially change the
value in certain case, but the naming here sounds not so good.
check_value? accept_value? or any other better solutions?
> } *feat_props[FEAT_TYPE_NUM];
>
> /*
>
> +static bool cat_check_change_val(const struct feat_node *feat,
> + unsigned long *cbm)
and keep this as cat_check_cbm(),
>
> +static bool mba_check_change_val(const struct feat_node *feat,
> + unsigned long *thrtl)
and this becomes mba_check_thrtl()?
Chao
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-08-09 1:33 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-20 8:49 [RFC v2 00/12] Enable Memory Bandwidth Allocation in Xen Yi Sun
2017-07-20 8:49 ` [RFC v2 01/12] docs: create Memory Bandwidth Allocation (MBA) feature document Yi Sun
2017-07-20 8:49 ` [RFC v2 02/12] Rename PSR sysctl/domctl interfaces and xsm policy to make them be general Yi Sun
2017-07-31 14:30 ` Wei Liu
2017-07-20 8:49 ` [RFC v2 03/12] x86: rename 'cbm_type' to 'psr_val_type' to make it general Yi Sun
2017-07-31 14:30 ` Wei Liu
2017-07-20 8:49 ` [RFC v2 04/12] x86: implement data structure and CPU init flow for MBA Yi Sun
2017-07-31 14:30 ` Wei Liu
2017-08-01 0:51 ` Yi Sun
2017-08-09 1:09 ` Chao Peng
2017-08-09 2:05 ` Yi Sun
2017-07-20 8:49 ` [RFC v2 05/12] x86: implement get hw info " Yi Sun
2017-08-09 1:12 ` Chao Peng
2017-07-20 8:49 ` [RFC v2 06/12] x86: implement get value interface " Yi Sun
2017-07-20 8:49 ` [RFC v2 07/12] x86: implement set value flow " Yi Sun
2017-08-09 1:33 ` Chao Peng [this message]
2017-07-20 8:49 ` [RFC v2 08/12] tools: create general interfaces to support psr allocation features Yi Sun
2017-07-31 14:30 ` Wei Liu
2017-08-01 0:56 ` Yi Sun
2017-08-01 9:05 ` Wei Liu
2017-07-20 8:49 ` [RFC v2 09/12] tools: implement the new get hw info interface suitable to all " Yi Sun
2017-07-31 14:30 ` Wei Liu
2017-07-20 8:49 ` [RFC v2 10/12] tools: implemet new get value interface suitable for " Yi Sun
2017-07-31 14:30 ` Wei Liu
2017-08-01 0:57 ` Yi Sun
2017-07-20 8:49 ` [RFC v2 11/12] tools: implemet new set " Yi Sun
2017-07-20 8:49 ` [RFC v2 12/12] docs: add MBA description in docs 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=1502242385.3636.25.camel@linux.intel.com \
--to=chao.p.peng@linux.intel.com \
--cc=andrew.cooper3@citrix.com \
--cc=dario.faggioli@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=julien.grall@arm.com \
--cc=kevin.tian@intel.com \
--cc=mengxu@cis.upenn.edu \
--cc=roger.pau@citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.org \
--cc=yi.y.sun@linux.intel.com \
/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).