Readit NewsFor Aarch64, Arm's official guide is pretty good https://developer.arm.com/documentation/102142/latest/
I am curious if you get to DMA before or after QEMU, and if before what your API will look like.
Instead the author uses Cranelift[1] and binja to solve the two interesting problems here.
While cool, I'm not sure if that's interesting enough to read through in its entirety. I use libraries all day every day, but is it the hacker spirit to make your entire project glue-code for libraries that do the thing you claim to do?
It's maybe more philosophical than anything.
The disassembler is my next step, since it's the easiest to tackle. Swapping binja for a custom solution on the existing code would be relatively straightforward.
The JIT is a completely different beast, it's essentially the IR -> codegen steps of a compiler (meaning without parsing, syntax/lexical analysis, object generation). Seeing as I wanted to target both x86_64 and aarch64 hosts, using an existing solution would get me started faster before I eventually write my own.
My plan is to split the JIT backends and keep cranelift for x86_64 support, but have my own aarch64 JIT also.
You have to pick your battles and assign priorities, you cannot re-invent everything at once.
(Author here)
It's not possible to run an android VM on QEMU right? As in, is it officially supported? (I know about Waydroid)
I distinctly remember being very confused about the spray of particles interjected between nouns and verbs, and trying to shut out the noise of the particles to be able to parse a sentence. I probably got a headache.
The problem is that, the meaning of "ενταύθα", "ουν", "ον", "γε", "δε", "ην", etc may be well known if you take them as individual words, but when you string them together they're apparently trying to say ... something. And that something is opaque and incomprehensible, like an ancient joke for which you have no context.
Meanwhile Plutarch enriches the laconic myth corpus by reporting that the Lacedaemonians were content with replying to a letter with only the words "About what you wrote: no." Writing style is part of the message.
https://www.perseus.tufts.edu/hopper/text?doc=Perseus%3Atext...
Growing up bilingual, I personally always found Greek more verbose than English even in brevity. It's good for avoiding ambiguity and getting your intent across but sometimes bad for colloquial communication.
This study focuses on artist-designed frames at the end of the 19th century, many of which are preserved in the Havemeyer collection at the Metropolitan Museum, with a particular emphasis on a material known at the time as pâte coulante, unique in its ability to render extraordinary profiles, some of which could not have been realized by any other method available at the time. Although frames in pâte coulante can be seen surrounding the works of many late 19th century and early 20th century paintings, this study refers to the few superb examples available for study in the Metropolitan Museum and in private collections, which in many cases surround works by Edgar Degas. For artists like Degas, this method became crucial for executing radical frame designs. To reinforce the argument that the process of template-cut pâte coulante granted artists and framemakers the freedom to turn any design into a reliable and serviceable moulding, replicas of period mouldings were recreated using the available historic information, and the results gleaned from this technical study are included here.
Keep in mind that TCG API and internals have no stable guarantees, so if you cross-reference with current QEMU code you are bound to find differences.