It was a Yocto 2.0 sysroot running on an Ubuntu 16.04 host.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1709170
Title:
QEMU fails to honor O_TMPFILE
Status in QEMU:
New
Bug description:
On 08/08/2017 05:42 AM, Peter Maydell wrote:
> Switch the alpha target from the old unassigned_access hook
> to the new do_transaction_failed hook. This allows us to
> resolve a ??? in the old hook implementation.
>
> The only part of the alpha target that does physical
> memory accesses is
On 08/08/2017 05:13 PM, Eric Blake wrote:
> On 08/08/2017 03:53 PM, Cleber Rosa wrote:
>> Most QMP commands and returns in the QAPI schema documentation
>> are valid "JSON-based wire format". A few examples are either
>> malformed, or contain comments.
>>
>> This fixes all the examples command
On Tue, Aug 08, 2017 at 04:05:56PM -0500, Eric Blake wrote:
> On 08/08/2017 03:38 PM, Jens Freimann wrote:
> > This implements a testcase for pxe-test using the vhost-user interface.
> > Spawn a
> > vhost-user-bridge process and connect it to the qemu process.
> >
> > To make the testcase work
On Mon, Aug 7, 2017 at 7:07 AM, Eric Blake wrote:
> On 08/05/2017 01:52 PM, Pranith Kumar wrote:
>> FYI,
>>
>> This commit breaks the build with gcc-7:
>>
>> CC block/vvfat.o
>> qemu/block/vvfat.c: In function ‘read_directory’:
>> qemu/block/vvfat.c:605:37: error:
Hi,
This series seems to have some coding style problems. See output below for
more information:
Message-id: 20170808162629.32493-1-quint...@redhat.com
Subject: [Qemu-devel] [PATCH v6 00/19] Multifd
Type: series
=== TEST SCRIPT BEGIN ===
#!/bin/bash
BASE=base
n=1
total=$(git log --oneline
It turns out that my recent fix to set rip_offset when emulating some
SSE4.1 instructions needs generalizing to cover a wider class of
instructions. Specifically, every instruction in the sse_op_table7
table, coming from various instruction set extensions, has an 8-bit
immediate operand that
On Tue, Aug 08, 2017 at 04:24:01PM +1000, David Gibson wrote:
> On Mon, Aug 07, 2017 at 04:33:29PM +1000, Sam Bobroff wrote:
> > The concept of a VCPU ID that differs from the CPU's index
> > (cpu->cpu_index) exists only within SPAPR machines so, move the
> > functions ppc_get_vcpu_id() and
Hi,
This series seems to have some coding style problems. See output below for
more information:
Message-id: 1502124810-6930-1-git-send-email-dve...@redhat.com
Subject: [Qemu-devel] [PATCH v3 0/3] Vmstate-static-checker.py fix upstream
Type: series
=== TEST SCRIPT BEGIN ===
#!/bin/bash
Hi,
This series seems to have some coding style problems. See output below for
more information:
Message-id: 1502134806-13669-1-git-send-email-dve...@redhat.com
Subject: [Qemu-devel] [PATCH 0/3] Vmstate-static-checker.py fix upstream
Type: series
=== TEST SCRIPT BEGIN ===
#!/bin/bash
BASE=base
Hi,
This series seems to have some coding style problems. See output below for
more information:
Message-id: 20170808162224.32419-1-quint...@redhat.com
Subject: [Qemu-devel] [PATCH v6 00/19] Multifd
Type: series
=== TEST SCRIPT BEGIN ===
#!/bin/bash
BASE=base
n=1
total=$(git log --oneline
On 08/08/2017 03:53 PM, Cleber Rosa wrote:
> Most QMP commands and returns in the QAPI schema documentation
> are valid "JSON-based wire format". A few examples are either
> malformed, or contain comments.
>
> This fixes all the examples command and return data, making them
> proper JSON, as
qemu uses wheel-up/down button events for mouse wheel input, however
linux applications typically want REL_WHEEL events.
This fixes wheel with linux guests. Tested with X11/wayland, and
windows virtio-input driver.
Signed-off-by: Marc-André Lureau
---
On 08/08/2017 05:00 PM, Eric Blake wrote:
On 08/08/2017 01:32 PM, John Snow wrote:
Out with the old, in with the new.
Signed-off-by: John Snow
---
hw/ide/piix.c | 11
hw/ide/trace-events | 33
hw/ide/via.c
Hi,
This series failed automatic build test. Please find the testing commands and
their output below. If you have docker installed, you can probably reproduce it
locally.
Message-id: 20170808203900.7661-1-jfreim...@redhat.com
Subject: [Qemu-devel] [PATCH v2 0/5] tests/pxe-test: add testcase
"Dr. David Alan Gilbert (git)" wrote:
> From: "Dr. David Alan Gilbert"
>
> After migration the chain4 alias mapping added by 80763888 (in 2011)
> might be missing, since there's no call to vga_update_memory_access
> in the post_load after the registers
On 08/08/2017 09:00, Peter Xu wrote:
> We were calling rcu_init_complete() twice in the child processes when
> fork happened. However the pthread library does not really suggest to do
> it that way:
>
> http://pubs.opengroup.org/onlinepubs/7908799/xsh/pthread_mutex_init.html
>
> "Attempting to
On Tue, 8 Aug 2017 07:19:54 +0200
Thomas Huth wrote:
> On 07.08.2017 22:35, Michael S. Tsirkin wrote:
> > On Thu, Aug 03, 2017 at 03:30:19PM +0200, Thomas Huth wrote:
> >> Now that we've got a firmware that can do TFTP booting on s390x (i.e.
> >> the
Cleber Rosa writes:
> On 07/21/2017 08:33 AM, Stefan Hajnoczi wrote:
>> On Thu, Jul 20, 2017 at 11:47:27PM -0400, Cleber Rosa wrote:
>>> This is a follow up to a previous discussion about reported failures when
>>> running some qemu-iotests. Turns out the failures were due to
Tested-by: Hua Yanghao
On Mon, Aug 7, 2017 at 4:39 PM, Peter Maydell wrote:
> Some ELF files have program headers that specify segments that
> are of zero size. Ignore them, rather than trying to create
> zero-length ROM blobs for them, because
"Dr. David Alan Gilbert" wrote:
> * Juan Quintela (quint...@redhat.com) wrote:
>> Signed-off-by: Juan Quintela
>> Reviewed-by: Dr. David Alan Gilbert
>
> Note you need to update this; you need to add the
> DEFINE_PROP_MIG_CAP in
"Dr. David Alan Gilbert" wrote:
> * Juan Quintela (quint...@redhat.com) wrote:
>> Indicates the number of threads that we would create. By default we
>> create 2 threads.
>>
>> Signed-off-by: Juan Quintela
>> Reviewed-by: Dr. David Alan Gilbert
On 08/08/2017 08:08 AM, David Gibson wrote:
> This adds a trivial implementation of the TIDR register added in
> POWER9. This isn't particularly important to qemu directly - it's
> used by accelerator modules that we don't emulate.
>
> However, since qemu isn't aware of it, its state is not
On Tue, 8 Aug 2017 16:21:06 +1000
David Gibson wrote:
[...]
> > > >
> > > > Does it make sense at all to use compat mode with KVM_PR since it
> > > > requires hypervisor privilege, that we're supposed not to have ?
> > >
> > > Uh.. what? Availability of the PCR
On Tue, Aug 08, 2017 at 10:40:08AM +0200, Juan Quintela wrote:
> "Daniel P. Berrange" wrote:
> > On Mon, Jul 17, 2017 at 03:42:24PM +0200, Juan Quintela wrote:
> >> The functions waits until it is able to write the full iov.
> >>
> >> Signed-off-by: Juan Quintela
** Project changed: qemu => qemu (Ubuntu)
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1357226
Title:
qemu: uncaught target signal 11 (Segmentation fault) - core dumped
Status in qemu package in
On 08/08/2017 02:43, Joseph Myers wrote:
> When emulating various SSE4.1 instructions such as pinsrd, the address
> of a memory operand is computed without allowing for the 8-bit
> immediate operand located after the memory operand, meaning that the
> memory operand uses the wrong address in the
Am 03.08.2017 um 17:02 hat Kevin Wolf geschrieben:
> This is the first part of some fixes to bdrv_reopen(), which seems
> reasonable enough to merge for 2.10.
>
> There is much more wrong with bdrv_reopen() currently, especially with
> respect to op blocker permissions (basically the required
Plus:
1 GB hugepages neither improved bandwidth nor latency. Results remained the
same.
2017-08-08 9:44 GMT+08:00 Bob Chen :
> 1. How to test the KVM exit rate?
>
> 2. The switches are separate devices of PLX Technology
>
> # lspci -s 07:08.0 -nn
> 07:08.0 PCI bridge
Am 07.08.2017 um 22:30 hat Eric Blake geschrieben:
> vpc_open() was checking for bdrv_getlength() failure in one, but
> not the other, location.
>
> Reported-by: Markus Armbruster
> Signed-off-by: Eric Blake
> ---
> block/vpc.c | 9 -
> 1 file
"Dr. David Alan Gilbert" wrote:
> * Juan Quintela (quint...@redhat.com) wrote:
>> Creation of the threads, nothing inside yet.
>>
>> Signed-off-by: Juan Quintela
>> +MultiFDSendParams *p = _send_state->params[i];
>> +
>> +
We were calling rcu_init_complete() twice in the child processes when
fork happened. However the pthread library does not really suggest to do
it that way:
http://pubs.opengroup.org/onlinepubs/7908799/xsh/pthread_mutex_init.html
"Attempting to initialise an already initialised mutex results in
Am 07.08.2017 um 22:30 hat Eric Blake geschrieben:
> This also requires changing the return type of get_cluster_offset()
> and adjusting all callers.
>
> Use osdep.h macros instead of open-coded rounding while in the
> area.
>
> Reported-by: Markus Armbruster
> Signed-off-by:
Am 08.08.2017 um 10:42 hat Vladimir Sementsov-Ogievskiy geschrieben:
> 07.08.2017 18:57, Kevin Wolf wrote:
> > Am 07.08.2017 um 16:16 hat Vladimir Sementsov-Ogievskiy geschrieben:
> > > 185 iotest is broken.
> > >
> > > How to test:
> > > > i=0; while ./check -qcow2 -nocache 185; do ((i+=1));
Fam Zheng writes:
> On Mon, 08/07 16:39, Alex Bennée wrote:
>> While adding the current user is a useful default behaviour for
>> creating new images it is not appropriate for Travis which already has
>> a default user.
>
> Target docker-travis@travis will not have NOUSER=1
On Fri, 4 Aug 2017 16:59:34 +0200
Cornelia Huck wrote:
> On Fri, 4 Aug 2017 13:29:37 +0200
> Cornelia Huck wrote:
>
> > Next version, not so many changes from v3.
> >
> > As you might have guessed, the goals are still the same:
> > - Being able to
On Tue, Aug 08, 2017 at 10:39:29AM +0800, Fam Zheng wrote:
> On Fri, 08/04 16:49, Daniel P. Berrange wrote:
> > This is odd. In the bdrv_aligned_readv() it looks very much like
> > we'll reference qiov->niov, if bytes != 0, so if qiov was NULL we
> > would crash.
>
> It doesn't make sense if
Just back from the signed-vs-unsigned swamp, still catching up, sorry
for the delay...
Eric Blake writes:
> On 07/26/2017 07:09 AM, no-re...@patchew.org wrote:
>> Hi,
>>
>> This series failed build test on s390x host. Please find the details below.
>>
>> Message-id:
On 08.08.2017 11:15, Cornelia Huck wrote:
> On Fri, 4 Aug 2017 16:59:34 +0200
> Cornelia Huck wrote:
>
>> On Fri, 4 Aug 2017 13:29:37 +0200
>> Cornelia Huck wrote:
>>
>>> Next version, not so many changes from v3.
>>>
>>> As you might have guessed, the
Hi Thiago,
What is the version of glibc on the targets you are building to? There
was an O_TMPFILE bug in older glibc's:
https://sourceware.org/bugzilla/show_bug.cgi?id=17912
** Bug watch added: Sourceware.org Bugzilla #17912
https://sourceware.org/bugzilla/show_bug.cgi?id=17912
--
You
Triaging old bug tickets ... can you still reproduce this issue with the
latest version of QEMU?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
I'm forwarding this upstream.
It looks like the same issue is present in 2.10-tobe.
13.06.2017 16:01, Sjoerd Simons wrote:
> Package: qemu-system
> Version: 1:2.8+dfsg-6
> Severity: normal
>
> Hey,
>
> For $reasons i'm exposing /boot over a filesystem share with the host system,
> fsdev is
Am 07.08.2017 um 22:30 hat Eric Blake geschrieben:
> It's been #if 0'd since its introduction in 2006, commit 585f8587.
> We can revive dead code if we need it, but in the meantime, it has
> bit-rotted (for example, not checking for failure in bdrv_getlength()).
>
> Signed-off-by: Eric Blake
Am 07.08.2017 um 22:30 hat Eric Blake geschrieben:
> qcow2_co_pwritev_compressed() should not call bdrv_truncate()
> if determining the size failed.
>
> Reported-by: Markus Armbruster
> Signed-off-by: Eric Blake
Reviewed-by: Kevin Wolf
"Daniel P. Berrange" wrote:
> On Mon, Jul 17, 2017 at 03:42:24PM +0200, Juan Quintela wrote:
>> The functions waits until it is able to write the full iov.
>>
>> Signed-off-by: Juan Quintela
>>
>> --
>>
>> Add tests.
>> ---
>> include/io/channel.h
Fam Zheng writes:
> On Mon, 08/07 16:39, Alex Bennée wrote:
>> If you invoke with NOCACHE=1 we pass --no-cache in the argv to
>> docker.py but may still not force a rebuild if the dockerfile checksum
>> hasn't changed. By testing for its presence we can force builds
>> without
08.08.2017 11:53, Kevin Wolf wrote:
Am 08.08.2017 um 10:42 hat Vladimir Sementsov-Ogievskiy geschrieben:
07.08.2017 18:57, Kevin Wolf wrote:
Am 07.08.2017 um 16:16 hat Vladimir Sementsov-Ogievskiy geschrieben:
185 iotest is broken.
How to test:
i=0; while ./check -qcow2 -nocache 185; do
08.08.2017 12:04, Vladimir Sementsov-Ogievskiy wrote:
08.08.2017 11:53, Kevin Wolf wrote:
Am 08.08.2017 um 10:42 hat Vladimir Sementsov-Ogievskiy geschrieben:
07.08.2017 18:57, Kevin Wolf wrote:
Am 07.08.2017 um 16:16 hat Vladimir Sementsov-Ogievskiy geschrieben:
185 iotest is broken.
How
On 08/08/2017 08:08 AM, David Gibson wrote:
> The PSSCR register added in POWER9 controls certain power saving mode
> behaviours. Mostly, it's not relevant to TCG, however because qemu
> doesn't know about it yet, it doesn't synchronize the state with KVM,
> and thus it doesn't get migrated.
>
>
Peter Xu wrote:
> On Mon, Jul 17, 2017 at 03:42:30PM +0200, Juan Quintela wrote:
>
> [...]
>
>> int multifd_load_setup(void)
>> {
>> int thread_count;
>> -uint8_t i;
>>
>> if (!migrate_use_multifd()) {
>> return 0;
>> }
>> thread_count =
"Dr. David Alan Gilbert (git)" wrote:
> From: "Dr. David Alan Gilbert"
>
> There's a race if someone does a 'stop' near the end of migrate;
> the migration process goes through two runstates:
> 'finish migrate'
> 'postmigrate'
>
> If the user
On Tue, Aug 08, 2017 at 09:02:54AM +0200, Juan Quintela wrote:
> "Dr. David Alan Gilbert (git)" wrote:
> > From: "Dr. David Alan Gilbert"
> >
> > There's a race if someone does a 'stop' near the end of migrate;
> > the migration process goes through two
On Tue, Aug 08, 2017 at 09:26:43AM +0200, Paolo Bonzini wrote:
> On 08/08/2017 09:00, Peter Xu wrote:
> > We were calling rcu_init_complete() twice in the child processes when
> > fork happened. However the pthread library does not really suggest to do
> > it that way:
> >
> >
Stefan Hajnoczi writes:
> On Wed, Jul 26, 2017 at 02:24:02PM -0400, Cleber Rosa wrote:
>>
>>
>> On 07/26/2017 01:58 PM, Stefan Hajnoczi wrote:
>> > On Tue, Jul 25, 2017 at 12:16:13PM -0400, Cleber Rosa wrote:
>> >> On 07/25/2017 11:49 AM, Stefan Hajnoczi wrote:
>> >>> On
On 08/08/2017 09:49, Peter Xu wrote:
> On Tue, Aug 08, 2017 at 09:26:43AM +0200, Paolo Bonzini wrote:
>> On 08/08/2017 09:00, Peter Xu wrote:
>>> We were calling rcu_init_complete() twice in the child processes when
>>> fork happened. However the pthread library does not really suggest to do
>>>
07.08.2017 18:57, Kevin Wolf wrote:
Am 07.08.2017 um 16:16 hat Vladimir Sementsov-Ogievskiy geschrieben:
185 iotest is broken.
How to test:
i=0; while ./check -qcow2 -nocache 185; do ((i+=1)); echo N = $i; \
done; echo N = $i
finished for me like this:
185 2s ... - output mismatch (see
On Tue, 8 Aug 2017 16:16:36 +1000
David Gibson wrote:
> On Mon, Aug 07, 2017 at 07:25:03PM +0200, Greg Kurz wrote:
> > It is currently possible to start QEMU with two PHBs without using the
> > index property:
> >
> > -device spapr-pci-host-bridge,id=pci1,\
> >
This series adds a couple of new POWER9 SPRs: TIDR and PSSCR.
These aren't particularly complete implementations - the registers
aren't all that interesting from a TCG / qemu point of view. However
having them at least minimally represented means that state is synced
with KVM and migrated, which
Triaging old bug tickets ... can you still reproduce this issue with the
latest version of QEMU and the kernel, or did the patch mentioned in
comment #2 fix it?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml,
Triaging old bug tickets ... can you still reproduce this issue with the
latest version of QEMU and the kernel?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Triaging old bug tickets ... can you still reproduce this issue with the
latest version of QEMU?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Thanks for your reply
For some reason, I can't update my version. I believe the latest version have
fixed the problem in commit 3432a1929ee18e08787ce35476abd74f2c93a17c or
27a7649a48f9019fa5bd2998d8e342791397bdda. But I'm not sure the first patch
have fixed the problem, as the second patch is
On Mon, Aug 07, 2017 at 11:00:18AM +0200, Greg Kurz wrote:
> On Fri, 4 Aug 2017 12:35:30 +1000
> David Gibson wrote:
>
> > On Thu, Aug 03, 2017 at 07:28:06PM +0200, Greg Kurz wrote:
> > > On Thu, 13 Jul 2017 11:21:18 +1000
> > > David Gibson
On Mon, Aug 07, 2017 at 07:24:39PM +0200, Greg Kurz wrote:
> object_property_add_child() can only fail in two cases:
> - the child already has a parent, which shouldn't happen since the DRC was
> allocated a few lines above
> - the parent already has a child with the same name, which would mean
On Mon, Aug 07, 2017 at 07:25:03PM +0200, Greg Kurz wrote:
> It is currently possible to start QEMU with two PHBs without using the
> index property:
>
> -device spapr-pci-host-bridge,id=pci1,\
> buid=0x8002001,\
>
On Mon, Aug 07, 2017 at 04:33:29PM +1000, Sam Bobroff wrote:
> The concept of a VCPU ID that differs from the CPU's index
> (cpu->cpu_index) exists only within SPAPR machines so, move the
> functions ppc_get_vcpu_id() and ppc_get_cpu_by_vcpu_id() into spapr.c
> and rename them appropriately.
>
>
This adds a trivial implementation of the TIDR register added in
POWER9. This isn't particularly important to qemu directly - it's
used by accelerator modules that we don't emulate.
However, since qemu isn't aware of it, its state is not synchronized
with KVM and therefore not migrated, which
The PSSCR register added in POWER9 controls certain power saving mode
behaviours. Mostly, it's not relevant to TCG, however because qemu
doesn't know about it yet, it doesn't synchronize the state with KVM,
and thus it doesn't get migrated.
To fix that, this adds a minimal stub implementation of
Re-using the boot_sector code buffer from x86 for other architectures
is not very nice, especially if we add more architectures later. It's
also ugly that the test uses a huge pre-initialized array - the size
of the executable is very huge due to this array. So let's use a
separate buffer for each
On 08.08.2017 18:26, Greg Kurz wrote:
> On Tue, 8 Aug 2017 17:38:27 +0200
> Cornelia Huck wrote:
>
>> Nothing in fsdev/ or hw/9pfs/ depends on pci; it should rather depend
>> on CONFIG_VIRTFS and on the presence of an appropriate virtio transport
>> device.
>>
>> Let's
On 08/08/17 17:51, Laszlo Ersek wrote:
> On 08/08/17 12:39, Marcin Juszkiewicz wrote:
>> Anyway, beyond the things written in that comment, there is one very
>> interesting symptom that makes me think another (milder?) bottleneck
>> could be in QEMU:
>>
>> When having a large number of PCI(e)
The following changes since commit 54affb3a3623b1d36c95e34faa722a5831323a74:
Update version for v2.10.0-rc2 release (2017-08-08 19:07:46 +0100)
are available in the git repository at:
git://git.kernel.org/pub/scm/virt/kvm/mst/qemu.git tags/for_upstream
for you to fetch changes up to
From: Jens Freimann
End processing of messages when VHOST_USER_NONE
is received.
Without this we run into a vubr_panic() call and get
"PANIC: Unhandled request: 0"
Signed-off-by: Jens Freimann
Reviewed-by: Michael S. Tsirkin
From: Jens Freimann
This patch fixes -netdev socket,fd= for UDP sockets
Currently -netdev socket,fd=<...> results in
qemu: error: specified mcastaddr "127.0.0.1" (0x7f01) does not
contain a multicast address
qemu-system-x86_64: -netdev
socket,id=n1,fd=3:
Signed-off-by: Michael S. Tsirkin
---
tests/acpi-test-data/q35/DSDT| Bin 7782 -> 7782 bytes
tests/acpi-test-data/q35/DSDT.bridge | Bin 7799 -> 7799 bytes
tests/acpi-test-data/q35/DSDT.cphp | Bin 8245 -> 8245 bytes
tests/acpi-test-data/q35/DSDT.ipmibt | Bin 7857 ->
On Tue, Aug 08, 2017 at 09:09:23AM -0500, Eric Blake wrote:
> On 08/08/2017 02:49 AM, Peter Xu wrote:
> >> This doesn't work for error-checking mutexes: rcu_init_child has a
> >> different PID than the parent, so the mutexes aren't unlocked. It's
> >> also true that right now we don't use
On Tue, Aug 08, 2017 at 11:18:35AM +0200, Greg Kurz wrote:
> On Tue, 8 Aug 2017 16:16:36 +1000
> David Gibson wrote:
>
> > On Mon, Aug 07, 2017 at 07:25:03PM +0200, Greg Kurz wrote:
> > > It is currently possible to start QEMU with two PHBs without using the
> > >
The concept of a VCPU ID that differs from the CPU's index
(cpu->cpu_index) exists only within SPAPR machines so, move the
functions ppc_get_vcpu_id() and ppc_get_cpu_by_vcpu_id() into spapr.c
and rename them appropriately.
Signed-off-by: Sam Bobroff
---
Changes in v3:
Just the one minor change in this version.
Patch set changelog follows:
== Version 2 -> version 3: ==
Patch 1/1: ppc: spapr: Make VCPU ID handling private to SPAPR
* Implemented spapr_find_cpu() using spapr_vcpu_id() rather than direct access
to vcpu_id.
== Version 1 -> version
On Mon, Aug 07, 2017 at 10:56:59AM +0200, Ladi Prosek wrote:
> This is the QEMU part of the changes required for nested Hyper-V to read
> timestamps with RDTSC + TSC page. Without exposing the frequency MSRs,
> Windows with the Hyper-V role enabled use the much slower
> HV_X64_MSR_TIME_REF_COUNT
This reverts commit e2a7f28693aea7e194ec1435697ec4feb24f8a6f.
This was not supposed to go upstream yet. Reverting.
Signed-off-by: Michael S. Tsirkin
---
include/qom/cpu.h | 31 ---
qom/cpu.c | 34 --
2 files
From: Jens Freimann
Currently abort handlers only work for the first test function
in a testcase, because the list of abort handlers is not properly
cleared when qtest_quit() is called.
qtest_quit() only deletes the kill_qemu_hook but doesn't completely
clear the
On Wed, Aug 09, 2017 at 12:47:50AM +0200, Marc-André Lureau wrote:
> qemu uses wheel-up/down button events for mouse wheel input, however
> linux applications typically want REL_WHEEL events.
>
> This fixes wheel with linux guests. Tested with X11/wayland, and
> windows virtio-input driver.
>
>
On Wed, 9 Aug 2017 14:05:46 +1000
David Gibson wrote:
> On Wed, Aug 09, 2017 at 03:59:36AM +1000, Nicholas Piggin wrote:
> > Unicast H_SIGNAL_SYS_RESET does not find the target CPU if it
> > is not the current CPU.
> >
> > Signed-off-by: Nicholas Piggin
Hi,
This series seems to have some coding style problems. See output below for
more information:
Message-id: 20170808183306.27474-1-js...@redhat.com
Subject: [Qemu-devel] [PATCH 0/9] IDE: replace printfs with tracing
Type: series
=== TEST SCRIPT BEGIN ===
#!/bin/bash
BASE=base
n=1
total=$(git
On Tue, Aug 08, 2017 at 04:59:02PM -0700, no-re...@patchew.org wrote:
> Hi,
>
> This series failed automatic build test. Please find the testing commands and
> their output below. If you have docker installed, you can probably reproduce
> it
> locally.
>
> Message-id:
On Wed, Aug 09, 2017 at 10:02:44AM +1000, Sam Bobroff wrote:
> On Tue, Aug 08, 2017 at 04:24:01PM +1000, David Gibson wrote:
> > On Mon, Aug 07, 2017 at 04:33:29PM +1000, Sam Bobroff wrote:
> > > The concept of a VCPU ID that differs from the CPU's index
> > > (cpu->cpu_index) exists only within
On Wed, Aug 09, 2017 at 03:59:36AM +1000, Nicholas Piggin wrote:
> Unicast H_SIGNAL_SYS_RESET does not find the target CPU if it
> is not the current CPU.
>
> Signed-off-by: Nicholas Piggin
> ---
>
> Unfortunately this slipped through without my noticing because the
> Linux
The first patch improves the buffer handling in the pxe tester a
little bit by allocating a separate buffer on the heap for each
architecture. This also gets rid of the huge pre-initialized
array in the tester, shrinking the size of the executable by
half of a megabyte!
The second patch adds s390x
Now that we've got a firmware that can do TFTP booting on s390x (i.e.
the pc-bios/s390-netboot.img), we can enable the PXE tester for this
architecture, too.
Signed-off-by: Thomas Huth
---
tests/Makefile.include | 1 +
tests/boot-sector.c| 20
On Tue, Aug 08, 2017 at 01:40:08PM -0600, Alex Williamson wrote:
> On Thu, 27 Jul 2017 12:50:42 +0100
> "Daniel P. Berrange" wrote:
>
> > On Thu, Jul 27, 2017 at 08:53:48PM +1000, David Gibson wrote:
> > > On Thu, Jul 27, 2017 at 10:11:48AM +0100, Peter Maydell wrote:
> >
On Wed, Aug 09, 2017 at 03:07:19PM +1000, Nicholas Piggin wrote:
> On Wed, 9 Aug 2017 14:05:46 +1000
> David Gibson wrote:
>
> > On Wed, Aug 09, 2017 at 03:59:36AM +1000, Nicholas Piggin wrote:
> > > Unicast H_SIGNAL_SYS_RESET does not find the target CPU if it
> > >
On Tue, Aug 08, 2017 at 01:41:13PM +0200, Juan Quintela wrote:
> Peter Xu wrote:
> > On Mon, Jul 17, 2017 at 03:42:34PM +0200, Juan Quintela wrote:
>
> >> +static void multifd_recv_page(uint8_t *address, uint16_t fd_num)
> >> +{
> >> +int thread_count;
> >> +
"Daniel P. Berrange" wrote:
> On Mon, Jul 17, 2017 at 03:42:32PM +0200, Juan Quintela wrote:
>> We now send several pages at a time each time that we wakeup a thread.
>>
>> Signed-off-by: Juan Quintela
>>
>> --
>>
>> Use iovec's insead of creating the
On 08/08/2017 12:44, Peter Maydell wrote:
> +``cpu_{ld,st}_*``
> +~
> +
> +These functions operate on a guest virtual address. Be aware
> +that these functions may cause a guest CPU exception to be
> +taken (eg for an alignment fault or MMU fault) which will
> +result in guest CPU
Am 08.08.2017 um 13:04 hat Paolo Bonzini geschrieben:
> On 08/08/2017 12:02, Kevin Wolf wrote:
> > Am 04.08.2017 um 13:46 hat Paolo Bonzini geschrieben:
> >> On 04/08/2017 11:58, Stefan Hajnoczi wrote:
> the root cause of this bug is related to this as well:
>
On Fri, Aug 04, 2017 at 04:01:18PM +0200, Markus Armbruster wrote:
> blk_getlength() can fail. I figure the following need fixing:
>
> hw/arm/musicpal.c: musicpal_init()
Seems okay:
flash_size = blk_getlength(blk);
if (flash_size != 8*1024*1024 && flash_size != 16*1024*1024 &&
flash_size
On Fri, Aug 04, 2017 at 09:32:25PM +0300, Lluís Vilanova wrote:
> Stefan Hajnoczi writes:
>
> > On Sun, Jul 30, 2017 at 05:08:18PM +0300, Lluís Vilanova wrote:
> >> The hypertrace channel allows guest code to emit events in QEMU (the host)
> >> using
> >> its tracing infrastructure (see
On Wed, Jul 26, 2017 at 04:42:17PM +0200, Lukáš Doktor wrote:
> No actual code changes, just several pylint/style fixes and docstring
> clarifications.
>
> Signed-off-by: Lukáš Doktor
> ---
> scripts/qemu.py | 76
> -
>
On Tue, Aug 08, 2017 at 10:06:04AM +0200, Markus Armbruster wrote:
> Stefan Hajnoczi writes:
>
> > On Wed, Jul 26, 2017 at 02:24:02PM -0400, Cleber Rosa wrote:
> >>
> >>
> >> On 07/26/2017 01:58 PM, Stefan Hajnoczi wrote:
> >> > On Tue, Jul 25, 2017 at 12:16:13PM -0400,
1 - 100 of 392 matches
Mail list logo