All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@citrix.com>
To: Chong Li <lichong659@gmail.com>
Cc: Chong Li <chong.li@wustl.edu>, Sisu Xi <xisisu@gmail.com>,
	George Dunlap <george.dunlap@eu.citrix.com>,
	xen-devel <xen-devel@lists.xen.org>,
	Meng Xu <mengxu@cis.upenn.edu>, Jan Beulich <jbeulich@suse.com>,
	Dagaen Golomb <dgolomb@seas.upenn.edu>
Subject: Re: [PATCH v2 for Xen 4.6 1/4] xen: enabling XL to set per-VCPU parameters of a domain for RTDS scheduler
Date: Thu, 4 Jun 2015 17:10:09 +0200	[thread overview]
Message-ID: <1433430609.6291.13.camel@citrix.com> (raw)
In-Reply-To: <CAGHO-ioHKGt6cpTRMUJO8_7cFxdqDMA770t0Sh51t41QA-+jNw@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 2132 bytes --]

On Fri, 2015-05-29 at 11:47 -0500, Chong Li wrote:
> On Fri, May 29, 2015 at 8:51 AM, Dario Faggioli
> <dario.faggioli@citrix.com> wrote:
> > On Mon, 2015-05-25 at 19:05 -0500, Chong Li wrote:
> >
> >> diff --git a/xen/common/domctl.c b/xen/common/domctl.c
> >> index 28aea55..8143c44 100644
> >> --- a/xen/common/domctl.c
> >> +++ b/xen/common/domctl.c
> 
> >
> > /* Set or get info? */
> > #define XEN_DOMCTL_SCHEDOP_putinfo 0
> > #define XEN_DOMCTL_SCHEDOP_getinfo 1
> > #define XEN_DOMCTL_SCHEDOP_putvcpuinfo 2
> > #define XEN_DOMCTL_SCHEDOP_getvcpuinfo 3
> > struct xen_domctl_scheduler_op {
> >     uint32_t sched_id;  /* XEN_SCHEDULER_* */
> >     uint32_t cmd;       /* XEN_DOMCTL_SCHEDOP_* */
> >     union {
> >         xen_domctl_schedparam_t d;
> >         struct {
> >             XEN_GUEST_HANDLE_64(xen_domctl_schedparam_vcpu_t) vcpus;
> >             uint16_t nr_vcpus;
> >         } v;
> >     } u;
> > };
> > typedef struct xen_domctl_scheduler_op xen_domctl_scheduler_op_t;
> > DEFINE_XEN_GUEST_HANDLE(xen_domctl_scheduler_op_t);
> >
> > I'm also attaching a (build-tested only) patch to that effect (I'm
> > killing SEDF in there, so I don't have to care about it, as it's going
> > away anyway).
> >
> > Thoughts?
> >
> I see. So now we put per-dom params and per-vcpu params into the same
> structure (xen_domctl_scheduler_op). This structure will be handled in
> sched_adjust and there should be a "switch" in that function to
> distinguish per-dom get/set and per-vcpu get/set. Right?
> 
You're describing correctly what I had in mind and tried to do in the
draft patch, yes. Whether to do it or not, well, it's a proposal. George
says he also thinks the thing makes sense to him too, so I guess you can
go ahead and try doing so in v3.

Of course, others, feel free to chime in.

Regards,
Dario

-- 
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2015-06-04 15:10 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-26  0:05 [PATCH v2 for Xen 4.6 1/4] xen: enabling XL to set per-VCPU parameters of a domain for RTDS scheduler Chong Li
2015-05-26  9:08 ` Jan Beulich
2015-05-26 17:18   ` Chong Li
2015-05-27  5:33     ` Chong Li
2015-05-27 11:42       ` Jan Beulich
2015-05-27 11:41     ` Jan Beulich
2015-05-29 13:01       ` Dario Faggioli
2015-05-29 13:14         ` Jan Beulich
2015-06-04 15:27           ` Dario Faggioli
2015-05-27 10:02 ` Chao Peng
2015-05-27 22:16   ` Chong Li
2015-05-29 13:51 ` Dario Faggioli
2015-05-29 16:47   ` Chong Li
2015-06-04 15:10     ` Dario Faggioli [this message]
2015-06-02 16:06   ` George Dunlap
2015-06-02 16:28 ` George Dunlap
2015-06-04 15:14   ` Dario Faggioli

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=1433430609.6291.13.camel@citrix.com \
    --to=dario.faggioli@citrix.com \
    --cc=chong.li@wustl.edu \
    --cc=dgolomb@seas.upenn.edu \
    --cc=george.dunlap@eu.citrix.com \
    --cc=jbeulich@suse.com \
    --cc=lichong659@gmail.com \
    --cc=mengxu@cis.upenn.edu \
    --cc=xen-devel@lists.xen.org \
    --cc=xisisu@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.