06.02.2018 19:06, Eric Blake wrote:
On 02/06/2018 09:29 AM, Vladimir Sementsov-Ogievskiy wrote:
most of commands, ported to hmp are done in same style: they just call
corresponding qmp command.
Isn't it better to provide common interface for calling qmp
commands through
HMP monitor, to never
06.02.2018 20:29, Daniel P. Berrangé wrote:
On Tue, Feb 06, 2018 at 08:16:42PM +0300, Vladimir Sementsov-Ogievskiy wrote:
Support default luks options in VM.add_drive and in new library
function qemu_img_create. Use it in 205 iotests.
Signed-off-by: Vladimir Sementsov-Ogievskiy
---
instead of
On 02/06/2018 06:19 PM, Cornelia Huck wrote:
> On Mon, 5 Feb 2018 13:37:17 +0100
> David Hildenbrand wrote:
>
>> On 05.02.2018 13:22, Cornelia Huck wrote:
>>> On Mon, 5 Feb 2018 12:27:33 +0100
>>> David Hildenbrand wrote:
>>>
On 05.02.2018 12:22, Christian Borntraeger wrote:
> Lo
On 02/06/2018 11:57 AM, Vladimir Sementsov-Ogievskiy wrote:
+luks_default_secret_id = 'luks_secret_default_iotests_id'
Can we just call this "keysec0", so we matchh convention used by
the shell script based tests.
Here I'm trying to avoid intersection with some user-defined id.
You're ove
On Tue, 6 Feb 2018 17:34:25 +
Peter Maydell wrote:
> On 5 February 2018 at 18:56, Alex Williamson
> wrote:
> > The following changes since commit f24ee107a07f093bd7ed475dd48d7ba57ea3d8fe:
> >
> > Merge remote-tracking branch
> > 'remotes/kraxel/tags/ui-20180202-pull-request' into staging
06.02.2018 18:50, Eric Blake wrote:
On 02/06/2018 08:07 AM, Vladimir Sementsov-Ogievskiy wrote:
Set (and clear) histogram through new command
block-latency-histogram-set and show new statistics in
query-blockstats results.
Signed-off-by: Vladimir Sementsov-Ogievskiy
---
qapi/block-core.json
06.02.2018 21:04, Eric Blake wrote:
On 02/06/2018 11:57 AM, Vladimir Sementsov-Ogievskiy wrote:
+luks_default_secret_id = 'luks_secret_default_iotests_id'
Can we just call this "keysec0", so we matchh convention used by
the shell script based tests.
Here I'm trying to avoid intersection wit
On Tue, Feb 06, 2018 at 08:57:38PM +0300, Vladimir Sementsov-Ogievskiy wrote:
> 06.02.2018 20:29, Daniel P. Berrangé wrote:
> > On Tue, Feb 06, 2018 at 08:16:42PM +0300, Vladimir Sementsov-Ogievskiy
> > wrote:
> > > Support default luks options in VM.add_drive and in new library
> > > function qem
[I've cc'd a fairly random selection of people who I thought
might be interested or have an opinion.]
It's fairly common to have a setup where we have a QOM container
object (like an SoC) which in turn instantiates a lot of child
objects (for all the devices). The neat way of doing this looks
like
On 02/06/2018 04:31 PM, Eric Blake wrote:
> On 02/06/2018 01:46 AM, Christian Borntraeger wrote:
>> This patch is the s390 implementation of guest crash information,
>> similar to commit d187e08dc4 ("i386/cpu: add crash-information QOM
>> property") and the related commits. We will detect several
Support default luks options in VM.add_drive and in new library
function qemu_img_create. Use it in 205 iotests.
Signed-off-by: Vladimir Sementsov-Ogievskiy
---
v2: use keysec0 and IMGKEYSECRET
tests/qemu-iotests/205| 4 ++--
tests/qemu-iotests/iotests.py | 31 +++
On Tue, Feb 06, 2018 at 09:25:07PM +0300, Vladimir Sementsov-Ogievskiy wrote:
> Support default luks options in VM.add_drive and in new library
> function qemu_img_create. Use it in 205 iotests.
>
> Signed-off-by: Vladimir Sementsov-Ogievskiy
> ---
Reviewed-by: Daniel P. Berrange
Regards,
Dan
* Vladimir Sementsov-Ogievskiy (vsement...@virtuozzo.com) wrote:
> 26.01.2018 18:05, Dr. David Alan Gilbert wrote:
> > * Vladimir Sementsov-Ogievskiy (vsement...@virtuozzo.com) wrote:
> > > 17.01.2018 19:03, Eric Blake wrote:
> > > > On 01/17/2018 09:51 AM, Vladimir Sementsov-Ogievskiy wrote:
> > >
The following changes since commit 20e0d439a6ded635ec89f6135c08cd5541c68962:
Merge remote-tracking branch 'remotes/rth/tags/pull-hppa-20180204' into
staging (2018-02-06 14:21:41 +)
are available in the Git repository at:
git://github.com/awilliam/qemu-vfio.git tags/vfio-update-20180206.
From: Alexey Kardashevskiy
This adds get_attr() to IOMMUMemoryRegionClass, like
iommu_ops::domain_get_attr in the Linux kernel.
This defines the first attribute - IOMMU_ATTR_SPAPR_TCE_FD - which
will be used between the pSeries machine and VFIO-PCI.
Signed-off-by: Alexey Kardashevskiy
Acked-by
The fields were removed in the referenced commit, but the comment
still mentions them.
Fixes: 2fb9636ebf24 ("vfio-pci: Remove unused fields from VFIOMSIXInfo")
Tested-by: Alexey Kardashevskiy
Reviewed-by: Eric Auger
Tested-by: Eric Auger
Signed-off-by: Alex Williamson
---
hw/vfio/pci.h |2
Add an option which allows the user to specify a PCI BAR number,
including an 'off' and 'auto' selection.
Cc: Markus Armbruster
Cc: Eric Blake
Tested-by: Alexey Kardashevskiy
Reviewed-by: Eric Auger
Tested-by: Eric Auger
Reviewed-by: Markus Armbruster
Signed-off-by: Alex Williamson
---
hw/
From: Alexey Kardashevskiy
In order to enable TCE operations support in KVM, we have to inform
the KVM about VFIO groups being attached to specific LIOBNs. The KVM
already knows about VFIO groups, the only bit missing is which
in-kernel TCE table (the one with user visible TCEs) should update
the
From: Alexey Kardashevskiy
In order to enable TCE operations support in KVM, we have to inform
the KVM about VFIO groups being attached to specific LIOBNs;
the necessary bits are implemented already by IOMMU MR and VFIO.
This defines get_attr() for the SPAPR TCE IOMMU MR which makes VFIO
call th
From: Eric Auger
Add the initialization of the mutex protecting the interrupt list.
Signed-off-by: Eric Auger
Signed-off-by: Alex Williamson
---
hw/vfio/platform.c |2 ++
1 file changed, 2 insertions(+)
diff --git a/hw/vfio/platform.c b/hw/vfio/platform.c
index da84abf4fc4c..0d4bc0aae889
Add one more layer to our stack of MemoryRegions, this base region
allows us to register BARs independently of the vfio region or to
extend the size of BARs which do map to a region. This will be
useful when we want hypervisor defined BARs or sections of BARs,
for purposes such as relocating MSI-X
From: Alexey Kardashevskiy
There is already @hostwin in vfio_listener_region_add() so there is no
point in having the other one.
Fixes: 2e4109de8e58 ("vfio/spapr: Create DMA window dynamically (SPAPR IOMMU
v2)")
Signed-off-by: Alexey Kardashevskiy
Signed-off-by: Alex Williamson
---
hw/vfio/c
The kernel provides similar emulation of PCI BAR register access to
QEMU, so up until now we've used that for things like BAR sizing and
storing the BAR address. However, if we intend to resize BARs or add
BARs that don't exist on the physical device, we need to switch to the
pure QEMU emulation o
On 22 January 2018 at 17:26, Ard Biesheuvel wrote:
> This implements emulation of the new SHA-512 instructions that have
> been added as an optional extensions to the ARMv8 Crypto Extensions
> in ARM v8.2.
>
> Signed-off-by: Ard Biesheuvel
> +void HELPER(crypto_sha512h)(void *vd, void *vn, void
Recently proposed vfio-pci kernel changes (v4.16) remove the
restriction preventing userspace from mmap'ing PCI BARs in areas
overlapping the MSI-X vector table. This change is primarily intended
to benefit host platforms which make use of system page sizes larger
than the PCI spec recommendation
On 02/06/2018 12:21 PM, Christian Borntraeger wrote:
+ CRASH_REASON_UNKNOWN, /* default value of 0 on reset */
+ CRASH_REASON_PGM,
+ CRASH_REASON_EXT,
+ CRASH_REASON_WAITPSW,
+ CRASH_REASON_OPEREXC,
...you have an internal enum for decoding some of those integer values into
These quirks are necessary for GeForce, but not for Quadro/GRID/Tesla
assignment. Leaving them enabled is fully functional and provides the
most compatibility, but due to the unique NVIDIA MSI ACK behavior[1],
it also introduces latency in re-triggering the MSI interrupt. This
overhead is typical
On 02/06/2018 12:26 PM, Daniel P. Berrangé wrote:
On Tue, Feb 06, 2018 at 09:25:07PM +0300, Vladimir Sementsov-Ogievskiy wrote:
Support default luks options in VM.add_drive and in new library
function qemu_img_create. Use it in 205 iotests.
Signed-off-by: Vladimir Sementsov-Ogievskiy
---
Rev
On 6 February 2018 at 18:56, Ard Biesheuvel wrote:
> On 6 February 2018 at 18:45, Peter Maydell wrote:
>> On 22 January 2018 at 17:26, Ard Biesheuvel
>> wrote:
>>> This implements emulation of the new SHA-512 instructions that have
>>> been added as an optional extensions to the ARMv8 Crypto Ex
On 06.02.2018 18:25, Marc-André Lureau wrote:
> Hi
>
> On Tue, Feb 6, 2018 at 5:36 PM, Thomas Huth wrote:
>> Let's provide some links to the videos from DevConf and FOSDEM.
>>
>> Signed-off-by: Thomas Huth
>> ---
>> I've tried my best to find all talks that are related to QEMU, not sure
>> whe
On Mon, 5 Feb 2018 11:29:35 +0100
David Hildenbrand wrote:
> For now, the kernel does not properly indicate configured CPU subfunctions
> to the guest, but simply uses the host values (as support in KVM is still
> missing). That's why we missed to model the PTFF subfunctions that come
> with Mul
On 6 February 2018 at 18:45, Peter Maydell wrote:
> On 22 January 2018 at 17:26, Ard Biesheuvel wrote:
>> This implements emulation of the new SHA-512 instructions that have
>> been added as an optional extensions to the ARMv8 Crypto Extensions
>> in ARM v8.2.
>>
>> Signed-off-by: Ard Biesheuvel
On Tue, Feb 06, 2018 at 06:18:25PM +, Peter Maydell wrote:
> [I've cc'd a fairly random selection of people who I thought
> might be interested or have an opinion.]
>
> It's fairly common to have a setup where we have a QOM container
> object (like an SoC) which in turn instantiates a lot of c
On 02/06/2018 12:06 PM, Vladimir Sementsov-Ogievskiy wrote:
06.02.2018 18:50, Eric Blake wrote:
On 02/06/2018 08:07 AM, Vladimir Sementsov-Ogievskiy wrote:
Set (and clear) histogram through new command
block-latency-histogram-set and show new statistics in
query-blockstats results.
The commi
On 6 February 2018 at 18:57, Ard Biesheuvel wrote:
> On 6 February 2018 at 18:56, Ard Biesheuvel wrote:
>> On 6 February 2018 at 18:45, Peter Maydell wrote:
>>> On 22 January 2018 at 17:26, Ard Biesheuvel
>>> wrote:
This implements emulation of the new SHA-512 instructions that have
From: Fam Zheng
Management tools create overlays of running guests with qemu-img:
$ qemu-img create -b /image/in/use.qcow2 -f qcow2 /overlay/image.qcow2
but this doesn't work anymore due to image locking:
qemu-img: /overlay/image.qcow2: Failed to get shared "write" lock
Is another pr
Hi everyone,
The following new patches are queued for QEMU stable v2.11.1:
https://github.com/mdroth/qemu/commits/stable-2.11-staging
The release is planned for 2017-02-14:
https://wiki.qemu.org/P
From: Peter Maydell
The GICv2 specification says that reserved register addresses
must RAZ/WI; now that we implement external abort handling
for Arm CPUs this means we must return MEMTX_OK rather than
MEMTX_ERROR, to avoid generating a spurious guest data abort.
Cc: qemu-sta...@nongnu.org
Signed
From: Eduardo Habkost
Add the new feature word and the "ibpb" feature flag.
Based on a patch by Paolo Bonzini.
Signed-off-by: Eduardo Habkost
Message-Id: <20180109154519.25634-5-ehabk...@redhat.com>
Signed-off-by: Eduardo Habkost
(cherry picked from commit 1b3420e1c4d523c49866cca4e7544753201c
From: "Michael S. Tsirkin"
Backends don't need to know what frontend requested a reset,
and notifying then from virtio_error is messy because
virtio_error itself might be invoked from backend.
Let's just set the status directly.
Cc: qemu-sta...@nongnu.org
Reported-by: Ilya Maximets
Signed-off-
From: Peter Maydell
Since ssi-sd is still using the legacy SD card API, the SD
card created by sd_init() is not plugged into any bus. This
means that the controller has to reset it manually.
Failing to do this mostly didn't affect the guest since the
guest typically does a programmed SD card res
From: Peter Maydell
Since pl181 is still using the legacy SD card API, the SD
card created by sd_init() is not plugged into any bus. This
means that the controller has to reset it manually.
Failing to do this mostly didn't affect the guest since the
guest typically does a programmed SD card rese
From: Peter Maydell
In commit e3af7c788b73a6495eb9d94992ef11f6ad6f3c56 we
replaced direct calls to to cpu_ld*_code() with calls
to the x86_ld*_code() wrappers which incorporate an
advance of s->pc. Unfortunately we didn't notice that
in one place the old code was deliberately not incrementing
s->
From: Peter Maydell
The GICv3 specification says that reserved register addresses
should RAZ/WI. This means we need to return MEMTX_OK, not MEMTX_ERROR,
because now that we support generating external aborts the
latter will cause an abort on new board models.
Cc: qemu-sta...@nongnu.org
Signed-of
From: Peter Maydell
Since milkymist-memcard is still using the legacy SD card API,
the SD card created by sd_init() is not plugged into any bus.
This means that the controller has to reset it manually.
Failing to do this mostly didn't affect the guest since the
guest typically does a programmed
From: Stefan Hajnoczi
scsi_write_same_complete() can retry the write if the request was
unaligned. Make sure to release the AioContext when that code path is
taken!
This patch fixes a hang when QEMU terminates after an unaligned WRITE
SAME request has been processed with dataplane. The hang oc
From: Eduardo Habkost
The new MSR IA32_SPEC_CTRL MSR was introduced by a recent Intel
microcode updated and can be used by OSes to mitigate
CVE-2017-5715. Unfortunately we can't change the existing CPU
models without breaking existing setups, so users need to
explicitly update their VM configura
From: Jay Zhou
QEMU will assert on vhost-user backed virtio device hotplug if QEMU is
using more RAM regions than VHOST_MEMORY_MAX_NREGIONS (for example if
it were started with a lot of DIMM devices).
Fix it by returning error instead of asserting and let callers of
vhost_set_mem_table() handle
From: Peter Maydell
Our locking order is that the tb lock should be taken
inside the mmap_lock, but fork_start() grabs locks the
other way around. This means that if a heavily multithreaded
guest process (such as Java) calls fork() it can deadlock,
with the thread that called fork() stuck in fork
From: Eduardo Habkost
Add the feature name and a CPUID_7_0_EDX_SPEC_CTRL macro.
Signed-off-by: Eduardo Habkost
Message-Id: <20180109154519.25634-4-ehabk...@redhat.com>
Signed-off-by: Eduardo Habkost
(cherry picked from commit a2381f0934432ef2cd47a335348ba8839632164c)
Signed-off-by: Michael Rot
On 6 February 2018 at 19:06, Peter Maydell wrote:
> SM4EKEY, SM4E
Sample SM4EKEY failure:
insn 0xce78cbdd (SM4EKEY V29.4S, V30.4S, V24.4S)
V24 : 6ee7a2520059bd15bac75e4436b3a1bd
V30 : a67d04e738f68da895ffd0c3e154e3e7
V29 actual: a67d04e7b98aaef47bf01b8158da5407
V29 expected: 8d4922
From: Marcel Apfelbaum
If we try to use more pcie_root_ports then available slots
and an IO hint is passed to the port, QEMU crashes because
we try to init the "IO hint" capability even if the device
is not created.
Fix it by checking for error before adding the capability,
so QEMU can fail grace
From: Claudio Imbrenda
Fix storage attribute migration so that it does not fail for guests
with more than a few GB of RAM.
With such guests, the index in the buffer would go out of bounds,
usually by large amounts, thus receiving -EFAULT from the kernel.
Migration itself would be successful, but
From: Paolo Bonzini
Signed-off-by: Eduardo Habkost
Message-Id: <20180109154519.25634-3-ehabk...@redhat.com>
Signed-off-by: Eduardo Habkost
(cherry picked from commit a33a2cfe2f771b360b3422f6cdf566a560860bfc)
Signed-off-by: Michael Roth
---
target/i386/cpu.h | 3 +++
target/i386/kvm.c
From: Fam Zheng
Because usb-storage creates an internal scsi device, we should propagate
options. We already do so for bootindex etc, but failed to take care of
share-rw. Fix it in an apparent way: add a new parameter to
scsi_bus_legacy_add_drive and pass in s->conf.share_rw.
Cc: qemu-sta...@non
From: Eduardo Habkost
It is valid to have a 48-character model ID on CPUID, however the
definition of X86CPUDefinition::model_id is char[48], which can
make the compiler drop the null terminator from the string.
If a CPU model happens to have 48 bytes on model_id, "-cpu help"
will print garbage
From: Eric Auger
Update headers against v4.15-rc1.
Signed-off-by: Eric Auger
Message-id: 1511883692-11511-4-git-send-email-eric.au...@redhat.com
Signed-off-by: Peter Maydell
(cherry picked from commit dd8739669f95b30653a3a05cb2e21da3f52894fa)
Signed-off-by: Michael Roth
---
include/standard-
From: Eduardo Habkost
EPYC-IBPB is a copy of the EPYC CPU model with
just CPUID_8000_0008_EBX_IBPB added.
Cc: Jiri Denemark
Cc: Tom Lendacky
Cc: Brijesh Singh
Signed-off-by: Eduardo Habkost
Message-Id: <20180109154519.25634-7-ehabk...@redhat.com>
Signed-off-by: Eduardo Habkost
(cherry picke
From: David Gibson
Because PAPR is a paravirtual environment access to certain CPU (or other)
facilities can be blocked by the hypervisor. PAPR provides ways to
advertise in the device tree whether or not those features are available to
the guest.
In some places we automatically determine wheth
From: Cornelia Huck
Update headers against 4.15-rc9.
Signed-off-by: Cornelia Huck
(cherry picked from commit 9cbb636270b4df6f0a548e5c34b895330db5df8b)
Signed-off-by: Michael Roth
---
include/standard-headers/asm-s390/virtio-ccw.h | 6 +-
linux-headers/asm-powerpc/kvm.h| 2
From: Peter Maydell
The SPARC code in linux-user/signal.c defines a set of
MC_* constants. On some SPARC hosts these are also defined
by sys/ucontext.h, resulting in build failures:
linux-user/signal.c:2786:0: error: "MC_NGREG" redefined [-Werror]
#define MC_NGREG 19
In file included from /usr
From: David Gibson
Decimal Floating Point has been available on POWER7 and later (server)
cpus. However, it can be disabled on the hypervisor, meaning that it's
not available to guests.
We currently handle this by conditionally advertising DFP support in the
device tree depending on whether the
From: Fam Zheng
We could hit lock failure if there is a signal that makes fcntl return
-1 and errno set to EINTR. In this case we should retry.
Cc: qemu-sta...@nongnu.org
Signed-off-by: Fam Zheng
Reviewed-by: Eric Blake
Signed-off-by: Kevin Wolf
(cherry picked from commit f86428a1f4f91a460ed5
From: Peter Lieven
we forgot to set the allocmap to invalid if an UNMAP call fails.
Cc: qemu-sta...@nongnu.org
Signed-off-by: Peter Lieven
Message-Id: <1512733868-9009-2-git-send-email...@kamp.de>
Reviewed-by: Eric Blake
Signed-off-by: Paolo Bonzini
(cherry picked from commit aef172ffdc2f9c41
From: Christian Borntraeger
We need to handle the bpb control on reset and migration. Normally
stfle.82 is transparent (and the normal guest part works without
hypervisor activity). To prevent any issues we require full
host kernel support for this feature.
Cc: qemu-sta...@nongnu.org
Signed-off-
From: David Gibson
This adds an spapr capability bit for Hardware Transactional Memory. It is
enabled by default for pseries-2.11 and earlier machine types. with POWER8
or later CPUs (as it must be, since earlier qemu versions would implicitly
allow it). However it is disabled by default for th
From: David Gibson
Now that the "pseries" machine type implements optional capabilities (well,
one so far) there's the possibility of having different capabilities
available at either end of a migration. Although arguably a user error,
it would be nice to catch this situation and fail as gracefu
From: Greg Kurz
In various place we don't correctly check if the device supports MSI or
MSI-X. This can cause devices to be advertised with MSI support, even
if they only support MSI-X (like virtio-pci-* devices for example):
ethernet@0 {
ibm,req#msi = <0x
From: David Gibson
We currently have some conditionals in the spapr device tree code to decide
whether or not to advertise the availability of the VMX (aka Altivec) and
VSX vector extensions to the guest, based on whether the guest cpu has
those features.
This can lead to confusion and subtle fa
From: Laurent Vivier
if KVM is enabled and KVM capabilities MMU radix is available,
the partition table entry (patb_entry) for the radix mode is
initialized by default in ppc_spapr_reset().
It's a problem if we want to migrate the guest to a POWER8 host
while the kernel is not started to set the
From: Jose Ricardo Ziviani
Increases the max smt mode to 8 for Power9. That's because KVM supports
smt emulation in this platform so QEMU should allow users to use it as
well.
Today if we try to pass -smp ...,threads=8, QEMU will silently truncate
it to smt4 mode and may cause a crash if we try
From: Christian Borntraeger
stfle.81 (ppa15) is a transparent facility that can be passed to the
guest without the need to implement hypervisor support. As this feature
can be provided by firmware we add it to all full models.
Cc: qemu-sta...@nongnu.org
Signed-off-by: Christian Borntraeger
Mess
From: Cédric Le Goater
and use them in a couple of obvious places. Other macros will be used
in the model of the XIVE interrupt controller.
Signed-off-by: Cédric Le Goater
Signed-off-by: David Gibson
(cherry picked from commit 2a83f9976efa9a85e8ceb9d1035a68f25c321334)
Signed-off-by: Michael Ro
From: Suraj Jitindar Singh
Currently spapr_caps are tied to boolean values (on or off). This patch
reworks the caps so that they can have any uint8 value. This allows more
capabilities with various values to be represented in the same way
internally. Capabilities are numbered in ascending order.
From: David Gibson
While we're at it fix a couple of small errors in the 2.11 and 2.10 models
(they didn't have any real effect, but don't quite match the template).
Signed-off-by: David Gibson
(cherry picked from commit 2b6154120cbd7f5514cefd3c6084d39922d26d88)
Signed-off-by: Michael Roth
---
From: David Gibson
When constructing the "host" cpu class we modify whether the VMX and VSX
vector extensions and DFP (Decimal Floating Point) are available
based on whether KVM can support those instructions. This can depend on
policy in the host kernel as well as on the actual host cpu capabil
From: Suraj Jitindar Singh
Add three new kvm capabilities used to represent the level of host support
for three corresponding workarounds.
Host support for each of the capabilities is queried through the
new ioctl KVM_PPC_GET_CPU_CHAR which returns four uint64 quantities. The
first two, characte
From: Alex Bennée
This fixes bug #1735384 while running java under qemu-sh4. When debug
was enabled it showed a problem with TCG temps. Once fixed I was able
to run java -version normally.
Cc: qemu-sta...@nongnu.org
Reported-by: John Paul Adrian Glaubitz
Suggested-by: Richard Henderson
Signed-
From: Greg Kurz
Commit 51f84465dd98 changed the compatility mode setting logic:
- machine reset only sets compatibility mode for the boot CPU
- compatibility mode is set for other CPUs when they are put online
by the guest with the "start-cpu" RTAS call
This causes a regression for machines st
From: Kevin Wolf
bdrv_drain_all_begin() used to call the .bdrv_co_drain_begin() driver
callback inside its polling loop. This means that how many times it got
called for each node depended on long it had to poll the event loop.
This is obviously not right and results in nodes that stay drained e
From: Suraj Jitindar Singh
The vmstate description and the contained needed function for migration
of spapr_caps is the same for each cap, with the name of the cap
substituted. As such introduce a macro to allow for easier generation of
these.
Convert the three existing spapr_caps (htm, vsx, and
On 5 February 2018 at 19:28, Paolo Bonzini wrote:
> The following changes since commit f24ee107a07f093bd7ed475dd48d7ba57ea3d8fe:
>
> Merge remote-tracking branch 'remotes/kraxel/tags/ui-20180202-pull-request'
> into staging (2018-02-02 18:54:11 +)
>
> are available in the git repository at:
From: Suraj Jitindar Singh
Add new tristate cap cap-cfpc to represent the cache flush on privilege
change capability.
Signed-off-by: Suraj Jitindar Singh
Reviewed-by: David Gibson
Signed-off-by: David Gibson
(cherry picked from commit 8f38eaf8f9dd194c9961cf76c675724930ce4570)
Signed-off-by: M
On 06/02/2018 19:44, Thomas Huth wrote:
> Sure, I can add them ... actually, there are even some more talks
> related to KVM , e.g. the one from Vitaly:
>
> https://fosdem.org/2018/schedule/event/vai_kvm_on_hyperv/
>
> or related to Xen:
>
> https://fosdem.org/2018/schedule/event/vai_pci_emula
From: Suraj Jitindar Singh
spapr_caps are used to represent the level of support for various
capabilities related to the spapr machine type. Currently there is
only support for boolean capabilities.
Add support for tristate capabilities by implementing their get/set
functions. These capabilities
From: Suraj Jitindar Singh
Add new tristate cap cap-sbbc to represent the speculation barrier
bounds checking capability.
Signed-off-by: Suraj Jitindar Singh
Reviewed-by: David Gibson
Signed-off-by: David Gibson
(cherry picked from commit 09114fd8179977e4157b36aab2e3d68eaf08adca)
Signed-off-b
On 6 February 2018 at 19:15, Peter Maydell wrote:
> On 6 February 2018 at 19:06, Peter Maydell wrote:
>> SM4EKEY, SM4E
>
> Sample SM4EKEY failure:
> insn 0xce78cbdd (SM4EKEY V29.4S, V30.4S, V24.4S)
> V24 : 6ee7a2520059bd15bac75e4436b3a1bd
> V30 : a67d04e738f68da895ffd0c3e154e3e7
>
> V29
On 01/29/2018 05:08 AM, Stefan Hajnoczi wrote:
On Fri, Jan 26, 2018 at 01:34:39PM -0600, Eric Blake wrote:
We don't need the can_write_zeroes_with_unmap field in
BlockDriverInfo, because it is redundant information with
supported_zero_flags & BDRV_REQ_MAY_UNMAP. Note that
BlockDriverInfo and su
From: Kevin Wolf
This change separates bdrv_drain_invoke(), which calls the BlockDriver
drain callbacks, from bdrv_drain_recurse(). Instead, the function
performs its own recursion now.
One reason for this is that bdrv_drain_recurse() can be called multiple
times by bdrv_drain_all_begin(), but t
From: Suraj Jitindar Singh
The new H-Call H_GET_CPU_CHARACTERISTICS is used by the guest to query
behaviours and available characteristics of the cpu.
Implement the handler for this new H-Call which formulates its response
based on the setting of the spapr_caps cap-cfpc, cap-sbbc and cap-ibs.
S
On 02/05/2018 09:18 AM, Max Reitz wrote:
This new field can be set by block drivers to list the runtime options
they accept that may influence the contents of the respective BDS. As of
a follow-up patch, this list will be used by the common
bdrv_refresh_filename() implementation to decide which o
From: Markus Armbruster
Commit 43f187a broke --help: it put colons into blank lines. It
removed the colon from DEFHEADING(TITLE:) and added it back in the
macro expansion of DEFHEADING(TITLE), so hxtool can emit "@subsection
TITLE" more easily. Trouble is it's added back even for the blank
line
From: Suraj Jitindar Singh
Add new tristate cap cap-ibs to represent the indirect branch
serialisation capability.
Signed-off-by: Suraj Jitindar Singh
Reviewed-by: David Gibson
Signed-off-by: David Gibson
(cherry picked from commit 4be8d4e7d935fc8919d61f53a0f0fb7230052bb3)
Signed-off-by: Mich
Suggested-by: Halil Pasic
Signed-off-by: Markus Armbruster
Message-Id: <1502359588-29451-1-git-send-email-arm...@redhat.com>
Reviewed-by: Eric Blake
Reviewed-by: Halil Pasic
---
include/qapi/error.h | 8
1 file changed, 8 insertions(+)
diff --git a/include/qapi/error.h b/include/qapi
From: Alistair Francis
Replace a large number of the fprintf(stderr, "*\n" calls with
error_report(). The functions were renamed with these commands and then
compiler issues where manually fixed.
find ./* -type f -exec sed -i \
'N;N;N;N;N;N;N;N;N;N;N;N; {s|fprintf(stderr,
"\(.*\)\\n"\(.*\))
From: Murilo Opsfelder Araujo
The find_desc_by_name() from util/qemu-option.c relies on the .name not being
NULL to call strcmp(). This check becomes unsafe when the list is not
NULL-terminated, which is the case of nbd_runtime_opts in block/nbd.c, and can
result in segmentation fault when strcmp
The following changes since commit 20e0d439a6ded635ec89f6135c08cd5541c68962:
Merge remote-tracking branch 'remotes/rth/tags/pull-hppa-20180204' into
staging (2018-02-06 14:21:41 +)
are available in the git repository at:
git://repo.or.cz/qemu/armbru.git tags/pull-error-2018-02-06
for y
On 6 February 2018 at 20:41, Peter Maydell wrote:
> On 6 February 2018 at 19:15, Peter Maydell wrote:
>> On 6 February 2018 at 19:06, Peter Maydell wrote:
>>> SM4EKEY, SM4E
>>
>> Sample SM4EKEY failure:
>> insn 0xce78cbdd (SM4EKEY V29.4S, V30.4S, V24.4S)
>> V24 : 6ee7a2520059bd15bac75e4436b3
From: Alistair Francis
Replace a large number of the fprintf(stderr, "*\n" calls with
error_report(). The functions were renamed with these commands and then
compiler issues where manually fixed.
find ./* -type f -exec sed -i \
'N;N;N;N;N;N;N;N;N;N;N;N; {s|fprintf(stderr,
"\(.*\)\\n"\(.*\))
From: Paolo Bonzini
1) Return a generic sense if TEST UNIT READY does not provide one;
2) Fix two mistakes in copying from the spec.
Cc: qemu-sta...@nongnu.org
Reported-by: Dr. David Alan Gilbert
Signed-off-by: Paolo Bonzini
(cherry picked from commit a4a9b6eaf35dbe4bf0e069854945bf5e45fc7eab)
201 - 300 of 422 matches
Mail list logo
