From: Meng Xu <mengxu@cis.upenn.edu>
To: Dario Faggioli <raistlin@linux.it>
Cc: Wei Liu <wei.liu2@citrix.com>,
George Dunlap <george.dunlap@eu.citrix.com>,
Julien Grall <julien.grall@linaro.org>,
Ian Jackson <ian.jackson@eu.citrix.com>,
George Dunlap <George.Dunlap@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH v4 4/5] xentrace: enable per-VCPU extratime flag for RTDS
Date: Thu, 16 Nov 2017 11:30:24 -0500 [thread overview]
Message-ID: <CAENZ-+nNe5cL8KfdMsonqxz2iyL4zHOzsqLd9T2HhCtGWkxK5A@mail.gmail.com> (raw)
In-Reply-To: <1508227851.6552.135.camel@linux.it>
Hi all,
On Tue, Oct 17, 2017 at 4:10 AM, Dario Faggioli <raistlin@linux.it> wrote:
>
> On Wed, 2017-10-11 at 14:02 -0400, Meng Xu wrote:
> > Change repl_budget event output for xentrace formats and xenalyze
> >
> > Signed-off-by: Meng Xu <mengxu@cis.upenn.edu>
> >
> I'd say:
>
> Reviewed-by: Dario Faggioli <raistlin@linux.it>
>
Just a friendly reminder:
This patch has not been pushed into either the staging or master
branch of xen.git.
This is an essential patch for the new version of RTDS scheduler which
Dario and I are maintaining.
This patch won't affect other features.
It has been a while without hearing complaints from the tools maintainers.
Is it ok to push it?
>
> However...
>
> > diff --git a/tools/xentrace/xenalyze.c b/tools/xentrace/xenalyze.c
> > index 79bdba7..19e050f 100644
> > --- a/tools/xentrace/xenalyze.c
> > +++ b/tools/xentrace/xenalyze.c
> > @@ -7935,23 +7935,29 @@ void sched_process(struct pcpu_info *p)
> > unsigned int vcpuid:16, domid:16;
> > uint64_t cur_bg;
> > int delta;
> > + unsigned priority_level;
> > + unsigned has_extratime;
> >
> ...this last field is 'bool' in Xen.
>
> I appreciate that xenalyze does not build if you just make this bool as
> well. But it does build for me, if you do that, and also include
> stdbool.h, which I think is a fine thing to do.
>
> Anyway, I'll leave this to George and tools' maintainers.
If it turns out bool is prefered, I can change it and send out a new one.
But please just let me know so that we can have a complete toolstack
for the new version of RTDS scheduler.
Thanks,
Meng
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-11-16 16:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-11 18:02 [PATCH v4 0/5] Towards work-conserving RTDS Meng Xu
2017-10-11 18:02 ` [PATCH v4 1/5] xen:rtds: towards work conserving RTDS Meng Xu
2017-10-11 18:02 ` [PATCH v4 2/5] libxl: enable per-VCPU extratime flag for RTDS Meng Xu
2017-10-11 18:02 ` [PATCH v4 3/5] xl: " Meng Xu
2017-10-11 18:02 ` [PATCH v4 4/5] xentrace: " Meng Xu
2017-10-17 8:10 ` Dario Faggioli
2017-10-17 13:22 ` Meng Xu
2017-10-23 18:50 ` Meng Xu
2017-10-25 14:31 ` Wei Liu
2017-11-02 13:49 ` Meng Xu
2017-11-16 16:30 ` Meng Xu [this message]
2017-10-11 18:02 ` [PATCH v4 5/5] docs: " Meng Xu
2017-10-12 9:02 ` [PATCH v4 0/5] Towards work-conserving RTDS Wei Liu
2017-10-12 14:34 ` Meng Xu
2017-10-17 7:26 ` Dario Faggioli
2017-10-17 7:29 ` Dario Faggioli
2017-10-17 13:19 ` Meng Xu
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=CAENZ-+nNe5cL8KfdMsonqxz2iyL4zHOzsqLd9T2HhCtGWkxK5A@mail.gmail.com \
--to=mengxu@cis.upenn.edu \
--cc=George.Dunlap@citrix.com \
--cc=george.dunlap@eu.citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=julien.grall@linaro.org \
--cc=raistlin@linux.it \
--cc=wei.liu2@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).