-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Any plan to bump QEMU version? #1798
Comments
Yes, we indeed plan to do so but as said in the FAQ it's impossible to always keep Unicorn sync-ed with upstream QEMU. |
We want to, but that is a lot of work. And our time is not paid.
…On Fri, Mar 3, 2023, 15:18 reito ***@***.***> wrote:
I see unicorn is inevitably strongly coupled to QEMU, so it is hard to
merge upstream changes since QEMU is completely off track.
However the current version 5.0.1 is kind of out-dated and some new target
like RISC-V has many changes since 2019.
Is there any plan to keep the track?
—
Reply to this email directly, view it on GitHub
<#1798>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABNQNYGCQN6ZF23TOSTOQ5DW2GLLPANCNFSM6AAAAAAVOIEM24>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Thanks for your good work! I find out that you modified all tcg functions to make it instantiable, which is a huge work if not tools assisted. |
A probably fool question: |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 15 days. |
Porting mtcg is not helpful for Unicorn API design I think. |
The current latest version of QEMU is 8.1: https://wiki.qemu.org/ChangeLog/8.1 You might want to consider eventual porting of at least some of the features to TCG plugins, like some other projects do: |
I have been keeping an eye on TCG plugins development and I think it's possible to migrate all unicorn-specific hack to TCG plugins, though meaning bunch of rework. |
While there are some overlap, Unicorn is quite different from that plugin
architecture of Qemu, so that is not a solution in my view.
…On Thu, Aug 24, 2023, 13:18 Anton Kochkov ***@***.***> wrote:
The current latest version of QEMU is 8.1:
https://wiki.qemu.org/ChangeLog/8.1
You might want to consider eventual porting of at least some of the
features to TCG plugins, like some other projects do:
-
***@***.***/T/#md4f5cc5eecdd2cb5b0672d760dc811c32aa68ba3
- panda-re/panda#570 <panda-re/panda#570>
—
Reply to this email directly, view it on GitHub
<#1798 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABNQNYGP7MYEXU3UMRYP36LXW3W5FANCNFSM6AAAAAAVOIEM24>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
can i request some elaboration here? is the concern primarily the fact that TCG plugins are merely observers of system state, whereas the arch of unicorn engine allows the user to completely control and manipulate system state? |
Yes exactly.
From: daxie117 ***@***.***>
Date: Friday, 10 May 2024 at 7:07 AM
To: unicorn-engine/unicorn ***@***.***>
Cc: lazymio ***@***.***>, Comment ***@***.***>
Subject: Re: [unicorn-engine/unicorn] Any plan to bump QEMU version? (Issue #1798)
can i request some elaboration here?
is the concern primarily the fact that TCG plugins are merely observers of system state, whereas the arch of unicorn engine allows the user to completely control and manipulate system state?
—
Reply to this email directly, view it on GitHub<#1798 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AHJULO2HDSZ63LGO7NUF7MDZBP6RVAVCNFSM6AAAAAAVOIEM26VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBTGU3TSOJUGQ>.
You are receiving this because you commented.Message ID: ***@***.***>
|
I see unicorn is inevitably strongly coupled to QEMU, so it is hard to merge upstream changes since it is completely off track.
However the current version 5.0.1 is kind of out-dated and some new target like RISC-V has many changes since 2019.
Is there any plan to keep the track?
The text was updated successfully, but these errors were encountered: