xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Chao Peng <chao.p.peng@linux.intel.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: keir@xen.org, Ian.Campbell@citrix.com,
	stefano.stabellini@eu.citrix.com, George.Dunlap@eu.citrix.com,
	andrew.cooper3@citrix.com, Ian.Jackson@eu.citrix.com,
	xen-devel@lists.xen.org, dgdegra@tycho.nsa.gov
Subject: Re: [PATCH v14 01/10] x86: add generic resource (e.g. MSR) access hypercall
Date: Tue, 2 Sep 2014 16:33:10 +0800	[thread overview]
Message-ID: <20140902083310.GA15872@pengc-linux> (raw)
In-Reply-To: <5400BB24020000780002F1BF@mail.emea.novell.com>

On Fri, Aug 29, 2014 at 04:40:52PM +0100, Jan Beulich wrote:
> >>> On 28.08.14 at 09:43, <chao.p.peng@linux.intel.com> wrote:
> > +static void resource_access_one(void *info)
> > +{
> > +    struct xen_resource_access *ra = info;
> > +    int ret = 0;
> > +
> > +    switch ( ra->data.cmd )
> > +    {
> > +    case XEN_RESOURCE_OP_MSR_READ:
> > +    case XEN_RESOURCE_OP_MSR_WRITE:
> > +        if ( ra->data.idx >> 32 )
> > +            ret = -EINVAL;
> > +        if ( !allow_access_msr(ra->data.idx) )
> > +            ret = -EACCES;
> > +        if ( ra->data.cmd == XEN_RESOURCE_OP_MSR_READ )
> > +            ret = rdmsr_safe(ra->data.idx, ra->data.val);
> > +        else
> > +            ret = wrmsr_safe(ra->data.idx, ra->data.val);
> > +        break;
> 
> Did you mean these latter tow if()-s perhaps be "else if"?
It is true, thanks.
> 
> > +    case XENPF_resource_op:
> > +    {
> > +        struct xen_resource_access ra;
> > +        struct xenpf_resource_op *rsc_op = &op->u.resource_op;
> > +        unsigned int i, j = 0, cpu = smp_processor_id();
> > +
> > +        for ( i = 0; i < rsc_op->nr; i++ )
> > +        {
> > +            if ( copy_from_guest_offset(&ra.data, rsc_op->data, i, 1) )
> > +            {
> > +                ret = -EFAULT;
> > +                break;
> > +            }
> > +
> > +            if ( ra.data.cpu == cpu )
> > +                resource_access_one(&ra);
> > +            else if ( cpu_online(ra.data.cpu) )
> > +                on_selected_cpus(cpumask_of(ra.data.cpu),
> > +                                 resource_access_one, &ra, 1);
> > +            else
> > +            {
> > +                ret = -ENODEV;
> > +                break;
> > +            }
> > +
> > +            if ( ra.ret )
> > +            {
> > +                ret = ra.ret;
> > +                break;
> > +            }
> > +
> > +            if ( copy_to_guest_offset(rsc_op->data, i, &ra.data, 1) )
> > +            {
> > +                ret = -EFAULT;
> > +                break;
> > +            }
> > +
> > +            /* Find the start point that requires no preemption */
> > +            if ( ra.data.flag && j == 0 )
> > +                j = i;
> > +            /* Set j = 0 when walking out of the non-preemption area */
> > +            if ( ra.data.flag == 0 )
> > +                j = 0;
> > +            if ( hypercall_preempt_check() )
> > +            {
> > +                ret = hypercall_create_continuation(
> > +                    __HYPERVISOR_platform_op, "ih",
> > +                    ra.data.flag ? j : i, u_xenpf_op);
> 
> Which means everything starting from j will be re-executed
> another time when continuing. That creates three problems: You
> can't guarantee forwards progress, you may do something
> having side effects more than once, and you break the operation
> in a place that was requested to not be preemptible.
I saw the problem here. Actually the j or i here will not be passed to
next iteration successfully. Possibly a 'count' param is needed to be
added to do_platform_op() for this purpose.
> 
> > +struct xenpf_resource_data {
> > +    uint16_t cmd;       /* XEN_RESOURCE_OP_* */
> > +    uint16_t flag;      /* avoid preemption between certain iterations */
> 
> You want to use just one bit out of this field (and verify all other bits
> are zero, so they can get assigned a meaning later).
OK, I will add a one-bit flag macro to indicate this.
> 
> Jan
> 
> > +    uint32_t cpu;
> > +    uint64_t idx;
> > +    uint64_t val;
> > +};

  reply	other threads:[~2014-09-02  8:33 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-28  7:43 [PATCH v14 00/10] enable Cache QoS Monitoring (CQM) feature Chao Peng
2014-08-28  7:43 ` [PATCH v14 01/10] x86: add generic resource (e.g. MSR) access hypercall Chao Peng
2014-08-29 15:40   ` Jan Beulich
2014-09-02  8:33     ` Chao Peng [this message]
2014-09-02  8:52       ` Jan Beulich
2014-09-02 10:04         ` Chao Peng
2014-09-02 10:24           ` Jan Beulich
2014-08-28  7:43 ` [PATCH v14 02/10] xsm: add resource operation related xsm policy Chao Peng
2014-08-29 18:55   ` Daniel De Graaf
2014-08-28  7:43 ` [PATCH v14 03/10] tools: provide interface for generic resource access Chao Peng
2014-08-28  7:43 ` [PATCH v14 04/10] x86: detect and initialize Platform QoS Monitoring feature Chao Peng
2014-08-28 10:52   ` Andrew Cooper
2014-09-02  8:40     ` Chao Peng
2014-09-01 11:38   ` Jan Beulich
2014-09-02  9:05     ` Chao Peng
2014-09-02  9:30       ` Jan Beulich
2014-08-28  7:43 ` [PATCH v14 05/10] x86: dynamically attach/detach QoS monitoring service for a guest Chao Peng
2014-09-01 11:39   ` Jan Beulich
2014-08-28  7:43 ` [PATCH v14 06/10] x86: collect global QoS monitoring information Chao Peng
2014-09-01 11:44   ` Jan Beulich
2014-08-28  7:43 ` [PATCH v14 07/10] x86: enable QoS monitoring for each domain RMID Chao Peng
2014-09-01 11:49   ` Jan Beulich
2014-08-28  7:43 ` [PATCH v14 08/10] x86: add QoS monitoring related MSRs in allowed list Chao Peng
2014-08-28  7:43 ` [PATCH v14 09/10] xsm: add platform QoS related xsm policies Chao Peng
2014-08-28  7:43 ` [PATCH v14 10/10] tools: CMDs and APIs for Platform QoS Monitoring 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=20140902083310.GA15872@pengc-linux \
    --to=chao.p.peng@linux.intel.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=andrew.cooper3@citrix.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).