Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Session 9 Report #10

Open
7 tasks
far2000 opened this issue Dec 27, 2024 · 0 comments
Open
7 tasks

Session 9 Report #10

far2000 opened this issue Dec 27, 2024 · 0 comments
Labels
documentation Improvements or additions to documentation

Comments

@far2000
Copy link

far2000 commented Dec 27, 2024

Team Name: [FILL HERE]

Student Name of member 1: Amirhossein Farahani
Student No. of member 1: 97106154

Student Name of member 2: Saba Molaei
Student No. of member 2: 99100947

  • Read Session Contents.

Section 9.3

  • I can't understand the question, so I upload screenshot from code:
image
  • Printing all linux interrupts
    • I found the Linux interrupt file according to the available manual and then read it line by line. Then, by running this executable file in C language, I displayed all the interrupts available in the operating system in the output.

    • This is the output after executing code

image
  • Requirements (I can't understand it exactly, but I answer it in general)
  1.   access to /proc/interrupts
    
  2.   gcc
    
  3.   access to execute code
    

Section 9.4

image I used this code to make some interrupts by using softirq, but I got an error after trying to makefile. I can't debug it but I guess in Debian 12 (my version of Debian) I can't access interrupts headers. description: the first function defines a custom SoftIRQ handler (`my_softirq_handler`) to process the SoftIRQ when raised. The module initializes the SoftIRQ during loading (`my_softirq_init`) using `open_softirq`, raises it with `raise_softirq`, and cleans up the resources during module unloading (`my_softirq_exit`). also I should mention that, we can't call this interrupt with user level program. this interrupt only manage by kernel.
  • Adding a new interrupt - in this section i use another method to simulate interrupt with assembly.
image
- [ ] `I Just use svc for calling an interrupt`
- [ ] `FILL HERE with screenshot of execution`
image
- [ ] `Requirements: just like the previous section`
@far2000 far2000 added the documentation Improvements or additions to documentation label Dec 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

1 participant