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

Move 'upgrade' device logic to xenopsd #40

Open
djs55 opened this issue Oct 19, 2014 · 1 comment
Open

Move 'upgrade' device logic to xenopsd #40

djs55 opened this issue Oct 19, 2014 · 1 comment

Comments

@djs55
Copy link
Collaborator

djs55 commented Oct 19, 2014

I believe the upgrade thing is really a policy decision -- we decided which devices we wanted to use in future. I think it's better if the Device_number module focuses on the type:

  • what is a device number
  • how can one be created
  • what properties can one have (in theory, even if not all are currently used)
  • how do they correspond to Xenstore devids

So I think we should move the 'upgrade_device_number' function to the caller in Xenopsd, if possible.

@djs55
Copy link
Collaborator Author

djs55 commented Oct 19, 2014

Furthermore the functions which take an 'hvm: bool' argument should have the argument removed, if we are now treating PV and HVM domains the same.

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

No branches or pull requests

1 participant