[Qemu-devel] [Bug 1615079] Re: GTK+ UI virtual consoles scrolling broken

2019-06-22 Thread Launchpad Bug Tracker
[Expired for QEMU because there has been no activity for 60 days.] ** Changed in: qemu Status: Incomplete => Expired -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1615079 Title: GTK+ UI

[Qemu-devel] [PATCH v8 2/2] hw/arm: Add arm SBSA reference machine, devices part

2019-06-22 Thread Hongbo Zhang
Following the previous patch, this patch adds peripheral devices to the newly introduced SBSA-ref machine. Signed-off-by: Hongbo Zhang --- hw/arm/sbsa-ref.c | 523 +- 1 file changed, 517 insertions(+), 6 deletions(-) diff --git

[Qemu-devel] [PATCH v8 1/2] hw/arm: Add arm SBSA reference machine, skeleton part

2019-06-22 Thread Hongbo Zhang
For the Aarch64, there is one machine 'virt', it is primarily meant to run on KVM and execute virtualization workloads, but we need an environment as faithful as possible to physical hardware, for supporting firmware and OS development for pysical Aarch64 machines. This patch introduces new

[Qemu-devel] [PATCH v8 0/2] Add Arm SBSA Reference Machine

2019-06-22 Thread Hongbo Zhang
For the Aarch64, there is one machine 'virt', it is primarily meant to run on KVM and execute virtualization workloads, but we need an environment as faithful as possible to physical hardware, to support firmware and OS development for pysical Aarch64 machines. This machine comes with: -

Re: [Qemu-devel] [SeaBIOS] [PATCH v3 3/4] geometry: Add boot_lchs_find_*() utility functions

2019-06-22 Thread Sam Eiderman
> On 22 Jun 2019, at 18:27, Kevin O'Connor wrote: > > On Sat, Jun 22, 2019 at 11:51:48AM +0300, Sam Eiderman wrote: >> But maybe someone wants bootorder but doesn’t want to override legacy disk >> translations… >> >> I’m thinking of maybe adding >> >> if (!CONFIG_BOOTORDER ||

Re: [Qemu-devel] [RFC v2 PATCH] hw/arm/virt: makes virt a default machine type

2019-06-22 Thread Peter Maydell
On Fri, 21 Jun 2019 at 20:04, Cleber Rosa wrote: > The experience acquired here deserves the highest consideration, but I > can't help myself to wonder if this isn't one of the (conceptual) > reasons for parameters such as '-nodefaults'. I know QEMU doesn't > promise the same behavior across

Re: [Qemu-devel] [PATCH v3 1/5] virtio: add "use-started" property

2019-06-22 Thread Greg Kurz
On Mon, 17 Jun 2019 14:04:10 +0800 Yongji Xie wrote: > On Mon, 17 Jun 2019 at 13:24, Greg Kurz wrote: > > > > On Mon, 17 Jun 2019 10:14:30 +0800 > > Yongji Xie wrote: > > > > > On Fri, 14 Jun 2019 at 19:45, Greg Kurz wrote: > > > > > > > > On Fri, 14 Jun 2019 17:31:17 +0800 > > > >

Re: [Qemu-devel] [PULL 00/10] MIPS queue for June 21st, 2019

2019-06-22 Thread Peter Maydell
On Fri, 21 Jun 2019 at 10:54, Aleksandar Markovic wrote: > > From: Aleksandar Markovic > > The following changes since commit 33d609990621dea6c7d056c86f707b8811320ac1: > > Merge remote-tracking branch 'remotes/kevin/tags/for-upstream' into staging > (2019-06-18 17:00:52 +0100) > > are

Re: [Qemu-devel] [SeaBIOS] [PATCH v3 3/4] geometry: Add boot_lchs_find_*() utility functions

2019-06-22 Thread Kevin O'Connor
On Sat, Jun 22, 2019 at 11:51:48AM +0300, Sam Eiderman wrote: > But maybe someone wants bootorder but doesn’t want to override legacy disk > translations… > > I’m thinking of maybe adding > > if (!CONFIG_BOOTORDER || !CONFIG_BIOS_GEOMETRY) > return NULL; That's fine - though it's

Re: [Qemu-devel] [Qemu-block] [PATCH v5 00/12] Add support for io_uring

2019-06-22 Thread Stefan Hajnoczi
On Tue, Jun 11, 2019 at 10:57 AM Stefan Hajnoczi wrote: > On Mon, Jun 10, 2019 at 07:18:53PM +0530, Aarushi Mehta wrote: > > This patch series adds support for the newly developed io_uring Linux AIO > > interface. Linux io_uring is faster than Linux's AIO asynchronous I/O code, > > offers

Re: [Qemu-devel] [Qemu-block] [PATCH v5 04/12] block/io_uring: implements interfaces for io_uring

2019-06-22 Thread Stefan Hajnoczi
On Mon, Jun 17, 2019 at 1:27 PM Maxim Levitsky wrote: > On Mon, 2019-06-10 at 19:18 +0530, Aarushi Mehta wrote: > > +if (!cqes) { > > +break; > > +} > > +LuringAIOCB *luringcb = io_uring_cqe_get_data(cqes); > > +ret = cqes->res; > > + > > +if

Re: [Qemu-devel] [PATCH v4 0/7] tcg/ppc: Add vector opcodes

2019-06-22 Thread Mark Cave-Ayland
On 22/06/2019 15:20, Mark Cave-Ayland wrote: > I've just given your tcg-ppc-vsx branch a spin here, and like Howard I'm > getting > segfaults trying to launch my MacOS images :( The segfault is weird: it > doesn't get > caught by an attached gdb and the qemu-system-ppc process seems to hang >

Re: [Qemu-devel] [PATCH v8 00/10] hw/m68k: add Apple Machintosh Quadra 800 machine

2019-06-22 Thread Mark Cave-Ayland
On 19/06/2019 23:19, Laurent Vivier wrote: > I'm rebasing some of these patches for seven years now, > too many years... > > if you want to test the machine, I'm sorry, it doesn't boot > a MacROM, but you can boot a linux kernel from the command line. > > You can install your own disk using

Re: [Qemu-devel] [PATCH v4 0/7] tcg/ppc: Add vector opcodes

2019-06-22 Thread Mark Cave-Ayland
On 19/06/2019 06:07, Mark Cave-Ayland wrote: > On 18/06/2019 06:00, Richard Henderson wrote: > >> Ping. Otherwise I'll include it in my next tcg pull. >> >> r~ > > I can give this another spin on my test images on a G4 over the next few > days. I've > also added Howard on CC as he reported

Re: [Qemu-devel] [PATCH v4 04/10] block/pflash_cfi02: Implement intereleaved flash devices

2019-06-22 Thread Philippe Mathieu-Daudé
Hi Stephen, This series haven't fall through the cracks, however it is taking me longer than expected to review it. On 4/26/19 6:26 PM, Stephen Checkoway wrote: > It's common for multiple narrow flash chips to be hooked up in parallel > to support wider buses. For example, four 8-bit wide flash

Re: [Qemu-devel] [PATCH 0/2] target/i386: kvm: Fix treatment of AMD SVM in nested migration

2019-06-22 Thread Liran Alon
> On 22 Jun 2019, at 5:39, no-re...@patchew.org wrote: > > Patchew URL: >

Re: [Qemu-devel] [SeaBIOS] [PATCH v3 3/4] geometry: Add boot_lchs_find_*() utility functions

2019-06-22 Thread Sam Eiderman
But maybe someone wants bootorder but doesn’t want to override legacy disk translations… I’m thinking of maybe adding if (!CONFIG_BOOTORDER || !CONFIG_BIOS_GEOMETRY) return NULL; In each of the get_*_devpath functions (which will normally return an allocated string, not on stack).