The copy method in sys/cpuset assumes they are the same size, if you have different sizes the non-used bits will not be set to 0 unless the creator explicitly sets them.
> -----Original Message----- > From: ged...@gwmail.gwu.edu [mailto:ged...@gwmail.gwu.edu] On > Behalf Of Gedare Bloom > Sent: Thursday, February 27, 2014 9:11 AM > To: Jennifer Averett > Cc: rtems-devel@rtems.org > Subject: Re: patch for pthread attribute get and set affinity > > Do you need to check if the attr->setsize == cpusetsize in setaffinity? > > Is it ever the case that the cpusetsize > attr->setsize in getaffinity, but > that is > ok? similarly in setaffinity if attr->setsize > > cpusetsize? That is to say, is strict equality between the > cpusetsize and the destination of CPU_COPY required, or can the destination > be larger than the source? > > I did not look at the test. > > -Gedare > > On Thu, Feb 27, 2014 at 8:26 AM, Jennifer Averett > <jennifer.aver...@oarcorp.com> wrote: > > Attached patches are for pthread attribute get and set affinity. As > > well as a test for the new functions > > > > > > Jennifer Averett > > On-Line Applications Research > > _______________________________________________ > > rtems-devel mailing list > > rtems-devel@rtems.org > > http://www.rtems.org/mailman/listinfo/rtems-devel > > _______________________________________________ rtems-devel mailing list rtems-devel@rtems.org http://www.rtems.org/mailman/listinfo/rtems-devel
