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

Allocate MMIO ranges & GSIs #136

Open
andreeaflorescu opened this issue May 25, 2021 · 2 comments
Open

Allocate MMIO ranges & GSIs #136

andreeaflorescu opened this issue May 25, 2021 · 2 comments
Labels

Comments

@andreeaflorescu
Copy link
Member

Implement an abstraction for generating unique MMIO configurations (address ranges and interrupt numbers).

At the moment the vmm-reference only supports configuring one block device and one network device on the MMIO bus. Each of these devices have a predefined interrupt number and MMIO range assigned. As we add the RTC & Serial Console devices on the MMIO bus (for the aarch64 support) handling these in a static way becomes challenging. The legacy devices are typically using a fixed GSI for interrupts (i.e. serial port 1 uses GSI 4), and the static initialization is not allowing us to extend the vmm-reference to have more than one device type.

There were some discussions at some point to implement a SystemAllocator in rust-vmm. We should see what is the best way of upstreaming this functionality such that it can be reused by multiple VMMs. As a starting point, we can provide a POC in vmm-reference, and in parallel propose a new crate (or update vm-device).

The system allocator is also needed for adding PCI support.

(This issue should be moved to where we are going to implement the vm-allocator).

@andreeaflorescu andreeaflorescu moved this to Todo in GSoC 2022 Jun 27, 2022
@ramyak-mehra ramyak-mehra moved this from Todo to Next Items in GSoC 2022 Jul 25, 2022
@ramyak-mehra ramyak-mehra moved this from Next Items to In Progress in GSoC 2022 Aug 1, 2022
@ramyak-mehra ramyak-mehra moved this from In Progress to Review in GSoC 2022 Aug 23, 2022
@ramyak-mehra ramyak-mehra moved this from Review to Done in GSoC 2022 Sep 12, 2022
@AlexandruCihodaru
Copy link

What about integrating vm-allocator?

@andreeaflorescu
Copy link
Member Author

What about integrating vm-allocator?

I think this is the right path forward, this issue was created before we implemented the vm-allocator crate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Done
Development

No branches or pull requests

2 participants