From: Tamas K Lengyel <tamas@tklengyel.com>
To: "Roger Pau Monné" <roger.pau@citrix.com>
Cc: Julien Grall <julien@xen.org>,
Stefano Stabellini <sstabellini@kernel.org>,
Tamas K Lengyel <tamas.lengyel@intel.com>, Wei Liu <wl@xen.org>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
George Dunlap <george.dunlap@citrix.com>,
Jan Beulich <jbeulich@suse.com>,
Xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [Xen-devel] [PATCH v12 1/3] xen/mem_sharing: VM forking
Date: Wed, 25 Mar 2020 10:16:42 -0600 [thread overview]
Message-ID: <CABfawhn-YAb8AQfQpPrXiF4+81T+azXrkydVMY2u1beEb+Y1SA@mail.gmail.com> (raw)
In-Reply-To: <20200325154702.GD28601@Air-de-Roger>
> > +static int bring_up_vcpus(struct domain *cd, struct domain *d)
> > +{
> > + unsigned int i;
> > + int ret = -EINVAL;
>
> Nit: you can get rid of ret...
>
> > +
> > + if ( d->max_vcpus != cd->max_vcpus ||
> > + (ret = cpupool_move_domain(cd, d->cpupool)) )
> > + return ret;
>
> ...and just return -EINVAL here. Seeing as it's not used anywhere
> else.
>
It is actually still needed, note that we store the return value of
cpupool_move_domain in it.
Tamas
next prev parent reply other threads:[~2020-03-25 16:18 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-23 17:04 [Xen-devel] [PATCH v12 0/3] VM forking Tamas K Lengyel
2020-03-23 17:04 ` [Xen-devel] [PATCH v12 1/3] xen/mem_sharing: " Tamas K Lengyel
2020-03-25 15:47 ` Roger Pau Monné
2020-03-25 16:04 ` Tamas K Lengyel
2020-03-25 16:16 ` Tamas K Lengyel [this message]
2020-03-25 16:34 ` Tamas K Lengyel
2020-03-25 16:42 ` Julien Grall
2020-03-25 16:47 ` Tamas K Lengyel
2020-03-25 16:51 ` Julien Grall
2020-03-25 17:00 ` Tamas K Lengyel
2020-03-25 17:16 ` Roger Pau Monné
2020-03-25 17:47 ` Tamas K Lengyel
2020-03-25 16:54 ` Roger Pau Monné
2020-03-26 7:02 ` Jan Beulich
2020-03-26 8:42 ` Roger Pau Monné
2020-03-26 7:07 ` Jan Beulich
2020-03-26 9:10 ` Roger Pau Monné
2020-03-26 17:01 ` Tamas K Lengyel
2020-03-26 12:33 ` Jan Beulich
2020-03-26 14:52 ` Tamas K Lengyel
2020-03-23 17:04 ` [Xen-devel] [PATCH v12 2/3] x86/mem_sharing: reset a fork Tamas K Lengyel
2020-03-25 15:52 ` Roger Pau Monné
2020-03-25 15:54 ` Tamas K Lengyel
2020-03-26 10:16 ` Jan Beulich
2020-03-26 14:48 ` Tamas K Lengyel
2020-03-26 14:52 ` Jan Beulich
2020-03-26 14:53 ` Tamas K Lengyel
2020-03-26 23:40 ` Tamas K Lengyel
2020-03-23 17:04 ` [Xen-devel] [PATCH v12 3/3] xen/tools: VM forking toolstack side Tamas K Lengyel
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=CABfawhn-YAb8AQfQpPrXiF4+81T+azXrkydVMY2u1beEb+Y1SA@mail.gmail.com \
--to=tamas@tklengyel.com \
--cc=andrew.cooper3@citrix.com \
--cc=george.dunlap@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--cc=tamas.lengyel@intel.com \
--cc=wl@xen.org \
--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).