arm and i386 has almost the same function acpi_add_rom_blob(), except
giving different FWCfgCallback function.
This patch extract acpi_add_rom_blob() to aml-build.c by passing
FWCfgCallback to it.
Signed-off-by: Wei Yang
---
hw/acpi/aml-build.c | 8
hw/arm/virt-acpi-build.c
On Wed, 13 Mar 2019 at 14:37, Palmer Dabbelt wrote:
>
> merged tag 'pull-request-2019-03-12'
> Primary key fingerprint: 27B8 8847 EEE0 2501 18F3 EAB9 2ED9 D774 FE70 2DB5
> The following changes since commit 3f3bbfc7cef4490c5ed5550766a81e7d18f08db1:
>
> Merge remote-tracking branch
> 'remotes/h
arm and i386 has almost the same function acpi_add_rom_blob(), except
giving different FWCfgCallback function.
This patch extract acpi_add_rom_blob() to aml-build.c by passing
FWCfgCallback to it.
Signed-off-by: Wei Yang
---
v2:
* remove unused header in original source file
---
hw/acpi/aml-
On Wed, Mar 13, 2019 at 09:55:19PM -0700, Richard Henderson wrote:
> Use a better interface for random numbers than rand,
> plus some useless floating point arithmetic.
>
> Cc: Gerd Hoffmann
> Signed-off-by: Richard Henderson
Reviewed-by: Gerd Hoffmann
On 3/14/19 3:10 AM, David Gibson wrote:
> On Mon, Mar 11, 2019 at 09:41:12PM +0100, Cédric Le Goater wrote:
>> On 2/26/19 1:01 AM, David Gibson wrote:
>>> On Fri, Feb 22, 2019 at 02:13:13PM +0100, Cédric Le Goater wrote:
This extends the KVM XIVE device backend with 'synchronize_state'
me
On Wed, 13 Mar 2019 18:16:18 -0300
"Maxiwell S. Garcia" wrote:
> On Tue, Mar 12, 2019 at 11:52:24AM +0100, Greg Kurz wrote:
>
> Hi Greg,
>
Hi Maxiwell,
> > On Mon, 11 Mar 2019 19:57:08 -0300
> > "Maxiwell S. Garcia" wrote:
> >
> > > The pseries options 'host-serial' and 'host-model' accep
From: Joel Stanley
The Linux kernel driver was updated in commit 4451d3f59f2a
("clocksource/drivers/fttmr010: Fix set_next_event handler) to fix an
issue observed on hardware:
> RELOAD register is loaded into COUNT register when the aspeed timer
> is enabled, which means the next event may be
Hello,
This series was initially sent by Andrew on the OpenBMC list :
https://lists.ozlabs.org/pipermail/openbmc/2019-January/014640.html
We had an issue with the introduction of 4451d3f59f2a
("clocksource/drivers/fttmr010: Fix set_next_event handler") in Linux
where our QEMU Aspeed machine we
From: Andrew Jeffery
>From the datasheet:
This register stores the current status of counter #N. When timer
enable bit TMC30[N * b] is disabled, the reload register will be
loaded into this counter. When timer bit TMC30[N * b] is set, the
counter will start to decrement. CPU can update t
From: Andrew Jeffery
If the match value exceeds reload then we don't want to include it in
calculations for the next event.
Signed-off-by: Andrew Jeffery
Signed-off-by: Cédric Le Goater
---
hw/timer/aspeed_timer.c | 13 ++---
1 file changed, 10 insertions(+), 3 deletions(-)
diff --gi
From: Andrew Jeffery
First up: This is not the way the hardware behaves.
However, it helps resolve real-world problems with short periods being
used under Linux. Commit 4451d3f59f2a ("clocksource/drivers/fttmr010:
Fix set_next_event handler") in Linux fixed the timer driver to
correctly schedule
From: Christian Svensson
If the host decrements the counter register that results in a negative
delta. This is then passed to muldiv64 which only handles unsigned
numbers resulting in bogus results.
This fix ensures the data being operated on is signed before it is
ultimately casted to the final
Patchew URL: https://patchew.org/QEMU/20190314084235.9887-1-...@kaod.org/
Hi,
This series failed the 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.
=== TEST SCRIPT BEGIN ===
#!/bin/b
There no @device parameter, only the @id one.
Signed-off-by: Vladimir Sementsov-Ogievskiy
---
qapi/block-core.json | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/qapi/block-core.json b/qapi/block-core.json
index ca684a8a04..7c1d47365d 100644
--- a/qapi/block-core.
12.03.2019 20:30, Kevin Wolf wrote:
> From: Vladimir Sementsov-Ogievskiy
>
> Signed-off-by: Vladimir Sementsov-Ogievskiy
> Signed-off-by: Kevin Wolf
Not critical, but it is v4, when in v5 description and examples were fixed to
be s/device/id.
I'll send a follow-up.
> ---
> qapi/block-core.
gets radeonfb going for me, on top of your i2c patches.
---
hw/display/ati_int.h | 1 +
hw/display/ati_regs.h | 1 +
hw/display/ati.c | 35 +++
3 files changed, 29 insertions(+), 8 deletions(-)
diff --git a/hw/display/ati_int.h b/hw/display/ati_int.h
index
Christian,
Could you please provide a fix for this patch ? patchew complains, see
attached log.
Thanks,
C.
On 3/14/19 9:42 AM, Cédric Le Goater wrote:
> From: Christian Svensson
>
> If the host decrements the counter register that results in a negative
> delta. This is then passed to muldiv6
> On Mar 14, 2019, at 1:35 AM, BALATON Zoltan wrote:
>
> On Wed, 13 Mar 2019, Chen Zhang wrote:
>> I sympathize with your situation, but the things on macOS seems a little
>> different.
>>
>> The QEMU Cocoa UI starts in the `main` thread and detach a `qemu_main`
>> thread which runs stuff i
Hello,
For the time being, we can drop patch 5 from this series.
Thanks,
C.
On 3/14/19 9:59 AM, no-re...@patchew.org wrote:
> Patchew URL: https://patchew.org/QEMU/20190314084235.9887-1-...@kaod.org/
>
>
>
> Hi,
>
> This series failed the docker-mingw@fedora build test. Please find the
>
On Thu, 14 Mar 2019 15:38:36 +0800
Wei Yang wrote:
> arm and i386 has almost the same function acpi_add_rom_blob(), except
> giving different FWCfgCallback function.
>
> This patch extract acpi_add_rom_blob() to aml-build.c by passing
> FWCfgCallback to it.
>
> Signed-off-by: Wei Yang
>
> ---
On 3/11/19 12:29 PM, Yuval Shaia wrote:
Allow interrogating device internals through HMP interface.
The exposed indicators can be used for troubleshooting by developers or
sysadmin.
There is no need to expose these attributes to a management system (e.x.
libvirt) because (1) most of them are n
On Wed, Mar 13, 2019 at 09:45:57AM -0500, Eric Blake wrote:
> Commit 3fa2d384 added a binary 'elf2dmp' but did not ignore it
> during an in-tree build.
>
> Signed-off-by: Eric Blake
> ---
>
> Yes, I know we want to get rid of in-tree builds for 4.1; but
> for 4.0, this patch may still make sense
On 3/11/19 12:29 PM, Yuval Shaia wrote:
Use base object of PCIDevice in call to object_get_typename().
Signed-off-by: Yuval Shaia
---
hw/rdma/vmw/pvrdma_main.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/hw/rdma/vmw/pvrdma_main.c b/hw/rdma/vmw/pvrdma_main.c
index 4
On Wed, 13 Mar 2019 21:31:37 +
Wei Yang wrote:
> On Wed, Mar 13, 2019 at 05:09:43PM +0100, Igor Mammedov wrote:
> >On Wed, 13 Mar 2019 13:33:59 +
> >Wei Yang wrote:
> >
> >> On Wed, Mar 13, 2019 at 01:23:00PM +0100, Igor Mammedov wrote:
> >> >On Wed, 13 Mar 2019 12:42:53 +0800
> >> >
On 3/13/19 10:46 AM, Kamal Heib wrote:
The 'rdma_dev_res' parameter is not used in rdma_poll_cq(), so remove it.
Signed-off-by: Kamal Heib
---
hw/rdma/rdma_backend.c | 7 +++
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/hw/rdma/rdma_backend.c b/hw/rdma/rdma_backend.c
On 3/12/19 4:23 PM, Yuval Shaia wrote:
On Tue, Mar 12, 2019 at 02:23:22PM +0200, Kamal Heib wrote:
On 3/11/19 12:29 PM, Yuval Shaia wrote:
Utilize error_report for all pr_err calls and some pr_dbg that are
considered as errors.
For the remaining pr_dbg calls, the important ones were replace
On Wed, Mar 13, 2019 at 03:25:19PM +0100, Kevin Wolf wrote:
> We were trying to check whether bdrv_open_blockdev_ref() returned
> success, but accidentally checked the wrong variable. Spotted by
> Coverity (CID 1399703).
>
> Signed-off-by: Kevin Wolf
> ---
> block/qcow2.c | 2 +-
> 1 file change
> -Original Message-
> From: Markus Armbruster [mailto:arm...@redhat.com]
> Sent: 13 March 2019 17:45
> To: qemu-devel@nongnu.org
> Cc: sstabell...@kernel.org; Anthony Perard ; Paul
> Durrant
> ; xen-de...@lists.xenproject.org;
> qemu-bl...@nongnu.org
> Subject: [PATCH] xen-block: Replace
On 3/13/19 10:46 AM, Kamal Heib wrote:
Signed-off-by: Kamal Heib
---
hw/rdma/rdma_backend.c | 18 +-
hw/rdma/vmw/pvrdma_cmd.c| 2 +-
hw/rdma/vmw/pvrdma_qp_ops.c | 2 +-
3 files changed, 11 insertions(+), 11 deletions(-)
diff --git a/hw/rdma/rdma_backend.c b/hw
Hello,
Thanks for your answer.
The wrong size was definitely being stored in the TB, and, it only affected
ADDVL/RDVL/ADDPL (i.e. not all instructions are wrong). Here is what I think
was happening:
- The kernel disables SVE in EL0 (ZEN= 01).
- When the user space application is entered, the TB
On Tue, 12 Mar 2019 at 07:13, Gerd Hoffmann wrote:
>
> From: Kővágó, Zoltán
>
> Audio drivers now get an Audiodev * as config paramters, instead of the
> global audio_option structs. There is some code in audio/audio_legacy.c
> that converts the old environment variables to audiodev options (thi
On Thu, Mar 14, 2019 at 07:53:15AM +0100, Greg Kurz wrote:
> On Thu, 14 Mar 2019 07:38:55 +0100
> Cédric Le Goater wrote:
>
> > From: Benjamin Herrenschmidt
> >
> > H_IPOLL takes the CPU# of the processor to poll as an argument,
> > it doesn't operate on self.
> >
>
> True.
Applied to ppc-fo
On Wed, 13 Mar 2019 at 21:18, Samuel Thibault
wrote:
>
> The following changes since commit cd82b1e170019c4b722ed53116ee9346315d7791:
>
> slirp: remove empty state.h (2019-03-13 22:12:23 +0100)
>
> are available in the Git repository at:
>
> https://people.debian.org/~sthibault/qemu.git tags/s
On Wed, Mar 13, 2019 at 05:31:57PM +, Daniel P. Berrangé wrote:
> The slirp code is not yet split off into a separate repository, so
> configuring QEMU to use slirp as a submodule is premature. This
> causes the non-existant "slirp" to be requested from git when syncing
> submodules. This in tu
On Wed, Mar 13, 2019 at 11:35:33AM -0700, Richard Henderson wrote:
> On 3/13/19 10:57 AM, Daniel P. Berrangé wrote:
> > We already have an internal API for providing strong random bytes in
> > QEMU qcrypto_random_bytes. It is preferentially backed by gnutls or
> > gcrypt, but if those aren't built-
On Wed, Mar 13, 2019 at 03:43:13PM -0400, Stefan Berger wrote:
> Hello!
>
> If you have some feedback regarding a seccomp profile extension for swtpm
> for v0.2, please let me know. I created this github issue here:
>
>
> https://github.com/stefanberger/swtpm/issues/115
>
>
> Basically the ch
On Mon, 11 Mar 2019 at 08:54, Gerd Hoffmann wrote:
>
> From: BALATON Zoltan
>
> At least two machines, the PPC mac99 and MIPS fulong2e, have an ATI
> gfx chip by default (Rage 128 Pro and M6/RV100 respectively) and
> guests running on these and the PMON2000 firmware of the fulong2e
> expect this
It's not safe to treat bdrv_is_allocated error as unallocated: if we
mistake we may rewrite guest data.
Signed-off-by: Vladimir Sementsov-Ogievskiy
---
block/io.c | 12 +++-
1 file changed, 7 insertions(+), 5 deletions(-)
diff --git a/block/io.c b/block/io.c
index 2ba603c7bc..dccad64d46
Paolo Bonzini writes:
> On 13/03/19 12:45, Sergio Lopez wrote:
>>
>> Peter Xu writes:
>>
>>> Previously we have per-device system memory aliases when DMAR is
>>> disabled by the system. It will slow the system down if there are
>>> lots of devices especially when DMAR is disabled, because eac
On 14/03/19 00:52, Richard Henderson wrote:
> On 3/13/19 5:40 AM, Paolo Bonzini wrote:
>> Because safe-syscall.S does not go through the C compiler, the
>> .note.gnu.property note has to be added manually. Safe syscalls do not
>> involve any indirect branch or stack unwinding, so they are triviall
Commit 5d75648b56e generates 'tests/test-qapi-emit-events.[ch]' but
did not ignore them for in-tree builds.
Signed-off-by: Stefano Garzarella
---
tests/.gitignore | 1 +
1 file changed, 1 insertion(+)
diff --git a/tests/.gitignore b/tests/.gitignore
index c88f8f2537..f9c0170881 100644
--- a/tes
On Wed, 13 Mar 2019 at 11:08, Stefan Hajnoczi wrote:
>
> The following changes since commit 3f3bbfc7cef4490c5ed5550766a81e7d18f08db1:
>
> Merge remote-tracking branch
> 'remotes/huth-gitlab/tags/pull-request-2019-03-12' into staging (2019-03-12
> 21:06:26 +)
>
> are available in the Git re
This series could be useless when we will no longer support in-tree builds,
but for 4.0 I think it's useful to ignore these files.
Stefano Garzarella (2):
.gitignore: ignore docs/built created for in-tree builds
tests/.gitignore: ignore test-qapi-emit-events.[ch] for in-tree builds
.gitignor
Commit 1290e6711 creates 'docs/built' for in-tree builds of
Sphinx manuals but did not ignore it.
Signed-off-by: Stefano Garzarella
---
.gitignore | 1 +
1 file changed, 1 insertion(+)
diff --git a/.gitignore b/.gitignore
index 77522561b8..0adb17347f 100644
--- a/.gitignore
+++ b/.gitignore
@@
On 14/03/19 01:56, Richard Henderson wrote:
> Hmm. The gcc for aarch64 names the similar feature -mbranch-protection. I'm
> rather annoyed that the i386 gcc folk appropriated a generic -f name without
> actually making the feature generic at the same time.
Wouldn't -fcf-protection=branch also ap
On 14/03/19 02:05, Richard Henderson wrote:
> On 3/13/19 5:40 AM, Paolo Bonzini wrote:
>> +static void tcg_out_endbr(TCGContext *s)
>> +{
>> +#if defined __CET__ && (__CET__ & 1)
>> +#ifdef __x86_64__
>> +tcg_out32(s, 0xfa1e0ff3);
>> +#else
>> +tcg_out32(s, 0xfb1e0ff3);
>> +#endif
>> +#endi
Amir CHARIF writes:
> Hello,
> Thanks for your answer.
>
> The wrong size was definitely being stored in the TB, and, it only affected
> ADDVL/RDVL/ADDPL (i.e. not all instructions are wrong). Here is what I think
> was happening:
>
> - The kernel disables SVE in EL0 (ZEN= 01).
> - When the u
Our coverity model of g_strdup() includes:
__coverity_string_size_sink__(s);
This seems to be causing Coverity to report false positives like
CID1399705 and 1399699 where we take a string from getenv() and
pass it to g_strdup() The getenv() string is untrusted data of unknown
length, and g_strdu
On 14/03/19 01:04, Richard Henderson wrote:
> On 3/13/19 5:40 AM, Paolo Bonzini wrote:
>> +static bool have_cet(void)
>> +{
>> +#if defined CONFIG_CET
>> +uint64_t ssp;
>> +asm ("xor %0, %0; rdsspq %0\n" : "=rm" (ssp));
>
> The xor is incompatible with a memory output.
> I don't think you
On 3/14/19 11:47 AM, Christian Svensson wrote:
> Hi all,
>
> I have a new patch but I'm not sure how you want me to post it.
> Should I do a "PATCH v2" with a single patch and this thread as the thread ID?
I would wait for feedback from Peter first.
Thanks,
C.
> Thanks,
> - Chris
>
>
> On
On Thu, 14 Mar 2019 at 08:43, Cédric Le Goater wrote:
>
> From: Christian Svensson
>
> If the host decrements the counter register that results in a negative
> delta. This is then passed to muldiv64 which only handles unsigned
> numbers resulting in bogus results.
>
> This fix ensures the data be
On 3/14/19 5:59 AM, Daniel P. Berrangé wrote:
On Wed, Mar 13, 2019 at 03:43:13PM -0400, Stefan Berger wrote:
Hello!
If you have some feedback regarding a seccomp profile extension for swtpm
for v0.2, please let me know. I created this github issue here:
https://github.com/stefanberger/swtpm
On Wed, Mar 13, 2019 at 10:05:51AM +0800, Yongji Xie wrote:
> On Wed, 13 Mar 2019 at 00:49, Michael S. Tsirkin wrote:
> >
> > On Thu, Feb 28, 2019 at 04:53:54PM +0800, elohi...@gmail.com wrote:
> > > From: Xie Yongji
> > >
> > > Since we now support the message VHOST_USER_GET_INFLIGHT_FD
> > > an
This patch isn't intended to merge. Just to reproduce a problem.
The test for x-ignore-shread capability fails on aarch64 + tcg:
Memory content inconsistency at 44c0 first_byte = 2 last_byte = 1 current =
d1 hit_edge = 1
Memory content inconsistency at 44c01000 first_byte = 2 last_byte = 1 cu
Hi
On Thu, Mar 14, 2019 at 7:17 AM Gerd Hoffmann wrote:
>
> It was never correct to not clear them. Due to commit "3912e66a3feb
> virtio-vga: fix reset." this became more obvious though. The virtio
> rings get properly reset now, and trying to process the stale commands
> will trigger an assert
On Wed, Mar 13, 2019 at 10:47:08AM +0800, Yongji Xie wrote:
> On Wed, 13 Mar 2019 at 09:16, Michael S. Tsirkin wrote:
> >
> > On Thu, Feb 28, 2019 at 04:53:54PM +0800, elohi...@gmail.com wrote:
> > > From: Xie Yongji
> > >
> > > Since we now support the message VHOST_USER_GET_INFLIGHT_FD
> > > an
Hi,
I've sent a mail about this problem:
[RFC PATCH] QEMU may write to system_memory before guest starts
Regards,
Yury
06.03.2019, 13:47, "Yury Kotov" :
> 05.03.2019, 21:06, "Dr. David Alan Gilbert" :
>> * Dr. David Alan Gilbert (dgilb...@redhat.com) wrote:
>>> * Yury Kotov (yury-ko...@yandex
On 14/03/19 11:51, Peter Maydell wrote:
> Our coverity model of g_strdup() includes:
> __coverity_string_size_sink__(s);
>
> This seems to be causing Coverity to report false positives like
> CID1399705 and 1399699 where we take a string from getenv() and
> pass it to g_strdup() The getenv() str
On Tue, Mar 12, 2019 at 12:49:35PM -0400, Michael S. Tsirkin wrote:
> On Thu, Feb 28, 2019 at 04:53:54PM +0800, elohi...@gmail.com wrote:
> > From: Xie Yongji
> >
> > Since we now support the message VHOST_USER_GET_INFLIGHT_FD
> > and VHOST_USER_SET_INFLIGHT_FD. The backend is able to restart
> >
On Wed, Mar 13, 2019 at 03:27:27PM +0100, Marc-André Lureau wrote:
> Hi
>
> On Wed, Mar 13, 2019 at 3:16 PM Michael S. Tsirkin wrote:
> >
> > On Tue, Mar 12, 2019 at 09:19:01PM +0100, Marc-André Lureau wrote:
> > > Hi
> > >
> > > On Tue, Mar 12, 2019 at 4:49 PM Michael S. Tsirkin
> > > wrote:
>
Hi Peter/Eric,
I think we should fix the regression issue instead of revert this patch, I
think the reason of
this issue is that QEMU modified some unexpected resisters, we should find
out.
Revert "arm: Allow system registers for KVM guests to be changed by QEMU
code"
This r
Hi Eric,
> -Original Message-
> From: Auger Eric [mailto:eric.au...@redhat.com]
> Sent: 11 March 2019 20:24
> To: Shameerali Kolothum Thodi ;
> qemu-devel@nongnu.org; qemu-...@nongnu.org; imamm...@redhat.com;
> peter.mayd...@linaro.org; shannon.zha...@gmail.com;
> sa...@linux.intel.com; se
On Thu, Mar 14, 2019 at 11:24:22AM +, Daniel P. Berrangé wrote:
> On Tue, Mar 12, 2019 at 12:49:35PM -0400, Michael S. Tsirkin wrote:
> > On Thu, Feb 28, 2019 at 04:53:54PM +0800, elohi...@gmail.com wrote:
> > > From: Xie Yongji
> > >
> > > Since we now support the message VHOST_USER_GET_INFL
On Thu, Mar 14, 2019 at 07:34:03AM -0400, Michael S. Tsirkin wrote:
> On Thu, Mar 14, 2019 at 11:24:22AM +, Daniel P. Berrangé wrote:
> > On Tue, Mar 12, 2019 at 12:49:35PM -0400, Michael S. Tsirkin wrote:
> > > On Thu, Feb 28, 2019 at 04:53:54PM +0800, elohi...@gmail.com wrote:
> > > > From: X
On Wed, 13 Mar 2019 at 12:14, Juan Quintela wrote:
>
> The following changes since commit 3f3bbfc7cef4490c5ed5550766a81e7d18f08db1:
>
> Merge remote-tracking branch
> 'remotes/huth-gitlab/tags/pull-request-2019-03-12' into staging (2019-03-12
> 21:06:26 +)
>
> are available in the Git repo
On Thu, 14 Mar 2019 at 11:31, gengdongjiu wrote:
>
> Hi Peter/Eric,
>I think we should fix the regression issue instead of revert this patch,
> I think the reason of
>this issue is that QEMU modified some unexpected resisters, we should find
> out.
Yes, I agree that we need to actua
If renderer_blocked is set do not call virtio_gpu_virgl_reset().
Instead set a flag indicating that virglrenderer needs a reset.
When renderer_blocked gets cleared do the actual reset call.
Without this we can trigger an assert in spice due to calling
spice_qxl_gl_scanout() while another operation
It was never correct to not clear them. Due to commit "3912e66a3feb
virtio-vga: fix reset." this became more obvious though. The virtio
rings get properly reset now, and trying to process the stale commands
will trigger an assert in the virtio core.
Signed-off-by: Gerd Hoffmann
---
hw/display/
Gerd Hoffmann (2):
virtio-gpu: delay virglrenderer reset when blocked.
virtio-gpu: clear command and fence queues on reset
include/hw/virtio/virtio-gpu.h | 1 +
hw/display/virtio-gpu.c| 26 +-
2 files changed, 26 insertions(+), 1 deletion(-)
--
2.18.1
On Thu, Mar 14, 2019 at 10:18:30AM +0100, Igor Mammedov wrote:
>On Wed, 13 Mar 2019 21:31:37 +
>Wei Yang wrote:
>
>> On Wed, Mar 13, 2019 at 05:09:43PM +0100, Igor Mammedov wrote:
>> >On Wed, 13 Mar 2019 13:33:59 +
>> >Wei Yang wrote:
>> >
>> >> On Wed, Mar 13, 2019 at 01:23:00PM +0100,
On Thu, Mar 14, 2019 at 12:01:27PM +0100, Marc-André Lureau wrote:
> Hi
>
> On Thu, Mar 14, 2019 at 7:17 AM Gerd Hoffmann wrote:
> >
> > It was never correct to not clear them. Due to commit "3912e66a3feb
> > virtio-vga: fix reset." this became more obvious though. The virtio
> > rings get prop
On Thu, Mar 14, 2019 at 10:25:14AM +0100, Igor Mammedov wrote:
>On Thu, 14 Mar 2019 15:38:36 +0800
>Wei Yang wrote:
>
>> arm and i386 has almost the same function acpi_add_rom_blob(), except
>> giving different FWCfgCallback function.
>>
>> This patch extract acpi_add_rom_blob() to aml-build.c by
On Thu, 14 Mar 2019 at 11:48, Peter Maydell wrote:
>
> On Wed, 13 Mar 2019 at 12:14, Juan Quintela wrote:
> >
> > The following changes since commit 3f3bbfc7cef4490c5ed5550766a81e7d18f08db1:
> >
> > Merge remote-tracking branch
> > 'remotes/huth-gitlab/tags/pull-request-2019-03-12' into stagin
On Mon, 11 Mar 2019 at 16:59, Aleksandar Markovic
wrote:
>
> Hello, all
>
> All of the sudden, the latest code doesn't build on my host: (the code from
> several days ago builds fine)
>
> Do you know what would be the culprit? Is it my environment, or a genuine
> build error?
Hi -- we've now co
Hi
On Thu, Mar 14, 2019 at 12:54 PM Gerd Hoffmann wrote:
>
> It was never correct to not clear them. Due to commit "3912e66a3feb
> virtio-vga: fix reset." this became more obvious though. The virtio
> rings get properly reset now, and trying to process the stale commands
> will trigger an asser
On Thu, Mar 14, 2019 at 11:43:26AM +, Daniel P. Berrangé wrote:
> On Thu, Mar 14, 2019 at 07:34:03AM -0400, Michael S. Tsirkin wrote:
> > On Thu, Mar 14, 2019 at 11:24:22AM +, Daniel P. Berrangé wrote:
> > > On Tue, Mar 12, 2019 at 12:49:35PM -0400, Michael S. Tsirkin wrote:
> > > > On Thu,
On Thu, 14 Mar 2019 at 11:23, Paolo Bonzini wrote:
>
> On 14/03/19 11:51, Peter Maydell wrote:
> > Our coverity model of g_strdup() includes:
> > __coverity_string_size_sink__(s);
> >
> > This seems to be causing Coverity to report false positives like
> > CID1399705 and 1399699 where we take a
On 3/14/19 3:52 AM, Vladimir Sementsov-Ogievskiy wrote:
> There no @device parameter, only the @id one.
>
> Signed-off-by: Vladimir Sementsov-Ogievskiy
> ---
> qapi/block-core.json | 10 +-
> 1 file changed, 5 insertions(+), 5 deletions(-)
Documentation fixes are appropriate during free
Am 14.03.2019 um 09:52 hat Vladimir Sementsov-Ogievskiy geschrieben:
> There no @device parameter, only the @id one.
>
> Signed-off-by: Vladimir Sementsov-Ogievskiy
Thanks, applied to the block branch.
Kevin
If you think this patch will introduce some issue, we can add one function
write_part_cpustate_to_list()[2] to change the specified
register instead of all the registers[1].
Below function that you added will modified all the register if new value is
different with old value.
[1]:
bool write_cpu
Am 14.03.2019 um 09:47 hat Vladimir Sementsov-Ogievskiy geschrieben:
> 12.03.2019 20:30, Kevin Wolf wrote:
> > From: Vladimir Sementsov-Ogievskiy
> >
> > Signed-off-by: Vladimir Sementsov-Ogievskiy
> > Signed-off-by: Kevin Wolf
>
> Not critical, but it is v4, when in v5 description and example
On 14/03/19 13:16, Peter Maydell wrote:
> Mmm, that makes sense. So in this particular case, do we
> want to try to avoid doing an unbounded allocation based
> on whatever rubbish the user passed us in the environment,
> or do we say "this particular case is OK" and mark it
> as a false-positive ?
On 3/14/19 5:46 AM, Stefano Garzarella wrote:
> This series could be useless when we will no longer support in-tree builds,
> but for 4.0 I think it's useful to ignore these files.
series:
Reviewed-by: Eric Blake
>
> Stefano Garzarella (2):
> .gitignore: ignore docs/built created for in-tree
Hi,
14.03.2019, 14:44, "Daniel P. Berrangé" :
> On Thu, Mar 14, 2019 at 07:34:03AM -0400, Michael S. Tsirkin wrote:
>> On Thu, Mar 14, 2019 at 11:24:22AM +, Daniel P. Berrangé wrote:
>> > On Tue, Mar 12, 2019 at 12:49:35PM -0400, Michael S. Tsirkin wrote:
>> > > On Thu, Feb 28, 2019 at 04:5
14.03.2019 13:14, Vladimir Sementsov-Ogievskiy wrote:
> It's not safe to treat bdrv_is_allocated error as unallocated: if we
> mistake we may rewrite guest data.
... with same data, which is not so bad.
So, it's ok, I'm wrong, drop it.
>
> Signed-off-by: Vladimir Sementsov-Ogievskiy
> ---
>
On Thu, Mar 14, 2019 at 12:16:06PM +, Peter Maydell wrote:
> On Thu, 14 Mar 2019 at 11:23, Paolo Bonzini wrote:
> >
> > On 14/03/19 11:51, Peter Maydell wrote:
> > > Our coverity model of g_strdup() includes:
> > > __coverity_string_size_sink__(s);
> > >
> > > This seems to be causing Coveri
On Thu, 14 Mar 2019 at 12:24, gengdongjiu wrote:
>
> If you think this patch will introduce some issue, we can add one function
> write_part_cpustate_to_list()[2] to change the specified
> register instead of all the registers[1].
It definitely does introduce an issue, but we need to address
it
On 2019/3/14 20:43, Peter Maydell wrote:
>> If you think this patch will introduce some issue, we can add one function
>> write_part_cpustate_to_list()[2] to change the specified
>> register instead of all the registers[1].
> It definitely does introduce an issue, but we need to address
> it by wo
Hi,
Thanks for not just killing processes anymore!
See the mesa thread
https://www.mail-archive.com/mesa-dev@lists.freedesktop.org/msg214474.html
for some background.
Thanks a lot and best
Mathias
On Wednesday, 13 March 2019 10:49:03 CET Daniel P. Berrangé wrote:
> The Mesa library tries to set
Thanks for the feedback,
On Thu, Mar 14, 2019, 11:57 Peter Maydell wrote:
> But overall I'm a little sceptical that the aspeed timer is
> really a special case that needs a signed version of this
> when no other timer in the system does...
I agree, and the v2 of the patch doesn't require it. H
Hi,
My apologies, I don't know how I missed those warnings.
I'll create a new patch.
- Chris
On Thu, Mar 14, 2019 at 10:06 AM Cédric Le Goater wrote:
> Hello,
>
> For the time being, we can drop patch 5 from this series.
>
> Thanks,
>
> C.
>
> On 3/14/19 9:59 AM, no-re...@patchew.org wrote:
>
Hi all,
I have a new patch but I'm not sure how you want me to post it.
Should I do a "PATCH v2" with a single patch and this thread as the thread
ID?
Thanks,
- Chris
On Thu, Mar 14, 2019 at 10:05 AM Cédric Le Goater wrote:
> Christian,
>
> Could you please provide a fix for this patch ? patc
On 2019/3/11 17:33, Greg Kurz wrote:
> On Tue, 5 Mar 2019 19:28:37 +0800
> wangyan wrote:
>
>> I am very happy for your reply.
>>
>> I am very interested in your old WIP and want to take a look.
>>
>> Our project still use 9pfs, and it needs to live migrate the
>> device while it is being used
On Mon, 2019-03-04 at 19:19 +0100, Paolo Bonzini wrote:
> Instead of including the same list of devices for each target,
> set CONFIG_PCI to true, and make the devices default to present
> whenever PCI is available. However, s390x does not want all the
> PCI devices, so there is a separate symbol
On 14/03/19 13:53, Andrea Bolognani wrote:
>
> $ ./riscv64-softmmu/qemu-system-riscv64 \
> -M virt \
> -device pcie-root-port
> qemu-system-riscv64: -device pcie-root-port: MSI-X is not
>supported by interrupt controller
>
> This is a limitation we have been aw
Hello,
Should this go through my tree, or perhaps it can be directly pushed to
master by Peter since it's no-code-only-copyright changes?
Samuel
Marc-André Lureau, le jeu. 14 mars 2019 14:10:41 +0100, a ecrit:
> In order to make slirp a standalone project, the project must have a
> clear license
On Tue, 12 Mar 2019 at 09:10, Eric Auger wrote:
>
> The GSIV numbers of the SPI based interrupts is not correct as
> ARM_SPI_BASE was not added to the irqmap[VIRT_SMMU] value. So
> this may collide with VIRTIO_MMIO irq window.
>
> Signed-off-by: Eric Auger
> ---
> hw/arm/virt-acpi-build.c | 2 +-
The slirp COPYRIGHT file is a BSD-3 license. Instead of referring to
another project file, the SPDX license notice present in all source
files states that unequivocally.
Signed-off-by: Marc-André Lureau
---
slirp/src/debug.h | 3 ---
slirp/src/if.h | 3 ---
slirp/src/main.h |
slirp has been maintained by the QEMU maintainers and will be
maintained under an independent project soon.
Reviewed-by: Eric Blake
Signed-off-by: Kelly Price
Signed-off-by: Marc-André Lureau
---
slirp/COPYRIGHT | 2 --
1 file changed, 2 deletions(-)
diff --git a/slirp/COPYRIGHT b/slirp/COPYR
Add SPDX license identifier to clarify the license of files without
explicit license header.
Signed-off-by: Marc-André Lureau
---
slirp/src/bootp.h | 1 +
slirp/src/ip6.h| 1 +
slirp/src/ip6_icmp.h | 1 +
slirp/src/libslirp.h | 1 +
slirp/src/slirp.h | 1 +
slirp/src/stream
1 - 100 of 348 matches
Mail list logo
