[gem5-users] Re: syscall perf_event_open (#241) unimplemented

2021-09-24 Thread Giacomo Travaglini via gem5-users
Hi

It can be implemented in SE mode, but that would require us to 
implement/emulate perf_events in gem5

Is there a specific reason why you need to use perf_events in SE mode? Have you 
considered gathering statistics
Through the gem5 ops?

Kind Regards

Giacomo

> -Original Message-
> From: walt...@yahoo.com 
> Sent: 23 September 2021 16:45
> To: gem5 users mailing list 
> Cc: Giacomo Travaglini 
> Subject: Re: [gem5-users] Re: syscall perf_event_open (#241)
> unimplemented
>
> Hi Giacomo,
>
>
> Thanks for your reply.
>
> Is there any reason for implementing it in full system simulation only?
>
> Can we implement it in SE mode?
>
> Best regards.
>
> On Thursday, September 23, 2021, 11:04:42 AM GMT+3, Giacomo Travaglini
> via gem5-users  wrote:
>
>
> Hi
>
> It has been fixed for full-system simulation (the patch you are referring to 
> is
> providing visibility of the PMU to the linux kernel), But the syscall in SE 
> mode
> is still un-implemented.
>
> Kind Regards
>
> Giacomo
>
>
>
> > -Original Message-
> > From: walt_90--- via gem5-users  > <mailto:gem5-users@gem5.org> >
> > Sent: 22 September 2021 20:06
> > To: Gem5 Users Mailing List  > <mailto:gem5-users@gem5.org> >
> > Cc: walt...@yahoo.com <mailto:walt...@yahoo.com>
> > Subject: [gem5-users] syscall perf_event_open (#241) unimplemented
> >
> > I got the following error while trying to run a binary with se.py
> >
> > build/ARM/sim/syscall_emul.cc:66: fatal: syscall perf_event_open
> > (#241) unimplemented.
> > Memory Usage: 703864 KBytes
> >
> > I am using the latest version of gem5 on Ubuntu 18.04.
> >
> >
> >
> > I read the related threads titled:
> >
> >
> > [gem5-users] Using perf_event with the ARM PMU inside gem5 on Linux
> >
> > gem5-dev] Change in gem5/gem5[develop]: arch-arm: Implement
> ArmPMU DTB
> > generation
> >
> >
> > According to my understanding to these threads, this problem have been
> > fixed, am I correct?
> >
> > Thanks.
>
> IMPORTANT NOTICE: The contents of this email and any attachments are
> confidential and may also be privileged. If you are not the intended 
> recipient,
> please notify the sender immediately and do not disclose the contents to any
> other person, use it for any purpose, or store or copy the information in any
> medium. Thank you.
> ___
> gem5-users mailing list -- gem5-users@gem5.org <mailto:gem5-
> us...@gem5.org> To unsubscribe send an email to gem5-users-
> le...@gem5.org <mailto:gem5-users-le...@gem5.org>
> %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s

IMPORTANT NOTICE: The contents of this email and any attachments are 
confidential and may also be privileged. If you are not the intended recipient, 
please notify the sender immediately and do not disclose the contents to any 
other person, use it for any purpose, or store or copy the information in any 
medium. Thank you.
___
gem5-users mailing list -- gem5-users@gem5.org
To unsubscribe send an email to gem5-users-le...@gem5.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s


[gem5-users] Re: syscall perf_event_open (#241) unimplemented

2021-09-23 Thread walt_90--- via gem5-users
 HiĀ Giacomo,
Thanks for your reply.
Is there any reason for implementing it in full system simulation only?
Can we implement it in SE mode?
Best regards.
On Thursday, September 23, 2021, 11:04:42 AM GMT+3, Giacomo Travaglini via 
gem5-users  wrote:  
 
 Hi

It has been fixed for full-system simulation (the patch you are referring to is 
providing visibility of the PMU to the linux kernel),
But the syscall in SE mode is still un-implemented.

Kind Regards

Giacomo


> -Original Message-
> From: walt_90--- via gem5-users 
> Sent: 22 September 2021 20:06
> To: Gem5 Users Mailing List 
> Cc: walt...@yahoo.com
> Subject: [gem5-users] syscall perf_event_open (#241) unimplemented
>
> I got the following error while trying to run a binary with se.py
>
> build/ARM/sim/syscall_emul.cc:66: fatal: syscall perf_event_open (#241)
> unimplemented.
> Memory Usage: 703864 KBytes
>
> I am using the latest version of gem5 on Ubuntu 18.04.
>
>
>
> I read the related threads titled:
>
>
> [gem5-users] Using perf_event with the ARM PMU inside gem5 on Linux
>
> gem5-dev] Change in gem5/gem5[develop]: arch-arm: Implement ArmPMU
> DTB generation
>
>
> According to my understanding to these threads, this problem have been
> fixed, am I correct?
>
> Thanks.
IMPORTANT NOTICE: The contents of this email and any attachments are 
confidential and may also be privileged. If you are not the intended recipient, 
please notify the sender immediately and do not disclose the contents to any 
other person, use it for any purpose, or store or copy the information in any 
medium. Thank you.
___
gem5-users mailing list -- gem5-users@gem5.org
To unsubscribe send an email to gem5-users-le...@gem5.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
  ___
gem5-users mailing list -- gem5-users@gem5.org
To unsubscribe send an email to gem5-users-le...@gem5.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s

[gem5-users] Re: syscall perf_event_open (#241) unimplemented

2021-09-23 Thread Giacomo Travaglini via gem5-users
Hi

It has been fixed for full-system simulation (the patch you are referring to is 
providing visibility of the PMU to the linux kernel),
But the syscall in SE mode is still un-implemented.

Kind Regards

Giacomo


> -Original Message-
> From: walt_90--- via gem5-users 
> Sent: 22 September 2021 20:06
> To: Gem5 Users Mailing List 
> Cc: walt...@yahoo.com
> Subject: [gem5-users] syscall perf_event_open (#241) unimplemented
>
> I got the following error while trying to run a binary with se.py
>
> build/ARM/sim/syscall_emul.cc:66: fatal: syscall perf_event_open (#241)
> unimplemented.
> Memory Usage: 703864 KBytes
>
> I am using the latest version of gem5 on Ubuntu 18.04.
>
>
>
> I read the related threads titled:
>
>
> [gem5-users] Using perf_event with the ARM PMU inside gem5 on Linux
>
> gem5-dev] Change in gem5/gem5[develop]: arch-arm: Implement ArmPMU
> DTB generation
>
>
> According to my understanding to these threads, this problem have been
> fixed, am I correct?
>
> Thanks.
IMPORTANT NOTICE: The contents of this email and any attachments are 
confidential and may also be privileged. If you are not the intended recipient, 
please notify the sender immediately and do not disclose the contents to any 
other person, use it for any purpose, or store or copy the information in any 
medium. Thank you.
___
gem5-users mailing list -- gem5-users@gem5.org
To unsubscribe send an email to gem5-users-le...@gem5.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s