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

review cfg down_cores, down_chips, down_links #247

Open
Christian-B opened this issue Mar 13, 2024 · 1 comment
Open

review cfg down_cores, down_chips, down_links #247

Christian-B opened this issue Mar 13, 2024 · 1 comment

Comments

@Christian-B
Copy link
Member

Questions.

  1. Do we still want to support this functionality?
  2. In down_cores do we continue to support both physical, virtual downs, both or neither

If we want to continue to support physical down core we will have to.
a. Pass this down into Chip and not guess the virtual one
b. Support Spin2 2D processor addresses

If support virtual down cores why?

@rowleya
Copy link
Member

rowleya commented Mar 15, 2024

Doing this can be useful when you can't update the blacklist on a real machine. It can also be useful when you have a real machine but can't access it right now, but still want to work on other things e.g. placement or routing, and then it is useful to be able to copy a real machine (hence also support in virtual machine).

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

2 participants