Am 18.01.2018 um 00:41 schrieb Justin Terry (VM) via Qemu-devel:
> Hey Paolo,
[...]
> 4. This will be supported on Windows 10 hosts (I don’t have the insider build
> number yet) and it will require an Intel processor with VT-x and Unrestricted
> Guest support. Will update the qemu-devel list once
On 17.01.2018 22:12, David Hildenbrand wrote:
> On 17.01.2018 20:37, Christian Borntraeger wrote:
>> 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
On Thu, Jan 18, 2018 at 04:44:28PM +1100, Alexey Kardashevskiy wrote:
> On 18/01/18 16:20, David Gibson wrote:
> > On Mon, Jan 15, 2018 at 05:32:35PM +1100, Suraj Jitindar Singh wrote:
> >> The new H-Call H_GET_CPU_CHARACTERISTICS is used by the guest to query
> >> behaviours and available characte
On Tue, Jan 16, 2018 at 01:46:14PM -0700, Alex Williamson wrote:
> On Mon, 15 Jan 2018 15:12:07 +1100
> Alexey Kardashevskiy wrote:
>
> > On 03/01/18 04:51, Paolo Bonzini wrote:
> > > On 02/01/2018 06:28, Alexey Kardashevskiy wrote:
> > >> This is my current queue of the in-kernel TCE accelerat
On Wed, Jan 17, 2018 at 4:57 PM, Richard Henderson wrote:
> On 01/17/2018 12:39 PM, Alistair Francis wrote:
>> Since commit "linux-user: Tidy and enforce reserved_va initialization"
>> (18e80c55bb6ec17c05ec0ba717ec83933c2bfc07) the Yocto webkitgtk build
>> hangs when cross compiling for 32-bit x86
On 18/01/18 16:20, David Gibson wrote:
> On Mon, Jan 15, 2018 at 05:32:35PM +1100, Suraj Jitindar Singh wrote:
>> 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 form
> > > > > > On Mon, Jan 15, 2018 at 12:04:55 -0200, Eduardo Habkost wrote:
> > > > > > > CCing libvirt developers.
> > > > > > ...
> > > > > > > This case is slightly more problematic, however: the new
> > > > > > > feature is actually migratable (under very controlled
> > > > > > > circumstances)
On 18/01/18 14:47, Alexey Kardashevskiy wrote:
> At the moment the sPAPR PHB MMIO space does not have an address space
> object as it does not really need one - guest accesses it via virtual
> addresses (and we provide mappings to the CPU space), the device drivers
> in QEMU access MMIO directly (a
On Mon, Jan 15, 2018 at 05:58:37PM +1100, Suraj Jitindar Singh wrote:
> 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 retu
On Mon, Jan 15, 2018 at 05:32:35PM +1100, Suraj Jitindar Singh wrote:
> 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 o
On Mon, Jan 15, 2018 at 05:32:34PM +1100, Suraj Jitindar Singh wrote:
> Add new tristate cap cap-ibs to represent the indirect branch
> serialisation capability.
>
> Signed-off-by: Suraj Jitindar Singh
Reviewed-by: David Gibson
> ---
> hw/ppc/spapr.c | 2 ++
> hw/ppc/spapr_caps.c
On Mon, Jan 15, 2018 at 05:32:32PM +1100, Suraj Jitindar Singh wrote:
> 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
> ---
> hw/ppc/spapr.c | 2 ++
> hw/ppc/spapr_caps.c
On Mon, Jan 15, 2018 at 05:32:33PM +1100, Suraj Jitindar Singh wrote:
> Add new tristate cap cap-sbbc to represent the speculation barrier
> bounds checking capability.
>
> Signed-off-by: Suraj Jitindar Singh
Reviewed-by: David Gibson
> ---
> hw/ppc/spapr.c | 2 ++
> hw/ppc/spapr_cap
On Mon, Jan 15, 2018 at 05:32:31PM +1100, Suraj Jitindar Singh wrote:
> 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 imple
glib reported error when pty chardev used:
$ ./qemu-system-x86_64 -chardev pty,id=foo -device isa-serial,chardev=foo
qemu-system-x86_64: -chardev pty,id=foo: char device redirected to /dev/pts/2
(label foo)
(qemu-system-x86_64:27885): GLib-CRITICAL **: g_source_unref: assertion 'source
!= NULL'
On Wed, Jan 17, 2018 at 05:21:40PM +0100, Marc-André Lureau wrote:
> Hi
>
> On Tue, Jan 16, 2018 at 3:16 PM, Paolo Bonzini wrote:
> > From: Peter Xu
> >
> > It's a replacement of g_timeout_add[_seconds]() for chardevs. Chardevs
> > now can have dedicated gcontext, we should always bind chardev
On Wed, Jan 17, 2018 at 09:54:57AM +0100, Andrea Bolognani wrote:
> On Wed, 2018-01-17 at 10:26 +1100, Alexey Kardashevskiy wrote:
> > On 17/01/18 09:34, David Gibson wrote:
> > > On Tue, Jan 16, 2018 at 03:46:20PM +0100, Andrea Bolognani wrote:
> > > > On Wed, 2018-01-17 at 00:54 +1100, David Gibs
On 01/17/2018 11:52 PM, Fam Zheng wrote:
> Coverity doesn't like the ignored return value introduced in
> 9d3b155186c278 (hw/block: Fix the return type), and other callers are
> converted already in ceff3e1f01.
>
> This one was added lately in d9bcd6f7f23a and missed the train. Do it
> now.
>
> S
On Tue, Jan 16, 2018 at 08:41:57AM +0100, Cédric Le Goater wrote:
> The hypervisor doorbells are used by skiboot and Linux on POWER9
> processors to wake up secondaries.
>
> This adds processor control support to the Server architecture by
> reusing the Embedded support. They are very similar, onl
On Wed, Jan 17, 2018 at 10:20:42AM +0100, Greg Kurz wrote:
> 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" RT
On Wed, Jan 17, 2018 at 10:20:35AM +0100, Greg Kurz wrote:
> When QEMU is started, all cold-plugged CPUs are reset twice: first
> during initialization and then during machine reset. This is sub-
> optimal.
>
> The first reset is only needed for hot-plugged CPUs because the CPU
> hotplug code does
At the moment the sPAPR PHB MMIO space does not have an address space
object as it does not really need one - guest accesses it via virtual
addresses (and we provide mappings to the CPU space), the device drivers
in QEMU access MMIO directly (as they own MRs). The only case when
a driver in QEMU mi
Coverity doesn't like the ignored return value introduced in
9d3b155186c278 (hw/block: Fix the return type), and other callers are
converted already in ceff3e1f01.
This one was added lately in d9bcd6f7f23a and missed the train. Do it
now.
Signed-off-by: Fam Zheng
---
hw/scsi/scsi-generic.c | 9
On Wed, Jan 17, 2018 at 10:32:56AM +, Kang, Luwei wrote:
> > > > > On Mon, Jan 15, 2018 at 12:04:55 -0200, Eduardo Habkost wrote:
> > > > > > CCing libvirt developers.
> > > > > ...
> > > > > > This case is slightly more problematic, however: the new feature
> > > > > > is actually migratable (
From: Vladimir Sementsov-Ogievskiy
Signed-off-by: Vladimir Sementsov-Ogievskiy
Reviewed-by: Eric Blake
Message-Id: <20171122101958.17065-6-vsement...@virtuozzo.com>
Signed-off-by: Eric Blake
---
nbd/server.c | 40 +---
1 file changed, 13 insertions(+), 27 d
This will be useful for the next patch.
Based on a patch by Vladimir Sementsov-Ogievskiy
Signed-off-by: Eric Blake
Reviewed-by: Vladimir Sementsov-Ogievskiy
Message-Id: <20180110230825.18321-5-ebl...@redhat.com>
---
nbd/server.c | 24 ++--
1 file changed, 18 insertions(+),
No semantic change, but will make it easier for an upcoming patch
to refactor code without having to add forward declarations. Fix
a poor comment while at it.
Signed-off-by: Eric Blake
Reviewed-by: Vladimir Sementsov-Ogievskiy
Message-Id: <20180110230825.18321-2-ebl...@redhat.com>
---
nbd/serv
Rather than making every callsite perform length sanity checks
and error reporting, add the helper functions nbd_opt_read()
and nbd_opt_drop() that use the length stored in the client
struct; also add an assertion that optlen is 0 before any
option (ie. any previous option was fully handled), compl
From: Haozhong Zhang
When mmap(2) the backend files, QEMU uses the host page size
(getpagesize(2)) by default as the alignment of mapping address.
However, some backends may require alignments different than the page
size. For example, mmap a device DAX (e.g., /dev/dax0.0) on Linux
kernel 4.13 to
From: Thomas Huth
Instead of doing the clean-ups on errors multiple times, introduce
a jump label at the end of the function that can be used by all
error paths that need this cleanup.
Suggested-by: Igor Mammedov
Signed-off-by: Thomas Huth
Message-Id: <1509617407-21191-2-git-send-email-th...@r
When a client abruptly disconnects before we've finished reading
the name sent with NBD_OPT_EXPORT_NAME, we are better off logging
the failure as EIO (we can't communicate with the client), rather
than EINVAL (the client sent bogus data).
Signed-off-by: Eric Blake
Reviewed-by: Vladimir Sementsov-
From: Thomas Huth
The qdev_unplug() function contains a g_assert(hotplug_ctrl) statement,
so QEMU crashes when the user tries to device_add + device_del a device
that does not have a corresponding hotplug controller. This could be
provoked for a couple of devices in the past (see commit 4c9395065
From: Vladimir Sementsov-Ogievskiy
Instead of passing currently negotiating option and its length to
many of negotiation functions let's just store them on NBDClient
struct to be state-variables of negotiation phase.
This unifies semantics of negotiation functions and allows
tracking changes of
The following changes since commit 8e5dc9ba49743b46d955ec7dacb04e42ae7ada7c:
Merge remote-tracking branch 'remotes/rth/tags/pull-tcg-20180116' into
staging (2018-01-16 17:36:39 +)
are available in the Git repository at:
git://repo.or.cz/qemu/ericb.git tags/pull-nbd-2018-01-17
for you t
From: Igor Mammedov
Remove dependency of possible_cpus on 1st CPU instance,
which decouples configuration data from CPU instances that
are created using that data.
Also later it would be used for enabling early cpu to numa node
configuration at runtime qmp_query_hotpluggable_cpus() should
provid
The existing has_dynamic_sysbus flag makes the machine accept
every user-creatable sysbus device type on the command-line.
Replace it with a list of allowed device types, so machines can
easily accept some sysbus devices while rejecting others.
To keep exactly the same behavior as before, the exis
From: Thomas Huth
These are crashes / errors which have been fixed already in the past
months. We can remove these from the device-crash-test script now.
Signed-off-by: Thomas Huth
Message-Id: <1513613438-11017-1-git-send-email-th...@redhat.com>
Signed-off-by: Eduardo Habkost
---
scripts/devi
From: Marcel Apfelbaum
When all the fw_cfg slots are used, a write is made outside the
bounds of the fw_cfg files array as part of the sort algorithm.
Fix it by avoiding an unnecessary array element move.
Fix also an assert while at it.
Signed-off-by: Marcel Apfelbaum
Message-Id: <201801082150
From: Stefan Hajnoczi
The documentation should mention -object memory-backend-ram.
Suggested-by: Yumei Huang
Signed-off-by: Stefan Hajnoczi
Message-Id: <20171128161529.3025-3-stefa...@redhat.com>
Reviewed-by: Eric Blake
Reviewed-by: Eduardo Habkost
Signed-off-by: Eduardo Habkost
---
qemu-o
There's no need to make the machine allow every possible sysbus
device. We can now just add xen-sysdev to the allowed list.
Cc: Stefano Stabellini
Cc: Anthony Perard
Cc: xen-de...@lists.xenproject.org
Cc: Juergen Gross
Signed-off-by: Eduardo Habkost
Message-Id: <20171125151610.20547-6-ehabk..
From: Haozhong Zhang
Signed-off-by: Haozhong Zhang
Reviewed-by: Stefan Hajnoczi
Message-Id: <20171211072806.2812-3-haozhong.zh...@intel.com>
Reviewed-by: Michael S. Tsirkin
Signed-off-by: Eduardo Habkost
---
include/hw/mem/nvdimm.h | 3 +++
hw/mem/nvdimm.c | 2 +-
2 files changed, 4
From: Marc-André Lureau
Add a function to only create a memfd, without mmap. The function is
used in the following memory backend.
Signed-off-by: Marc-André Lureau
Reviewed-by: Philippe Mathieu-Daudé
Message-Id: <20171023141815.17709-2-marcandre.lur...@redhat.com>
Signed-off-by: Eduardo Habkos
From: Haozhong Zhang
Currently the only vNVDIMM backend can guarantee the guest write
persistence is device DAX on Linux, because no host-side kernel cache
is involved in the guest access to it. The approach to detect whether
the backend is device DAX needs to access sysfs, which may not work
wit
TYPE_SPAPR_PCI_HOST_BRIDGE is the only dynamic sysbus device not
rejected by ppc_spapr_reset(), so it can be the only entry on the
allowed list.
Cc: David Gibson
Cc: Alexander Graf
Cc: qemu-...@nongnu.org
Signed-off-by: Eduardo Habkost
Message-Id: <20171125151610.20547-5-ehabk...@redhat.com>
Ac
The following changes since commit 8e5dc9ba49743b46d955ec7dacb04e42ae7ada7c:
Merge remote-tracking branch 'remotes/rth/tags/pull-tcg-20180116' into
staging (2018-01-16 17:36:39 +)
are available in the Git repository at:
git://github.com/ehabkost/qemu.git tags/machine-next-pull-request
From: Stefan Hajnoczi
This patch adds undocumented memory-backend-file options to the
documentation.
Signed-off-by: Stefan Hajnoczi
Message-Id: <20171128161529.3025-2-stefa...@redhat.com>
Reviewed-by: Eric Blake
Reviewed-by: Eduardo Habkost
Signed-off-by: Eduardo Habkost
---
qemu-options.hx
The only user-creatable sysbus devices in qemu-system-x86_64 are
amd-iommu, intel-iommu, and xen-backend. xen-backend is handled
by xen_set_dynamic_sysbus(), so we only need to add amd-iommu and
intel-iommu.
Cc: "Michael S. Tsirkin"
Cc: Marcel Apfelbaum
Signed-off-by: Eduardo Habkost
Message-I
platform_bus_create_devtree() already rejects all dynamic sysbus
devices except TYPE_ETSEC_COMMON, so register it as the only
allowed dynamic sysbus device for the ppce500 machine-type.
Cc: Alexander Graf
Cc: David Gibson
Cc: qemu-...@nongnu.org
Signed-off-by: Eduardo Habkost
Message-Id: <20171
From: Marc-André Lureau
Signed-off-by: Marc-André Lureau
Reviewed-by: Philippe Mathieu-Daudé
Message-Id: <20171023141815.17709-3-marcandre.lur...@redhat.com>
Signed-off-by: Eduardo Habkost
---
util/memfd.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/util/memfd.c b/util/memfd.c
index
Replace the TYPE_SYS_BUS_DEVICE entry in the allowed sysbus
device list with the two device types that are really supported
by the virt machine: vfio-amd-xgbe and vfio-calxeda-xgmac.
Cc: Peter Maydell
Cc: qemu-...@nongnu.org
Signed-off-by: Eduardo Habkost
Message-Id: <20171125151610.20547-3-ehab
From: Igor Mammedov
commit 419fcdec3c (numa: add '-numa cpu,...' option for property based node
mapping)
added '-numa cpu' option but forgot to update appropriate section for '--help'.
Add '-numa cpu' description to '-help' output
Reported-by: Markus Armbruster
Signed-off-by: Igor Mammedov
Me
From: Paolo Bonzini
Signed-off-by: Eduardo Habkost
Message-Id: <20180109154519.25634-3-ehabk...@redhat.com>
Signed-off-by: Eduardo Habkost
---
target/i386/cpu.h | 3 +++
target/i386/kvm.c | 14 ++
target/i386/machine.c | 20
3 files changed, 37 inserti
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 configuration to use the new *-IB
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
---
target/i386/cpu.h | 3 +++
target/i386/cpu.c | 19 ++-
2 files ch
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
---
target/i386/cpu.h | 1 +
target/i386/cpu.c | 2 +-
2 files changed, 2 insertions(+), 1 deletion(-)
diff --git a/t
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 and the object_property_
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
---
target/i386/cpu.c | 46 +
The following changes since commit 8e5dc9ba49743b46d955ec7dacb04e42ae7ada7c:
Merge remote-tracking branch 'remotes/rth/tags/pull-tcg-20180116' into
staging (2018-01-16 17:36:39 +)
are available in the Git repository at:
git://github.com/ehabkost/qemu.git tags/x86-pull-request
for you t
From: Haozhong Zhang
Signed-off-by: Haozhong Zhang
Message-Id: <20171219033730.12748-2-haozhong.zh...@intel.com>
Signed-off-by: Eduardo Habkost
---
include/hw/i386/pc.h | 3 +++
hw/i386/pc_piix.c| 15 ---
hw/i386/pc_q35.c | 13 +++--
3 files changed, 26 insertions(
From: Haozhong Zhang
CPUID_7_0_EBX_CLFLUSHOPT is missed in current "Skylake-Server" cpu
model. Add it to "Skylake-Server" cpu model on pc-i440fx-2.12 and
pc-q35-2.12. Keep it disabled in "Skylake-Server" cpu model on older
machine types.
Signed-off-by: Haozhong Zhang
Message-Id: <20171219033730
On Wed, Jan 17, 2018 at 04:43:34PM +0100, Igor Mammedov wrote:
> cpu_init(cpu_model) were replaced by cpu_create(cpu_type) so
> no users are left, remove it.
>
> Signed-off-by: Igor Mammedov
Wonderful.
Reviewed-by: Eduardo Habkost
--
Eduardo
On Wed, Jan 17, 2018 at 04:43:32PM +0100, Igor Mammedov wrote:
> The last user of it was machine type 'none', which used field
> to create CPU id user requested it on CLI with -cpu option.
>
> We could compare pointers of MachineState::cpu_type and
> MachineClass::default_cpu_type to check for the
On Wed, Jan 17, 2018 at 04:43:23PM +0100, Igor Mammedov wrote:
> it will be used for for 2 purposes, 1st is to
> provide to cpu name resolving class for machine 'none'
> cpu_parse_cpu_model(machine_class->default_cpu_type, cpu_model)
> and later to drop a bunch of ifdefs *-user/main.c that
> set
On Wed, Jan 17, 2018 at 10:20:27AM +0100, Greg Kurz wrote:
> A variable is already defined at the begining of the function to
> hold a pointer to the CPU core object:
>
> sPAPRCPUCore *core = SPAPR_CPU_CORE(OBJECT(dev));
>
> No need to define it again in the pre-2.10 compatibility code snippl
On 01/17/2018 12:39 PM, Alistair Francis wrote:
> Since commit "linux-user: Tidy and enforce reserved_va initialization"
> (18e80c55bb6ec17c05ec0ba717ec83933c2bfc07) the Yocto webkitgtk build
> hangs when cross compiling for 32-bit x86 on a 64-bit x86 machine using
> musl.
>
> To fix the issue red
On 01/17/2018 06:41 PM, Alistair Francis wrote:
> On Wed, Jan 17, 2018 at 12:05 AM, Cleber Rosa wrote:
>> TL;DR
>> =
>>
>> This is about how QEMU developers can get started with functional
>> tests that are built on top of the Avocado libraries (and meant to be
>> run with the Avocado test r
On Wed, Jan 17, 2018 at 04:43:34PM +0100, Igor Mammedov wrote:
> cpu_init(cpu_model) were replaced by cpu_create(cpu_type) so
> no users are left, remove it.
>
> Signed-off-by: Igor Mammedov
ppc part
Acked-by: David Gibson
> ---
> CC: Richard Henderson (maintainer:Alpha)
> CC: Peter Maydell
Hey Paolo,
Thanks for all the feedback. After talking with various members of the team
around these scenarios I think its best we add the migration blockers for all
of your comments unfortunately. The answers to your question are below:
1. For CPUID. The API has support for an "EXTENDED_VM_EXIT
On Wed, Jan 17, 2018 at 12:05 AM, Cleber Rosa wrote:
> TL;DR
> =
>
> This is about how QEMU developers can get started with functional
> tests that are built on top of the Avocado libraries (and meant to be
> run with the Avocado test runner).
>
> The past
>
>
> The Avocado project[1]
On 01/17/2018 05:18 PM, no-re...@patchew.org wrote:
> Hi,
>
> This series failed build test on s390x host. Please find the details below.
>
@)(#_%(@)#_
I forgot to check in some changes in my local branch that keep the texi
from breaking.
Sorry for the noise...
Hi,
This series failed build test on s390x host. Please find the details below.
Type: series
Message-id: 20180117221210.28575-1-js...@redhat.com
Subject: [Qemu-devel] [PATCH v3] file-posix: specify expected filetypes
=== TEST SCRIPT BEGIN ===
#!/bin/bash
# Testing script will be invoked under th
Adjust each caller of raw_open_common to specify if they are expecting
host and character devices or not. Tighten expectations of file types upon
open in the common code and refuse types that are not expected.
This has two effects:
(1) Character and block devices are now considered deprecated for
On 17.01.2018 22:37, Christian Borntraeger wrote:
>
>
> On 01/17/2018 10:13 PM, David Hildenbrand wrote:
>> On 17.01.2018 20:37, Christian Borntraeger wrote:
>>> stfle.81 (ppa15) is a transparent facility that can be passed to the
>>> guest without the need to implement hypervisor support. As thi
On 01/17/2018 10:13 PM, David Hildenbrand wrote:
> On 17.01.2018 20:37, Christian Borntraeger wrote:
>> 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 f
Coverity found that the variable tx_rx in the function
xilinx_spips_flush_txfifo was being used uninitialized (CID 1383841). This
patch corrects this by always initializing tx_rx to zeros.
Signed-off-by: Francisco Iglesias
---
v2. Add a sanity check on the num_busses property when realizing the
On Wed, 2018-01-17 at 15:39 +0100, Cédric Le Goater wrote:
> Migration is a problem. We will need both backend QEMU objects to be
> available anyhow if we want to migrate. So we are back to the current
> solution creating both QEMU objects but we can try to defer some of the
> KVM inits and crea
On 17.01.2018 20:37, Christian Borntraeger wrote:
> 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.
>
> Signed-off-by: Christian Borntraeger
>
On 17.01.2018 20:37, Christian Borntraeger wrote:
> 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.
>
> Signed
On 17.01.2018 20:37, Christian Borntraeger wrote:
> replace with proper header sync
>
> Signed-off-by: Christian Borntraeger
> ---
> linux-headers/asm-s390/kvm.h | 9 -
> linux-headers/linux/kvm.h| 5 +++--
> 2 files changed, 7 insertions(+), 7 deletions(-)
>
> diff --git a/linux-he
On 01/17/2018 05:39 PM, Alistair Francis wrote:
> Since commit "linux-user: Tidy and enforce reserved_va initialization"
> (18e80c55bb6ec17c05ec0ba717ec83933c2bfc07) the Yocto webkitgtk build
> hangs when cross compiling for 32-bit x86 on a 64-bit x86 machine using
> musl.
>
> To fix the issue red
On Wed, Jan 17, 2018 at 12:39 PM, Philippe Mathieu-Daudé
wrote:
> On 01/17/2018 02:27 PM, Alistair Francis wrote:
>> Initial commit of the ZynqMP RTC device.
>>
>> Signed-off-by: Alistair Francis
>> ---
>> V2:
>> - Delete unused realise function
>> - Remove DB_PRINT()
>>
>> hw/timer/Makefile.o
On 01/17/2018 02:27 PM, Alistair Francis wrote:
> Signed-off-by: Alistair Francis
> Reviewed-by: Peter Maydell
Reviewed-by: Philippe Mathieu-Daudé
> ---
>
> hw/arm/xlnx-zynqmp.c | 14 ++
> include/hw/arm/xlnx-zynqmp.h | 2 ++
> 2 files changed, 16 insertions(+)
>
> diff
On 01/17/2018 02:27 PM, Alistair Francis wrote:
> Allow the guest to determine the time set from the QEMU command line.
>
> This includes adding a trace event to debug the new time.
>
> The migration logic was copied from the PL031 migration logic.
>
> Signed-off-by: Alistair Francis
> ---
> V3
Since commit "linux-user: Tidy and enforce reserved_va initialization"
(18e80c55bb6ec17c05ec0ba717ec83933c2bfc07) the Yocto webkitgtk build
hangs when cross compiling for 32-bit x86 on a 64-bit x86 machine using
musl.
To fix the issue reduce the MAX_RESERVED_VA macro to be a closer match
to what i
On 01/17/2018 02:27 PM, Alistair Francis wrote:
> Initial commit of the ZynqMP RTC device.
>
> Signed-off-by: Alistair Francis
> ---
> V2:
> - Delete unused realise function
> - Remove DB_PRINT()
>
> hw/timer/Makefile.objs | 1 +
> hw/timer/xlnx-zynqmp-rtc.c | 218
> +++
On 17 January 2018 at 19:15, Igor Mammedov wrote:
> On Wed, 17 Jan 2018 16:12:09 +
> Peter Maydell wrote:
>> I like moving this from being an ifdef ladder into per-cpu
>> code, but I don't think the definition belongs in target/$ARCH.
>> It's part of the choice usermode makes about how to han
Hi Kevin and Anatol.
Kevin, thanks for your review.
More inline below...
On 01/15/18 07:54, Kevin Wolf wrote:
Am 21.12.2017 um 18:25 hat Jack Schwartz geschrieben:
Properly account for the possibility of multiboot kernels with a zero
bss_end_addr. The Multiboot Specification, section 3.1.3 a
It is just a header sync and mimics the kernel.
The previous header sync added the the commit that added the SPDX tag and this
header sync added the commit that removed the now redundant licence text.
On 01/17/2018 08:46 PM, Eric Blake wrote:
> On 01/17/2018 01:37 PM, Christian Borntraeger wrote:
On 01/17/2018 01:37 PM, Christian Borntraeger wrote:
> replace with proper header sync
>
> Signed-off-by: Christian Borntraeger
> ---
> linux-headers/asm-s390/kvm.h | 9 -
> linux-headers/linux/kvm.h| 5 +++--
> 2 files changed, 7 insertions(+), 7 deletions(-)
>
> diff --git a/linux
On 2018-01-17 17:54, Eric Blake wrote:
> As requested here:
> https://lists.gnu.org/archive/html/qemu-devel/2018-01/msg03984.html
>
> Eric Blake (1):
> iotests: Split 177 into two parts for compat=0.10
>
> Max Reitz (1):
> iotests: Disable some tests for compat=0.10
Thanks! Applied to my bl
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.
Signed-off-by: Christian Borntraeger
---
target/s390x/cpu.c
replace with proper header sync
Signed-off-by: Christian Borntraeger
---
linux-headers/asm-s390/kvm.h | 9 -
linux-headers/linux/kvm.h| 5 +++--
2 files changed, 7 insertions(+), 7 deletions(-)
diff --git a/linux-headers/asm-s390/kvm.h b/linux-headers/asm-s390/kvm.h
index 32d372e..1
We want to provide more hw features to guests, namely the new bpb
control as well as other transparent facilities that might be
introduced by firmware updates (e.g. the stfle facility 81).
See the kernel discussion for the KVM side
https://www.spinics.net/lists/kernel/msg2700551.html
v1->v2: - st
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.
Signed-off-by: Christian Borntraeger
---
target/s390x/cpu_features.c | 1 +
target/s390x/cpu_
On Wed, Jan 17, 2018 at 01:02:07PM -0600, Eric Blake wrote:
> On 01/17/2018 10:41 AM, Daniel P. Berrange wrote:
> > Replace the keymap_qcode table with automatically generated
> > tables.
> >
> > Missing entries in keymap_qcode now fixed:
> >
>
> >
> > When a keycode is removed from the list of
On Wed, 17 Jan 2018 17:04:31 +0100
David Hildenbrand wrote:
> On 17.01.2018 16:43, Igor Mammedov wrote:
> > it will be used for for 2 purposes, 1st is to
> > provide to cpu name resolving class for machine 'none'
> > cpu_parse_cpu_model(machine_class->default_cpu_type, cpu_model)
> > and later
The gen_pcie_root_port mem-reserve and pref32-reserve properties are
defined as size (so uint64_t), but passed as uint32_t when building
the 'IO hints' vendor specific capability.
Passing 4G (or more) gets truncated and passed as a zero reservation.
Is not a huge issue since the guest firmware will
On Wed, 17 Jan 2018 16:12:09 +
Peter Maydell wrote:
> On 17 January 2018 at 15:43, Igor Mammedov wrote:
> > Series is finishing work on generalizing cpu_model parsing
> > and limiting parts that deal with inconsistent cpu_model
> > naming to "-cpu" CLI option processing in vl.c/*-user.main.c
On 01/17/2018 10:41 AM, Daniel P. Berrange wrote:
> Replace the keymap_qcode table with automatically generated
> tables.
>
> Missing entries in keymap_qcode now fixed:
>
>
> When a keycode is removed from the list of possible keycodes that host can
> send to the guest, it means that the guest
On Wed, 17 Jan 2018 17:53:48 +0100
Andrew Jones wrote:
> On Wed, Jan 17, 2018 at 04:18:30PM +, Peter Maydell wrote:
> > On 17 January 2018 at 16:15, Igor Mammedov wrote:
> > > my idea was to drop fixed RAM base for virt board (at least for
> > > new machine types) so that QEMU could specif
1 - 100 of 376 matches
Mail list logo
