[Qemu-devel] [PULL v2 0/3] linux-user fixes for -rc3

The following changes since commit df6378eb0e6cfd58a22a1c3ff8fa4a9039f1eaa8: Merge remote-tracking branch 'remotes/kraxel/tags/ui-20180410-pull-request' into staging (2018-04-10 14:04:27 +0100) are available in the Git repository at: git://github.com/vivier/qemu.git tags/linux-user

[Qemu-devel] [PATCH 1/2] Fix error message about compressed clusters with OFLAG_COPIED

Compressed clusters are not supposed to have the COPIED bit set. "qemu-img check" detects that and prints an error message reporting the number of the affected host cluster. This doesn't make much sense because compressed clusters are not aligned to host clusters, so it would be better to report

[Qemu-devel] [Bug 1754038] Re: ARM M: Systick first wrap delayed (qemu-timers/icount prb?)

Now fixed in master, commit c52e7132d7c885, and will be in 2.12.0. ** Changed in: qemu Status: New => Fix Committed -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1754038 Title: ARM M:

[Qemu-devel] [PULL v2 1/3] linux-user: fix microblaze get_sp_from_cpustate()

get_sigframe() uses regs[1] and this is actual SP. Signed-off-by: Laurent Vivier Message-Id: <20180409115212.875-1-laur...@vivier.eu> --- linux-user/microblaze/target_signal.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[Qemu-devel] [Bug 1761401] Re: ARM/Neon: vcvt rounding error

Hi Christophe -- we think that commit bd49e6027cbc207c, now in master, should have fixed this bug. Could you retry your testcase with a QEMU build including that fix? -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU.

[Qemu-devel] [Bug 1761535] Re: qemu-aarch64-static docker arm64v8/openjdk coredump

Now fixed in master, commit 7f0f4208b3a96, and will be in 2.12.0. ** Changed in: qemu Status: In Progress => Fix Committed -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1761535 Title:

[Qemu-devel] [PATCH 0/2] Minor fixes about compressed clusters with OFLAG_COPIED

Hi, while reviewing one previous patch about data corruption and compressed clusters we discussed that the documentation doesn't clarify that L2 entries for compressed clusters are not supposed to have the OFLAG_COPIED bit set. Here's a patch to update the documentation and another one to fix

[Qemu-devel] [PULL v2 2/3] linux-user: add microblaze/microblazeel magic numbers in qemu-binfmt-conf.sh

Signed-off-by: Laurent Vivier Message-Id: <20180409115212.875-2-laur...@vivier.eu> --- scripts/qemu-binfmt-conf.sh | 12 ++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/scripts/qemu-binfmt-conf.sh b/scripts/qemu-binfmt-conf.sh index

[Qemu-devel] [PULL v2 3/3] linux-user: implement HWCAP bits on MIPS

From: James Cowgill Add support for the two currently defined HWCAP bits on MIPS - R6 and MSA. Buglink: https://bugs.launchpad.net/qemu/+bug/1754372 Signed-off-by: James Cowgill Reviewed-by: Laurent Vivier Message-Id:

Re: [Qemu-devel] [PULL 00/12] target-arm queue

erge remote-tracking branch 'remotes/xtensa/tags/20180409-xtensa' into > staging (2018-04-10 10:22:45 +0100) > > are available in the Git repository at: > > git://git.linaro.org/people/pmaydell/qemu-arm.git > tags/pull-target-arm-20180410 > > for you to fetch changes up

[Qemu-devel] [PULL 5/7] qemu-iotests: Remove _supported_fmt dmg

qemu-iotests doesn't support dmg, and the dmg block driver doesn't support image creation. Two test cases declare dmg as supported, but that's obviously wrong for both reasons. Remove the declaration. Signed-off-by: Kevin Wolf Reviewed-by: Eric Blake ---

[Qemu-devel] [PULL 0/7] Block layer patches for 2.12.0-rc3

The following changes since commit df6378eb0e6cfd58a22a1c3ff8fa4a9039f1eaa8: Merge remote-tracking branch 'remotes/kraxel/tags/ui-20180410-pull-request' into staging (2018-04-10 14:04:27 +0100) are available in the git repository at: git://repo.or.cz/qemu/kevin.git tags/for-upstream

[Qemu-devel] [PULL 7/7] qemu-iotests: update 185 output

From: Stefan Hajnoczi Commit 4486e89c219c0d1b9bd8dfa0b1dd5b0d51ff2268 ("vl: introduce vm_shutdown()") added a bdrv_drain_all() call. As a side-effect of the drain operation the block job iterates one more time than before. The 185 output no longer matches and the test is

[Qemu-devel] [PULL 6/7] commit/stream: Reset delay_ns

Streaming and the commit block job only want to apply throttling when they actually copied data instead of skipping it, so they made the calculation of delay_ns conditional. However, delay_ns isn't reset when skipping some sectors, so instead of not waiting, the old delay is applied again.

[Qemu-devel] [PULL 2/7] hw/block/pflash_cfi: fix off-by-one error

From: Philippe Mathieu-Daudé ASAN reported: hw/block/pflash_cfi02.c:245:33: runtime error: index 82 out of bounds for type 'uint8_t [82]' Since the 'cfi_len' member is not used, remove it to keep the code safer. Cc: qemu-sta...@nongnu.org Reported-by: AddressSanitizer

[Qemu-devel] [PULL 4/7] iotests: blacklist bochs and cloop for 205 and 208

From: Vladimir Sementsov-Ogievskiy Blacklist these formats, as they don't support image creation, as they say: > ./qemu-img create -f bochs x 1m qemu-img: x: Format driver 'bochs' does not support image creation > ./qemu-img create -f cloop x 1m

[Qemu-devel] [PULL 3/7] iotests.py: improve verify_image_format helper

From: Vladimir Sementsov-Ogievskiy Support "generic" formats like in bash tests with their _supported_fmt generic The test, supporting "generic" formats will run if IMGFMT_GENERIC = true, which is default, except for bochs and cloop. However, you can use

[Qemu-devel] [PULL 1/7] iotests.py: support unsupported_fmts in main()

From: Vladimir Sementsov-Ogievskiy Signed-off-by: Vladimir Sementsov-Ogievskiy Signed-off-by: Kevin Wolf --- tests/qemu-iotests/iotests.py | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git

Re: [Qemu-devel] [PATCH v2] linux-user: implement HWCAP bits on MIPS

Le 10/04/2018 à 15:53, Peter Maydell a écrit : > On 15 March 2018 at 15:25, Laurent Vivier wrote: >> Le 15/03/2018 à 16:13, James Cowgill a écrit : >>> Add support for the two currently defined HWCAP bits on MIPS - R6 and >>> MSA. >>> >>> Buglink:

[Qemu-devel] [PULL 0/1] migration queue

From: "Dr. David Alan Gilbert" <dgilb...@redhat.com> The following changes since commit df6378eb0e6cfd58a22a1c3ff8fa4a9039f1eaa8: Merge remote-tracking branch 'remotes/kraxel/tags/ui-20180410-pull-request' into staging (2018-04-10 14:04:27 +0100) are available in th

[Qemu-devel] [PATCH 4/4] pc-bios/s390-ccw: fix non-sequential boot entries (enum)

zIPL boot menu entries can be non-sequential. Let's account for this issue for the s390 enumerated boot menu. Since we can no longer print a range of available entries to the user, we have to present a list of each available entry. An example of this menu: s390-ccw Enumerated Boot Menu.

[Qemu-devel] [PULL 1/1] Revert "migration: Don't activate block devices if using -S"

From: "Dr. David Alan Gilbert" This reverts commit 0746a92612276aee69e66dfe6782b0f882d221d5. Discussion with kwolf suggests this is actually an API change that we need to gate on a capability. Push to 2.13. Signed-off-by: Dr. David Alan Gilbert ---

[Qemu-devel] [PATCH 1/4] pc-bios/s390-ccw: rename MAX_TABLE_ENTRIES to MAX_BOOT_ENTRIES

The MAX_TABLE_ENTRIES constant has a name that is too generic. As we want to declare a limit for boot menu entries, let's rename it to a more fitting MAX_BOOT_ENTRIES and set its value to 31 (30 boot entries and 1 default entry). Also we move it from bootmap.h to s390-ccw.h to make it available

[Qemu-devel] [PATCH 2/4] pc-bios/s390-ccw: fix loadparm initialization and int conversion

Rename the loadparm char array in main.c to loadparm_str and increase the size by one byte to account for a null termination when converting the loadparm string to an int via atoui. Also allow the boot menu to be enabled when loadparm is set to an empty string or a series of spaces.

[Qemu-devel] [PATCH 0/4] Small fixes for s390x QEMU boot menu

These patches fix the following: - The QEMU zIPL boot menu does not allow accurate selection of non-sequential entries. - The QEMU zIPL boot menu does not have all the capabilities of the real zIPL menu (such as commandline args). We should print a different

[Qemu-devel] [PATCH 3/4] pc-bios/s390-ccw: fix non-sequential boot entries (eckd)

zIPL boot menu entries can be non-sequential. Let's account for this issue for the s390 zIPL boot menu. Since this boot menu is actually an imitation and is not completely capable of everything the real zIPL menu can do, let's also print a different banner to the user. Signed-off-by: Collin

Re: [Qemu-devel] [PATCH] migration: Don't activate block devices if using -S

Am 10.04.2018 um 16:22 hat Dr. David Alan Gilbert geschrieben: > * Kevin Wolf (kw...@redhat.com) wrote: > > Am 10.04.2018 um 12:40 hat Dr. David Alan Gilbert geschrieben: > > > Hmm; having chatted to Jiri I'm OK with reverting it, on the condition > > > that I actually understand how this

Re: [Qemu-devel] [PATCH v2 17/17] target/riscv: convert to TranslatorOps

On Tue, Apr 10, 2018 at 09:05:06 -0500, Eric Blake wrote: > On 04/10/2018 07:59 AM, Emilio G. Cota wrote: > > On Tue, Apr 10, 2018 at 11:24:37 +1000, Richard Henderson wrote: > >> On 04/07/2018 04:20 AM, Emilio G. Cota wrote: > >>> +next_page = (ctx->base.pc_first & TARGET_PAGE_MASK) + >

Re: [Qemu-devel] [PATCH for-2.12 v2] qemu-iotests: update 185 output

Am 10.04.2018 um 10:11 hat Stefan Hajnoczi geschrieben: > On Wed, Apr 04, 2018 at 06:16:12PM +0200, Max Reitz wrote: > > On 2018-04-04 17:01, Stefan Hajnoczi wrote: > > === Start mirror job and exit qemu === > > > > This seems to be independent of whether there is actually data on > > TEST_IMG

Re: [Qemu-devel] [PATCH for-2.12] make-release: add skiboot .version file

On 10 April 2018 at 15:23, Michael Roth wrote: > Quoting Peter Maydell (2018-04-10 02:31:04) >> On 10 April 2018 at 01:57, Michael Roth wrote: >> > # FIXME: The following line is a workaround for avoiding filename >> > collisions >> > #

[Qemu-devel] [Bug 1762707] Re: VFIO device gets DMA failures when virtio-balloon leak from highmem to lowmem

Ballooning is currently incompatible with device assignment. When the balloon is inflated (memory removed from the VM), the pages are zapped from the process without actually removing them from the vfio DMA mapping. The pages are still pinned from the previous mapping, making the balloon

Re: [Qemu-devel] [PATCH for-2.12] make-release: add skiboot .version file

Quoting Peter Maydell (2018-04-10 02:31:04) > On 10 April 2018 at 01:57, Michael Roth wrote: > > This is needed to build skiboot from tarball-distributed sources > > since the git data the make_release.sh script relies on to generate > > it is not available. > > > > Cc:

Re: [Qemu-devel] [PATCH v2 06/17] target/mips: convert to DisasJumpType

On Tue, Apr 10, 2018 at 13:56:25 +1000, Richard Henderson wrote: > Ok, well, there are existing bugs within the MIPS translation here, and we > might as well fix them within this patch set. > > (1) The description for BS_STOP says we want to stop, but (what will become) > mips_tr_tb_stop calls

Re: [Qemu-devel] [PATCH] migration: Don't activate block devices if using -S

* Kevin Wolf (kw...@redhat.com) wrote: > Am 10.04.2018 um 12:40 hat Dr. David Alan Gilbert geschrieben: > > * Kevin Wolf (kw...@redhat.com) wrote: > > > Am 10.04.2018 um 10:45 hat Dr. David Alan Gilbert geschrieben: > > > > * Kevin Wolf (kw...@redhat.com) wrote: > > > > > Am 10.04.2018 um 09:36

Re: [Qemu-devel] [RfC PATCH] Add udmabuf misc device

Hi, > Generally we try to cache mappings as much as possible. And wrt finding a > slot: Create a sufficiently sized BAR on the virgl device, just for that? Well. virtio has no concept of "bars" ... The most common virtio transport layer happens to be pci, which actually has bars. But we

Re: [Qemu-devel] [PULL 0/4] Ui 20180410 patches

are available in the git repository at: > > git://git.kraxel.org/qemu tags/ui-20180410-pull-request > > for you to fetch changes up to c6093a05d6a84d2144bb6462cf20e907eddf8aeb: > > configure: don't warn SDL

[Qemu-devel] [Bug 1748434] Re: Possibly wrong GICv3 behavior when secure enabled

Now fixed in master in commit a2e2d7fc46fd8be, so will be in 2.12.0. ** Changed in: qemu Status: In Progress => Fix Committed -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1748434 Title:

Re: [Qemu-devel] [PATCH v2 17/17] target/riscv: convert to TranslatorOps

On 04/10/2018 07:59 AM, Emilio G. Cota wrote: > On Tue, Apr 10, 2018 at 11:24:37 +1000, Richard Henderson wrote: >> On 04/07/2018 04:20 AM, Emilio G. Cota wrote: >>> +next_page = (ctx->base.pc_first & TARGET_PAGE_MASK) + >>> TARGET_PAGE_SIZE; >>> +if (ctx->base.pc_next >=

[Qemu-devel] [Bug 1755479] Re: Cortex M:qemu abort with optimized code and icount

This is now fixed in master (and will be in 2.12.0) with commits 0790f8686107 and 87f963be66a32453e001. ** Changed in: qemu Status: New => Fix Committed -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU.

[Qemu-devel] [Bug 1760262] Re: cmsdk-apb-uart doesn't appear to clear interrupt flags

Thanks for the bug report; I've submitted this patch (which is similar to but not quite the same as your fix): https://patchwork.ozlabs.org/patch/896715/ Hopefully this will get into 2.12, but we're quite close to release now so it will depend on whether we need to spin an extra release

[Qemu-devel] [Bug 1756519] Re: qemu linux-user crash in QOM path canonicalization during do_fork() call to cpu_create

Should be fixed by 73a988d957b9142e0 (which is the patch jcmvbkbc mentions in comment #4), now in master and will be in 2.12.0. ** Changed in: qemu Status: New => Fix Committed -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU.

Re: [Qemu-devel] [PATCH 2/2] qemu-thread: let cur_mon be per-thread

On 04/10/2018 07:49 AM, Peter Xu wrote: > cur_mon was only used in main loop so we don't really need that to be > per-thread variable. Now it's possible that we have more than one > thread to operate on it. Let's start to let it be per-thread variable. > > In case we'll create threads within a

Re: [Qemu-devel] [PATCH v2] linux-user: implement HWCAP bits on MIPS

On 15 March 2018 at 15:25, Laurent Vivier wrote: > Le 15/03/2018 à 16:13, James Cowgill a écrit : >> Add support for the two currently defined HWCAP bits on MIPS - R6 and >> MSA. >> >> Buglink: https://bugs.launchpad.net/qemu/+bug/1754372 >> Signed-off-by: James Cowgill

[Qemu-devel] QEMU - DOS - simulate DPR-RAM

Hello, i have old DOS 6.22 Systems with a DPR (dual ported ram) at Adress d000:0 with 4kB size. Now i want to emulate this system with QEMU in Windows and want to read/write data to this DPR memoryblock from my Windows System. Can i do that? is there an option to emulate a Memoryblock at the

Re: [Qemu-devel] [PATCH v2 1/2 for-2.12?] qapi: Parameter gl of DisplayType now accept an enum

On Tue, Apr 10, 2018 at 08:13:00AM -0500, Eric Blake wrote: > On 04/10/2018 07:02 AM, Elie Tournier wrote: > > Signed-off-by: Elie Tournier > > --- > > qapi/ui.json | 21 - > > vl.c | 10 +- > > 2 files changed, 25 insertions(+), 6

Re: [Qemu-devel] [PATCH v2 00/17] Translation loop conversion for sh4/sparc/mips/s390x/openrisc/riscv targets

On 04/10/2018 03:40 PM, Emilio G. Cota wrote: > On Tue, Apr 10, 2018 at 15:16:19 +0200, Bastian Koppelmann wrote: >> On 04/10/2018 03:03 PM, Emilio G. Cota wrote: >>> On Tue, Apr 10, 2018 at 14:24:23 +1000, Richard Henderson wrote: On 04/10/2018 02:11 AM, Emilio G. Cota wrote: > On Mon,

[Qemu-devel] [PATCH for-2.12] hw/char/cmsdk-apb-uart.c: Correctly clear INTSTATUS bits on writes

The CMSDK APB UART INTSTATUS register bits are all write-one-to-clear. We were getting this correct for the TXO and RXO bits (which need special casing because their state lives in the STATE register), but had forgotten to handle the normal bits for RX and TX which we do store in our s->intstatus

Re: [Qemu-devel] [PATCH v2 00/17] Translation loop conversion for sh4/sparc/mips/s390x/openrisc/riscv targets

On Tue, Apr 10, 2018 at 15:16:19 +0200, Bastian Koppelmann wrote: > On 04/10/2018 03:03 PM, Emilio G. Cota wrote: > > On Tue, Apr 10, 2018 at 14:24:23 +1000, Richard Henderson wrote: > >> On 04/10/2018 02:11 AM, Emilio G. Cota wrote: > >>> On Mon, Apr 09, 2018 at 16:01:36 +0200, Bastian Koppelmann

Re: [Qemu-devel] [PATCH 1/2] qemu-thread: always keep the posix wrapper layer

On 04/10/2018 07:49 AM, Peter Xu wrote: > We will conditionally have a wrapper layer depending on whether the host > has the PTHREAD_SETNAME capability. It complicates stuff. Let's just > keep the wrapper there, meanwhile we opt out the pthread_setname_np() > call only. The layer can be helpful

Re: [Qemu-devel] [PATCH v2 1/2 for-2.12?] qapi: Parameter gl of DisplayType now accept an enum

> # @off: Disable OpenGL (default). > > > + # 'on'Use OpenGL, pick context type automatically. > > + # Would better be named 'auto' but is called 'on' for backward > > + # compatibility with bool type. > > See below... > DisplayOptions was added in 2.12. This is a

[Qemu-devel] [Bug 1761027] Re: Unexpected error: "AioContext polling is not implemented on Windows"

** Summary changed: - Unexpected error + Unexpected error: "AioContext polling is not implemented on Windows" -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1761027 Title: Unexpected error:

[Qemu-devel] [PULL 1/3] iotests: fix wait_until_completed()

From: Peter Xu If there are more than one events, wait_until_completed() might return the 2nd event even if the 1st event is JOB_COMPLETED, since the for loop will continue to run even if completed is set to True. It never happened before, but it can be triggered when OOB is

[Qemu-devel] [PULL 3/3] monitor: bind dispatch bh to iohandler context

From: Peter Xu Eric Auger reported the problem days ago that OOB broke ARM when running with libvirt: http://lists.gnu.org/archive/html/qemu-devel/2018-03/msg06231.html The problem was that the monitor dispatcher bottom half was bound to qemu_aio_context now, which could be

[Qemu-devel] [PULL 0/3] QAPI patches for 2018-04-10, 2.12-rc3

The following changes since commit fb4fe32d5b6290deabe752b51cc1cc2a9e8573db: Merge remote-tracking branch 'remotes/xtensa/tags/20180409-xtensa' into staging (2018-04-10 10:22:45 +0100) are available in the Git repository at: git://repo.or.cz/qemu/ericb.git tags/pull-qapi-2018-04-10 for

[Qemu-devel] [PULL 2/3] iothread: workaround glib bug which hangs qmp-test

From: Peter Xu Free the AIO context earlier than the GMainContext (if we have) to workaround a glib2 bug that GSource context pointer is not cleared even if the context has already been destroyed (while it should). The patch itself only changed the order to destroy the

Re: [Qemu-devel] [PATCH v3 3/7] s390x/cpumodel: Set up CPU model for AP device support

On 04/06/2018 10:51 AM, Pierre Morel wrote: On 16/03/2018 00:24, Tony Krowiak wrote: A new CPU model feature and two new CPU model facilities are introduced to support AP devices for a KVM guest. CPU model features: 1. The KVM_S390_VM_CPU_FEAT_AP CPU model feature indicates that AP

Re: [Qemu-devel] [PATCH v2 00/17] Translation loop conversion for sh4/sparc/mips/s390x/openrisc/riscv targets

On 04/10/2018 03:03 PM, Emilio G. Cota wrote: > On Tue, Apr 10, 2018 at 14:24:23 +1000, Richard Henderson wrote: >> On 04/10/2018 02:11 AM, Emilio G. Cota wrote: >>> On Mon, Apr 09, 2018 at 16:01:36 +0200, Bastian Koppelmann wrote: Thanks for doing this grunt work. Me and a colleague were

[Qemu-devel] [PATCH] timer: fix record/replay timerlist probe

Ciro Santilli reported that commit a5ed352596a8b7eb2f9acce34371b944ac3056c4 breaks the execution replay. It happens due to the probing the clock for the new instances of iothread. Probing of the timerlists' clock instead of using them for the deadlines calculation is critical for the replay.

Re: [Qemu-devel] [PATCH v2 1/2 for-2.12?] qapi: Parameter gl of DisplayType now accept an enum

On 04/10/2018 07:02 AM, Elie Tournier wrote: > Signed-off-by: Elie Tournier > --- > qapi/ui.json | 21 - > vl.c | 10 +- > 2 files changed, 25 insertions(+), 6 deletions(-) > > diff --git a/qapi/ui.json b/qapi/ui.json > index

Re: [Qemu-devel] [PULL 0/6] Net patches

On 10 April 2018 at 04:39, Jason Wang wrote: > The following changes since commit 915d34c5f99b0ab91517c69f54272bfdb6ca2b32: > > Merge remote-tracking branch 'remotes/bonzini/tags/for-upstream' into > staging (2018-04-09 17:29:10 +0100) > > are available in the git

Re: [Qemu-devel] [PATCH for-2.12] fpu: Fix rounding mode for floatN_to_uintM_round_to_zero

Richard Henderson writes: > We incorrectly passed in the current rounding mode > instead of float_round_to_zero. > > Signed-off-by: Richard Henderson Oops, Reviewed-by: Alex Bennée > --- > > Found while

[Qemu-devel] [PULL 5/7] tests/boot-serial: Test the sam460ex board

From: Thomas Huth We've got a U-Boot firmware for this board in our repository, and the firmware prints some output to the serial console, so we can check this board in the boot-serial tester, too. Signed-off-by: Thomas Huth Signed-off-by: David Gibson

Re: [Qemu-devel] [PATCH v2 00/17] Translation loop conversion for sh4/sparc/mips/s390x/openrisc/riscv targets

On Tue, Apr 10, 2018 at 14:24:23 +1000, Richard Henderson wrote: > On 04/10/2018 02:11 AM, Emilio G. Cota wrote: > > On Mon, Apr 09, 2018 at 16:01:36 +0200, Bastian Koppelmann wrote: > >> Thanks for doing this grunt work. Me and a colleague were planning to do > >> this as well after converting

Re: [Qemu-devel] [PATCH v2 0/2] Use SDL to create an OpenGL ES context for virglrenderer.

Hi, This series seems to have some coding style problems. See output below for more information: Type: series Message-id: 20180410120222.31845-1-tournier.e...@gmail.com Subject: [Qemu-devel] [PATCH v2 0/2] Use SDL to create an OpenGL ES context for virglrenderer. === TEST SCRIPT BEGIN ===

[Qemu-devel] [PULL 7/7] roms/u-boot-sam460ex: Change to qemu git mirror and update

From: BALATON Zoltan Now that we have a mirror of this repo on git.qemu.org change the submodule to use that and update it to latest commit which fixes a dangling symlink and removes two big binaries that are not needed. Signed-off-by: BALATON Zoltan

Re: [Qemu-devel] [PATCH v2 17/17] target/riscv: convert to TranslatorOps

On Tue, Apr 10, 2018 at 11:24:37 +1000, Richard Henderson wrote: > On 04/07/2018 04:20 AM, Emilio G. Cota wrote: > > +next_page = (ctx->base.pc_first & TARGET_PAGE_MASK) + > > TARGET_PAGE_SIZE; > > +if (ctx->base.pc_next >= next_page) { > > This fails for the last page of the

[Qemu-devel] [PULL 3/7] target/ppc: Fix backwards migration of msr_mask

21b786f "PowerPC: Add TS bits into msr_mask" added the transaction states to msr_mask for recent POWER CPUs to allow correct migration of machines that are in certain interim transactional memory states. This was correct, but unfortunately breaks backwards of pseries-2.7 and earlier machine types

[Qemu-devel] [PULL 4/7] spapr: Initialize reserved areas list in FDT in H_CAS handler

From: Alexey Kardashevskiy At the moment the device tree produced by the H_CAS handler has no reserved map initialized at all which is not correct as at least one empty record is required to be present as a marker of the end. This does not cause problems now as the only consumer

Re: [Qemu-devel] [PATCH for-2.12] commit/stream: Reset delay_ns

On 04/10/2018 03:58 AM, Kevin Wolf wrote: > Streaming and the commit block job only want to apply throttling when > they actually copied data instead of skipping it, so they made the > calculation of delay_ns conditional. However, delay_ns isn't reset when > skipping some sectors, so instead of

Re: [Qemu-devel] [PATCH for-2.12] linux-user/signal.c: Ensure AArch64 signal frame isn't too small

On 9 April 2018 at 23:05, Richard Henderson wrote: > On 04/10/2018 12:07 AM, Peter Maydell wrote: >> In particular the dash shell >> would segfault if the frame wasn't as big enough. > > Ah, that was the critical difference in my failure to replicate -- the fedora > sysroot

[Qemu-devel] [PULL 2/7] hw/misc/macio: Fix crash when listing device properties of macio device

From: Thomas Huth The macio-newworld device can currently be used to abort QEMU unexpectedly: $ ppc-softmmu/qemu-system-ppc -S -M ref405ep,accel=qtest -qmp stdio {"QMP": {"version": {"qemu": {"micro": 50, "minor": 11, "major": 2}, "package": "build-all"}, "capabilities": []}}

[Qemu-devel] [PULL 0/7] ppc-for-2.12 queue 20180410

The following changes since commit 915d34c5f99b0ab91517c69f54272bfdb6ca2b32: Merge remote-tracking branch 'remotes/bonzini/tags/for-upstream' into staging (2018-04-09 17:29:10 +0100) are available in the Git repository at: git://github.com/dgibson/qemu.git tags/ppc-for-2.12-20180410

[Qemu-devel] [PULL 6/7] sam460ex: Fix timer frequency and clock multipliers

From: BALATON Zoltan We only emulate timer running at CPU frequency which is what most guests expect so set the frequency to match real hardware. This also allows setting clock multipliers which caused slowdown previously due to wrong timer frequency. Signed-off-by: BALATON

[Qemu-devel] [PULL 1/7] target/ppc: Initialize lazy_tlb_flush correctly

ppc_tr_init_disas_context() correctly sets lazy_tlb_flush to true on certain CPU models. However, it leaves it uninitialized, instead of setting it to false on all others. It wasn't caught before now because we didn't have examples in the tests that exercised this path. However it can now be

[Qemu-devel] [PATCH 2/2] qemu-thread: let cur_mon be per-thread

cur_mon was only used in main loop so we don't really need that to be per-thread variable. Now it's possible that we have more than one thread to operate on it. Let's start to let it be per-thread variable. In case we'll create threads within a valid cur_mon setup, we'd better let the child

[Qemu-devel] [PATCH 0/2] qemu-thread: allow cur_mon be per thread

This should be for 2.13. But I'd like to get early review comments too if there is any. Now cur_mon is still only be accessed by the main thread. So we don't even need per-thread cur_mon. However after more commands become OOB compatible, cur_mon can be accessed by more than main thread now.

[Qemu-devel] [PATCH 1/2] qemu-thread: always keep the posix wrapper layer

We will conditionally have a wrapper layer depending on whether the host has the PTHREAD_SETNAME capability. It complicates stuff. Let's just keep the wrapper there, meanwhile we opt out the pthread_setname_np() call only. The layer can be helpful in future patches to pass data from the parent

Re: [Qemu-devel] [PATCH for-2.12 v2] monitor: bind dispatch bh to iohandler context

On 04/10/2018 12:01 AM, Stefan Hajnoczi wrote: > On Tue, Apr 10, 2018 at 12:49:42PM +0800, Peter Xu wrote: >> Eric Auger reported the problem days ago that OOB broke ARM when running >> with libvirt: >> >> http://lists.gnu.org/archive/html/qemu-devel/2018-03/msg06231.html >> >> The problem was

Re: [Qemu-devel] [PATCH v2 2/2] sdl: Allow OpenGL ES context creation

On Tue, Apr 10, 2018 at 01:02:22PM +0100, Elie Tournier wrote: > Signed-off-by: Elie Tournier > --- > include/ui/sdl2.h | 1 + > qemu-options.hx | 2 +- > ui/sdl2-gl.c | 17 +++-- > ui/sdl2.c | 1 + > vl.c | 4 > 5

Re: [Qemu-devel] [PATCH v2 1/2] qapi: Parameter gl of DisplayType now accept an enum

> -if (dpy.has_gl && dpy.gl && display_opengl == 0) { > +if (dpy.has_gl && !dpy.gl == DISPLAYGL_MODE_OFF && display_opengl == 0) { That should be "... && !(dpy.gl == DISPLAYGL_MODE_OFF) && ..." to work correctly. Or just "dpy.gl != DISPLAYGL_MODE_OFF" ... cheers, Gerd

Re: [Qemu-devel] [PATCH] qemu-iotests: Remove _supported_fmt dmg

On 04/10/2018 03:42 AM, Kevin Wolf wrote: > qemu-iotests doesn't support dmg, and the dmg block driver doesn't > support image creation. Two test cases declare dmg as supported, but > that's obviously wrong for both reasons. Remove the declaration. > > Signed-off-by: Kevin Wolf

[Qemu-devel] [PULL 06/12] hw/arm/allwinner-a10: Do not use nd_table in instance_init function

From: Thomas Huth The instance_init function of a device can be called at any time, even if the device is not going to be used (i.e. not going to be realized). So a instance_init function must not do things that could cause QEMU to exit, like calling

[Qemu-devel] [PULL 01/12] hw/arm: Allow manually specified /psci node

From: Andrey Smirnov Change the code to avoid exiting QEMU if user provided DTB contains manually specified /psci node and skip any /psci related fixups instead. Fixes: 4cbca7d9b4 ("hw/arm: Move virt's PSCI DT fixup code to arm/boot.c") Signed-off-by: Andrey Smirnov

Re: [Qemu-devel] [PATCH] migration: Don't activate block devices if using -S

Am 10.04.2018 um 12:40 hat Dr. David Alan Gilbert geschrieben: > * Kevin Wolf (kw...@redhat.com) wrote: > > Am 10.04.2018 um 10:45 hat Dr. David Alan Gilbert geschrieben: > > > * Kevin Wolf (kw...@redhat.com) wrote: > > > > Am 10.04.2018 um 09:36 hat Jiri Denemark geschrieben: > > > > > On Mon,

[Qemu-devel] [PULL 02/12] hw/arm/integratorcp: Don't do things that could be fatal in the instance_init

From: Thomas Huth An instance_init function must not fail - and might be called multiple times, e.g. during device introspection with the 'device-list-properties' QMP command. Since the integratorcm device ignores this rule, QEMU currently aborts in this case (though it really

[Qemu-devel] [PULL 03/12] target-arm: Check undefined opcodes for SWP in A32 decoder

From: Onur Sahin Make sure we are not treating architecturally Undefined instructions as a SWP, by verifying the opcodes as per section A8.8.229 of ARMv7-A specification. Bits [21:20] must be zero for this to be a SWP or SWPB. We also choose to UNDEF for the

[Qemu-devel] [PULL 00/12] target-arm queue

in the Git repository at: git://git.linaro.org/people/pmaydell/qemu-arm.git tags/pull-target-arm-20180410 for you to fetch changes up to bd49e6027cbc207c87633c7add3ebd7d3474cd35: fpu: Fix rounding mode for floatN_to_uintM_round_to_zero (2018-04-10 13:02:26 +0100

[Qemu-devel] [PULL 05/12] hw/sd/bcm2835_sdhost: Don't raise spurious interrupts

The Linux bcm2835_sdhost driver doesn't work on QEMU, because our model raises spurious data interrupts. Our function bcm2835_sdhost_fifo_run() will flag an interrupt any time it is called with s->datacnt == 0, even if the host hasn't actually issued a data read or write command yet. This means

[Qemu-devel] [PULL 07/12] hw/arm/fsl-imx: Fix introspection problem with fsl-imx6 and fsl-imx7

From: Thomas Huth QEMU currently exits unexpectedly when trying to introspect the fsl-imx6 and fsl-imx7 devices on systems with many SMP CPUs: $ echo "{'execute':'qmp_capabilities'}"\ "{'execute':'device-list-properties',"\ " 'arguments':{'typename':'fsl,imx6'}}"

[Qemu-devel] [PULL 08/12] target/arm: Report unsupported MPU region sizes more clearly

Currently our PMSAv7 and ARMv7M MPU implementation cannot handle MPU region sizes smaller than our TARGET_PAGE_SIZE. However we report that in a slightly confusing way: DRSR[3]: No support for MPU (sub)region alignment of 9 bits. Minimum is 10 The problem is not the alignment of the region, but

[Qemu-devel] [PULL 12/12] fpu: Fix rounding mode for floatN_to_uintM_round_to_zero

From: Richard Henderson We incorrectly passed in the current rounding mode instead of float_round_to_zero. Signed-off-by: Richard Henderson Message-id: 20180410055912.934-1-richard.hender...@linaro.org Reviewed-by: Peter Maydell

[Qemu-devel] [PULL 11/12] tcg: Introduce tcg_set_insn_start_param

From: Richard Henderson The parameters for tcg_gen_insn_start are target_ulong, which may be split into two TCGArg parameters for storage in the opcode on 32-bit hosts. Fixes the ARM target and its direct use of tcg_set_insn_param, which would set the wrong

[Qemu-devel] [PULL 10/12] linux-user/signal.c: Ensure AArch64 signal frame isn't too small

The AArch64 signal frame design was extended for SVE in commit 8c5931de0ac77388096d79ceb, so that instead of having a fixed setup we now add various records to the frame, with some of them possibly overflowing into an extra space outside the original 4K reserved block in the target_sigcontext.

[Qemu-devel] [PULL 04/12] hw/sd/bcm2835_sdhost: Add tracepoints

Add some tracepoints to the bcm2835_sdhost driver, to assist debugging. Signed-off-by: Peter Maydell Reviewed-by: Philippe Mathieu-Daudé Tested-by: Gerd Hoffmann Message-id: 20180319161556.16446-2-peter.mayd...@linaro.org ---

[Qemu-devel] [PULL 09/12] cpus.c: ensure running CPU recalculates icount deadlines on timer expiry

When we run in TCG icount mode, we calculate the number of instructions to execute using tcg_get_icount_limit(), which ensures that we stop execution at the next timer deadline. However there is a bug where currently we do not recalculate that limit if the guest reprograms a timer so that the next

Re: [Qemu-devel] [qemu RFC] qapi: add "firmware.json"

On 04/10/18 12:20, Daniel P. Berrangé wrote: > On Sat, Apr 07, 2018 at 02:01:17AM +0200, Laszlo Ersek wrote: >> +{ 'struct' : 'SystemFirmware', >> + 'data' : { 'executable' : 'FirmwareFile', >> + 'type' : 'SystemFirmwareType', >> +

[Qemu-devel] [PATCH v2 2/2] sdl: Allow OpenGL ES context creation

Signed-off-by: Elie Tournier --- include/ui/sdl2.h | 1 + qemu-options.hx | 2 +- ui/sdl2-gl.c | 17 +++-- ui/sdl2.c | 1 + vl.c | 4 5 files changed, 22 insertions(+), 3 deletions(-) diff --git a/include/ui/sdl2.h

[Qemu-devel] [PATCH v2 1/2] qapi: Parameter gl of DisplayType now accept an enum

Signed-off-by: Elie Tournier --- qapi/ui.json | 21 - vl.c | 10 +- 2 files changed, 25 insertions(+), 6 deletions(-) diff --git a/qapi/ui.json b/qapi/ui.json index 5d01ad4304..c8005867e5 100644 --- a/qapi/ui.json +++

[Qemu-devel] [PATCH v2 0/2] Use SDL to create an OpenGL ES context for virglrenderer.

Hello everyone, I submitted the v1 of this series before kraxel's display system rework. Currently, virglrenderer [1] support OpenGL ES 2.0 on the guest side and OpenGL ES 3.0 on the host side. Thanks to this work, we are able to run QEMU on system that only support OpenGL ES. The support of

Re: [Qemu-devel] [qemu RFC] qapi: add "firmware.json"

On 04/10/18 11:55, Daniel P. Berrangé wrote: > On Tue, Apr 10, 2018 at 11:51:31AM +0200, Gerd Hoffmann wrote: Hmm, I'm wondering whenever it is useful to model things this way. It's not like you can actually configure things for -bios seabios.rom or -kernel uboot.elf. Only pflash

<    1   2   3   >