why we need this config?
Recently I've implemented a virtio-net driver which supports the latest features in the specification. The packed option enables a feature called Packed Virtqueue.
and which qemu version that you use @nuta
I'm using 5.0.0. It seems the option is added in this commit: qemu/qemu@74b3e46
just didnt get why it halted because of packed disabled or?
Hmm, that's strange... I think it's not occurred by disabling the packed option.
my config: https://0x0.st/ilS0.txt
Please enable Kernel > Use semihosting features config in make menuconfig. If the option is enabled, the kernel terminates QEMU using a special I/O port.
Hello everyone!
This is Yashraj, a third-year undergraduate student from Ahmedabad University, India. I and my friends came across Resea recently and are looking forward to dedicating 6-weeks of our time to contribute as a part of our course project on Operating Systems.
We went through the documentation and the project board, but we're not able to create a timeline for ourselves for the coming weeks as we're just learning the subject. We're really excited about this and want to make quality contributions to this project.
We'd be really grateful if some regular contributor can show us some direction.
Thanks a lot!
Hello Mr. Seiya,
Thanks a lot for a quick response!
We're looking for things which connect to what we learn in an elementary OS course - process management, scheduling, memory management, virtual memory, threading, interprocess communication etc. We also don't mind shifting a bit out of our comfort zones. We'd possibly want to avoid subjects which are not related to core OS concepts for example, such as networking-related things as of now.
Please let us know how this sounds to you. We're really excited to work with Resea for our project.
Sounds great! Off the top of my head, project ideas for Resea are:
- Improving
mallocimplementation. Currently it uses a very primitive algorithm. We need to implement another smarter algorithm to mitigate fragmentation. - User-level scheduler. In microkernel-based systems, task schedulers are implemented in the user-space using special kernel interfaces. I've implemented
task_schedulesystem call for that purpose, but we haven't yet implemented various scheduling algorithms (in the userspace). See MINIX3's approach for more details.
I'll let you know if I come up with other ideas.
By the way, you might already know but a microkernel-based OS is quite different from monolithic kernel based OS. AFAIK most operating system courses are implicitly based on monolithic ones.
For example, microkernels are based on a philosophy called "separation of mechanism and policy": we avoid adding code to the kernel as much as possible. Instead, we implement operating system features (like high-level process/memory management, process scheduler, referred to as policy) in the userspace. The kernel only provides a simple but flexible features (mechanism) to implement them.
For that reason, I highly recommend surveying microkernel research (e.g. MINIX3, L4) a little. You don't have to understand everything but they would stimulate your curiocity.
Hello @nuta, we have finalized working on resea for our project with our instructor. We have proposed the malloc implementation and zero-copy IPC as the issues that we'd like to tackle.
Also, we're looking forward to try our hands with implementing new features. We saw your project board and we were hooked by some of the ideas like - random number generation and Datetime management server. We're also excited by the idea of writing applications in Rust. As the maintainer and the person behind the thinking, can you please tell us what is in our mind regarding these?
Also, we'll be putting up our thoughts in the issue comments as we go through them. I hope you won't mind assigning them to us once we do so.
malloc() and its pretty daunting