Re: [Qemu-devel] [Qemu-arm] [PATCH] hw/arm/virt: support 4 serial ports

2017-10-24 Thread Jason A. Donenfeld
Hey folks, In case you're curious, this is the kind of hideous workaround required until this is fixed: https://git.zx2c4.com/WireGuard/commit/?id=2456a56729f7247bf88476317fed0ac822a31e92 Please let me know if you intend to fix this or if you will accept working patches from me for it, or if you

Re: [Qemu-devel] [Qemu-arm] [PATCH] hw/arm/virt: support 4 serial ports

2017-10-26 Thread Jason A. Donenfeld
On Thu, Oct 26, 2017 at 3:34 PM, Andrew Jones wrote: > You could make the PL011 user instantiate-able and make the necessary > changes to use the dynamic FDT node generation framework (sysbus-fdt), > and then you'd be able to add as many additional UARTs as you like to > mach-virt's platform bus.

Re: [Qemu-devel] [Qemu-arm] [PATCH] hw/arm/virt: support 4 serial ports

2017-10-26 Thread Jason A. Donenfeld
On Thu, Oct 26, 2017 at 4:36 PM, Peter Maydell wrote: > This has *never* been guaranteed or indeed true. It's just happened > to be true for the x86 PC machine and perhaps for some others that > you've been using. For instance, the MIPS boston board only has > one uart. highbank has one. integrato

Re: [Qemu-devel] [Qemu-arm] [PATCH] hw/arm/virt: support 4 serial ports

2017-10-26 Thread Jason A. Donenfeld
On Thu, Oct 26, 2017 at 6:34 PM, Peter Maydell wrote: > Reordering it would break existing users of the trustzone uart, > whose command lines would stop working. I thought this was the reason for all of those virt26, virt28,etc types -- people who want stability code the revision into their scrip

Re: [Qemu-devel] [Qemu-arm] [PATCH] hw/arm/virt: support 4 serial ports

2017-10-26 Thread Jason A. Donenfeld
On Thu, Oct 26, 2017 at 6:41 PM, Peter Maydell wrote: > Those are primarily about migration compatibility -- you should > be able to live migrate a guest from QEMU 2.6's virt-2.6 machine to > QEMU 2.7's virt-2.6 machine. That's a stricter requirement than > the compatibility we want to keep for no

Re: [PATCH] drivers/virt: vmgenid: add vm generation id driver

2020-10-17 Thread Jason A. Donenfeld
After discussing this offline with Jann a bit, I have a few general comments on the design of this. First, the UUID communicated by the hypervisor should be consumed by the kernel -- added as another input to the rng -- and then userspace should be notified that it should reseed any userspace RNGs

[PATCH] linux-user: add TARGET_SO_{DOMAIN,PROTOCOL}

2021-02-04 Thread Jason A. Donenfeld
These were defined for other platforms but mistakenly left out of mips and generic, so this commit adds them to the places missing. Then it makes them be translated in getsockopt. Signed-off-by: Jason A. Donenfeld --- linux-user/generic/sockbits.h | 3 +++ linux-user/mips/sockbits.h| 2

[PATCH] sparc: implement addr function

2020-06-01 Thread Jason A. Donenfeld
Signed-off-by: Jason A. Donenfeld --- After this lands, somebody will need to update the submodule and prebuilt inside of qemu. forth/device/extra.fs | 6 ++ 1 file changed, 6 insertions(+) diff --git a/forth/device/extra.fs b/forth/device/extra.fs index 9ca6b78..f778f7a 100644 --- a/forth

[PATCH] q800: map reset function to poweroff of some random kernel

2020-01-01 Thread Jason A. Donenfeld
g some code there to tinker with it, or something else. Signed-off-by: Jason A. Donenfeld --- hw/m68k/q800.c | 1 + 1 file changed, 1 insertion(+) diff --git a/hw/m68k/q800.c b/hw/m68k/q800.c index 4ca8678007..bd75dd3141 100644 --- a/hw/m68k/q800.c +++ b/hw/m68k/q800.c @@ -339,6 +339,7 @@ s

[PATCH] q800: implement mac rom reset function for BIOS-less mode

2020-01-02 Thread Jason A. Donenfeld
st crashes when trying to reboot. So, this commit adds a very simple implementation at that location, which just writes to via2 to power down. Signed-off-by: Jason A. Donenfeld --- hw/m68k/q800.c | 21 + 1 file changed, 21 insertions(+) diff --git a/hw/m68k/q800.c b/hw/m6

Re: [PATCH] q800: map reset function to poweroff of some random kernel

2020-01-02 Thread Jason A. Donenfeld
Superseded by https://lore.kernel.org/qemu-devel/20200102103644.233370-1-ja...@zx2c4.com , thankfully.

[PATCH v2] q800: implement mac rom reset function for BIOS-less mode

2020-01-02 Thread Jason A. Donenfeld
st crashes when trying to reboot. So, this commit adds a very simple implementation at that location, which just writes to via2 to power down. We also correct the value of ROMBASE while we're at it. Signed-off-by: Jason A. Donenfeld --- hw/m68k/q800.c | 29 -

Re: [PATCH] q800: implement mac rom reset function for BIOS-less mode

2020-01-02 Thread Jason A. Donenfeld
On Thu, Jan 2, 2020 at 12:41 PM Laurent Vivier wrote: > > Le 02/01/2020 à 12:10, Laurent Vivier a écrit : > > Le 02/01/2020 à 11:36, Jason A. Donenfeld a écrit : > >> On Linux, calling `reboot(RB_AUTOBOOT);` will result in > >> arch/m68k/mac/misc.c's mac_reset

CONFIG_JUMP_LABEL=y on 32-bit x86 leads to intermittent qemu crashes

2020-01-02 Thread Jason A. Donenfeld
Hi, Here's an interesting crash I've seen pop up since enabling CONFIG_JUMP_LABEL=y: [4.716238] EIP: secure_tcp_seq+0x1e/0xa0^M [4.716238] Code: c1 e8 46 90 fb ff eb a2 8d 74 26 00 55 89 e5 83 ec 18 89 75 f8 89 c6 0f b7 45 08 89 5d f4 0f b7 d9 89 7d fc 89 d7 89 45 ec 3e <8d> 74 26 00 8b 4

[PATCH] hw/acpi: specify 64-bit acpi table

2020-06-15 Thread Jason A. Donenfeld
SSDTs cannot address 64-bit physical addresses in 32-bit tables, so we increment the revision to '2' so that these larger addresses are addressable. This matters because the DSDT revision represents the maximum capability of all other SSDTs. This is also what arm does. Signed-off-b

Re: [PATCH] hw/acpi: specify 64-bit acpi table

2020-06-16 Thread Jason A. Donenfeld
On Tue, Jun 16, 2020 at 2:16 AM Igor Mammedov wrote: > On Mon, 15 Jun 2020 18:36:54 -0600 > "Jason A. Donenfeld" wrote: > > SSDTs cannot address 64-bit physical addresses in 32-bit tables, so we > please clarify what accesses waht within tables (i.e. be more concrete).

Re: [PATCH] hw/acpi: specify 64-bit acpi table

2020-06-16 Thread Jason A. Donenfeld
> > increment the revision to '2' so that these larger addresses are > > addressable. This matters because the DSDT revision represents the > > maximum capability of all other SSDTs. This is also what arm does. > it was keept at 1 for compat reasons with WindowsXP. > by now it is long time EOL, so

vm events, userspace, the vmgenid driver, and the future [was: the uevent revert thread]

2024-09-18 Thread Jason A. Donenfeld
[broadened subject line and added relevant parties to cc list] On Tue, Sep 17, 2024 at 10:55:20PM +0200, Alexander Graf wrote: > What is still open are user space applications that require event based > notification on VM clone events - and *only* VM clone events. This > mostly caters for tools

<    1   2   3   4   5