qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Luiz Capitulino <lcapitulino@redhat.com>
To: Lai Jiangshan <laijs@cn.fujitsu.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: [Qemu-devel] Re: [PATCH v2 1/2] QError: new QERR_INVALID_CPU_INDEX
Date: Fri, 10 Dec 2010 08:58:58 -0200	[thread overview]
Message-ID: <20101210085858.38768d17@doriath> (raw)
In-Reply-To: <4D01CA51.4060603@cn.fujitsu.com>

On Fri, 10 Dec 2010 14:36:01 +0800
Lai Jiangshan <laijs@cn.fujitsu.com> wrote:

> 
> Signed-off-by:  Lai Jiangshan <laijs@cn.fujitsu.com>

As Markus said, we report this as an invalid parameter in do_cpu(), we can do
the same for inject-nmi.

> ---
> diff --git a/qerror.c b/qerror.c
> index ac2cdaf..f59fb58 100644
> --- a/qerror.c
> +++ b/qerror.c
> @@ -117,6 +117,10 @@ static const QErrorStringTable qerror_table[] = {
>          .desc      = "Invalid block format '%(name)'",
>      },
>      {
> +        .error_fmt = QERR_INVALID_CPU_INDEX,
> +        .desc      = "Invalid CPU index '%(cpu_index)'",
> +    },
> +    {
>          .error_fmt = QERR_INVALID_PARAMETER,
>          .desc      = "Invalid parameter '%(name)'",
>      },
> diff --git a/qerror.h b/qerror.h
> index 943a24b..9117dda 100644
> --- a/qerror.h
> +++ b/qerror.h
> @@ -102,6 +102,9 @@ QError *qobject_to_qerror(const QObject *obj);
>  #define QERR_INVALID_BLOCK_FORMAT \
>      "{ 'class': 'InvalidBlockFormat', 'data': { 'name': %s } }"
>  
> +#define QERR_INVALID_CPU_INDEX \
> +    "{ 'class': 'InvalidCPUIndex', 'data': { 'cpu_index': %d } }"
> +
>  #define QERR_INVALID_PARAMETER \
>      "{ 'class': 'InvalidParameter', 'data': { 'name': %s } }"
>  
> 

      reply	other threads:[~2010-12-10 10:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-10  6:36 [Qemu-devel] [PATCH v2 1/2] QError: new QERR_INVALID_CPU_INDEX Lai Jiangshan
2010-12-10 10:58 ` Luiz Capitulino [this message]

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=20101210085858.38768d17@doriath \
    --to=lcapitulino@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=laijs@cn.fujitsu.com \
    --cc=qemu-devel@nongnu.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).