linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Anshuman Khandual <khandual@linux.vnet.ibm.com>
To: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Cc: mikey@neuling.org, shuahkh@osg.samsung.com
Subject: Re: [PATCH V3 00/13] POWER DSCR fixes, improvements, docs and tests
Date: Tue, 12 May 2015 11:31:55 +0530	[thread overview]
Message-ID: <55519753.4020807@linux.vnet.ibm.com> (raw)
In-Reply-To: <1428654612-23539-1-git-send-email-khandual@linux.vnet.ibm.com>

On 04/10/2015 01:59 PM, Anshuman Khandual wrote:
> 	This patch series has patches for POWER DSCR fixes, improvements,
> in code documentaion, kernel support user documentation and selftest based
> test cases. It has got five test cases which are derived from Anton's DSCR
> test bucket which can be listed as follows.
> 
> (1) http://ozlabs.org/~anton/junkcode/dscr_default_test.c
> (2) http://ozlabs.org/~anton/junkcode/dscr_explicit_test.c
> (3) http://ozlabs.org/~anton/junkcode/dscr_inherit_exec_test.c
> (4) http://ozlabs.org/~anton/junkcode/dscr_inherit_test.c
> (5) http://ozlabs.org/~anton/junkcode/user_dscr_test.c
> 
> So the derivied test cases have Anton's copyright along with mine but the
> commit message as of now has only my signed-off-by statement. As Anton
> mentioned before he would put his signed-off-by after reviewing these
> modified test cases.
> 
> NOTE1: Anton's original inherit exec test expected the child to have system
> default DSCR value instead of the inherited DSCR value from it's parent.
> But looks like thats not the case when we execute the test, it always
> inherits it's parent's DSCR value over the exec call as well. So I have
> changed the test program assuming its correct to have the inherited DSCR
> value in the fork/execed child program. Please let me know if thats not
> correct and I am missing something there.
> 
> Changes in V3:
> -------------
> - Minor changes to last couple of sysfs test cases
> - Added .gitignore file for the new test directory

Hey Michael/Ben/Mikey,

Do you have any thoughts or updates on this patch series. Its already
been a month for this latest version to be on the list.

      parent reply	other threads:[~2015-05-12  6:02 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-10  8:29 [PATCH V3 00/13] POWER DSCR fixes, improvements, docs and tests Anshuman Khandual
2015-04-10  8:30 ` [PATCH V3 01/13] powerpc: Fix handling of DSCR related facility unavailable exception Anshuman Khandual
2015-04-10  8:30 ` [PATCH V3 02/13] powerpc, process: Remove the unused extern dscr_default Anshuman Khandual
2015-04-10  8:30 ` [PATCH V3 03/13] powerpc, offset: Change PACA_DSCR to PACA_DSCR_DEFAULT Anshuman Khandual
2015-04-10  8:30 ` [PATCH V3 04/13] powerpc, dscr: Added some in-code documentation Anshuman Khandual
2015-04-10  8:30 ` [PATCH V3 05/13] documentation, powerpc: Add documentation for DSCR support Anshuman Khandual
2015-04-10  8:30 ` [PATCH V3 06/13] selftests, powerpc: Add test for system wide DSCR default Anshuman Khandual
2015-04-10  8:30 ` [PATCH V3 07/13] selftests, powerpc: Add test for explicitly changing DSCR value Anshuman Khandual
2015-04-10  8:30 ` [PATCH V3 08/13] selftests, powerpc: Add test for DSCR SPR numbers Anshuman Khandual
2015-04-10  8:30 ` [PATCH V3 09/13] selftests, powerpc: Add test for DSCR value inheritence across fork Anshuman Khandual
2015-05-18  5:09   ` Anton Blanchard
2015-05-18 10:48     ` Anshuman Khandual
2015-04-10  8:30 ` [PATCH V3 10/13] selftests, powerpc: Add test for DSCR inheritence across fork & exec Anshuman Khandual
2015-04-10  8:30 ` [PATCH V3 11/13] selftests, powerpc: Add test for all DSCR sysfs interfaces Anshuman Khandual
2015-04-10  8:30 ` [PATCH V3 12/13] selftests, powerpc: Add thread based stress test for " Anshuman Khandual
2015-04-10  8:30 ` [PATCH V3 13/13] selftests, powerpc: Add gitignore file for the new DSCR tests Anshuman Khandual
2015-05-12  6:01 ` Anshuman Khandual [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=55519753.4020807@linux.vnet.ibm.com \
    --to=khandual@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mikey@neuling.org \
    --cc=shuahkh@osg.samsung.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 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).