qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Bharata B Rao <bharata@linux.vnet.ibm.com>
Cc: zhugh.fnst@cn.fujitsu.com, ehabkost@redhat.com, agraf@suse.de,
	qemu-devel@nongnu.org, imammedo@redhat.com, afaerber@suse.de
Subject: Re: [Qemu-devel] [PATCH v3 1/3] cpus: Add Error argument to cpu_exec_init()
Date: Mon, 25 May 2015 11:03:31 +1000	[thread overview]
Message-ID: <20150525010331.GD6255@voom.redhat.com> (raw)
In-Reply-To: <1432184528-31252-2-git-send-email-bharata@linux.vnet.ibm.com>

[-- Attachment #1: Type: text/plain, Size: 876 bytes --]

On Thu, May 21, 2015 at 10:32:06AM +0530, Bharata B Rao wrote:
> Add an Error argument to cpu_exec_init() to let users collect the
> error. This is in preparation to change the CPU enumeration logic
> in cpu_exec_init(). With the new enumeration logic, cpu_exec_init()
> can fail if cpu_index values corresponding to max_cpus have already
> been handed out.
> 
> Since all current callers of cpu_exec_init() are from instance_init,
> use error_abort Error arugment to abort in case of an error.
> 
> Signed-off-by: Bharata B Rao <bharata@linux.vnet.ibm.com>
> Reviewed-by: Eduardo Habkost <ehabkost@redhat.com>

Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

  parent reply	other threads:[~2015-05-25  1:38 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-21  5:02 [Qemu-devel] [PATCH v3 0/3] Bitmap based CPU enumeration Bharata B Rao
2015-05-21  5:02 ` [Qemu-devel] [PATCH v3 1/3] cpus: Add Error argument to cpu_exec_init() Bharata B Rao
2015-05-21  8:50   ` Igor Mammedov
2015-05-25  1:03   ` David Gibson [this message]
2015-05-29  5:02   ` Peter Crosthwaite
2015-05-21  5:02 ` [Qemu-devel] [PATCH v3 2/3] cpus: Convert cpu_index into a bitmap Bharata B Rao
2015-05-21  8:58   ` Igor Mammedov
2015-05-25  1:05   ` David Gibson
2015-05-29  5:15   ` Peter Crosthwaite
2015-05-21  5:02 ` [Qemu-devel] [PATCH v3 3/3] ppc: Move cpu_exec_init() call to realize function Bharata B Rao
2015-05-21  5:28   ` Andreas Färber
2015-05-21  5:37     ` Bharata B Rao
2015-05-21  9:05   ` Igor Mammedov
2015-05-21 10:18     ` Bharata B Rao
2015-05-21 11:24       ` Igor Mammedov
2015-05-29  5:17   ` Peter Crosthwaite
2015-05-29  7:33     ` Bharata B Rao
2015-05-29  2:27 ` [Qemu-devel] [PATCH v3 0/3] Bitmap based CPU enumeration Bharata B Rao
2015-05-29  4:59   ` Peter Crosthwaite
2015-06-04  3:08     ` Bharata B Rao
2015-06-04  5:44       ` Peter Crosthwaite
2015-06-04  8:09         ` Paolo Bonzini
2015-06-04  8:39           ` Peter Crosthwaite
2015-06-04  8:51             ` Paolo Bonzini

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=20150525010331.GD6255@voom.redhat.com \
    --to=david@gibson.dropbear.id.au \
    --cc=afaerber@suse.de \
    --cc=agraf@suse.de \
    --cc=bharata@linux.vnet.ibm.com \
    --cc=ehabkost@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=zhugh.fnst@cn.fujitsu.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).