From: yangzi <wei.yang@windriver.com>
To: Garrett Cooper <yanegomi@gmail.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH] Probe an bigger linear available address to attachment.
Date: Wed, 01 Sep 2010 15:03:07 +0800 [thread overview]
Message-ID: <4C7DFAAB.9060704@windriver.com> (raw)
In-Reply-To: <AANLkTimHJjRYxkLSgr3kBQHD5Lu3=zwx0YR4PGX3KR01@mail.gmail.com>
Hi
It failed on the first sub-testcase and on the mips architecture.
Thanks
wei.yang
Garrett Cooper wrote:
> 2010/8/31 Yang, Wei <Wei.Yang@windriver.com>:
>> Hi
>>
>> When running shmat01 on some platforms, it fails on
>> "addr = shmat(*(tc.shmid), base_addr + tc.offset,tc.flags);"
>> with a INVAL error. Look at codes in "setup()", it probes
>> an available address and align the address to SHMLBA. After
>> alignment, the new address is no guarantee to be available
>> any more. Here a bigger size is used to probe so that it's
>> still valid address after alignment.Pertaining to the function
>> setup_tc(lc, &tc) ,when it outside of "for (i = 0; i < TST_TOTAL;
>> i++)",and printf the tc.offset value is always 0,add correct a mistake
>> of original codes to move "setup_tc()" to right place.
>
> Which of the sub-testcases fail and on which architecture(s)?
> Thanks,
> -Garrett
------------------------------------------------------------------------------
This SF.net Dev2Dev email is sponsored by:
Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2010-09-01 6:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-31 10:33 [LTP] [PATCH] Probe an bigger linear available address to attachment yangzi
2010-08-31 10:36 ` Yang, Wei
2010-09-01 6:30 ` Garrett Cooper
2010-09-01 7:03 ` yangzi [this message]
2010-09-06 16:16 ` Subrata Modak
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=4C7DFAAB.9060704@windriver.com \
--to=wei.yang@windriver.com \
--cc=ltp-list@lists.sourceforge.net \
--cc=yanegomi@gmail.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.