dsg/vhost
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
vmsilo fork of vhost rust libraries
31 commits 1 branch 42 tags 997 KiB
Find a file
Sebastien Boeuf 41f00984bf Allow for one exit_event per thread 
By adding the "thread_index" parameter to the function exit_event() from
the VhostUserBackend trait, the backend crate now has the ability to ask
the backend implementation about the exit event related to a specific
thread.

Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2020-11-25 17:01:17 +01:00
src Allow for one exit_event per thread 2020-11-25 17:01:17 +01:00
.gitmodules Initial commit 2020-09-17 13:51:21 +03:00
Cargo.toml Initial commit 2020-09-17 13:51:21 +03:00
CODEOWNERS Initial commit 2020-09-17 13:51:21 +03:00
coverage_config.json Initial commit 2020-09-17 13:51:21 +03:00
LICENSE-APACHE Initial commit 2020-09-17 13:51:21 +03:00
README.md Initial commit 2020-09-17 13:51:21 +03:00

README.md

Crate Name

Design

TODO: This section should have a high-level design of the crate.

Some questions that might help in writing this section:

  • What is the purpose of this crate?
  • What are the main components of the crate? How do they interact which each other?

Usage

TODO: This section describes how the crate is used.

Some questions that might help in writing this section:

  • What traits do users need to implement?
  • Does the crate have any default/optional features? What is each feature doing?
  • Is this crate used by other rust-vmm components? If yes, how?

Examples

TODO: Usage examples.

use my_crate;

...

License

!!!NOTICE: The BSD-3-Clause license is not included in this template. The license needs to be manually added because the text of the license file also includes the copyright. The copyright can be different for different crates. If the crate contains code from CrosVM, the crate must add the CrosVM copyright which can be found here. For crates developed from scratch, the copyright is different and depends on the contributors.