All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@citrix.com>
To: "JBeulich@suse.com" <JBeulich@suse.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
	George Dunlap <George.Dunlap@citrix.com>
Subject: Re: [PATCH v2] credit: generalize __vcpu_has_soft_affinity()
Date: Fri, 6 Mar 2015 13:44:44 +0000	[thread overview]
Message-ID: <1425649482.12503.83.camel@citrix.com> (raw)
In-Reply-To: <54F9BA7702000078000670C1@mail.emea.novell.com>


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

On Fri, 2015-03-06 at 13:32 +0000, Jan Beulich wrote:
> >>> On 06.03.15 at 14:23, <dario.faggioli@citrix.com> wrote:
> > Which means that, yes, this part of the condition must loose the '!', or
> > have the arguments of the call to cpumask_subset() switched. I
> > personally prefer the former:
> > 
> >     return !cpumask_subset(cpupool_online_cpumask(vc->domain->cpupool),
> >                            vc->cpu_soft_affinity) &&
> >            cpumask_subset(vc->cpu_soft_affinity, vc->cpu_hard_affinity) &&
> >            cpumask_intersects(vc->cpu_soft_affinity, mask);
> 
> The form without ! and with operands swapped isn't correct afaict,
> since subset(x,y) is not the same as !subset(y,x).
>
I was thinking to loose the '!' and don't swap them, but...

> In particular
> when the two are identical, they are also subsets of one another.
>
... that is true, and is not the only issue the variant I suggested
above would introduce. So forget it, '!' it is. :-)

Dario

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 181 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:[~2015-03-06 13:44 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-06  7:36 [PATCH v2] credit: generalize __vcpu_has_soft_affinity() Jan Beulich
2015-03-06  8:39 ` Dario Faggioli
2015-03-06  9:53 ` George Dunlap
2015-03-06 10:16   ` Jan Beulich
2015-03-06 11:32     ` George Dunlap
2015-03-06 11:44       ` Jan Beulich
2015-03-06 12:00         ` George Dunlap
2015-03-06 13:10           ` Jan Beulich
2015-03-06 13:23           ` Dario Faggioli
2015-03-06 13:32             ` Jan Beulich
2015-03-06 13:44               ` Dario Faggioli [this message]
2015-03-06 11:12   ` Dario Faggioli
2015-03-06 11:38     ` George Dunlap
2015-03-06 13:31       ` Dario Faggioli
2015-03-06 14:57         ` George Dunlap
2015-03-06 15:10           ` 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=1425649482.12503.83.camel@citrix.com \
    --to=dario.faggioli@citrix.com \
    --cc=George.Dunlap@citrix.com \
    --cc=JBeulich@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.