All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eduardo Habkost <ehabkost@redhat.com>
To: Bharata B Rao <bharata@linux.vnet.ibm.com>
Cc: zhugh.fnst@cn.fujitsu.com, agraf@suse.de, qemu-devel@nongnu.org,
	imammedo@redhat.com, afaerber@suse.de,
	david@gibson.dropbear.id.au
Subject: Re: [Qemu-devel] [PATCH v2 1/3] cpus: Add Error argument to cpu_exec_init()
Date: Mon, 18 May 2015 15:17:24 -0300	[thread overview]
Message-ID: <20150518181724.GC17796@thinpad.lan.raisama.net> (raw)
In-Reply-To: <1431408986-18323-2-git-send-email-bharata@linux.vnet.ibm.com>

On Tue, May 12, 2015 at 11:06:24AM +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>

-- 
Eduardo

  reply	other threads:[~2015-05-18 18:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-12  5:36 [Qemu-devel] [PATCH v2 0/3] Bitmap based CPU enumeration Bharata B Rao
2015-05-12  5:36 ` [Qemu-devel] [PATCH v2 1/3] cpus: Add Error argument to cpu_exec_init() Bharata B Rao
2015-05-18 18:17   ` Eduardo Habkost [this message]
2015-05-12  5:36 ` [Qemu-devel] [PATCH v2 2/3] cpus: Convert cpu_index into a bitmap Bharata B Rao
2015-05-18 18:36   ` Eduardo Habkost
2015-05-19  6:19     ` Bharata B Rao
2015-05-19 12:14       ` Eduardo Habkost
2015-05-12  5:36 ` [Qemu-devel] [PATCH v2 3/3] ppc: Move cpu_exec_init() call to realize function Bharata B Rao
2015-05-18 19:09 ` [Qemu-devel] [PATCH v2 0/3] Bitmap based CPU enumeration Eduardo Habkost
2015-05-19  5:16   ` Bharata B Rao
2015-05-19 13:04     ` Eduardo Habkost

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=20150518181724.GC17796@thinpad.lan.raisama.net \
    --to=ehabkost@redhat.com \
    --cc=afaerber@suse.de \
    --cc=agraf@suse.de \
    --cc=bharata@linux.vnet.ibm.com \
    --cc=david@gibson.dropbear.id.au \
    --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 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.