Re: [Xen-devel] [PATCH] xen: enable per-VCPU parameter for RTDS

[Dario Faggioli <dario.faggioli@xxxxxxxxxx>]

On Tue, 2016-04-05 at 10:18 +0100, George Dunlap wrote:
> On 05/04/16 00:14, Andrew Cooper wrote:
> > On 04/04/2016 23:45, Chong Li wrote:
> > > ---
> > >  xen/common/sched_credit.c  | 1 +
> > >  xen/common/sched_credit2.c | 1 +
> > >  2 files changed, 2 insertions(+)
> > > 
> > > diff --git a/xen/common/sched_credit.c
> > > b/xen/common/sched_credit.c
> > > index e5d15d8..fa6b7f0 100644
> > > --- a/xen/common/sched_credit.c
> > > +++ b/xen/common/sched_credit.c
> > > @@ -1101,6 +1101,7 @@ csched_dom_cntl(
> > >              sdom->cap = op->u.credit.cap;
> > >          break;
> > >      default:
> > > +        spin_unlock_irqrestore(&prv->lock, flags);
> > >          return -EINVAL;
> > >      }
> > >  
> > While Dario didn't care too much how you fixed the issue, I do.
> > 
> > Please use an "int rc = 0" and remove remove the return statement
> > (instead, assigning rc = -EINVAL; and a break;).  It makes far more
> > readable and understandable code, which is better in the long run.
>
> Well Dario's a scheduler maintainer and you're not.
> 
Eheh :-)

> But in any case, I also prefer the rc / break (or goto out) pattern
> enough to ask for a re-send.  (But I now see that a v3 has already
> been
> sent.)
> 
Yeah, I said I was ok in the event that we wanted to check in the fix
ASAP, editing the changelog during commit. If a resend were to be done,
I'd have hoped the structure to be changed as said above... I probably
should have said it more explicitly.

Impressive that we're all on the same page (at least, from a technical
point of view! :-P)

Thanks and 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: signature.asc
Description: This is a digitally signed message part

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