What is the difference between virtio-net-pci, virtio-net-pci-non-transitional and virtio-net-pci-transitional

2022-01-11 Thread Ahmad Ismail
I am seeing multiple virtio models for -nic. % qemu-system-x86_64 -nic model=help | grep virtio virtio-net-pci virtio-net-pci-non-transitional virtio-net-pci-transitional I want to know the difference between them. When to use what? Thanks and Best Regards, Ahmmad Ismail

Re: Question About Qemu > Hackintosh

2022-01-11 Thread Alex Bennée
Matt Stacy writes: > I was wondering will Qemu Linux ever be able to emulate Apple Silicon, > modified Arm? Only if someone writes the code for it. The core aarch64 emulation is pretty solid but there are custom Apple instructions and system registers which are undocumented. If you want to

Re: Modification to single Threaded Multi-Core emulation in TCG

2022-01-11 Thread Alex Bennée
Arnabjyoti Kalita writes: > Hello all, > > I have a requirement to use the single-threaded implementation of > multi-core emulation in TCG. This schedules the multiple cores in a > round robin fashion from what I understand, at the end of a set timer > interval. --accel tcg,thread=single will

Re: qemu-user aarch64 and pointer authentication

2022-01-11 Thread Peter Maydell
On Tue, 11 Jan 2022 at 17:06, zadig wrote: > > > Because qemu-user is specifically emulating a Linux kernel. > > We don't want to provide a million tweakable command line options, > > it gets unmaintainable very quickly. We just want to provide the > > process with the environment that the Linux

Re: qemu-user aarch64 and pointer authentication

2022-01-11 Thread zadig
Because qemu-user is specifically emulating a Linux kernel. We don't want to provide a million tweakable command line options, it gets unmaintainable very quickly. We just want to provide the process with the environment that the Linux kernel gives it. Yes, I agree. That's system emulation,

Re: qemu-user aarch64 and pointer authentication

2022-01-11 Thread Peter Maydell
On Tue, 11 Jan 2022 at 16:33, zadig wrote: > > Thanks for your celerity. > > > The architecture specifies that the number of bits used for the > > signature depends on various properties of the CPU and of > > the configuration that the host OS has put it into. > Yes, this is why I checked for the

Re: qemu-user aarch64 and pointer authentication

2022-01-11 Thread zadig
Thanks for your celerity. The architecture specifies that the number of bits used for the signature depends on various properties of the CPU and of the configuration that the host OS has put it into. Yes, this is why I checked for the TCR value, because basically it only depends on its value

Re: qemu-user aarch64 and pointer authentication

2022-01-11 Thread Peter Maydell
On Tue, 11 Jan 2022 at 15:28, zadig wrote: > > Hello, > > I am running some dummy aarch64 ELF I have built using clang with > -mbranch-protection=pac-ret+leaf+b-key. > > qemu successfully emulates the code, however the pointer authentication > signature seems weird to me: only one byte is used

qemu-user aarch64 and pointer authentication

2022-01-11 Thread zadig
Hello, I am running some dummy aarch64 ELF I have built using clang with -mbranch-protection=pac-ret+leaf+b-key. qemu successfully emulates the code, however the pointer authentication signature seems weird to me: only one byte is used for the signature. Here is an example: FE 07 C1 DA