All of lore.kernel.org
 help / color / mirror / Atom feed
From: "lina.zhao" <lina.zhao@windriver.com>
To: ltp-list@lists.sourceforge.net
Subject: [LTP] [patch]hugeshmat issue
Date: Thu, 12 Aug 2010 16:13:48 +0800	[thread overview]
Message-ID: <4C63AD3C.2090909@windriver.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 300 bytes --]

Hi,

In hugeshmat01 and hugeshmat02, the attach address for shard memory is 
0x90000eee.
For 32bits mips/Linux system, user space is under 0x7FFFFFFF,
0x90000eee is too big. The new address 0x60000eee has been tested
on mips and other arch systems, it hasn't caused a issue yet.

Regards,

Lina Zhao

[-- Attachment #2: hugeshmat-attach-address-change.patch --]
[-- Type: text/x-diff, Size: 1700 bytes --]

From e337a913dbf366f136b31e96d8662f8e111b9d81 Mon Sep 17 00:00:00 2001
From: Lina Zhao <lina.zhao@windriver.com>
Date: Thu, 12 Aug 2010 15:27:53 +0800
Subject: [PATCH] For 32bits mips/Linux system, user space is under 0x7FFFFFFF,
 0x90000eee is too big. The new address 0x60000eee has been tested
 on mips and other arch systems, it hasn't caused a issue yet.

Signed-off-by: Lina Zhao <lina.zhao@windriver.com>
---
 .../kernel/mem/hugetlb/hugeshmat/hugeshmat01.c     |    2 +-
 .../kernel/mem/hugetlb/hugeshmat/hugeshmat02.c     |    2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/testcases/kernel/mem/hugetlb/hugeshmat/hugeshmat01.c b/testcases/kernel/mem/hugetlb/hugeshmat/hugeshmat01.c
index 229b929..7087d26 100644
--- a/testcases/kernel/mem/hugetlb/hugeshmat/hugeshmat01.c
+++ b/testcases/kernel/mem/hugetlb/hugeshmat/hugeshmat01.c
@@ -70,7 +70,7 @@ unsigned long huge_pages_shm_to_be_allocated;
 #if __WORDSIZE==64
 #define UNALIGNED      0x10000000eee
 #else
-#define UNALIGNED      0x90000eee
+#define UNALIGNED      0x60000eee
 #endif
 
 int shm_id_1 = -1;
diff --git a/testcases/kernel/mem/hugetlb/hugeshmat/hugeshmat02.c b/testcases/kernel/mem/hugetlb/hugeshmat/hugeshmat02.c
index 2f56127..428eeab 100644
--- a/testcases/kernel/mem/hugetlb/hugeshmat/hugeshmat02.c
+++ b/testcases/kernel/mem/hugetlb/hugeshmat/hugeshmat02.c
@@ -74,7 +74,7 @@ void	*addr;				/* for result of shmat-call */
 #if __WORDSIZE==64
 #define NADDR   0x10000000eef           /* a 64bit non alligned address value */
 #else
-#define NADDR	0x90000eef		/* a non alligned address value */
+#define NADDR	0x60000eef		/* a non alligned address value */
 #endif
 
 struct test_case_t {
-- 
1.6.3.1


[-- Attachment #3: Type: text/plain, Size: 224 bytes --]

------------------------------------------------------------------------------
This SF.net email is sponsored by 

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev 

[-- Attachment #4: Type: text/plain, Size: 155 bytes --]

_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

             reply	other threads:[~2010-08-12  8:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-12  8:13 lina.zhao [this message]
     [not found] ` <AANLkTin5XdJw7Vwc2NK8trJ2-vaYuC90s6dk9KhodFBu@mail.gmail.com>
     [not found]   ` <4C68F324.30108@windriver.com>
2010-08-16 16:00     ` [LTP] [patch]hugeshmat issue Garrett Cooper

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=4C63AD3C.2090909@windriver.com \
    --to=lina.zhao@windriver.com \
    --cc=ltp-list@lists.sourceforge.net \
    /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.