All of lore.kernel.org
 help / color / mirror / Atom feed
From: Masaki Kanno <kanno.masaki@jp.fujitsu.com>
To: xen-devel@lists.xensource.com, ewan@xensource.com
Subject: Re: [PATCH] [Bug 936] Fix "cpus" in config.sxp
Date: Sat, 31 Mar 2007 01:44:20 +0900	[thread overview]
Message-ID: <1DC772EAA9D5D3kanno.masaki@jp.fujitsu.com> (raw)
In-Reply-To: <2C77086827ED1kanno.masaki@jp.fujitsu.com>

Hi Ewan,

Could you apply this patch?
If without it, we must register domains by using the xm new command 
whenever we start xend. 

Or have you already prepared other patch which can solve this issue? 
If so, could you include it in Xen3.0.5?

Best regards,
 Kan

>Hi,
>
>I fixed the Xen bugzilla 936. 
>http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=936
>
>Currently, "cpus" output to config.sxp is the following form.
>Therefore _parse_sxp() cannot convert '[1' to integer. 
>
>  e.g. (cpus '[1, 2]')   --- string
>
>This patch changes output form of "cpus".  The form is as follows. 
>
>  e.g. (cpus (1 2))
>
>However, the bug cannot be solved only by the change.  When xend 
>is started, "cpus" of the SXP configuration passes to _parse_sxp() 
>in the following form. 
>
>  e.g. ['cpus': ['1', '2']]   --- list of string
>
>Therefore this patch adds proceeding of to convert list of string 
>to list of integer for "cpus". 
>
>Signed-off-by: Masaki Kanno <kanno.masaki@jp.fujitsu.com>
>
>Best regards,
> Kan
>
>
>-------------------------------text/plain-------------------------------
>_______________________________________________
>Xen-devel mailing list
>Xen-devel@lists.xensource.com
>http://lists.xensource.com/xen-devel

      reply	other threads:[~2007-03-30 16:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-27 15:42 [PATCH] [Bug 936] Fix "cpus" in config.sxp Masaki Kanno
2007-03-30 16:44 ` Masaki Kanno [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=1DC772EAA9D5D3kanno.masaki@jp.fujitsu.com \
    --to=kanno.masaki@jp.fujitsu.com \
    --cc=ewan@xensource.com \
    --cc=xen-devel@lists.xensource.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.