Signed-off-by: Lluís Vilanova
---
docs/devel/tracing.txt |3 +
docs/hypertrace.txt| 225
2 files changed, 228 insertions(+)
create mode 100644 docs/hypertrace.txt
diff --git a/docs/devel/tracing.txt b/docs/devel/tracing.txt
index 5768a0b
The hypertrace channel allows guest code to emit events in QEMU (the host) using
its tracing infrastructure (see "docs/trace.txt"). This works in both 'system'
and 'user' modes, is architecture-agnostic and introduces minimal noise on the
guest.
See first commit for a full description, use-cases a
Le 27/07/2017 à 04:42, Philippe Mathieu-Daudé a écrit :
> linux-user/syscall.c:5581:9: warning: Dereference of undefined pointer value
> if (*host_rt_dev_ptr != 0) {
> ^~~~
>
> Reported-by: Clang Static Analyzer
> Suggested-by: Laurent Vivier
> Signed-off-by: Philippe Math
Le 27/07/2017 à 04:42, Philippe Mathieu-Daudé a écrit :
> linux-user/syscall.c:555:25: warning: Out of bound memory access (accessed
> memory precedes memory block)
> target_fd_trans[fd] = trans;
> ^~~
>
> Reported-by: Clang Static Analyzer
> Suggested-by: Laurent
On Tue, Jun 27, Stefano Stabellini wrote:
> From: Paul Durrant
> The blkif protocol has had provision for negotiation of multi-page shared
> rings for some time now and many guest OS have support in their frontend
> drivers.
> +++ b/hw/block/xen_disk.c
> +domids = g_malloc0_n(blkdev->nr_rin
On 07/26/2017 07:42 PM, Philippe Mathieu-Daudé wrote:
db3d7945ae extended gen_cc_cond() for cond [6, 7, 9, 10] but misswrote [4, 5]
target/m68k/translate.c:1323:70: warning: identical expressions on both sides
of logical operator
if (op == CC_OP_ADDB || op == CC_OP_ADDW || op == CC_OP_
On 26/07/17 18:40, Greg Kurz wrote:
> Hotplugging PHBs is a machine-level operation, but PHBs reside on the
> main system bus, so we register spapr machine as the handler for the
> main system bus.
>
> Signed-off-by: Michael Roth
> Signed-off-by: Greg Kurz
> ---
> - rebased against ppc-for-2.10
On 07/26/2017 06:40 PM, Philippe Mathieu-Daudé wrote:> patch 4: if no
system libdtc and submodule present, compile the dtc submodule
and verify it is at least v1.4.2. Prefixed RFC because I'm not sure about
these 3 lines:
+make -C dtc 1>/dev/null
which can leads to:
/bin/sh: 1: cannot cre
On 07/27/2017 12:43 AM, David Gibson wrote:
On Wed, Jul 26, 2017 at 11:42:23PM -0300, Philippe Mathieu-Daudé wrote:
sizeof(ptr) was used instead of sizeof(struct)...
also use g_malloc_n() which take care of possible type overflow.
hw/ppc/spapr_vio.c:641:22: warning: The code calls sizeof() on
On Wed, Jul 26, 2017 at 11:42:23PM -0300, Philippe Mathieu-Daudé wrote:
> sizeof(ptr) was used instead of sizeof(struct)...
>
> also use g_malloc_n() which take care of possible type overflow.
>
> hw/ppc/spapr_vio.c:641:22: warning: The code calls sizeof() on a pointer
> type. This can produce a
On Wed, Jul 26, 2017 at 11:36:43AM +0200, Greg Kurz wrote:
> On Wed, 26 Jul 2017 14:04:59 +1000
> David Gibson wrote:
>
> > On Tue, Jul 25, 2017 at 07:59:31PM +0200, Greg Kurz wrote:
> > > If object_property_add_alias() returns an error in realize(), we should
> > > propagate it to the caller and
I tried take snapshots on a demo.qcow2 10 times.
cmd is below:
> qemu-img snapshots -c tag_1 demo.qcow2
when I take snapshots 7 times and console shows:
> mark image as corrupted and preventing from invalid write
and I can't take snapshots anymore then.
Can I avoid this situation or remove th
I just realized what we need in order to test QEMU better. We need a list of
people who
are willing to support a certain operating system.
The list would probably be located here: http://wiki.qemu.org/Testing/Windows
It would look like this:
Operating systemTester
Windows 3.1
On 07/27/2017 01:02 AM, Michael S. Tsirkin wrote:
On Wed, Jul 26, 2017 at 11:48:41AM +0800, Wei Wang wrote:
On 07/23/2017 09:45 AM, Michael S. Tsirkin wrote:
On Fri, Jul 14, 2017 at 03:12:43PM +0800, Wei Wang wrote:
On 07/14/2017 04:19 AM, Michael S. Tsirkin wrote:
On Thu, Jul 13, 2017 at 03:
>From the Exynos4210 User Manual [1]:
14.4.1.3 I2CADDn (MULTI-MASTER I2C-Bus Address Register)
[7-1] slave address, latched from the I2C-bus.
bit [0] is not mapped.
[1]: Exynos_4_Dual_45nm_User_Manaul_Public_REV1.00-0.pdf
Signed-off-by: Philippe Mathieu-Daudé
---
hw/i2c/exynos4210_i2c.c |
(note this is how other functions also handle the errors).
hw/9pfs/9p.c:948:18: warning: Loss of sign in implicit conversion
offset = err;
^~~
Reported-by: Clang Static Analyzer
Signed-off-by: Philippe Mathieu-Daudé
---
hw/9pfs/9p.c | 6 ++
1 file changed, 2 inserti
sizeof(ptr) was used instead of sizeof(struct)...
also use g_malloc_n() which take care of possible type overflow.
hw/ppc/spapr_vio.c:641:22: warning: The code calls sizeof() on a pointer type.
This can produce an unexpected result
qdevs = g_malloc(sizeof(qdev) * num);
^
hw/bt/sdp.c:753:5: warning: Potential leak of memory pointed to by 'data'
qsort(record->attribute_list, record->attributes,
^
Reported-by: Clang Static Analyzer
Signed-off-by: Philippe Mathieu-Daudé
---
hw/bt/*:
get_maintainer.pl: No maintainers found
hw/bt/sdp.c | 6 --
1 file
linux-user/syscall.c:5581:9: warning: Dereference of undefined pointer value
if (*host_rt_dev_ptr != 0) {
^~~~
Reported-by: Clang Static Analyzer
Suggested-by: Laurent Vivier
Signed-off-by: Philippe Mathieu-Daudé
---
linux-user/syscall.c | 1 +
1 file changed, 1 insertio
linux-user/syscall.c:1627:35: warning: 1st function call argument is an
uninitialized value
target_saddr->sa_family = tswap16(addr->sa_family);
^~~~
linux-user/syscall.c:1629:25: warning: The left operand of '==' is a garbage
value
linux-user/syscall.c:555:25: warning: Out of bound memory access (accessed
memory precedes memory block)
target_fd_trans[fd] = trans;
^~~
Reported-by: Clang Static Analyzer
Suggested-by: Laurent Vivier
Signed-off-by: Philippe Mathieu-Daudé
---
linux-user/syscall
So we have sizeof(struct in6_address) != sizeof(uintptr_t)
and Clang > Coverity on this, see 4555ca6816c :)
net/eth.c:426:30: warning: The code calls sizeof() on a pointer type. This can
produce an unexpected result
return bytes_read == sizeof(dst_addr);
^
db3d7945ae extended gen_cc_cond() for cond [6, 7, 9, 10] but misswrote [4, 5]
target/m68k/translate.c:1323:70: warning: identical expressions on both sides
of logical operator
if (op == CC_OP_ADDB || op == CC_OP_ADDW || op == CC_OP_ADDL ||
op == CC_OP_ADDB || op == CC_OP_ADDW
hw/vfio/pci.c:308:29: warning: Use of memory after it is freed
qemu_set_fd_handler(*pfd, NULL, NULL, vdev);
^~~~
Reported-by: Clang Static Analyzer
Signed-off-by: Philippe Mathieu-Daudé
Reviewed-by: Paolo Bonzini
---
hw/vfio/pci.c | 11 +++
1 file cha
Extract the (correct) cleaning code as a new function vnc_free_addresses() then
use it to remove the memory leaks.
Reported-by: Clang Static Analyzer
Signed-off-by: Philippe Mathieu-Daudé
Reviewed-by: Daniel P. Berrange
---
ui/vnc.c | 36 ++--
1 file changed, 18
It seems this assert() was somehow misplaced.
block/qcow2-refcount.c:2193:42: warning: Array access (from variable
'on_disk_reftable') results in a null pointer dereference
on_disk_reftable[refblock_index] = refblock_offset;
^
Reported-by: Clang S
free the data _after_ using it.
hw/vfio/platform.c:126:29: warning: Use of memory after it is freed
qemu_set_fd_handler(*pfd, NULL, NULL, NULL);
^~~~
Reported-by: Clang Static Analyzer
Signed-off-by: Philippe Mathieu-Daudé
Reviewed-by: Paolo Bonzini
---
hw/v
thunk.c:91:32: warning: Call to 'malloc' has an allocation size of 0 bytes
se->field_offsets[i] = malloc(nb_fields * sizeof(int));
^~~
Reported-by: Clang Static Analyzer
Signed-off-by: Philippe Mathieu-Daudé
---
thunk.c | 3 ++-
nbd/client.c:385:12: warning: Potential leak of memory pointed to by 'buf'
Reported-by: Clang Static Analyzer
Signed-off-by: Philippe Mathieu-Daudé
Reviewed-by: Eric Blake
---
nbd/client.c | 8 +---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/nbd/client.c b/nbd/client.c
in
Hi,
This series is the result of [now NOT] having fun with Clang's Static Analyzer
(see https://clang-analyzer.llvm.org/).
v2:
- addressed review feedbacks,
- added various R-b,
- dropped noise (Peter sharp eye),
- dropped dup patches
Patches 1-13 are already reviewed,
Patches 14,15 address feed
not hit since 2009! :)
linux-user/elfload.c:1102:20: warning: Out of bound memory access (access
exceeds upper limit of memory block)
(*regs[i]) = tswap32(env->gregs[i]);
~~~^~~~
Reported-by: Clang Static Analyzer
Signed-off-by: Philippe Mathieu-Daudé
since a negative value means it errored.
hw/core/loader.c:149:9: warning: Loss of sign in implicit conversion
if (size > max_sz) {
^~~~
hw/core/loader.c:171:9: warning: Loss of sign in implicit conversion
if (size > memory_region_size(mr)) {
^~~~
Reported-by: Clang Static
This allow a one liner from fresh repository clone, i.e.:
./configure && make -j check-qtest-aarch64
Signed-off-by: Philippe Mathieu-Daudé
Reviewed-by: Alex Bennée
Reviewed-by: Stefan Hajnoczi
Reviewed-by: John Snow
---
tests/Makefile.include | 2 +-
1 file changed, 1 insertion(+), 1 delet
Screwed up in commit 3a55fc0f, v2.6.0.
If qemu_chr_fe_read_all() returns -EINTR the do {} statement continues and the
n accumulator used to complete reads upto sizeof(msg) is decremented by 4 (the
value of EINTR on Linux).
To avoid that, use simpler if() statements and continue if EINTR occured.
> On Jul 26, 2017, at 10:28 AM, qemu-devel-requ...@nongnu.org wrote:
>
> Message: 3
> Date: Wed, 26 Jul 2017 15:30:20 +0200
> From: Igor Mammedov
> To: Paolo Bonzini
> Cc: Laszlo Ersek , Phil Dennis-Jordan
> , "Daniel P. Berrange" ,
> PhilDennis-Jordan , ehabk...@redhat.com,
>
Qemu_savevm_state_cleanup takes about 300ms in my ram migration tests
with a 8U24G vm(20G is really occupied), the main cost comes from
KVM_SET_USER_MEMORY_REGION ioctl when mem.memory_size = 0 in
kvm_set_user_memory_region. In kmod, the main cost is
kvm_zap_obsolete_pages, which traverses the acti
On Wed, Jul 26, 2017 at 06:24:11PM +0300, Alexey Perevalov wrote:
> On 07/26/2017 11:43 AM, Peter Xu wrote:
> >On Wed, Jul 26, 2017 at 11:07:17AM +0300, Alexey Perevalov wrote:
> >>On 07/26/2017 04:49 AM, Peter Xu wrote:
> >>>On Thu, Jul 20, 2017 at 09:52:34AM +0300, Alexey Perevalov wrote:
> T
> On 26/07/2017 03:28, peng.h...@zte.com.cn wrote:
> >
> >
> > when the problem happens , windows kernel is checking whether REG_A_UIP is
> > changing after periodic timer has stopped. windows kernel access REG_A
> > according to INB instrunction and it will spend several microseconds becau
On Wed, Jul 26, 2017 at 11:37:13PM +0300, Michael S. Tsirkin wrote:
> On Mon, Jul 17, 2017 at 09:53:27AM +0800, Peter Xu wrote:
> > On Fri, Jul 14, 2017 at 03:28:09PM +0800, Jason Wang wrote:
> > >
> > >
> > > On 2017年07月14日 12:32, Peter Xu wrote:
> > > >On Thu, Jul 13, 2017 at 04:48:42PM +0800,
The atomics.txt is not in the docs directory but in docs/devel/
instead.
Signed-off-by: Jiang Biao
---
tcg/README | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tcg/README b/tcg/README
index bf49e82..03bfb6a 100644
--- a/tcg/README
+++ b/tcg/README
@@ -446,7 +446,7 @@ when M
@rpath and @ sock_name are not freed and leaked.
Signed-off-by: Zhipeng Lu lu.zhip...@zte.com.cn
---
fsdev/virtfs-proxy-helper.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/fsdev/virtfs-proxy-helper.c b/fsdev/virtfs-proxy-helper.c
index 6c066ec..8e48500 100644
--- a/fsdev/virtfs-proxy-h
A successful completion of rchp should signal a solicited channel path
initialized CRW (channel report word), while the current implementation
always generates an un-solicited one. Let's fix this.
Reported-by: Halil Pasic
Signed-off-by: Dong Jia Shi
---
hw/s390x/css.c | 15 +
When a channel path is hot plugged into a CSS, we should generate
a channel path initialized CRW (channel report word). The current
code does not do that, instead it puts a stub function with a TODO
reminder there.
This implements the css_generate_chp_crws() function by:
1. refactor the existing c
This series is trying to:
1. clear up CRW related code.
2. generate the right channel path related CRW at the right time.
I did this mainly because it's a requirement from my current work, that is I'm
in preparation of a group of patch for channel path virtualization. I can use
the inerface that p
Let's use a macro for the ERC (error recover code) when generating a
Channel Subsystem Event-information pending CRW (channel report word).
Signed-off-by: Dong Jia Shi
---
hw/s390x/css.c| 2 +-
include/hw/s390x/ioinst.h | 5 +++--
2 files changed, 4 insertions(+), 3 deletions(-)
dif
Public bug reported:
When attempting to run wineserver on a 64-bit ppc64el host via QEMU's
user-mode i386 emulation, a file locking operation fails.
Command line:
qemu-i386-static /usr/lib/wine-development/wineserver32
Output:
wineserver: fcntl /tmp/.wine-0/server-17-14d21bf/lock: Invalid argume
This series was motivated by the discussion in this thread:
https://www.redhat.com/archives/libvir-list/2017-June/msg01370.html
The issue this series addresses is that when libvirt unplugs a VFIO PCI device,
it may attempt to bind the host device back to the host driver when QEMU emits
the DEVI
This reverts commit abed886ec60cf239a03515cf0b30fb11fa964c44.
This patch originally addressed an issue where a DEVICE_DELETED
event could be emitted (in device_unparent()) before a Device's
QemuOpts were cleaned up (in device_finalize()), leading to a
"duplicate ID" error if management attempted t
device_unparent(dev, ...) is called when a device is unparented,
either directly, or as a result of a parent device being
finalized, and handles some final cleanup for the device. Part
of this includes emiting a DEVICE_DELETED QMP event to notify
management, which includes the device's path in the
DEVICE_DEL is currently emitted when a Device is unparented, as
opposed to when it is finalized. The main design motivation for this
seems to be that after unparent()/unrealize(), the Device is no
longer visible to the guest, and thus the operation is complete
from the perspective of management.
H
On 07/26/2017 08:56 PM, Aurelien Jarno wrote:
From: Alexey Kardashevskiy
This reverts c8e1158cf611 "elf-loader: warn about invalid endianness"
as it produces a useless message every time an LE kernel image is
passed via -kernel on a ppc64-pseries machine. The pseries machine
already checks for
On 07/26/2017 08:56 PM, Aurelien Jarno wrote:
Emulated MIPS boards bail out with a simple "could not load kernel" when
a kernel could not be load, without specifying the underlying reason.
Fix that by calling load_elf_strerror.
At the same time use error_report to report the error instead of
fpr
On 07/14/2017 09:25 PM, Stefan Hajnoczi wrote:
On Thu, Jul 13, 2017 at 04:01:09PM +0800, Wang Dong wrote:
On 07/10/2017 08:40 PM, Stefan Hajnoczi wrote:
On Mon, Jul 10, 2017 at 01:24:23PM +0800, Xie Changlong wrote:
在 7/9/2017 5:57 PM, Wang Dong 写道:
Hi,
I am new to QEMU. But I got some pro
* Halil Pasic [2017-07-26 18:45:34 +0200]:
[...]
> >>> @@ -946,6 +953,17 @@ static void sch_handle_start_func_virtual(SubchDev
> >>> *sch)
> >>> suspend_allowed = true;
> >>> }
> >>> sch->last_cmd_valid = false;
> >>> +if (sch->channel_prog & (CCW1_ADDR_MASK |
> >>> +
On Wed, Jul 26, 2017 at 4:46 PM, Rik van Riel wrote:
> On Wed, 2017-07-26 at 14:40 -0700, Dan Williams wrote:
>> On Wed, Jul 26, 2017 at 2:27 PM, Rik van Riel
>> wrote:
>> > On Wed, 2017-07-26 at 09:47 -0400, Pankaj Gupta wrote:
>> > > >
>> > >
>> > > Just want to summarize here(high level):
>> >
* Halil Pasic [2017-07-26 13:38:33 +0200]:
>
>
> On 07/26/2017 05:01 AM, Dong Jia Shi wrote:
> > Hello Halil,
> >
> > * Halil Pasic [2017-07-26 00:44:42 +0200]:
> >
> >> According to the PoP bit positions 0-3 and 8-32 of the format-1 CCW must
> >> contain zeros. Bits 0-3 are already covered
> -Original Message-
> From: Stefan Hajnoczi [mailto:stefa...@redhat.com]
> Sent: Wednesday, July 26, 2017 6:35 PM
> To: Liu, Changpeng
> Cc: qemu-devel@nongnu.org; pbonz...@redhat.com; fel...@nutanix.com;
> m...@redhat.com
> Subject: Re: [PATCH 1/2] vhost-user-blk: introduce a new vhost
This patchset improves the MIPS board error reporting when loading a
kernel with the wrong endianness, using load_elf_strerror.
That way the check added to loader.c can be removed, as it harms the
pseries platform. Indeed it can change its endianness dynamically at
runtime and thus can load both
On 2017-07-21 17:30, Alexey Kardashevskiy wrote:
> On 21/07/17 16:48, Philippe Mathieu-Daudé wrote:
> > Hi Alexey,
> >
> > On 07/21/2017 01:19 AM, Alexey Kardashevskiy wrote:
> >> This reverts c8e1158cf611 "elf-loader: warn about invalid endianness"
> >> as it produces a useless message every time
From: Alexey Kardashevskiy
This reverts c8e1158cf611 "elf-loader: warn about invalid endianness"
as it produces a useless message every time an LE kernel image is
passed via -kernel on a ppc64-pseries machine. The pseries machine
already checks for ELF_LOAD_WRONG_ENDIAN and tries with big_endian=
Emulated MIPS boards bail out with a simple "could not load kernel" when
a kernel could not be load, without specifying the underlying reason.
Fix that by calling load_elf_strerror.
At the same time use error_report to report the error instead of
fprintf.
Signed-off-by: Aurelien Jarno
---
hw/mi
On Wed, 2017-07-26 at 14:40 -0700, Dan Williams wrote:
> On Wed, Jul 26, 2017 at 2:27 PM, Rik van Riel
> wrote:
> > On Wed, 2017-07-26 at 09:47 -0400, Pankaj Gupta wrote:
> > > >
> > >
> > > Just want to summarize here(high level):
> > >
> > > This will require implementing new 'virtio-pmem' de
On 07/25/2017 05:15 PM, Eric Blake wrote:
From: Markus Armbruster
The qmp_FOO() take a printf-like format string. In a few places, we
assign a string literal to a variable and pass that instead of simply
passing the literal. Clean that up.
Bonus: gets rid of non-literal format strings. A
On Thu, Jul 27, 2017 at 12:54:07AM +0300, Alexander Bezzubikov wrote:
> 2017-07-26 22:43 GMT+03:00 Michael S. Tsirkin :
> > On Sun, Jul 23, 2017 at 01:15:41AM +0300, Aleksandr Bezzubikov wrote:
> >> On PCI init PCI bridges may need some
> >> extra info about bus number to reserve, IO, memory and
>
On 07/24/2017 03:27 PM, Philippe Mathieu-Daudé wrote:
Reported-by: Clang Static Analyzer
Signed-off-by: Philippe Mathieu-Daudé
---
hw/usb/dev-mtp.c | 36 +---
1 file changed, 21 insertions(+), 15 deletions(-)
diff --git a/hw/usb/dev-mtp.c b/hw/usb/dev-mtp.c
in
On 07/25/2017 09:34 AM, Gerd Hoffmann wrote:
case CMD_GET_OBJECT_INFO:
-o = usb_mtp_object_lookup(s, c->argv[0]);
+if (c->argc > 0) {
+o = usb_mtp_object_lookup(s, c->argv[0]);
+}
How about zero-initializing c->argv instead?
I checked the MTP specs r
On 07/26/17 23:54, Alexander Bezzubikov wrote:
> 2017-07-26 22:43 GMT+03:00 Michael S. Tsirkin :
>> On Sun, Jul 23, 2017 at 01:15:41AM +0300, Aleksandr Bezzubikov wrote:
>>> +PCIBridgeQemuCap cap;
>>
>> This leaks info to guest. You want to init all fields here:
>>
>> cap = {
>> .len =
>
On 07/24/2017 06:06 PM, Peter Maydell wrote:
On 24 July 2017 at 19:27, Philippe Mathieu-Daudé wrote:
In a ARM multicore system, write_secondary_boot() only initializes fixups for
FIXUP_GIC_CPU_IF and FIXUP_BOOTREG, while smpboot[] also uses FIXUP_DSB.
This results in write_bootloader() using un
On 07/24/2017 03:37 PM, Eric Blake wrote:
On 07/24/2017 01:27 PM, Philippe Mathieu-Daudé wrote:
thunk.c:91:32: warning: Call to 'malloc' has an allocation size of 0 bytes
se->field_offsets[i] = malloc(nb_fields * sizeof(int));
^~~~
Hello,
I'm getting a segfault in generated code that I don't know how to debug
further. The back trace shows:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffe87f7700 (LWP 24372)]
0x557ee0a1 in io_readx (env=0x7fffe88002a0, iotlbentry=0x7fffe8811d60,
ad
On Tue, Jul 25, 2017 at 05:56:44PM +0200, Max Reitz wrote:
> Without redirecting qemu's stderr to stdout, _filter_qemu will not apply
> to warnings. This results in $QEMU_PROG not being replaced by QEMU_PROG
> which is not great if your qemu executable is not called
> qemu-system-x86_64 (e.g. qemu
On Tue, Jul 25, 2017 at 05:56:43PM +0200, Max Reitz wrote:
> On one hand, the _make_test_img invocation for creating the target image
> was missing a -u because its backing file is not supposed to exist at
> that point.
>
> On the other hand, nobody noticed probably because the backing file is
> c
On 07/26/2017 06:56 PM, Eric Blake wrote:
On 07/26/2017 04:47 PM, no-re...@patchew.org wrote:
This series failed build test on s390x host. Please find the details below.
[...]
=== PACKAGES === >> dtc-1.4.2-1.fc25.s390x
=== TEST BEGIN ===
Using CC: /home/fam/bin/cc
ERROR: fdt disabled but
On 07/26/2017 06:51 PM, Eric Blake wrote:
On 07/26/2017 04:40 PM, Philippe Mathieu-Daudé wrote:
In the subject: s/remember/remind/
Signed-off-by: Philippe Mathieu-Daudé
---
configure | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/configure b/configure
index f8b1d0
On 07/26/2017 04:47 PM, no-re...@patchew.org wrote:
> Hi,
>
> This series failed build test on s390x host. Please find the details below.
>
> Type: series
> Subject: [Qemu-devel] [PATCH for 2.10 0/4] check dtc submodule is outdated
> Message-id: 20170726214010.420-1-f4...@amsat.org
>
> === TEST
2017-07-26 22:43 GMT+03:00 Michael S. Tsirkin :
> On Sun, Jul 23, 2017 at 01:15:41AM +0300, Aleksandr Bezzubikov wrote:
>> On PCI init PCI bridges may need some
>> extra info about bus number to reserve, IO, memory and
>> prefetchable memory limits. QEMU can provide this
>> with special
>
> with a
On 07/26/2017 04:40 PM, Philippe Mathieu-Daudé wrote:
> Signed-off-by: Philippe Mathieu-Daudé
> ---
> configure | 18 +-
> 1 file changed, 9 insertions(+), 9 deletions(-)
Reviewed-by: Eric Blake
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
On 07/26/2017 04:40 PM, Philippe Mathieu-Daudé wrote:
In the subject: s/remember/remind/
> Signed-off-by: Philippe Mathieu-Daudé
> ---
> configure | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/configure b/configure
> index f8b1d014d7..063de32773 100755
> --- a/c
Hi,
This series failed build test on s390x host. Please find the details below.
Type: series
Subject: [Qemu-devel] [PATCH for 2.10 0/4] check dtc submodule is outdated
Message-id: 20170726214010.420-1-f4...@amsat.org
=== TEST SCRIPT BEGIN ===
#!/bin/bash
# Testing script will be invoked under th
On Wed, Jul 26, 2017 at 2:27 PM, Rik van Riel wrote:
> On Wed, 2017-07-26 at 09:47 -0400, Pankaj Gupta wrote:
>> >
>> Just want to summarize here(high level):
>>
>> This will require implementing new 'virtio-pmem' device which
>> presents
>> a DAX address range(like pmem) to guest with read/write(
Reported-by: John Arbuckle
Message-Id: <65ed9743-b53c-4e6a-866f-c88365091...@gmail.com>
Signed-off-by: Philippe Mathieu-Daudé
---
configure | 24 +++-
1 file changed, 19 insertions(+), 5 deletions(-)
diff --git a/configure b/configure
index 2d803d6a77..386262ec33 100755
---
instead of fdt_first_subnode() which is v1.4.0
Signed-off-by: Philippe Mathieu-Daudé
---
configure | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/configure b/configure
index 0d5bdb3ae9..2d803d6a77 100755
--- a/configure
+++ b/configure
@@ -3565,7 +3565,10 @@ if test "$fd
On http://lists.nongnu.org/archive/html/qemu-devel/2017-07/msg07987.html John
hit the following error:
hw/core/loader-fit.c:105:41: error: expected expression
*addr = fdt32_to_cpu(*(fdt32_t *)prop);
^
having his ./configure --target-list=mips64el-sof
Signed-off-by: Philippe Mathieu-Daudé
---
configure | 18 +-
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/configure b/configure
index 063de32773..0d5bdb3ae9 100755
--- a/configure
+++ b/configure
@@ -3558,15 +3558,6 @@ for target in $target_list; do
esac
done
Signed-off-by: Philippe Mathieu-Daudé
---
configure | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/configure b/configure
index f8b1d014d7..063de32773 100755
--- a/configure
+++ b/configure
@@ -502,6 +502,7 @@ if test -f "./configure"; then
pwd_is_source_path="y"
el
On Wed, 2017-07-26 at 09:47 -0400, Pankaj Gupta wrote:
> >
> Just want to summarize here(high level):
>
> This will require implementing new 'virtio-pmem' device which
> presents
> a DAX address range(like pmem) to guest with read/write(direct
> access)
> & device flush functionality. Also, qemu
> On 27 Jul 2017, at 8:58 AM, kr...@berkeley.edu wrote:
>
>
> Given that one of the goals of RISC-V is extensibility, it would be
> nice if the QEMU port was done in a way to make it easier to extend by
> third parties, including other automated tools. I'm sure that, over
> time, the preprocess
Given that one of the goals of RISC-V is extensibility, it would be
nice if the QEMU port was done in a way to make it easier to extend by
third parties, including other automated tools. I'm sure that, over
time, the preprocessor can be improved to automatically incorporate
optimizations for bett
On 07/26/2017 01:46 PM, Programmingkid wrote:
On Jul 26, 2017, at 6:24 AM, Peter Maydell wrote:
On 26 July 2017 at 06:15, Programmingkid wrote:
On Jul 26, 2017, at 12:13 AM, Philippe Mathieu-Daudé wrote:
Hi John,
On 07/25/2017 07:55 PM, Programmingkid wrote:
While compiling the mips64el-so
On 07/26/2017 01:46 PM, Programmingkid wrote:
On Jul 26, 2017, at 6:24 AM, Peter Maydell wrote:
On 26 July 2017 at 06:15, Programmingkid wrote:
On Jul 26, 2017, at 12:13 AM, Philippe Mathieu-Daudé wrote:
Hi John,
On 07/25/2017 07:55 PM, Programmingkid wrote:
While compiling the mips64el-so
On Mon, Jul 17, 2017 at 09:53:27AM +0800, Peter Xu wrote:
> On Fri, Jul 14, 2017 at 03:28:09PM +0800, Jason Wang wrote:
> >
> >
> > On 2017年07月14日 12:32, Peter Xu wrote:
> > >On Thu, Jul 13, 2017 at 04:48:42PM +0800, Jason Wang wrote:
> > >>
> > >>On 2017年07月12日 16:13, Peter Xu wrote:
> > >>>It i
I've tested the patch set using Greg's Github branch. It worked fine in
my tests
using a Fedora 26 and an Ubuntu 17.04 guests. I have two observations
though:
1 - This is not related to this patch set per se because it is
reproducible on master, but
I think it is interfering with this new featu
On Wed, Jul 26, 2017 at 04:24:41PM -0400, Paolo Bonzini wrote:
>
> > The point is that for PC we really should not keep piling up hacks,
> > compatibility is more important.
>
> Non-explosion of the test matrix is just as important.
Absolutely.
> > > Doing it for PC only would mean switching
>
> The point is that for PC we really should not keep piling up hacks,
> compatibility is more important.
Non-explosion of the test matrix is just as important.
> > Doing it for PC only would mean switching
> > back from FADT rev3 to rev1, which is worse for guest OS support,
>
> It's only OSX A
- Original Message -
> From: "Michael S. Tsirkin"
> To: "Paolo Bonzini"
> Cc: seab...@seabios.org, "Kevin O'Connor" ,
> qemu-devel@nongnu.org, ler...@redhat.com,
> li...@philjordan.eu, imamm...@redhat.com, p...@philjordan.eu,
> programmingk...@gmail.com, kra...@redhat.com
> Sent: Wedn
> > (4) would be acceptable I guess. However I think it's a bit worse
> > because fw-cfg files are a somewhat scarce resource. The "legacy"
> > aspect is something that SeaBIOS is in the best position to address,
> > because it knows what OSes are running on it; QEMU instead only takes
> > care o
On Wed, Jul 26, 2017 at 04:09:37PM +0200, Igor Mammedov wrote:
> On Tue, 25 Jul 2017 16:36:06 +0300
> "Michael S. Tsirkin" wrote:
>
> > On Mon, Jul 24, 2017 at 03:50:20PM +0200, Igor Mammedov wrote:
> > > w2k used to boot on QEMU until revision of FADT has
> > > been bumped to rev3
> > > (commit
On Wed, Jul 26, 2017 at 03:01:25PM +0200, Paolo Bonzini wrote:
> On 26/07/2017 14:52, Michael S. Tsirkin wrote:
> > On Wed, Jul 26, 2017 at 11:31:36AM +0200, Paolo Bonzini wrote:
> >> The tables that QEMU provides are not ACPI 1.0 compatible since commit
> >> 77af8a2b95 ("hw/i386: Use Rev3 FADT (AC
On Wed, Jul 26, 2017 at 11:42:34AM +0200, Paolo Bonzini wrote:
> Old operating systems would like to have a rev1 (ACPI 1.0) FADT, but
> new operating systems would like to have rev3 (ACPI 2.0).
>
> Since old operating systems do not know about XSDTs, the
> solution is to point the RSDT to a rev1 F
On Sun, Jul 23, 2017 at 01:15:41AM +0300, Aleksandr Bezzubikov wrote:
> On PCI init PCI bridges may need some
> extra info about bus number to reserve, IO, memory and
> prefetchable memory limits. QEMU can provide this
> with special
with a special
> vendor-specific PCI capability.
>
> Sizes of
1 - 100 of 398 matches
Mail list logo