From: Tianyang Chen <tiche@seas.upenn.edu>
To: xen-devel@lists.xenproject.org
Cc: dario.faggioli@citrix.com, Tianyang Chen <tiche@seas.upenn.edu>,
george.dunlap@citrix.com, mengxu@cis.upenn.edu
Subject: [PATCH 0/2] xen: sched: rtds refactor code
Date: Sun, 15 May 2016 19:54:48 -0400 [thread overview]
Message-ID: <1463356490-9780-1-git-send-email-tiche@seas.upenn.edu> (raw)
The first part of this patch series aims at fixing coding syle issue
for control structures. Because locks are grabbed in schedule.c before
hooks are called, underscores in front of function names are removed.
The second part replaces atomic bit-ops with non-atomic ones since locks
are grabbed in schedule.c.
Discussions:
http://lists.xenproject.org/archives/html/xen-devel/2016-03/msg01528.html
http://www.gossamer-threads.com/lists/xen/devel/431251?do=post_view_threaded#431251
Tianyang Chen (2):
xen: sched: rtds refactor code
xen: sched: rtds: use non-atomic bit-ops
xen/common/sched_rt.c | 122 ++++++++++++++++++++++++++-----------------------
1 file changed, 64 insertions(+), 58 deletions(-)
--
1.7.9.5
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next reply other threads:[~2016-05-15 23:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-15 23:54 Tianyang Chen [this message]
2016-05-15 23:54 ` [PATCH 1/2] xen: sched: rtds refactor code Tianyang Chen
2016-05-17 15:06 ` Meng Xu
2016-06-22 15:51 ` George Dunlap
2016-06-22 16:16 ` Meng Xu
2016-06-23 10:42 ` George Dunlap
2016-06-24 7:45 ` Dario Faggioli
2016-06-24 11:36 ` Meng Xu
2016-05-15 23:54 ` [PATCH 2/2] xen: sched: rtds: use non-atomic bit-ops Tianyang Chen
2016-05-17 15:08 ` Meng Xu
2016-05-17 15:05 ` [PATCH 0/2] xen: sched: rtds refactor code 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=1463356490-9780-1-git-send-email-tiche@seas.upenn.edu \
--to=tiche@seas.upenn.edu \
--cc=dario.faggioli@citrix.com \
--cc=george.dunlap@citrix.com \
--cc=mengxu@cis.upenn.edu \
--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).