Reviewed-by: Thomas Huth
Reviewed-by: Aurelien Jarno
Signed-off-by: Richard Henderson
---
target/s390x/mem_helper.c | 11 ++-
target/s390x/translate.c | 1 -
2 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/target/s390x/mem_helper.c b/target/s390x/mem_helper.c
index 5068
Reviewed-by: Thomas Huth
Reviewed-by: Aurelien Jarno
Signed-off-by: Richard Henderson
---
target/s390x/helper.h | 2 +-
target/s390x/mem_helper.c | 9 +
target/s390x/translate.c | 3 +--
3 files changed, 7 insertions(+), 7 deletions(-)
diff --git a/target/s390x/helper.h b/target/s
Reviewed-by: Aurelien Jarno
Signed-off-by: Richard Henderson
---
target/s390x/mem_helper.c | 31 ++-
target/s390x/translate.c | 1 -
2 files changed, 18 insertions(+), 14 deletions(-)
diff --git a/target/s390x/mem_helper.c b/target/s390x/mem_helper.c
index 7d6133b.
Reviewed-by: Aurelien Jarno
Signed-off-by: Richard Henderson
---
target/s390x/mem_helper.c | 31 ++-
target/s390x/translate.c | 1 -
2 files changed, 18 insertions(+), 14 deletions(-)
diff --git a/target/s390x/mem_helper.c b/target/s390x/mem_helper.c
index 90b62fa.
From: Thomas Huth
TEST BLOCK was likely once used to execute basic memory
tests, but nowadays it's just a (slow) way to clear a page.
Reviewed-by: Aurelien Jarno
Reviewed-by: David Hildenbrand
Reviewed-by: Richard Henderson
Signed-off-by: Thomas Huth
Message-Id: <1495128400-23759-1-git-send-
This will avoid needing forward declarations in following patches.
Reviewed-by: Aurelien Jarno
Signed-off-by: Richard Henderson
---
target/s390x/mem_helper.c | 161 +++---
1 file changed, 81 insertions(+), 80 deletions(-)
diff --git a/target/s390x/mem_he
Reviewed-by: Thomas Huth
Reviewed-by: Aurelien Jarno
Signed-off-by: Richard Henderson
---
target/s390x/mem_helper.c | 10 ++
1 file changed, 2 insertions(+), 8 deletions(-)
diff --git a/target/s390x/mem_helper.c b/target/s390x/mem_helper.c
index 0c6a0d9..e3325a4 100644
--- a/target/s39
:
Merge remote-tracking branch 'remotes/xtensa/tags/20170606-xtensa' into
staging (2017-06-06 17:00:12 +0100)
are available in the git repository at:
git://github.com/rth7680/qemu.git tags/pull-s390-20170606
for you to fetch changes up to 49921d6886c54ec8727f2253b7698f173166b
Add helpers to gather cache info from the host at init-time.
For now, only export the host's I/D cache line sizes, which we
will use to improve cache locality to avoid false sharing.
Suggested-by: Richard Henderson
Suggested-by: Geert Martin Ijewski
Tested-by:Geert Martin Ijewski
Signed-of
On Mon, 06/05 14:38, Paolo Bonzini wrote:
> v3->v4: rebased and included fixes in Fam's v2 pull request
> new patch 18, fixing testsuite failures on OS X
Queued, thanks.
On Tue, Jun 6, 2017 at 3:14 PM, Paolo Bonzini wrote:
>
>
> On 06/06/2017 18:30, Alistair Francis wrote:
>>>
>>> This is somehow confusing. I don't think it is worth having another
>>> qemu_log_stderr() function rather than using error_report() but this very
>>> call might deserve a comment explain
Fixed in >=2.7 and thereby >=Zesty.
Needs to be considered for SRUs now.
** Also affects: qemu (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Also affects: qemu (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: qemu (Ubuntu)
Status: Triaged => Fix
hmm, the change still did not made it upstream.
I lost track on it and only see it now checking bugs that became dormant - was
that fixed in another way?
** Changed in: qemu (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of qemu-
dev
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.
Type: series
Message-id: 1496790745-314-1-git-send-email-c...@braap.org
Subject: [Qemu-devel] [PATCH v3 0/2] tcg: allocate TB
Fixed in 2.7 and thereby >=Zesty
** Changed in: qemu-kvm (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1319100
Title:
qemu-arm-static bug in signa
I can't guess very well how important this would be for an SRU (or not),
leaving that up for user feedback to be decided.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1319100
Title:
qemu-arm-stati
Add helpers to gather cache info from the host at init-time.
For now, only export the host's I/D cache line sizes, which we
will use to improve cache locality to avoid false sharing.
Suggested-by: Richard Henderson
Suggested-by: Geert Martin Ijewski
Tested-by:Geert Martin Ijewski
Signed-of
Allocating an arbitrarily-sized array of tbs results in either
(a) a lot of memory wasted or (b) unnecessary flushes of the code
cache when we run out of TB structs in the array.
An obvious solution would be to just malloc a TB struct when needed,
and keep the TB array as an array of pointers (rec
v2: https://lists.gnu.org/archive/html/qemu-devel/2017-06/msg01147.html
Changes from v2:
- Dropped the configure-time check. Instead, do this at init-time
as suggested by Richard.
- Added Pranith's R-b tag to the TCG patch.
- Added cache info query for Windows thanks to Geerd's help.
- Added
Quoting David Gibson (2017-06-06 08:05:32)
> This function is fairly short, and so is its only caller. There's no
> particular logical distinction between them, so fold them together.
>
> Signed-off-by: David Gibson
> ---
> hw/ppc/spapr_pci.c | 53 ++-
> >> Is there an obvious test that we can enhance to add coverage of the new
> >> QMP command?
> >
> > You could have a new test covering hw/char/serial.c, but I wouldn't let
> > that hold the patch.
>
> Holding patches is pretty much the only leverage I have to get tests for
> new stuff :)
>
> A
On 06/06/2017 18:30, Alistair Francis wrote:
>>
>> This is somehow confusing. I don't think it is worth having another
>> qemu_log_stderr() function rather than using error_report() but this very
>> call might deserve a comment explaining this unusual use. What do you think?
>
> The problem with
On 06/06/2017 19:49, Peter Maydell wrote:
> Things that would be interesting to explain/document:
> * what is special about vmxnet3 that makes it the only pci device
>that needs to use this rather than having a vmstate struct?
Nothing, it should be replaced by VMSTATE_MSIX (at the cost of bre
Am 06.06.2017 um 23:38 schrieb Emilio G. Cota:
> On Tue, Jun 06, 2017 at 22:28:23 +0200, Geert Martin Ijewski wrote:
>> On a fully patched Windows 10 with an i5-4690 this code works for me
(TM):
>
> Thanks!
> Can you please test this?
>
>Emilio
> ---
> #include "qemu/osdep.h"
> #incl
On Tue, Jun 06, 2017 at 22:28:23 +0200, Geert Martin Ijewski wrote:
> On a fully patched Windows 10 with an i5-4690 this code works for me (TM):
Thanks!
Can you please test this?
Emilio
---
#include "qemu/osdep.h"
#include
static unsigned int linesize_win(PROCESSOR_CACHE_TYPE ty
Quoting David Gibson (2017-06-06 03:32:20)
> There are 3 types of "indicator" associated with hotplug in the PAPR spec
> the "allocation state", "isolation state" and "DR-indicator". The first
> two are intimately tied to the various state transitions associated with
> hotplug. The DR-indicator,
Quoting David Gibson (2017-06-06 03:32:19)
> In theory the RTAS set-indicator call can be used for a number of
> "indicators" defined by PAPR. In practice the only ones we're ever likely
> to implement are those used for Dynamic Reconfiguration (i.e. hotplug).
> Because of this, the current implem
Quoting David Gibson (2017-06-06 03:32:21)
> DRC objects have attach & detach methods, but there's only one
> implementation. Although there are some differences in its behaviour for
> different DRC types, the overall structure is the same, so while we might
> want different method implementations
Am 06.06.2017 um 19:39 schrieb Richard Henderson:
On 06/06/2017 09:11 AM, Emilio G. Cota wrote:
On Tue, Jun 06, 2017 at 01:39:45 -0400, Pranith Kumar wrote:
On Mon, Jun 5, 2017 at 6:49 PM, Emilio G. Cota wrote:
This is a constant used as a hint for padding structs to hopefully
avoid
false ca
On Tue, 6 Jun 2017, Markus Armbruster wrote:
> >> Is there an obvious test that we can enhance to add coverage of the new
> >> QMP command?
> >
> > You could have a new test covering hw/char/serial.c, but I wouldn't let
> > that hold the patch.
>
> Holding patches is pretty much the only leverage
Marc-André Lureau writes:
> Hi
>
> On Thu, Jun 1, 2017 at 6:10 PM Markus Armbruster wrote:
>
>> Marc-André Lureau writes:
>>
>> > Suggested by Markus Armbruster:
>> >
>> > We should systematically cover the integers, in particular the
>> > boundaries (because that's where bugs like to hide):
>>
"Michael S. Tsirkin" writes:
> On Tue, Jun 06, 2017 at 06:14:02PM +0200, Markus Armbruster wrote:
>> "Michael S. Tsirkin" writes:
>>
>> > On Fri, Jun 02, 2017 at 03:54:37PM +0800, Mao Zhongyi wrote:
>> >> On success, pci_add_capability2() returns a positive value. On
>> >> failure, it sets an e
From: Greg Kurz
The docker-run-test-build@debian-s390x-cross target fails with:
strip --strip-unneeded s390-ccw.elf -o s390-ccw.img
strip: Unable to recognise the format of the input file `s390-ccw.elf'
The configure script defines a STRIP makefile variable whose default
value is ${cross_prefix
Add testmodes for SynIC messages and events. The message or event
connection setup / teardown is initiated by the guest via new control
codes written to the test device port. Then the test connections bounce
the respective operations back to the guest, i.e. the incoming messages
are posted or the
Signed-off-by: Roman Kagan
---
target/i386/hyperv.h | 1 +
hw/misc/hyperv_testdev.c | 1 +
target/i386/hyperv.c | 1 +
3 files changed, 3 insertions(+)
diff --git a/target/i386/hyperv.h b/target/i386/hyperv.h
index f82c770..cca4723 100644
--- a/target/i386/hyperv.h
+++ b/target/i386/hype
Add infrastructure to deliver SynIC messages to the guest SynIC message
page.
Note that KVM also may want to deliver (SynIC timer) messages to the
same message slot.
The problem is that the access to a SynIC message slot is controlled by
the value of its .msg_type field which indicates if the slo
From: David Hildenbrand
Let's also properly forward that bit. It should always be set. I
verified it under z/VM, it seems to be always set there. For now,
zKVM guests never get that bit set when the CPU model is active.
The PoP mentiones, that z800 + z900 (HW generation 7) always set this
bit to
Signed-off-by: Roman Kagan
---
MAINTAINERS | 7 +++
1 file changed, 7 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 120788d..16c5422 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -852,6 +852,13 @@ F: hw/core/machine.c
F: hw/core/null-machine.c
F: include/hw/boards.h
+Hyper-V
Add infrastructure to signal SynIC event flags by atomically setting the
corresponding bit in the event flags page and firing a SINT if
necessary.
Signed-off-by: Roman Kagan
---
target/i386/hyperv.h | 2 ++
target/i386/hyperv.c | 32
2 files changed, 34 insertio
From: David Hildenbrand
Currently, under z/VM on a 0x2827, QEMU will detect a 0x2828 if no
IBC value is provided. QEMU will simply take the last model of that HW
generation, which happens to be the BC version.
Let's improve our search for that case by selecting the latest CPU
definition that mat
Per Hyper-V spec, SynIC message and event flag pages are to be
implemented as so called overlay pages. That is, they are owned by the
hypervisor and, when mapped into the guest physical address space,
overlay the guest physical pages such that
1) the overlaid guest page becomes invisible to the g
Add handling of SIGNAL_EVENT hypercall. For that, provide an interface
to associate an EventNotifier with an event connection number, so that
it's signaled when the SIGNAL_EVENT hypercall with the matching
parameters is called by the guest.
TODO: we should be able to move this to KVM and avoid ex
From: Cornelia Huck
MIDA (modified indirect data addressing) is an optional facility, and
we (currently) don't support it. Let's post an operand exception if
the guest tries to set it in the orb and a channel program check
if it is set in a ccw, as specified in the Principles of Operation.
Revie
Make sint ack callback accept an opaque pointer, that is stored on
sint_route at creation time.
This allows for more convenient interaction with the callback.
Besides, nothing outside hyperv.c should need to know the layout of
HvSintRoute fields any more so its declaration can be removed from the
There is a design flaw in the Hyper-V SynIC implementation in KVM: when
message page or event flags page is enabled by setting the corresponding
msr, KVM zeroes it out. This violates the spec in general (per spec,
the pages have to be overlay ones and only zeroed at cpu reset), but
it's non-fatal
Here is a bunch of fixes. Most have been on the list already,
"fence off MIDA" was not posted before. I plan to submit a
pull request on Thursday or Friday.
Cornelia Huck (1):
s390x/css: fence off MIDA
David Hildenbrand (2):
s390x/cpumodel: take care of the cpuid format bit for KVM
s390x/cp
From: Halil Pasic
Prior to the virtio-ccw-2.7 machine (and commit 2a79eb1a), our virtio
devices residing under the virtual-css bus do not have qdev_path based
migration stream identifiers (because their qdev_path is NULL). The ids
are instead generated when the device is registered as a compositi
There's no point setting up an sint ack notifier if no callback is
specified.
Signed-off-by: Roman Kagan
---
target/i386/hyperv.c | 33 +++--
1 file changed, 19 insertions(+), 14 deletions(-)
diff --git a/target/i386/hyperv.c b/target/i386/hyperv.c
index 9aa5ec5..3ed
Make Hyper-V SynIC a device which is attached as a child to X86CPU. For
now it only makes SynIC visibile in the qom hierarchy and exposes a few
properties which are maintained in sync with the respecitve msrs of the
parent cpu.
Signed-off-by: Roman Kagan
---
target/i386/hyperv.h | 4 ++
targ
Add handling of POST_MESSAGE hypercall. For that, add an interface to
regsiter a handler for the messages arrived from the guest on a
particular connection id (IOW set up a message connection in Hyper-V
speak).
Signed-off-by: Roman Kagan
---
target/i386/hyperv.h | 5 +++
target/i386/hyperv.c |
Make sure HV_X64_MSR_SVERSION and HV_X64_MSR_SINTx are properly
initialized at guest start.
For that, move the field containing SVERSION value into the region in
CPUX86State which is preserved across resets, and move the
initialization of SINTx to kvm_arch_vcpu_reset().
Signed-off-by: Roman Kagan
Multiple entities (e.g. VMBus devices) can use the same SINT route. To
make their lives easier in maintaining SINT route ownership, make it
reference-counted. Adjust the respective API names accordingly.
Signed-off-by: Roman Kagan
---
target/i386/hyperv.h | 10 +-
hw/misc/hyperv_te
Wrap the bulk of kvm_cpu_exec with cpu_exec_start/end, so that kvm
version can also enjoy performing certain operations while all vCPUs are
quiescent.
Signed-off-by: Roman Kagan
---
kvm-all.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/kvm-all.c b/kvm-all.c
index 494b925..85668fb 10064
This series applies miscellaneous fixes and enhancements to Hyper-V
emulation code in QEMU, and lays out the ground for VMBus devices.
To give you a heads up, we currently have an implementation of VMBus
SCSI storage controller that works with native drivers in Windows
2008sp2 to 2016 and Linux; w
Signed-off-by: Roman Kagan
---
target/i386/hyperv.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/target/i386/hyperv.c b/target/i386/hyperv.c
index 480bdfe..9aa5ec5 100644
--- a/target/i386/hyperv.c
+++ b/target/i386/hyperv.c
@@ -88,7 +88,7 @@ HvSintRoute *kvm_hv_sint_route_
Make hyperv_testdev slightly easier to follow and enhance in future.
For that, put the hyperv sint routes (wrapped in a helper structure) on
a linked list rather than a fixed-size array.
Signed-off-by: Roman Kagan
---
hw/misc/hyperv_testdev.c | 113 ++-
The definitions for Hyper-V emulation are currently taken from a header
imported from the Linux kernel.
However, as these describe a third-party protocol rather than a kernel
API, it probably wasn't a good idea to publish it in the kernel uapi.
This patch introduces a header that provides all the
All definitions related to Hyper-V emulation are now taken from the QEMU
own header, so the one imported from the kernel is no longer needed.
Unfortunately it's included by kvm_para.h.
So, until this is fixed in the kernel, teach the header harvesting
script to substitute kernel's hyperv.h with a
Hyper-V identifies vcpus by the virtual processor (VP) index which is
normally queried by the guest via HV_X64_MSR_VP_INDEX msr.
It has to be owned by QEMU in order to preserve it across migration.
However, the current implementation in KVM doesn't allow to set this
msr, and KVM uses its own noti
Locate the vcpu by its VP index (equal to QEMU cpu_index).
Signed-off-by: Roman Kagan
---
target/i386/hyperv.h | 1 +
target/i386/hyperv.c | 5 +
2 files changed, 6 insertions(+)
diff --git a/target/i386/hyperv.h b/target/i386/hyperv.h
index 35da0b1..c5843c9 100644
--- a/target/i386/hyperv.
From: Evgeny Yakovlev
Hyper-V has a notion of partition-wide MSRs. Those MSRs are read and
written as usual on each VCPU, however the hypervisor maintains a single
global value for all VCPUs. Thus writing such an MSR from any single
VCPU affects the global value that is read by all other VCPUs.
On 06/04/17 17:56, Zhang Chen wrote:
>
>
> On 06/03/2017 06:49 AM, Laszlo Ersek wrote:
>> On 06/02/17 11:55, Marc-André Lureau wrote:
>>> Hi
>>>
>>> On Fri, Jun 2, 2017 at 1:46 PM Marc-André Lureau
>>>
>>> wrote:
>>>
Hi
On Thu, Jun 1, 2017 at 10:19 PM Eric Blake wrote:
>
On 06/06/2017 08:07 PM, Christian Borntraeger wrote:
> On 06/06/2017 08:02 PM, Halil Pasic wrote:
>>
>>
>> On 06/06/2017 10:21 AM, Christian Borntraeger wrote:
>>> On 06/02/2017 04:05 PM, Halil Pasic wrote:
Let's vmstatify virtio_ccw_save_config and virtio_ccw_load_config for
flexibilit
Hi,
This series seems to have some coding style problems. See output below for
more information:
Type: series
Subject: [Qemu-devel] [PATCH v4 0/1] qemu-ga: add guest-get-osinfo command
Message-id: cover.1496755908.git.tgole...@redhat.com
=== TEST SCRIPT BEGIN ===
#!/bin/bash
BASE=base
n=1
total
On 06/05/17 18:02, Michael S. Tsirkin wrote:
> On Sat, Jun 03, 2017 at 09:36:23AM +0200, Laszlo Ersek wrote:
>> On 06/02/17 17:45, Laszlo Ersek wrote:
>>
>>> The patches can cause linker/loader breakage when old firmware is booted
>>> on new QEMU. However, that's no problem (it's nothing new), the
On 06/06/2017 08:02 PM, Halil Pasic wrote:
>
>
> On 06/06/2017 10:21 AM, Christian Borntraeger wrote:
>> On 06/02/2017 04:05 PM, Halil Pasic wrote:
>>> Let's vmstatify virtio_ccw_save_config and virtio_ccw_load_config for
>>> flexibility (extending using subsections) and for fun.
>>>
>>> To achie
On Tue, Jun 06, 2017 at 06:14:02PM +0200, Markus Armbruster wrote:
> "Michael S. Tsirkin" writes:
>
> > On Fri, Jun 02, 2017 at 03:54:37PM +0800, Mao Zhongyi wrote:
> >> On success, pci_add_capability2() returns a positive value. On
> >> failure, it sets an error and return a negative value.
> >>
On 06/06/2017 10:21 AM, Christian Borntraeger wrote:
> On 06/02/2017 04:05 PM, Halil Pasic wrote:
>> Let's vmstatify virtio_ccw_save_config and virtio_ccw_load_config for
>> flexibility (extending using subsections) and for fun.
>>
>> To achieve this we need to hack the config_vector, which is Vi
On Tue, Jun 6, 2017 at 12:22 AM, Haozhong Zhang
wrote:
> Applications in Linux guest that use device-dax never trigger flush
> that can be trapped by KVM/QEMU. Meanwhile, if the host backend is not
> device-dax, QEMU cannot guarantee the persistence of guest writes.
> Before solving this flushing
Kevin Wolf wrote:
> Am 06.06.2017 um 07:24 hat QingFeng Hao geschrieben:
>> In load_snapshot, mis->from_src_file is freed twice, the first free is by
>> qemu_fclose, the second is by migration_incoming_state_destroy and
>> it causes Illegal instruction exception. The fix is just to remove the
>> f
On 06/05/17 11:54, Igor Mammedov wrote:
> BTW:
> how OVMF would deal with booting 32-bit OS if it would allocate
> ACPI tables above 4Gb?
> For BIOS on baremetal I'd expect some switch in settings, something
> like "Disable 32-bit OS support".
In order to answer your question exhaustively, I'd ha
On 6 June 2017 at 03:51, David Gibson wrote:
> From: Laurent Vivier
>
> We can replace the four remaining calls of register_savevm() by
> calls to register_savevm_live(). So we can remove the function and
> as we don't allocate anymore the ops pointer with g_new0()
> we don't have to free it then
Eric Blake wrote:
> On 06/01/2017 05:08 PM, Juan Quintela wrote:
>> Signed-off-by: Juan Quintela
>> ---
>> migration/migration.c | 4 +++-
>> migration/ram.c | 4 ++--
>> migration/ram.h | 2 +-
>> qapi-schema.json | 6 +-
>> 4 files changed, 11 insertions(+), 5 deletions(-)
On 6 June 2017 at 15:02, Paolo Bonzini wrote:
> The following changes since commit 70f31414e71250c6049a46851372ee6ea76f40dd:
>
> Merge remote-tracking branch 'remotes/ehabkost/tags/numa-pull-request' into
> staging (2017-06-01 10:58:47 +0100)
>
> are available in the git repository at:
>
> gi
* Kevin Wolf (kw...@redhat.com) wrote:
> Am 06.06.2017 um 07:24 hat QingFeng Hao geschrieben:
> > In load_snapshot, mis->from_src_file is freed twice, the first free is by
> > qemu_fclose, the second is by migration_incoming_state_destroy and
> > it causes Illegal instruction exception. The fix is
When reporting bugs to the QEMU project, please always try with the
latest release first (distros are often not shipping the latest
version). So can you please try with the latest release of QEMU
(currently version 2.9.0)?
** Changed in: qemu
Status: New => Incomplete
--
You received this
Peter Xu wrote:
> On Fri, Jun 02, 2017 at 12:08:13AM +0200, Juan Quintela wrote:
>> We create the variable while we are at migration and we remove it
>> after migration.
>>
>> Signed-off-by: Juan Quintela
>> @@ -1818,6 +1825,8 @@ static int ram_state_init(RAMState *rs)
>> error_rep
On 06/06/2017 09:11 AM, Emilio G. Cota wrote:
On Tue, Jun 06, 2017 at 01:39:45 -0400, Pranith Kumar wrote:
On Mon, Jun 5, 2017 at 6:49 PM, Emilio G. Cota wrote:
This is a constant used as a hint for padding structs to hopefully avoid
false cache line sharing.
The constant can be set at config
lowing changes since commit a0d4aac7467dd02e5657b79e867f067330266a24:
>
> Merge remote-tracking branch 'remotes/rth/tags/pull-tcg-20170605' into
> staging (2017-06-05 18:03:43 +0100)
>
> are available in the git repository at:
>
> git://github.com/OSLL/qemu-xtensa.g
Peter Xu wrote:
> On Mon, Jun 05, 2017 at 01:34:45PM +0100, Dr. David Alan Gilbert wrote:
>> * Juan Quintela (quint...@redhat.com) wrote:
>> > RAM Statistics need to survive migration to make info migrate work, so we
>> > need to store them outside of RAMState. As we already have an struct
>> > w
On Tue, Jun 06, 2017 at 10:02:17 -0700, Richard Henderson wrote:
> On 06/06/2017 09:25 AM, Emilio G. Cota wrote:
> >For this particular case we can get away without padding the structs if
> >we're OK with having the end of a TB struct immediately followed
> >by its translated code, instead of havin
Quoting David Gibson (2017-06-06 03:32:15)
> DRC classes have an entity_sense method to determine (in a specific PAPR
> sense) the presence or absence of a device plugged into a DRC. However,
> we only have one implementation of the method, which explicitly tests for
> different DRC types. This c
Quoting David Gibson (2017-06-06 03:32:16)
> DRConnectorClass has a get_name method, however:
> * There's only one implementation, and only ever likely to be one
> * There's exactly one caller, which is (now) local
> * The implementation is trivial
>
> So just open-code what we need.
>
> Si
Quoting David Gibson (2017-06-06 03:32:18)
> With some combinations of migration and hotplug we can lost temporary state
> indicating how many DRCs (guest side hotplug handles) are still connected
> to a DIMM object in the process of removal. When we hit that situation
> spapr_recover_pending_dimm
Public bug reported:
Hi,
Encryption-at-rest has been supported for some time now. The client is
responsible for encrypting the files with a help of a master key file.
I have a properly setup environment and everything appears to be working
fine but when I use qemu-img to move a file to gluster I
I'm using Fedora 24 with version:
qemu-img 2.6.2
glusterfs-api-3.8.12
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1696180
Title:
Issues with qemu-img, libgfapi, and encryption at rest
Status in
On 2 June 2017 at 17:28, Krzysztof Kozlowski wrote:
> Hi,
>
> I split non-intrusive changes from my previous attempts [1].
>
> This patchset contains only cleanups, minor improvements and support for
> power off. Power off itself will not happen because kernel will hang
> before trying it, on sync
On Tue, Jun 06, 2017 at 01:36:50 -0400, Pranith Kumar wrote:
> Reviewed-by: Pranith Kumar
>
> Thanks for doing this Emilio. Do you plan to continue working on rth's
> suggestions in that email? If so, can we co-ordinate our work?
My plan is to work on instrumentation. This was just low-hanging f
On Sat, Mar 25, 2017 at 12:52:35 -0400, Pranith Kumar wrote:
(snip)
> * Implement an LRU translation block code cache.
>
> In the current TCG design, when the translation cache fills up, we flush all
> the translated blocks (TBs) to free up space. We can improve this situation
> by not flush
Hi,
This series seems to have some coding style problems. See output below for
more information:
Type: series
Message-id: 20170606121747.25356-1-pbonz...@redhat.com
Subject: [Qemu-devel] [PATCH 0/7] megasas: fix TOCTOU and segmentation fault
bugs
=== TEST SCRIPT BEGIN ===
#!/bin/bash
BASE=base
On 06/06/2017 09:25 AM, Emilio G. Cota wrote:
For this particular case we can get away without padding the structs if
we're OK with having the end of a TB struct immediately followed
by its translated code, instead of having that code on the following
cache line.
Uh, no, if you can manually pad
Gerd, can you please comment on this?
Thanks
Laszlo
On 05/30/17 23:26, Laszlo Ersek wrote:
> The q35 machine type currently lets the guest firmware select a 1MB, 2MB
> or 8MB TSEG (basically, SMRAM) size. In edk2/OVMF, we use 8MB, but even
> that is not enough when a lot of VCPUs (more than appro
In some cases a failing VMSTATE_*_EQUAL does not mean we detected a bug
(it's actually the best we can do). Especially in these cases a verbose
error message is required.
Let's introduce infrastructure for specifying a error hint to be used if
equal check fails.
Signed-off-by: Halil Pasic
---
Ma
This one has to be fixed up to 's390x: vmstatify config migration for
virtio-ccw' provided we want to achieve the same as 's390x/css: catch
section mismatch on load' does.
Signed-off-by: Halil Pasic
---
This is on tom of 's390x: vmstatify config migration for virtio-ccw'
which ain't on top of 's
Verbose error reporting for the _EQUAL family. Modify the standard _EQUAL
so the hint states the assertion probably failed due to a bug. Introduce
_EQUAL_HINT for specifying a context specific hint.
Signed-off-by: Halil Pasic
---
Keeping this separate for now because we may want something differe
The goal is to be able to specify a hint for the case
a vmstate equal assertion fails. Was previously discussed
here:
https://patchwork.kernel.org/patch/9720029/
The third patch is an usage example. It's on top of this
https://www.mail-archive.com/qemu-devel@nongnu.org/msg454941.html
patch and mi
On 06.06.2017 18:12, Greg Kurz wrote:
> This function has three implementations. Two are stubs that do nothing
> and the third one only passes the obj_path argument to:
>
> Object *object_resolve_path(const char *path, bool *ambiguous);
>
> Signed-off-by: Greg Kurz
> Reviewed-by: Philippe Mathie
On Tue, Jun 6, 2017 at 6:37 AM, Philippe Mathieu-Daudé wrote:
> On 06/06/2017 08:58 AM, Marc-André Lureau wrote:
>>
>> Hi
>>
>> On Mon, Jun 5, 2017 at 10:37 PM Alistair Francis <
>> alistair.fran...@xilinx.com> wrote:
>>
>>> When QEMU is waiting for a TCP socket connection it reports that message
On 6 June 2017 at 17:28, Markus Armbruster wrote:
> Paolo Bonzini writes:
>
>> This is for the future interoperability & management guide. It includes
>> the QAPI docs, including the automatically generated ones, other socket
>> protocols (vhost-user, VNC), and the qcow2 file format.
>>
>> Signe
Paolo Bonzini writes:
> This is for the future interoperability & management guide. It includes
> the QAPI docs, including the automatically generated ones, other socket
> protocols (vhost-user, VNC), and the qcow2 file format.
>
> Signed-off-by: Paolo Bonzini
No objections to adding a bit mor
101 - 200 of 410 matches
Mail list logo
