All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@citrix.com>
To: Juergen Gross <jgross@suse.com>, xen-devel@lists.xenproject.org
Cc: George Dunlap <george.dunlap@citrix.com>,
	Jan Beulich <jbeulich@suse.com>
Subject: Re: [PATCH] xen: sched: don't call hooks of the wrong scheduler via VCPU2OP
Date: Fri, 17 Mar 2017 12:46:43 +0100	[thread overview]
Message-ID: <1489751203.15340.1.camel@citrix.com> (raw)
In-Reply-To: <791f6a11-6a3c-63e3-b9e8-0941aa3b1fee@suse.com>


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

On Fri, 2017-03-17 at 06:28 +0100, Juergen Gross wrote:
> On 16/03/17 22:30, Dario Faggioli wrote:
> > [..]
> > Fix this by taking care, in VCPU2OP, of the case
> > when the vcpu is an idle one.
> > 
> > Signed-off-by: Dario Faggioli <dario.faggioli@citrix.com>
> 
> Reviewed-by: Juergen Gross <jgross@suse.com>
> 
Thanks. I won't apply this tag to v2 though, as I'm changing the patch
a bit, as a result of Jan's comment.

> ... with or without the remark below addressed.
> 
About this...

> > --- a/xen/common/schedule.c
> > +++ b/xen/common/schedule.c
> > @@ -78,7 +78,19 @@ static struct scheduler __read_mostly ops;
> >            : (typeof((opsptr)->fn(opsptr, ##__VA_ARGS__)))0 )
> >  
> >  #define DOM2OP(_d)    (((_d)->cpupool == NULL) ? &ops : ((_d)-
> > >cpupool->sched))
> > -#define VCPU2OP(_v)   (DOM2OP((_v)->domain))
> > +static inline struct scheduler* VCPU2OP(const struct vcpu *v)
> 
> Rename, e.g. get_scheduler() ?
> 
I indeed like the idea, and will do that. But in another patch (which
I'll include when posting v2). In fact, since I want this to be
backported, I don't want to change too much code around, making future
backports more difficult.

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: 819 bytes --]

[-- Attachment #2: Type: text/plain, Size: 127 bytes --]

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

  reply	other threads:[~2017-03-17 11:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-16 21:30 [PATCH] xen: sched: don't call hooks of the wrong scheduler via VCPU2OP Dario Faggioli
2017-03-17  5:28 ` Juergen Gross
2017-03-17 11:46   ` Dario Faggioli [this message]
2017-03-17  7:42 ` Jan Beulich
2017-03-17 12:22   ` 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=1489751203.15340.1.camel@citrix.com \
    --to=dario.faggioli@citrix.com \
    --cc=george.dunlap@citrix.com \
    --cc=jbeulich@suse.com \
    --cc=jgross@suse.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.