xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Tianyang Chen <tiche@cis.upenn.edu>
To: xen-devel@lists.xenproject.org
Cc: dario.faggioli@citrix.com, Tianyang Chen <tiche@cis.upenn.edu>,
	george.dunlap@citrix.com, mengxu@cis.upenn.edu
Subject: [PATCH v2 0/2] xen: sched: rtds clean-up
Date: Sat, 25 Jun 2016 20:48:32 -0400	[thread overview]
Message-ID: <1466902114-21694-1-git-send-email-tiche@cis.upenn.edu> (raw)

The first part of this patch series aims at fixing coding syle issue
for control structures, as well as aligning comments in the structs.

Related discussions: 
http://lists.xenproject.org/archives/html/xen-devel/2016-03/msg01528.html

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 code clean-up
  xen: sched: rtds: use non-atomic bit-ops

 xen/common/sched_rt.c |  106 ++++++++++++++++++++++++++-----------------------
 1 file changed, 56 insertions(+), 50 deletions(-)

-- 
1.7.9.5


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

             reply	other threads:[~2016-06-26  0:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-26  0:48 Tianyang Chen [this message]
2016-06-26  0:48 ` [PATCH v2 1/2] xen: sched: rtds code clean-up Tianyang Chen
2016-06-29 16:21   ` Dario Faggioli
2016-06-26  0:48 ` [PATCH v2 2/2] xen: sched: rtds: use non-atomic bit-ops Tianyang Chen
2016-06-29 16:44   ` 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=1466902114-21694-1-git-send-email-tiche@cis.upenn.edu \
    --to=tiche@cis.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).