Jump to content

ANKUR SAINI

Members
  • Content Count

    17
  • Joined

  • Last visited

About ANKUR SAINI

  • Rank
    Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. ANKUR SAINI

    How SystemC kernel is implemented !!

    @Roman Popov: Thanks for the information.. Appreciate that.. I got your point that SystemC is basically running as single thread only on my OS. But how exactly SystemC threads are modeled then ? Also, what is the significance of sc_simcontext() in SystemC. What it means by having multiple contexts in a simulation. I know I am little confused with all these terms, but that's why I need some clarification on these..
  2. I have recently going through an online document centered on - "multi-threading of SystemC scheduler". Though I couldn't able to figure out the topic itself for initial time, but definitely it raised up lot of curiosity inside me to read it. While reading, there was a statement - "Single threaded simulation kernel inherent to SystemC prevents it from utilizing the computing power of multi-CPU machines to speed up the simulation." I would like to understand what it means by single threaded simulation kernel.
  3. ANKUR SAINI

    Need understanding of SystemC model use-cases

    @Eyck: Thanks for such a detailed info. This definitely has given a lot of insights. And I am really excited now to look at the pointer you mentioned above. I have ran through it and looks like this doc is really highlighting the important aspects of Virtual Platforms and their usage and applications. Once again thanks for sparing out time and sharing this knowledge.
  4. As we know, SystemC can be used to create system level models @ different abstraction levels. It could be either used for Architectural analysis, performance modeling or software development purposes. I would like to understand and want to get an insight on - what are the key differences while modeling these different models @ different levels. In what ways or context they differ !
  5. ANKUR SAINI

    Debugging Multi threaded program in SystemC

    @AmeyaVS: Thanks for pointing out the document pointers. I will try to go through them. @David Black: Thanks for your detailed comment. I got your point on context switching with both sc_method and sc_thread and in either case it is unavoidable. But still, I think the best practice is to use sc_method wherever possible because that will definitely gonna aid us in debugging. As it gets executes in one shot, no suspend in between.
  6. I have been working on maintaining IP's that are written quite old (Legacy :-)). Most of the code use SC_THREAD extensively. I know that it's not a good practice to use sc_thread and we should minimize it's use wherever possible to avoid context-switching. But I would like to know what are the debugging techniques that can help in debug these multi threaded programs efficiently. As sometimes it's a nightmare to identify issues in a program surrounded by tons of threads running parallely. Regards, Ankur Saini
  7. ANKUR SAINI

    SystemC 2.3.2 installation error

    Hello Roman, I have performed few other simulations as well using SystemC 2.0 build with this GCC version itself on my same platform. So, I guess there shouldn't be any issue with compiler. Regards, Ankur Saini
  8. ANKUR SAINI

    SystemC 2.3.2 installation error

    Hello Ameya, Thanks for your prompt response. But I don't have cmake setup on my system. I have 'make' and 'gmake' build system. My GCC version is 4.3.5. Can you help me in the installation with this setup. Regards, Ankur Saini
  9. I am trying to install systemc 2.3.2 on my linux system (x86_64).I followed the steps mentioned here (http://rkrara.blogspot.in/2012/12/install-systemc-230-on-linux.html) But I am getting the errors while running make command. (PFA the error log) Please help me with the installation. make.log
  10. @David Black: Hello David.. Nice solution.. just one comment.. as you mentioned the usage of callbacks -"before_end_of_elaboration" and "end_of_elaboration", I guess we can use the "start_of_simulation" and "end_of_simulation" also to do the same stuff you written in the code above. Correct me if I am wrong anywhere.
  11. ANKUR SAINI

    before_end_of_elaboration callback

    If I am right, with SystemC 2.x onwards, it gave us a flexibility to still leave the ports unbound if they are defined with SC_ZERO_OR_MORE_BOUND binding policy. Correct me in-case I am wrong.
  12. ANKUR SAINI

    before_end_of_elaboration callback

    @maehne: I got your point to some extent. So that means this callback is just provided to bind/create additional hierarchy which is not part of the actual design but rather helpful for debugging and understanding !! Apart from this is there any other use-case of this callback which you think is worth explaining its existence inside the standard (Just to get little insight)
  13. ANKUR SAINI

    before_end_of_elaboration callback

    @Philipp A Hartmann: I really want to know the significance of "before_end_of_elaboration" callback in SystemC. On Doulos website (https://www.doulos.com/knowhow/systemc/new_standard/), it is mentioned that it can be used in the scenarios where we bind the module monitor ports to the top level singleton monitor channel. Referring to the attached example, why are we not binding the module monitor ports to the top level monitor channel in the top level constructor ? Why the binding of ports is done in the particular module callback function ? Also, what is the need of providing an additional callback function to instantiate module/ports when we can do the same thing in the constructor itself ?
  14. ANKUR SAINI

    How exactly sc_main works !!

    @Philipp A Hartmann: Thanks for the short summary. It really gave me a good understanding from the top level.
  15. ANKUR SAINI

    How exactly sc_main works !!

    How "sc_main" works in SystemC ? I mean what I understood from library is that - there is a main function defined in library which calls the sc_elab_and_sim which in turns calls the sc_main function. But my question is SystemC library is distributed as source which user builds at his end; and links to his application. And if SystemC has main inside it then it should have got compiled into exe! Am I right ? Can somebody help me in understanding this flow ?
×