xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@citrix.com>
To: Nathan Studer <nate.studer@dornerworks.com>
Cc: Ian Campbell <ian.campbell@citrix.com>,
	Xi Sisu <xisisu@gmail.com>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
	George Dunlap <george.dunlap@eu.citrix.com>,
	Ian Jackson <ian.jackson@eu.citrix.com>,
	Robert VanVossen <robert.vanvossen@dornerworks.com>,
	xen-devel@lists.xen.org,
	Joshua Whitehead <josh.whitehead@dornerworks.com>,
	Dario Faggioli <dario.faggioli@eu.citrix.com>
Subject: Re: [RFC Patch 3/3] Fix formatting and misleading comments/variables in sedf
Date: Mon, 17 Mar 2014 17:49:52 +0100	[thread overview]
Message-ID: <1395074992.4159.305.camel@Solace> (raw)
In-Reply-To: <1394824400-2796-4-git-send-email-nate.studer@dornerworks.com>


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

On ven, 2014-03-14 at 15:13 -0400, Nathan Studer wrote:
> From: Nathan Studer <nate.studer@dornerworks.com>
> 
> Update the sedf scheduler to correct some of the more aggregious formatting
> issues.  Also update some of the misleading comments/variable names.
> Specifically the sedf scheduler still implies that a domain and a vcpu
> are the same thing, which while true in the past is no longer the case.
> 
> Signed-off-by: Nathan Studer <nate.studer@dornerworks.com>
> Signed-off-by: Joshua Whitehead <josh.whitehead@dornerworks.com>
>
Both this and the previous patch looks fine, and, as said replying to
the cover letter, are something I think we want.

I'd provide a formal Reviewed-by tag, but I guess it's not that
important, as this is an RFC.... I'll do as soon as a non-RFC series
will pop up.

One question, on what is this based? I tried to apply the series on
today's tip, and it fails :-/

This is what I get trying to apply the first patch:
checking file xen/common/sched_sedf.c
Hunk #1 FAILED at 25.
Hunk #2 succeeded at 58 (offset -3 lines).
Hunk #3 succeeded at 73 (offset -3 lines).
Hunk #4 succeeded at 94 (offset -3 lines).
Hunk #5 succeeded at 179 (offset -3 lines).
Hunk #6 FAILED at 199.
Hunk #7 succeeded at 205 with fuzz 2 (offset -12 lines).
Hunk #8 succeeded at 221 (offset -12 lines).
Hunk #9 succeeded at 303 (offset -12 lines).
Hunk #10 succeeded at 313 (offset -12 lines).
Hunk #11 succeeded at 402 (offset -12 lines).
Hunk #12 succeeded at 441 (offset -12 lines).
Hunk #13 succeeded at 461 (offset -12 lines).
Hunk #14 succeeded at 503 (offset -12 lines).
Hunk #15 succeeded at 513 (offset -12 lines).
Hunk #16 succeeded at 525 (offset -12 lines).
Hunk #17 succeeded at 540 (offset -12 lines).
Hunk #18 succeeded at 575 (offset -12 lines).
Hunk #19 succeeded at 600 (offset -12 lines).
Hunk #20 succeeded at 609 (offset -12 lines).
Hunk #21 succeeded at 627 (offset -12 lines).
Hunk #22 succeeded at 641 (offset -12 lines).
Hunk #23 succeeded at 667 (offset -12 lines).
Hunk #24 succeeded at 678 (offset -12 lines).
Hunk #25 succeeded at 710 (offset -12 lines).
Hunk #26 succeeded at 730 (offset -12 lines).
Hunk #27 succeeded at 781 (offset -12 lines).
Hunk #28 succeeded at 894 (offset 69 lines).
Hunk #29 FAILED at 842.
Hunk #30 FAILED at 859.
4 out of 30 hunks FAILED

Can you provide an updated version?

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: 198 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:[~2014-03-17 16:49 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-14 19:13 [RFC Patch 0/3] Putting the "Simple" back in sedf Nathan Studer
2014-03-14 19:13 ` [RFC Patch 1/3] Remove sedf extra, weight, and latency parameter support Nathan Studer
2014-03-17  8:13   ` Jan Beulich
2014-03-17 17:02   ` Dario Faggioli
2014-03-21 11:16   ` Ian Campbell
2014-03-21 12:25     ` Nate Studer
2014-03-21 16:16       ` Dario Faggioli
2014-03-21 16:50         ` Sisu Xi
2014-03-24 15:44           ` Dario Faggioli
2014-03-14 19:13 ` [RFC Patch 2/3] Remove extra queues, latency scaling, and weight support from sedf Nathan Studer
2014-03-14 19:13 ` [RFC Patch 3/3] Fix formatting and misleading comments/variables in sedf Nathan Studer
2014-03-17 16:49   ` Dario Faggioli [this message]
2014-03-17 17:00     ` Nate Studer
2014-03-14 19:22 ` [RFC Patch 0/3] Putting the "Simple" back " George Dunlap
2014-03-14 20:13   ` Nate Studer
2014-03-14 20:31     ` Nate Studer
2014-03-17 10:29       ` Dario Faggioli
2014-03-17 15:51     ` Dario Faggioli
2014-03-17 17:01       ` Sisu Xi

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=1395074992.4159.305.camel@Solace \
    --to=dario.faggioli@citrix.com \
    --cc=dario.faggioli@eu.citrix.com \
    --cc=george.dunlap@eu.citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=josh.whitehead@dornerworks.com \
    --cc=nate.studer@dornerworks.com \
    --cc=robert.vanvossen@dornerworks.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --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 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).