Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Joel Sherrill <joel.sherrill@oarcorp.com>
To: teawater <teawater@gmail.com>
Cc: "gdb-patches@sourceware.org" <gdb@sourceware.org>
Subject: Re: Add SystemV IPC drivers to PSIM
Date: Fri, 07 Nov 2008 18:51:00 -0000	[thread overview]
Message-ID: <49148DF5.2060301@oarcorp.com> (raw)
In-Reply-To: <daef60380811051834i614d530aw8afa6eb2d321b66b@mail.gmail.com>

teawater wrote:
> Hi Joel,
>
> I think maybe you need cc this mail to maintainer of ppc sim Andrew
> Cagney <ac131313@redhat.com>.
>
>   
FWIW that bounces.  I found a gnu.org email
address for him and it didn't bounce but I haven't
heard back either. :(

Most of it is boilerplate for adding a device.  Looking
at the ChangeLog, Andrew hasn't done anything
except commit someone else's patch in a few years.
Is anyone other than Andrew capable of reviewing it?

> And porting this patch to gdb-cvs-head 
Coming shortly
> and divide it to some small
> ones are better for other people review it.
>
>   
It can only be divided by two since it adds two device
simulations.  Worse they are somewhat related since the
semaphore is used to protect the shared memory during
accesses.  So all the test code I have uses both.


--joel
> Thanks,
> Hui
>
> On Thu, Nov 6, 2008 at 00:54, Joel Sherrill <joel.sherrill@oarcorp.com> wrote:
>   
>> Hi,
>>
>> This is a repost of the patch was originally submitted 8 Sept.
>>
>> http://sourceware.org/ml/gdb/2008-09/msg00047.html
>>
>> Could someone please review and commit it?
>>
>> Thanks.
>>
>>
>> --joel
>>
>> =====================
>>
>> As the first year in the copyright shows, this code
>> has been around a while. I found a message in the
>> RTEMS archives where I was updating it to gdb 4.17. :)
>>
>>
>>
>>
>> It adds support for System V semaphores and shared memory to psim.
>> It adds two files (hw_sem.c and hw_shm.c) and touches configure.ac
>> to add tests for support of System V IPC.  Please regenerate
>> configure after patching.
>>
>>
>> The shared memory device maps System V shared memory
>> into the simulated PowerPC's address space. This lets
>> the simulated CPU share data with the host environment.
>> This data area can be protected by using the System V
>> semaphore device to lock the memory.
>>
>>
>> We use this to run RTEMS multiprocessor tests where the
>> two simulated CPUs communicate through the shared memory.
>> It has also been used by RTEMS applications to do "device IO"
>> to the shared memory and have a custom system simulator
>> provide feedback.
>>
>>
>> Can someone please review and commit? Thanks.
>>
>> 2008-09-08 Joel Sherrill <joel.sherrill@oarcorp.com>
>>
>>  * configure: Regenerated.
>>  * configure.ac: Add test for System V shared memory and semaphore.
>>  * debug.c, debug.h: Add trace support for new devices.
>>  * hw_sem.c, hw_shm.c: New files.
>>  * Makefile.in: Add hw_sem.c and hw_shm.c
>>
>> --
>> Joel Sherrill, Ph.D.             Director of Research & Development
>> joel.sherrill@OARcorp.com        On-Line Applications Research
>> Ask me about RTEMS: a free RTOS  Huntsville AL 35805
>>  Support Available             (256) 722-9985
>>
>>
>>
>>     


-- 
Joel Sherrill, Ph.D.             Director of Research & Development
joel.sherrill@OARcorp.com        On-Line Applications Research
Ask me about RTEMS: a free RTOS  Huntsville AL 35805
   Support Available             (256) 722-9985



  reply	other threads:[~2008-11-07 18:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-05 16:55 Joel Sherrill
2008-11-06  2:35 ` teawater
2008-11-07 18:51   ` Joel Sherrill [this message]
2008-11-07 19:01     ` Daniel Jacobowitz
2008-11-07 20:58       ` Joel Sherrill
2008-11-08  0:07         ` Doug Evans
2008-11-10 14:42           ` Daniel Jacobowitz
2008-11-12 19:18             ` Doug Evans
2008-11-10 20:28           ` Joel Sherrill
  -- strict thread matches above, loose matches on Subject: below --
2008-09-08 15:45 Joel Sherrill

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=49148DF5.2060301@oarcorp.com \
    --to=joel.sherrill@oarcorp.com \
    --cc=gdb@sourceware.org \
    --cc=teawater@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox