|
From: <sv...@va...> - 2013-03-29 09:40:55
|
sewardj 2013-03-29 09:40:48 +0000 (Fri, 29 Mar 2013)
New Revision: 13350
Log:
Enable prctl on ppc64-linux. Fixes #308089.
Modified files:
trunk/coregrind/m_syswrap/syswrap-ppc64-linux.c
Modified: trunk/coregrind/m_syswrap/syswrap-ppc64-linux.c (+1 -1)
===================================================================
--- trunk/coregrind/m_syswrap/syswrap-ppc64-linux.c 2013-03-28 22:52:14 +00:00 (rev 13349)
+++ trunk/coregrind/m_syswrap/syswrap-ppc64-linux.c 2013-03-29 09:40:48 +00:00 (rev 13350)
@@ -882,7 +882,7 @@
LINX_(__NR_setresgid, sys_setresgid), // 169
LINXY(__NR_getresgid, sys_getresgid), // 170
-// _____(__NR_prctl, sys_prctl), // 171
+ LINXY(__NR_prctl, sys_prctl), // 171
PLAX_(__NR_rt_sigreturn, sys_rt_sigreturn), // 172
LINXY(__NR_rt_sigaction, sys_rt_sigaction), // 173
LINXY(__NR_rt_sigprocmask, sys_rt_sigprocmask), // 174
|
|
From: Sebastian F. <seb...@gm...> - 2013-03-29 13:55:19
|
It might be a bit offtopic for this list, but how can someone *test* 64k MMU pages on PPC64 without physical hardware? Does QEMU support PPC64 with 64k pages and valgrind? On Fri, Mar 29, 2013 at 10:40 AM, <sv...@va...> wrote: > sewardj 2013-03-29 09:40:48 +0000 (Fri, 29 Mar 2013) > > New Revision: 13350 > > Log: > Enable prctl on ppc64-linux. Fixes #308089. > > Modified files: > trunk/coregrind/m_syswrap/syswrap-ppc64-linux.c > > > Modified: trunk/coregrind/m_syswrap/syswrap-ppc64-linux.c (+1 -1) > =================================================================== > --- trunk/coregrind/m_syswrap/syswrap-ppc64-linux.c 2013-03-28 22:52:14 +00:00 (rev 13349) > +++ trunk/coregrind/m_syswrap/syswrap-ppc64-linux.c 2013-03-29 09:40:48 +00:00 (rev 13350) > @@ -882,7 +882,7 @@ > LINX_(__NR_setresgid, sys_setresgid), // 169 > > LINXY(__NR_getresgid, sys_getresgid), // 170 > -// _____(__NR_prctl, sys_prctl), // 171 > + LINXY(__NR_prctl, sys_prctl), // 171 > PLAX_(__NR_rt_sigreturn, sys_rt_sigreturn), // 172 > LINXY(__NR_rt_sigaction, sys_rt_sigaction), // 173 > LINXY(__NR_rt_sigprocmask, sys_rt_sigprocmask), // 174 > > > ------------------------------------------------------------------------------ > Own the Future-Intel(R) Level Up Game Demo Contest 2013 > Rise to greatness in Intel's independent game demo contest. Compete > for recognition, cash, and the chance to get your game on Steam. > $5K grand prize plus 10 genre and skill prizes. Submit your demo > by 6/6/13. http://altfarm.mediaplex.com/ad/ck/12124-176961-30367-2 > _______________________________________________ > Valgrind-developers mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-developers |
|
From: Sebastian F. <seb...@gm...> - 2013-04-01 04:14:18
|
On Fri, Mar 29, 2013 at 2:55 PM, Sebastian Feld <seb...@gm...> wrote: > > It might be a bit offtopic for this list, but how can someone *test* > 64k MMU pages on PPC64 without physical hardware? Does QEMU support > PPC64 with 64k pages and valgrind? Anyone? |
|
From: Julian S. <js...@ac...> - 2013-04-01 13:32:36
|
On 03/29/2013 02:55 PM, Sebastian Feld wrote: > It might be a bit offtopic for this list, but how can someone *test* > 64k MMU pages on PPC64 without physical hardware? Does QEMU support > PPC64 with 64k pages and valgrind? I don't know (for both questions). I just committed whatever patch was on this bug and assumed it was correct. I have a PPC970 box, which I think (not sure) can do 64k pages, but I didn't use it to test the patch. J |
|
From: Rick G. <rcg...@ve...> - 2013-04-02 17:00:29
|
Hi, I'm trying to implement support for x86_64 LWP (LightWeight Profiling).
I think I've got the necessary decode content in place, but I'm not sure
about the IR generation.
There are 4 instructions for this group
llwpcb <reg64> - this loads the address specified by <reg64> ==
rax/rcx/... into an internal-to-the-processor bit of state.
I'm pretty sure I need something like:
reg = <from the decode>
IRTemp t1 = newTemp(Ity_I64)
assign(t1, getIReg64(reg))
There are no side effects or guest visible bit of state that are
otherwise affected.
Do I need to emit some other 'close-out-the-statement'/irexit() bits?
Similarly, slwpcb <reg64> stores an address into <reg64> from this
internal-to-the-processor state.
Thanks in advance,
Rick Gorton
|