Re: [PATCH 0/2] hw/riscv/virt.c: change default CPU to 'max'

2025-05-19 Thread David Abdurachmanov
On Mon, May 19, 2025 at 3:20 AM Alistair Francis wrote: > > On Tue, May 6, 2025 at 8:47 AM Daniel Henrique Barboza > wrote: > > > > Hi Alistair, > > > > > > I think we should push this upstream and see what happens. We'll have a > > full release cycle to undo the change in case we find unintended

Re: [PATCH 0/2] hw/riscv/virt.c: change default CPU to 'max'

2025-05-18 Thread Alistair Francis
On Tue, May 6, 2025 at 8:47 AM Daniel Henrique Barboza wrote: > > Hi Alistair, > > > I think we should push this upstream and see what happens. We'll have a > full release cycle to undo the change in case we find unintended side > effects. I'm fairly optimistic that this change will be a no-op for

Re: [PATCH 0/2] hw/riscv/virt.c: change default CPU to 'max'

2025-05-05 Thread Daniel Henrique Barboza
Hi Alistair, I think we should push this upstream and see what happens. We'll have a full release cycle to undo the change in case we find unintended side effects. I'm fairly optimistic that this change will be a no-op for most users and will benefit us when we'll have to deal with RVA23 specifi

[PATCH 0/2] hw/riscv/virt.c: change default CPU to 'max'

2025-04-04 Thread Daniel Henrique Barboza
Hi, The 'rv64' CPU, the default CPU for the 'virt' machine, is a strange CPU. It is a collection of extensions that were enabled/disabled as extensions were being added in TCG, and in the end we ended up with a CPU that we can't say exactly what it does. This is further aggravated by the distros