Re: [Xen-devel] potential bug in "xm atropos" implementation

[Christian Limpach <Christian.Limpach@xxxxxxxxxxxx>]

On Mon, Oct 18, 2004 at 04:30:48PM -0700, Diwaker Gupta wrote:
> > No, the 6th argument you see in the xc_atropos_domain_set function
> > signature (i.e. the function's 1st argument -- xc_handle) is added
> > in the Pyhton<->xc interface function pyxc_atropos_domain_set
> > (in tools/python/xen/lowlevel/xc/xc.c).
> 
> I see. Basically I was running into this problem:

ah I see, now your patch makes sense ;-)  args[2:5] does (confusingly)
not include the 5th element and len (of course) counts from 0.  The 6th
argument which xend_domain_cpu_atropos_set expects (its 1st) is not
the 1st argument for xc_atropos_domain_set though...

I've applied your patch...  Thanks!

    christian



-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel