Upstreaming of the Elbrus2000 architecture support

Upstreaming of the Elbrus2000 architecture support

[Gleb Popov]

Hello QEMU devs.

MCST, a company behind the Elbrus2000 (e2k) architecture has
open-sourced their QEMU fork that features e2k support [1]. I
volunteered to help them get their work merged upstream. I realize
that it might take a decent amount of time and labor, but I'm fully
committed to this. On the MCST part they dispatched a developer team
(CCed) to help in reviewing, answer questions and provide future code
maintenance once it gets merged.

So, if the whole idea sounds interesting to the QEMU community, what
would be our first steps?

[1] https://git.openelbrus.ru/mcst/qemu

Re: Upstreaming of the Elbrus2000 architecture support

[Alex Bennée]

Gleb Popov <arrowd@freebsd.org> writes:

> Hello QEMU devs.
>
> MCST, a company behind the Elbrus2000 (e2k) architecture has
> open-sourced their QEMU fork that features e2k support [1]. I
> volunteered to help them get their work merged upstream. I realize
> that it might take a decent amount of time and labor, but I'm fully
> committed to this. On the MCST part they dispatched a developer team
> (CCed) to help in reviewing, answer questions and provide future code
> maintenance once it gets merged.
>
> So, if the whole idea sounds interesting to the QEMU community, what
> would be our first steps?

I think your first problem is finding people that can review and merge
the code. As MCST is on the sanctions list a potentially large section
of the regular contributors can't be involved in code review.

You may find a maintainer willing to process the PRs after they have
been reviewed but IANAL so check with your own counsel. It would be
worth making sure you have a plan before investing a lot of work into
re-basing and posting. 

>
> [1] https://git.openelbrus.ru/mcst/qemu

-- 
Alex Bennée
Virtualisation Tech Lead @ Linaro