Some devices (like nvic in armv7m) are not accessable through
address_space_memory, therefore can not be tested with qtest.
Signed-off-by: Julia Suvorova
---
qtest.c | 39 ++-
1 file changed, 26 insertions(+), 13 deletions(-)
diff --git a/qtest.c b/qtest.c
in
On Fri, 06/29 17:04, John Snow wrote:
> Mine was indeed inspired by Fam's version, but I opted to rewrite it
> instead of continue with the python unit tests approach. This is why I
> lost the commit message, existing copyright text, etc.
>
> I can re-add him as author credit to my version, or at
virtio-rng device causing old guest kernels(2.6.32) to hang on latest qemu.
The driver attempts to read from the virtio-rng device too early in it's
initialization. Qemu detects guest is not ready and returns, resulting in
hang.
Fix is to handle pending request when guest is running and drive
"Dr. David Alan Gilbert" writes:
> * Markus Armbruster (arm...@redhat.com) wrote:
>> "Dr. David Alan Gilbert" writes:
>>
>> > * Markus Armbruster (arm...@redhat.com) wrote:
>> >> Markus Armbruster writes:
>> >>
>> >> > Andreas Färber writes:
>> >> >
>> >> >> Am 08.06.2018 um 11:41 schrieb Dr
On Fri, 06/29 12:24, Eric Blake wrote:
> On 06/29/2018 10:15 AM, Vladimir Sementsov-Ogievskiy wrote:
> > We need to synchronize backup job with reading from fleecing image
> > like it was done in block/replication.c.
> >
> > Otherwise, the following situation is theoretically possible:
> >
>
> G
virtio-rng device causing old guest kernels(2.6.32) to hang on latest qemu.
The driver attempts to read from the virtio-rng device too early in it's
initialization. Qemu detects guest is not ready and returns, resulting in
hang.
Fix is to handle pending request when guest is running and drive
On Thu, Jun 28, 2018 at 10:14:53PM +1000, Benjamin Herrenschmidt wrote:
> On Thu, 2018-06-28 at 10:00 +0200, Andrea Bolognani wrote:
> > On Thu, 2018-06-28 at 13:59 +1000, David Gibson wrote:
> > > On Wed, Jun 27, 2018 at 12:22:31PM +0200, Andrea Bolognani wrote:
> > > > On Tue, 2018-06-26 at 19:02
On Sun, 07/01 07:58, no-re...@patchew.org wrote:
> /var/tmp/patchew-tester-tmp-x_t1hkpk/src/block/file-posix.c:1853:13: error:
> redefinition of ‘raw_aio_attach_aio_context’
> static void raw_aio_attach_aio_context(BlockDriverState *bs,
> ^~
> /var/tmp/patchew
On Fri, Jun 29, 2018 at 11:48:40AM +0200, Greg Kurz wrote:
> It is currently not possible to run a pseries-2.12 or older machine
> with HV KVM. QEMU prints the following and exits right away.
>
> qemu-system-ppc64: KVM doesn't support for base page shift 34
>
> The "hpt-max-page-size" capability
On Fri, Jun 29, 2018 at 11:48:32AM +0200, Greg Kurz wrote:
11;rgb://> In a future patch the machine code will need to retrieve
the MMU
> information from KVM during machine initialization before the CPUs
> are created.
>
> Actually, KVM_PPC_GET_SMMU_INFO is a VM class ioctl, and thus,
On Fri, Jun 29, 2018 at 11:48:16AM +0200, Greg Kurz wrote:
> Now that we're checking our MMU configuration is supported by KVM,
> rather than adjusting it to KVM, it doesn't really make sense to
> have a fallback for kvm_get_smmu_info(). If KVM is too old or buggy
> to provide the details, we shoul
> From: Emilio G. Cota [mailto:c...@braap.org]
> On Fri, Jun 29, 2018 at 10:25:03 +0300, Pavel Dovgalyuk wrote:
> > This patch breaks record/replay.
> >
> > I run execution recording of the WindowsXP machine with the following
> > script:
> >
> > ./bin/qemu-system-i386 -d in_asm,exec -D xp_save.lo
More lose ends:
* scripts/qmp/ doesn't support OOB, yet. qmp-shell.py in particular
* test-qmp-cmds neglects to cover the OOB additions to qmp-dispatch.c
On Mon, Jul 02, 2018 at 02:02:39PM +1000, David Gibson wrote:
> On Sat, Jun 30, 2018 at 01:29:05PM +0200, BALATON Zoltan wrote:
> 11;rgb://> On Sat, 30 Jun 2018, David Gibson wrote:
> > > On Fri, Jun 29, 2018 at 08:06:10PM +0200, Sebastian Bauer wrote:
> > > > Hi,
> > > >
> > > > Am 20
Hi,
This series failed docker-mingw@fedora build test. Please find the testing
commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
Type: series
Message-id: 20180625110706.23332-1-sam...@daynix.com
Subject: [Qemu-devel] [RFC v2 0/2] Add BPF suupor
>
> On Wed, Jun 27, 2018 at 04:55:20PM +0530, Pankaj Gupta wrote:
> > +static void virtio_rng_set_status(VirtIODevice *vdev, uint8_t status)
> > +{
> > +VirtIORNG *vrng = VIRTIO_RNG(vdev);
> > +
> > +if (!vdev->vm_running) {
> > +return;
> > +}
> > +vdev->status = status;
On 2018-07-02 05:40, Jason Wang wrote:
>
>
> On 2018年06月30日 14:13, Jan Kiszka wrote:
>> On 2018-04-05 19:41, Jan Kiszka wrote:
>>> From: Jan Kiszka
>>>
>>> Only signal MSI/MSI-X events on rising edges. So far we re-triggered the
>>> interrupt sources even if the guest did no consumed the pending
[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/1312668
Title:
x86 cpu nx
[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/1314667
Title:
PMPrebUSB -
[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/1315257
Title:
QEMU get bl
[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/1305400
Title:
qmp-version
On Fri, Jun 29, 2018 at 04:08:22PM -0300, Eduardo Habkost wrote:
> On Thu, Jun 28, 2018 at 12:15:14PM +0200, Greg Kurz wrote:
> [...]
> > @@ -2527,6 +2527,18 @@ static void spapr_machine_init(MachineState *machine)
> > QLIST_INIT(&spapr->phbs);
> > QTAILQ_INIT(&spapr->pending_dimm_unplugs
On Sat, Jun 30, 2018 at 01:29:05PM +0200, BALATON Zoltan wrote:
11;rgb://> On Sat, 30 Jun 2018, David Gibson wrote:
> > On Fri, Jun 29, 2018 at 08:06:10PM +0200, Sebastian Bauer wrote:
> > > Hi,
> > >
> > > Am 2018-06-19 06:36, schrieb David Gibson:
> > > > Ok. However, your patch doe
On Fri, Jun 29, 2018 at 02:04:33PM +0200, BALATON Zoltan wrote:
> PPC440 SoCs such as the AMCC 460EX have a DMA controller which is used
> by AmigaOS on the sam460ex. Implement the parts used by AmigaOS so it
> can get further booting on the sam460ex machine.
>
> Signed-off-by: BALATON Zoltan
Ap
On Fri, Jun 29, 2018 at 02:47:32PM +1000, David Gibson wrote:
> On Fri, Jun 29, 2018 at 12:38:33AM +0200, BALATON Zoltan wrote:
> > The Sam460ex has an M41T80 serial RTC chip on I2C bus 0 at address 0x68.
> >
> > Signed-off-by: BALATON Zoltan
> > Reviewed-by: Cédric Le Goater
>
> With Cédric's
On Sun, Jul 01, 2018 at 07:19:53PM +0200, Cédric Le Goater wrote:
> When a PCI device is unplugged, the PCI memory regions are deleted
> before the optional ROM RAMBlock is flagged non-migratable. But, when
> this is done, the RAMBlock has already been cleared from the region,
> leading to a segv.
On 2018年06月30日 14:13, Jan Kiszka wrote:
On 2018-04-05 19:41, Jan Kiszka wrote:
From: Jan Kiszka
Only signal MSI/MSI-X events on rising edges. So far we re-triggered the
interrupt sources even if the guest did no consumed the pending one,
easily causing interrupt storms.
Issue was observabl
Hi,
This series seems to have some coding style problems. See output below for
more information:
Type: series
Message-id: 20180627111925.30292-1-kra...@redhat.com
Subject: [Qemu-devel] [PATCH] audio/hda: adjust larger gaps faster
=== TEST SCRIPT BEGIN ===
#!/bin/bash
BASE=base
n=1
total=$(git l
Reported-by: Max Reitz
Signed-off-by: Fam Zheng
---
block/qcow2.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/block/qcow2.c b/block/qcow2.c
index 3177c72de0..1a2e498a3c 100644
--- a/block/qcow2.c
+++ b/block/qcow2.c
@@ -3292,7 +3292,6 @@ qcow2_co_copy_range_from(BlockDriverState *bs,
One of them is a typo. But update both to be more readable.
Reported-by: Kevin Wolf
Signed-off-by: Fam Zheng
---
block/file-posix.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/block/file-posix.c b/block/file-posix.c
index 829ee538d8..e04e464e72 100644
--- a/block/file-po
Reported-by: Max Reitz
Signed-off-by: Fam Zheng
---
block/raw-format.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/block/raw-format.c b/block/raw-format.c
index b78da564d4..8e648a5666 100644
--- a/block/raw-format.c
+++ b/block/raw-format.c
@@ -177,7 +177,7 @@ static inli
These are the low priority ones spotted by Kevin and Max last week.
Fam Zheng (4):
qcow2: Drop unused cluster_data
file-posix: Fix fd_open check in raw_co_copy_range_to
qcow2: Drop unreachable break
raw: Drop superfluous semicolon
block/file-posix.c | 2 +-
block/qcow2.c | 3 ---
bl
Reported-by: Max Reitz
Signed-off-by: Fam Zheng
---
block/qcow2.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/block/qcow2.c b/block/qcow2.c
index 2f9e58e0c4..3177c72de0 100644
--- a/block/qcow2.c
+++ b/block/qcow2.c
@@ -3338,7 +3338,6 @@ qcow2_co_copy_range_to(BlockDriverState *bs,
Hi,
This series seems to have some coding style problems. See output below for
more information:
Type: series
Message-id: 20180625111935.26108-1-alex.ben...@linaro.org
Subject: [Qemu-devel] [PATCH v1 00/10] Travis updates and code coverage tweaks
=== TEST SCRIPT BEGIN ===
#!/bin/bash
BASE=base
Hi,
This series seems to have some coding style problems. See output below for
more information:
Type: series
Message-id: 20180629205232.27190-1-alex.ben...@linaro.org
Subject: [Qemu-devel] [PATCH v2 00/21] Travis, Code Coverage and Cross Build
updates
=== TEST SCRIPT BEGIN ===
#!/bin/bash
BAS
Hi,
This series seems to have some coding style problems. See output below for
more information:
Type: series
Message-id: 1530312483-23864-1-git-send-email-akrow...@linux.vnet.ibm.com
Subject: [Qemu-devel] [PATCH v6 0/5] s390x: vfio-ap: guest dedicated crypto
adapters
=== TEST SCRIPT BEGIN ===
Hi,
This series seems to have some coding style problems. See output below for
more information:
Type: series
Message-id: 20180628030330.15615-1-richard.hender...@linaro.org
Subject: [Qemu-devel] [PATCH v3 00/23] target/openrisc improvements
=== TEST SCRIPT BEGIN ===
#!/bin/bash
BASE=base
n=1
t
Hi,
This series seems to have some coding style problems. See output below for
more information:
Type: series
Message-id: 20180627205317.10343-1-laur...@vivier.eu
Subject: [Qemu-devel] [PATCH 0/3] linux-user: manage binfmt F flag
=== TEST SCRIPT BEGIN ===
#!/bin/bash
BASE=base
n=1
total=$(git l
Hi,
This series seems to have some coding style problems. See output below for
more information:
Type: series
Message-id: 20180629124052.331406-1-dplotni...@virtuozzo.com
Subject: [Qemu-devel] [PATCH v0 0/2] Postponed actions
=== TEST SCRIPT BEGIN ===
#!/bin/bash
BASE=base
n=1
total=$(git log -
Hi,
This series seems to have some coding style problems. See output below for
more information:
Type: series
Message-id: 1530098844-236851-1-git-send-email-robert...@linux.intel.com
Subject: [Qemu-devel] [PATCH v2 0/5] Add Icelake CPU model
=== TEST SCRIPT BEGIN ===
#!/bin/bash
BASE=base
n=1
t
Hi,
This series seems to have some coding style problems. See output below for
more information:
Type: series
Message-id: 20180626143538.5390-1-alex.ben...@linaro.org
Subject: [Qemu-devel] [PATCH] blogposts: add post about the new check-tcg
infrastructure
=== TEST SCRIPT BEGIN ===
#!/bin/bash
Hi,
This series seems to have some coding style problems. See output below for
more information:
Type: series
Message-id: 20180625203559.21370-1-laur...@vivier.eu
Subject: [Qemu-devel] [PATCH 0/1] target/m68k: correctly disassemble move16
=== TEST SCRIPT BEGIN ===
#!/bin/bash
BASE=base
n=1
tota
Hi,
This series seems to have some coding style problems. See output below for
more information:
Type: series
Message-id: 20180630030606.17288-1-programmingk...@gmail.com
Subject: [Qemu-devel] [PATCH v2] fix fdiv instruction
=== TEST SCRIPT BEGIN ===
#!/bin/bash
BASE=base
n=1
total=$(git log --
On 07/01/2018 09:49 PM, xinhua.Cao wrote:
> In the tcp_chr_write function, we checked errno,
> but errno was not reset before a read or write operation.
> Therefore, this check of errno's actions is often
> incorrect after EAGAIN has occurred.
> We reset errno before reading and writing to
> ensure
qemu_log_mask(GUEST_ERROR) is more appropriate:
$ qemu -d help
Log items (comma separated):
guest_errorslog when the guest OS does something invalid (eg accessing a
non-existent register)
Signed-off-by: Philippe Mathieu-Daudé
---
v2: do not remove "qemu/error-report.h" (patchew)
hw/
In the tcp_chr_write function, we checked errno,
but errno was not reset before a read or write operation.
Therefore, this check of errno's actions is often
incorrect after EAGAIN has occurred.
We reset errno before reading and writing to
ensure the correctness of errno's judgment
Signed-off-by: x
On Fri, 2018-06-29 at 16:29 +1000, David Gibson wrote:
> On Fri, Jun 29, 2018 at 04:20:24PM +1000, Suraj Jitindar Singh wrote:
> > The kernel patch
> > "powerpc/64s: Add support for a store forwarding barrier at kernel
> > entry/exit"
> > adds an eieio barrier instruction to kernel entry and exit p
On Fri, Jun 29, 2018 at 02:14:49PM +0200, BALATON Zoltan wrote:
> On Fri, 29 Jun 2018, David Gibson wrote:
> > On Fri, Jun 29, 2018 at 02:48:40PM +1000, David Gibson wrote:
> > > On Fri, Jun 29, 2018 at 12:38:33AM +0200, BALATON Zoltan wrote:
> > > > PPC440 SoCs such as the AMCC 460EX have a DMA co
On Jul 1, 2018, at 3:30 PM, Peter Maydell wrote:
> On 19 June 2018 at 02:58, John Arbuckle wrote:
>> When the user pushes Command-F in QEMU while the mouse is ungrabbed, QEMU
>> goes into full screen mode. When the user finally releases the command key,
>> it is sent to the guest as an event.
>
Alex Bennée writes:
> Use our new ability to use linux-user powered docker images to build
> ppc-softmmu.
>
> Signed-off-by: Alex Bennée
> ---
> .shippable.yml | 8
> 1 file changed, 8 insertions(+)
>
> diff --git a/.shippable.yml b/.shippable.yml
> index f74a3de3ff..12f9d3b221 10064
Le 28/06/2018 à 05:46, Philippe Mathieu-Daudé a écrit :
> Signed-off-by: Philippe Mathieu-Daudé
> Tested-By: Guido Günther
> ---
> linux-user/strace.c| 13 +
> linux-user/strace.list | 4 ++--
> 2 files changed, 15 insertions(+), 2 deletions(-)
>
> diff --git a/linux-user/strac
+cc Richard
On Mon, Jul 2, 2018, 3:30 AM Davidson Francis
wrote:
> Hello,
>
> Thanks for working on this, your tree works fine here and the issue
> seems to be fixed, I have nothing to complain about.
>
Great news.
-Stafford
Regards,
> Davidson Francis.
>
> On 01-07-2018 05:18, Stafford Ho
Le 28/06/2018 à 05:46, Philippe Mathieu-Daudé a écrit :
> Suggested-by: Laurent Vivier
> Signed-off-by: Philippe Mathieu-Daudé
> ---
> linux-user/strace.c | 20
> 1 file changed, 20 insertions(+)
>
> diff --git a/linux-user/strace.c b/linux-user/strace.c
> index bd897a3f20.
On 19 June 2018 at 02:58, John Arbuckle wrote:
> When the user pushes Command-F in QEMU while the mouse is ungrabbed, QEMU
> goes into full screen mode. When the user finally releases the command key,
> it is sent to the guest as an event.
What is "it" here? This sentences implies that "it" is th
On 8 June 2018 at 21:01, John Arbuckle wrote:
> Fix the cocoa front-end to correctly be able to use absolute mode.
>
> Signed-off-by: John Arbuckle
> case NSEventTypeMouseMoved:
> if (isAbsoluteEnabled) {
> -if (![self screenContainsPoint:p] || ![[self windo
On 18 June 2018 at 23:24, Programmingkid wrote:
> When using an usb-tablet device in QEMU, the Cocoa UI uses absolute
>mode code to handle mouse events. The absolute mode code does not
>correctly determine where QEMU's window is located. Tests indicate
>the current code thinks the window is locate
On Sun, Jun 17, 2018 at 4:40 AM, Doug Gale wrote:
> Correct the output of the "info mem" and "info tlb" monitor commands to
> correctly show canonical addresses.
>
> In 48-bit addressing mode, the upper 16 bits of linear addresses are
> equal to bit 47. In 57-bit addressing mode (LA57), the upper
Hello,
Thanks for working on this, your tree works fine here and the issue
seems to be fixed, I have nothing to complain about.
Regards,
Davidson Francis.
On 01-07-2018 05:18, Stafford Horne wrote:
Hello,
We have been working on a few patches to fixed QEMU for OpenRISC and I
included the chan
When a PCI device is unplugged, the PCI memory regions are deleted
before the optional ROM RAMBlock is flagged non-migratable. But, when
this is done, the RAMBlock has already been cleared from the region,
leading to a segv.
Fix the issue by testing the RAMBlock before flagging it, as it is
done i
Hi,
This series failed build test on s390x host. Please find the details below.
Type: series
Message-id: 20180627144838.26772-1-stefa...@redhat.com
Subject: [Qemu-devel] [PULL 0/2] Block patches
=== TEST SCRIPT BEGIN ===
#!/bin/bash
# Testing script will be invoked under the git checkout with
#
On 07/01/2018 01:12 AM, Stafford Horne wrote:
> The interrupt controller mask register (PICMR) allows writing any value
> to any of the 32 interrupt mask bits. Writing a 0 masks the interrupt
> writing a 1 unmasks (enables) the the interrupt.
>
> For some reason the old code was or'ing the write
On 06/30/2018 10:11 PM, Stafford Horne wrote:
> The delay slot exception flag is only set on the SR register during
> exception. Previously it was being set on both the ESR and SR this
> caused QEMU to differ from the spec. The was apparent as the linux
> kernel had a bug where it could boot on Q
On Tue, Jun 19, 2018 at 11:41:32AM -0400, Farhan Ali wrote:
> Hi,
>
> Currently the Linux virtio-crypto driver registers the crypto
> algorithm without verifying if the backend actually supports the
> algorithm.
>
> This kernel patch series adds support for registering algorithm
> with Linux cryp
On 30 June 2018 at 22:57, Jean-Christophe Dubois wrote:
> This series adds the i.MX6UL SOC from NXP/Freescale and the reference
> evaluation board.
>
> This series as tested by booting linux 4.18 (built using imx_v6_v7_defconfig)
> on the emulated board (with the appropriate device tree).
>
> Jean
On 30 June 2018 at 22:21, Max Filippov wrote:
> Hi Peter,
>
> please pull the following batch of updates for the target/xtensa.
>
> The following changes since commit e3800998e66c13b24d8cc8a06fdcc8d03cd408fc:
>
> Merge remote-tracking branch 'remotes/armbru/tags/pull-monitor-2018-06-30'
> into
Hello,
We have been working on a few patches to fixed QEMU for OpenRISC and I
included the change for picmr writes, richard added some changes to
SPR writes which might help with the masking/umasking work more
reliably.
If you want to try them out could you check:
https://github.com/stffrdhrn/
The interrupt controller mask register (PICMR) allows writing any value
to any of the 32 interrupt mask bits. Writing a 0 masks the interrupt
writing a 1 unmasks (enables) the the interrupt.
For some reason the old code was or'ing the write values to the PICMR
meaning it was not possible to ever
67 matches
Mail list logo
