Message ID | 20220106094200.1801206-1-gaosong@loongson.cn |
---|---|
Headers | show |
Series | Add LoongArch linux-user emulation support | expand |
On 1/6/22 1:41 AM, Song Gao wrote: > Based-on:<20220106074740.1754661-1-gaosong@loongson.cn> > > Hi all, > > This series only support linux-user emulation. > More about LoongArch at:https://github.com/loongson/ > > The latest kernel: > *https://github.com/loongson/linux/tree/loongarch-next > > Patches need review: > * 0018-linux-user-Add-LoongArch-specific-structures.patch > * 0019-linux-user-Add-LoongArch-signal-support.patch You're still blocked on no upstream kernel support. As shown in patch 19, the kernel abi is still in flux. It would be best if you could work toward getting full system emulation completed. Then all of the basic cpu emulation can be merged and all you'd need to keep updating is the linux-user portions. r~
Hi Richard. On 2022/1/7 下午1:01, Richard Henderson wrote: > On 1/6/22 1:41 AM, Song Gao wrote: >> Based-on:<20220106074740.1754661-1-gaosong@loongson.cn> >> >> Hi all, >> >> This series only support linux-user emulation. >> More about LoongArch at:https://github.com/loongson/ >> >> The latest kernel: >> *https://github.com/loongson/linux/tree/loongarch-next >> >> Patches need review: >> * 0018-linux-user-Add-LoongArch-specific-structures.patch >> * 0019-linux-user-Add-LoongArch-signal-support.patch > > You're still blocked on no upstream kernel support. > As shown in patch 19, the kernel abi is still in flux. > We hope the kernel will support as soon as possible. but ... > It would be best if you could work toward getting full system > emulation completed. Then all of the basic cpu emulation can be > merged and all you'd need to keep updating is the linux-user portions. > We are going to submit V4 system emulation, maybe tommorrow or next-week, and We'll keep updating the linux-user portions. Thanks Song > r~
Hi, On 1/7/22 15:59, gaosong wrote: > Hi Richard. > On 2022/1/7 下午1:01, Richard Henderson wrote: >> On 1/6/22 1:41 AM, Song Gao wrote: >>> Based-on:<20220106074740.1754661-1-gaosong@loongson.cn> >>> >>> Hi all, >>> >>> This series only support linux-user emulation. >>> More about LoongArch at:https://github.com/loongson/ >>> >>> The latest kernel: >>> *https://github.com/loongson/linux/tree/loongarch-next >>> >>> Patches need review: >>> * 0018-linux-user-Add-LoongArch-specific-structures.patch >>> * 0019-linux-user-Add-LoongArch-signal-support.patch >> >> You're still blocked on no upstream kernel support. >> As shown in patch 19, the kernel abi is still in flux. >> > We hope the kernel will support as soon as possible. but ... >> It would be best if you could work toward getting full system >> emulation completed. Then all of the basic cpu emulation can be >> merged and all you'd need to keep updating is the linux-user portions. >> > We are going to submit V4 system emulation, maybe tommorrow or next-week, and We'll keep updating the linux-user portions. I believe what Richard meant is suggesting you to re-order your patches so that the CPU emulation part (first half of this series) and the system emulation part (Xiaojuan's series) would be combined to one new series, to be reviewed and merged independent of the still-unstable Linux ABI that's blocking this series at the moment. To "keep updating the linux-user portions" without re-arranging the series will just delay inclusion further, IMO. In case the description above is not clear enough: We basically have 3 parts for full LoongArch target support: (a) CPU emulation, (b) privileged architecture & hw emulation, and (c) linux-user emulation. Currently this series consists of (a) and (c), while Xiaojuan's series has (b). And the tcg-dev branch you seem to be staging your work at [1] has the same ordering: (a) then (c) then (b), which is consistent with Xiaojuan's series cover letter. However, because (c) is blocked by kernel port upstreaming, (a) could not be merged, and by re-combining (a) with (b) we can speed up review and inclusion of things. This would require you to coordinate with Xiaojuan and reorder your patches in the tcg-dev branch, so that you can generate the right series to send. [1]: https://github.com/loongson/qemu/tree/tcg-dev > > Thanks > Song >> r~