* [Qemu-devel] GSOC 2011 @ 2011-02-17 0:32 yajin 2011-02-20 13:08 ` [Qemu-devel] " Aurelien Jarno 0 siblings, 1 reply; 6+ messages in thread From: yajin @ 2011-02-17 0:32 UTC (permalink / raw) To: qemu-devel, Aurelien Jarno, lcapitulino Hi all, I have proposed an idea of GSOC 2011 about adding KVM support to MIPS architecture. I have solid experience on MIPS architecture and familiar with qemu. I am very interested in this project. According to the GSOC, there should be a mentor to each participating project. Is there anyone interested to be the mentor of this project? I would be honored to work with you. Thanks & Regards -- yajin ^ permalink raw reply [flat|nested] 6+ messages in thread
* [Qemu-devel] Re: GSOC 2011 2011-02-17 0:32 [Qemu-devel] GSOC 2011 yajin @ 2011-02-20 13:08 ` Aurelien Jarno 2011-02-20 14:16 ` [Qemu-devel] Re: GSOC 2011 (KVM for MIPS) Jan Kiszka 2011-02-20 20:10 ` [Qemu-devel] Re: GSOC 2011 yajin 0 siblings, 2 replies; 6+ messages in thread From: Aurelien Jarno @ 2011-02-20 13:08 UTC (permalink / raw) To: yajin; +Cc: qemu-devel, lcapitulino On Wed, Feb 16, 2011 at 07:32:31PM -0500, yajin wrote: > Hi all, Hi, > I have proposed an idea of GSOC 2011 about adding KVM support to MIPS > architecture. I have solid experience on MIPS architecture and > familiar with qemu. I am very interested in this project. Having KVM support for MIPS would be really great. AFAIK there is not hardware virtualization support on MIPS (except if you plan to use the supervisor mode for that), so how do you plan to proceed here? Executing everything in user mode and emulating the trapped instructions? MIPS is using a split address space depending on the mode, so that may not be that easy. All of that to say it would be nice to have a more detailed description about such a GSOC, describing the your exact plans with a rough timeline. This is especially true, given that adding support for a new architecture in KVM seems to be a huge task for a GSOC. The best is probably to fill a new entry on the wiki, at this address: http://wiki.qemu.org/Google_Summer_of_Code_2011 > According to the GSOC, there should be a mentor to each participating > project. Is there anyone interested to be the mentor of this project? > I would be honored to work with you. I know almost nothing about KVM, so if we go for a GSOC about adding KVM support to MIPS, it would be nice to have another mentor who have a good knowledge about KVM. I am pretty fine with the MIPS part though. Aurelien -- Aurelien Jarno GPG: 1024D/F1BCDB73 aurelien@aurel32.net http://www.aurel32.net ^ permalink raw reply [flat|nested] 6+ messages in thread
* [Qemu-devel] Re: GSOC 2011 (KVM for MIPS) 2011-02-20 13:08 ` [Qemu-devel] " Aurelien Jarno @ 2011-02-20 14:16 ` Jan Kiszka 2011-02-21 1:09 ` yajin 2011-02-20 20:10 ` [Qemu-devel] Re: GSOC 2011 yajin 1 sibling, 1 reply; 6+ messages in thread From: Jan Kiszka @ 2011-02-20 14:16 UTC (permalink / raw) To: Aurelien Jarno; +Cc: lcapitulino, qemu-devel, kvm, yajin [-- Attachment #1: Type: text/plain, Size: 1314 bytes --] On 2011-02-20 14:08, Aurelien Jarno wrote: > On Wed, Feb 16, 2011 at 07:32:31PM -0500, yajin wrote: >> Hi all, > > Hi, > >> I have proposed an idea of GSOC 2011 about adding KVM support to MIPS >> architecture. I have solid experience on MIPS architecture and >> familiar with qemu. I am very interested in this project. > > Having KVM support for MIPS would be really great. AFAIK there is not > hardware virtualization support on MIPS (except if you plan to use the > supervisor mode for that), so how do you plan to proceed here? Executing > everything in user mode and emulating the trapped instructions? MIPS is > using a split address space depending on the mode, so that may not be > that easy. > > All of that to say it would be nice to have a more detailed description > about such a GSOC, describing the your exact plans with a rough > timeline. This is especially true, given that adding support for a new > architecture in KVM seems to be a huge task for a GSOC. MontaVista has KVM for MIPS on their product slides [1]. Maybe someone has a good contact to them and can poke for more details. They probably won't offer it for direct download but need to distribute it to their customers as open source anyway. Jan [1] http://www.mvista.com/product_detail_cge.php [-- Attachment #2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 259 bytes --] ^ permalink raw reply [flat|nested] 6+ messages in thread
* [Qemu-devel] Re: GSOC 2011 (KVM for MIPS) 2011-02-20 14:16 ` [Qemu-devel] Re: GSOC 2011 (KVM for MIPS) Jan Kiszka @ 2011-02-21 1:09 ` yajin 2011-02-21 8:43 ` Jan Kiszka 0 siblings, 1 reply; 6+ messages in thread From: yajin @ 2011-02-21 1:09 UTC (permalink / raw) To: Jan Kiszka; +Cc: kvm, qemu-devel, Aurelien Jarno, lcapitulino On Sun, Feb 20, 2011 at 9:16 AM, Jan Kiszka <jan.kiszka@web.de> wrote: > On 2011-02-20 14:08, Aurelien Jarno wrote: >> On Wed, Feb 16, 2011 at 07:32:31PM -0500, yajin wrote: >>> Hi all, >> >> Hi, >> >>> I have proposed an idea of GSOC 2011 about adding KVM support to MIPS >>> architecture. I have solid experience on MIPS architecture and >>> familiar with qemu. I am very interested in this project. >> >> Having KVM support for MIPS would be really great. AFAIK there is not >> hardware virtualization support on MIPS (except if you plan to use the >> supervisor mode for that), so how do you plan to proceed here? Executing >> everything in user mode and emulating the trapped instructions? MIPS is >> using a split address space depending on the mode, so that may not be >> that easy. >> >> All of that to say it would be nice to have a more detailed description >> about such a GSOC, describing the your exact plans with a rough >> timeline. This is especially true, given that adding support for a new >> architecture in KVM seems to be a huge task for a GSOC. > > MontaVista has KVM for MIPS on their product slides [1]. Maybe someone > has a good contact to them and can poke for more details. They probably > won't offer it for direct download but need to distribute it to their > customers as open source anyway. > Hi Jan, Thanks very much for your information. I am not sure how they distribute their source code. Anyone knows about that? Jan, would you like to be one of the mentors of this project? Your experience of KVM would be very helpful. Thanks --- yajin ^ permalink raw reply [flat|nested] 6+ messages in thread
* [Qemu-devel] Re: GSOC 2011 (KVM for MIPS) 2011-02-21 1:09 ` yajin @ 2011-02-21 8:43 ` Jan Kiszka 0 siblings, 0 replies; 6+ messages in thread From: Jan Kiszka @ 2011-02-21 8:43 UTC (permalink / raw) To: yajin; +Cc: kvm, qemu-devel, Aurelien Jarno, lcapitulino [-- Attachment #1: Type: text/plain, Size: 1926 bytes --] On 2011-02-21 02:09, yajin wrote: > On Sun, Feb 20, 2011 at 9:16 AM, Jan Kiszka <jan.kiszka@web.de> wrote: >> On 2011-02-20 14:08, Aurelien Jarno wrote: >>> On Wed, Feb 16, 2011 at 07:32:31PM -0500, yajin wrote: >>>> Hi all, >>> >>> Hi, >>> >>>> I have proposed an idea of GSOC 2011 about adding KVM support to MIPS >>>> architecture. I have solid experience on MIPS architecture and >>>> familiar with qemu. I am very interested in this project. >>> >>> Having KVM support for MIPS would be really great. AFAIK there is not >>> hardware virtualization support on MIPS (except if you plan to use the >>> supervisor mode for that), so how do you plan to proceed here? Executing >>> everything in user mode and emulating the trapped instructions? MIPS is >>> using a split address space depending on the mode, so that may not be >>> that easy. >>> >>> All of that to say it would be nice to have a more detailed description >>> about such a GSOC, describing the your exact plans with a rough >>> timeline. This is especially true, given that adding support for a new >>> architecture in KVM seems to be a huge task for a GSOC. >> >> MontaVista has KVM for MIPS on their product slides [1]. Maybe someone >> has a good contact to them and can poke for more details. They probably >> won't offer it for direct download but need to distribute it to their >> customers as open source anyway. >> > > Hi Jan, > > Thanks very much for your information. I am not sure how they > distribute their source code. Anyone knows about that? > > Jan, would you like to be one of the mentors of this project? Your > experience of KVM would be very helpful. Thanks Your project is really interesting. But given that my bandwidth is limited and I've already a different project proposal filed, I can't commit myself to this yet. I may serve as a backup mentor, but no promises at this point. Jan [-- Attachment #2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 259 bytes --] ^ permalink raw reply [flat|nested] 6+ messages in thread
* [Qemu-devel] Re: GSOC 2011 2011-02-20 13:08 ` [Qemu-devel] " Aurelien Jarno 2011-02-20 14:16 ` [Qemu-devel] Re: GSOC 2011 (KVM for MIPS) Jan Kiszka @ 2011-02-20 20:10 ` yajin 1 sibling, 0 replies; 6+ messages in thread From: yajin @ 2011-02-20 20:10 UTC (permalink / raw) To: Aurelien Jarno; +Cc: qemu-devel, lcapitulino > On Wed, Feb 16, 2011 at 07:32:31PM -0500, yajin wrote: >> Hi all, > > Hi, > >> I have proposed an idea of GSOC 2011 about adding KVM support to MIPS >> architecture. I have solid experience on MIPS architecture and >> familiar with qemu. I am very interested in this project. > > Having KVM support for MIPS would be really great. AFAIK there is not > hardware virtualization support on MIPS (except if you plan to use the > supervisor mode for that), so how do you plan to proceed here? Executing > everything in user mode and emulating the trapped instructions? MIPS is > using a split address space depending on the mode, so that may not be > that easy. Hi Aurelien, thanks for your reply. You are right. MIPS does NOT have hardware virtualization support currently. And I do not want to use the supervisor thing because this mode has been deprecated. Supervisor mode is now optional according to MIPS32 documents. So for the privilege instructions, the trap-emulation is the easy way although the performance may be not good. We may improve the performance after make this work. MIPS has an unique feature(or problem for virtualization) is that the MMU is bypassed by kseg0(and kseg1), in which the kernel code is residing. There are two possible solutions to this problem. The first one is we can trap all the access of kseg0 to VMM. The second one is to remap the guest kernel to other segment. This first one is transparent to guest kernel. However it will cause tremendous performance lost since the access of kseg0 is very common. The second one needs to make a little changes to the link script of guest linux kernel. > > All of that to say it would be nice to have a more detailed description > about such a GSOC, describing the your exact plans with a rough > timeline. This is especially true, given that adding support for a new > architecture in KVM seems to be a huge task for a GSOC. > > The best is probably to fill a new entry on the wiki, at this address: > > http://wiki.qemu.org/Google_Summer_of_Code_2011 I will make an entry on the wiki and keep it update. > >> According to the GSOC, there should be a mentor to each participating >> project. Is there anyone interested to be the mentor of this project? >> I would be honored to work with you. > > I know almost nothing about KVM, so if we go for a GSOC about adding KVM > support to MIPS, it would be nice to have another mentor who have a good > knowledge about KVM. I am pretty fine with the MIPS part though. > Thanks very much. Hope we can work together and make it happen. ----- yajin ^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2011-02-21 8:43 UTC | newest] Thread overview: 6+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2011-02-17 0:32 [Qemu-devel] GSOC 2011 yajin 2011-02-20 13:08 ` [Qemu-devel] " Aurelien Jarno 2011-02-20 14:16 ` [Qemu-devel] Re: GSOC 2011 (KVM for MIPS) Jan Kiszka 2011-02-21 1:09 ` yajin 2011-02-21 8:43 ` Jan Kiszka 2011-02-20 20:10 ` [Qemu-devel] Re: GSOC 2011 yajin
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).