If we silence docker when --quiet is given, we should also silence the
.pre script (i.e. debootstrap).
Only discards stdout, so some diagnostics (e.g. from git clone) are
still printed. Most of the verbose output is gone however and this way
we still have a chance to see error messages.
Signed-of
Building the debian-debootstrap image will usually fail if EXECUTABLE
isn't set (when using the Makefile). Warn the user in this case so
they know why it's failing.
Signed-off-by: Sascha Silbe
---
tests/docker/Makefile.include | 3 +++
1 file changed, 3 insertions(+)
diff --git a/tests/docker/M
On Wed, Aug 24, 2016 at 04:29:07PM +0200, Greg Kurz wrote:
> At various places in 9pfs, full paths are created by concatenating a guest
> originated string to the export path. A malicious guest could forge a
> relative path and access files outside the export path.
>
> A tentative fix was sent rec
A CPU model consists of a CPU definition, to which delta changes are
applied - features added or removed (e.g. z13-base,vx=on). In addition,
certain properties (e.g. cpu id) can later on change during migration
but belong into the CPU model. This data will later be filled from the
host model in the
Unlike Popen.communicate(), subprocess.call() doesn't read from the
stdout file descriptor. If the child process produces more output than
fits into the pipe buffer, it will block indefinitely.
If we don't intend to consume the output, just send it straight to
/dev/null to avoid this issue.
Signe
The mha is provided in the CPU model, so get any CPU and extract the value.
Acked-by: Cornelia Huck
Signed-off-by: David Hildenbrand
---
hw/s390x/sclp.c | 1 +
include/hw/s390x/sclp.h | 3 ++-
target-s390x/cpu_models.c | 14 ++
target-s390x/cpu_models.h | 1 +
4 files
When using the git version of debootstrap (because no usable version
of debootstrap was installed on the host), we need to run 'make' so
that devices.tar.gz gets built. Otherwise the first debootstrap stage
will fail without printing any error message.
Signed-off-by: Sascha Silbe
---
tests/docke
The 'realpath' executable is shipped in a separate package that isn't
installed by default on some distros.
We already use 'readlink -e' (provided by GNU coreutils) in some other
part of the code, so let's settle for that instead.
Signed-off-by: Sascha Silbe
---
Too bad there isn't a POSIX equiv
debootstrap prior to 1.0.67 generated an empty sources.list during
foreign bootstraps (Debian#732255 [1]). Fall back to the git checkout
if the installed debootstrap version is too old.
[1] https://bugs.debian.org/732255
Signed-off-by: Sascha Silbe
---
Not sure if this used to work in even older
Hi,
Your series seems to have some coding style problems. See output below for
more information:
Message-id: 1472062266-53206-1-git-send-email-d...@linux.vnet.ibm.com
Subject: [Qemu-devel] [Patch v3 00/30] s390x CPU models: exposing features
Type: series
=== TEST SCRIPT BEGIN ===
#!/bin/bash
BA
Let's provide a standardized interface to baseline two CPU models, to
create a third, compatible one. This is especially helpful when two
CPU models are not identical, but a CPU model is required that is
guaranteed to run under both configurations, where the original models run.
"query-cpu-model-b
Hi,
Following patch regresses Linux boot on PReP machine:
commit a2e71b28e832346409efc795ecd1f0a2bcb705a3
Author: Benjamin Herrenschmidt
Date: Tue Jun 21 23:48:46 2016 +0200
ppc: Fix rfi/rfid/hrfi/... emulation
This reworks emulation of the various "rfi" variants. I removed
some
On (Tue) 23 Aug 2016 [23:12:21], Markus Armbruster wrote:
> Amit Shah writes:
>
> > On (Mon) 22 Aug 2016 [16:09:27], Jason Wang wrote:
> >> From: Cao jin
> >>
> >> Commit 66bf7d58 removed internal msi state flag E1000E_USE_MSI,
> >> E1000E_USE_MSIX
> >> is not necessary too, remove it now. And
On 23 August 2016 at 17:34, Michael S. Tsirkin wrote:
> The following changes since commit 60ac136102098a70b97ab0c07bc7bf53131c:
>
> target-arm: Fix warn about implicit conversion (2016-08-12 11:12:24 +0100)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/virt/
On 08/24/2016 12:48 PM, Richard Henderson wrote:
> Patches 1-4 remove the use of ifunc from the implementation.
>
> Patch 6 adjusts the x86 implementation a bit more to take
> advantage of ptest (in sse4.1) and unaligned accesses (in avx1).
Do we really care about unaligned access? Or can we gua
On 24 August 2016 at 17:40, Greg Kurz wrote:
> On Wed, 24 Aug 2016 16:00:24 +0100
> Peter Maydell wrote:
>> Do we also need ".." and "." to be illegal names (for at least most
>> operations)?
> I understand how ".." could be an issue, but I don't for "."... can you
> please elaborate ?
If you t
On Wed, Aug 24, 2016 at 08:11:01PM +0200, David Hildenbrand wrote:
> Let's provide a standardized interface to expand CPU models. This interface
> can be used by tooling to get details about a specific CPU model in a
> certain configuration, e.g. about the "host" model.
>
> To take care of all arc
On Wed, Aug 24, 2016 at 08:11:02PM +0200, David Hildenbrand wrote:
> Let's provide a standardized interface to compare two CPU models.
> "query-cpu-model-compare" takes two models and returns how they compare
> in a specific configuration.
>
> The result will give guarantees about runnability. E.
On Wed, Aug 24, 2016 at 08:11:03PM +0200, David Hildenbrand wrote:
> Let's provide a standardized interface to baseline two CPU models, to
> create a third, compatible one. This is especially helpful when two
> CPU models are not identical, but a CPU model is required that is
> guaranteed to run un
On 08/24/16 09:44, Evan Hunter wrote:
Hi,
I noticed that QEMU would not compile on Windows in the MSYS2 environment.
Here is a patch that adds a check for it to the configure script and
amended some ifdefs so it now builds.
At the bottom of this email is a build script I made for building under
On 08/24/2016 12:18 PM, Eric Blake wrote:
On 08/24/2016 12:48 PM, Richard Henderson wrote:
Patches 1-4 remove the use of ifunc from the implementation.
Patch 6 adjusts the x86 implementation a bit more to take
advantage of ptest (in sse4.1) and unaligned accesses (in avx1).
Do we really care
So I encountered this test failure running 'make check' on
32-bit ARM:
MALLOC_PERTURB_=${MALLOC_PERTURB_:-$((RANDOM % 255 + 1))} gtester -k
--verbose -m=quick tests/test-qht
TEST: tests/test-qht... (pid=15763)
/qht/mode/default: OK
/qht/mode/re
On 24 August 2016 at 20:58, Stefan Weil wrote:
> Maybe you could start with documenting the MSYS2 based build process on
> http://wiki.qemu.org/Hosts/W32 and refer to a QEMU git clone which includes
> the necessary modifications.
>
> More feedback also from other contributors whether MSYS2 support
This patch tries to do the Right Thing™ to test for C11 features,
which is to test __STDC_VERSION__.
Signed-off-by: Pranith Kumar
---
include/qemu/atomic.h | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/include/qemu/atomic.h b/include/qemu/atomic.h
index 43b0645..d313e
Use the __atomic_*_n() primitives which take the value as argument. It
is not necessary to store the value locally before calling the
primitive, hence saving us a stack store and load.
Signed-off-by: Pranith Kumar
---
include/qemu/atomic.h | 16 +---
1 file changed, 5 insertions(+),
Remove the redundant barrier() after the fence as agreed in previous
discussion here:
https://lists.gnu.org/archive/html/qemu-devel/2016-04/msg00489.html
Signed-off-by: Pranith Kumar
---
include/qemu/atomic.h | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/include/qem
On 08/24/2016 01:10 PM, David Hildenbrand wrote:
> It might be of interest for tooling whether a CPU definition can be safely
> used when migrating, or if e.g. CPU features might get lost during
> migration when migrationg from/to a different QEMU version or host, even if
> the same compatibility m
> On 08/24/2016 01:10 PM, David Hildenbrand wrote:
> > It might be of interest for tooling whether a CPU definition can be safely
> > used when migrating, or if e.g. CPU features might get lost during
> > migration when migrationg from/to a different QEMU version or host, even if
> > the same compa
On Thu, Aug 18, 2016 at 08:38:47 -0700, Richard Henderson wrote:
> A couple of other notes, as I've thought about this some more.
Thanks for spending time on this.
I have a new patchset (will send as a reply to this e-mail in a few
minutes) that has good performance. Its main ideas:
- Use transa
On 24/08/16 19:39, Hervé Poussineau wrote:
> Hi,
>
> Following patch regresses Linux boot on PReP machine:
>
> commit a2e71b28e832346409efc795ecd1f0a2bcb705a3
> Author: Benjamin Herrenschmidt
> Date: Tue Jun 21 23:48:46 2016 +0200
>
> ppc: Fix rfi/rfid/hrfi/... emulation
>
> This re
> diff --git a/hw/virtio/virtio-pstore.c b/hw/virtio/virtio-pstore.c
> new file mode 100644
> index 000..b8fb4be
> --- /dev/null
> +++ b/hw/virtio/virtio-pstore.c
> @@ -0,0 +1,699 @@
> +/*
> + * Virtio Pstore Device
> + *
> + * Copyright (C) 2016 LG Electronics
> + *
> + * Authors:
> + * Nam
Signed-off-by: Emilio G. Cota
---
include/qemu/rcu.h | 7 +++
1 file changed, 7 insertions(+)
diff --git a/include/qemu/rcu.h b/include/qemu/rcu.h
index 83ae280..0f6e467 100644
--- a/include/qemu/rcu.h
+++ b/include/qemu/rcu.h
@@ -98,6 +98,13 @@ static inline void rcu_read_unlock(void)
Signed-off-by: Emilio G. Cota
---
include/qemu/htm.h | 43 +++
1 file changed, 43 insertions(+)
create mode 100644 include/qemu/htm.h
diff --git a/include/qemu/htm.h b/include/qemu/htm.h
new file mode 100644
index 000..dc84bc1
--- /dev/null
+++ b/incl
Signed-off-by: Emilio G. Cota
---
include/qemu/htm.h | 39 +++
1 file changed, 39 insertions(+)
diff --git a/include/qemu/htm.h b/include/qemu/htm.h
index dc84bc1..f367ee4 100644
--- a/include/qemu/htm.h
+++ b/include/qemu/htm.h
@@ -39,5 +39,44 @@ static inlin
This avoids the chance of reading a corrupted list of CPUs in usermode.
Note: this breaks hw/ppc/spapr due to the removal of CPU_FOREACH_REVERSE.
Signed-off-by: Emilio G. Cota
---
cpus.c | 2 +-
exec.c | 18 +++---
include/qom/cpu.h| 16 +++--
Signed-off-by: Emilio G. Cota
---
target-arm/helper-a64.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/target-arm/helper-a64.c b/target-arm/helper-a64.c
index 8ce518b..6f3fd17 100644
--- a/target-arm/helper-a64.c
+++ b/target-arm/helper-a64.c
@@ -453,7 +453,7 @@ uint64_
TODO: convert paired atomics as well.
Signed-off-by: Emilio G. Cota
---
cpu-exec.c | 4
target-arm/helper-a64.c| 31 +++
target-arm/helper-a64.h| 4
target-arm/op_helper.c | 4
target-arm/translate-a64.c | 16 ++---
Signed-off-by: Emilio G. Cota
---
cpu-exec.c | 38 +++---
1 file changed, 11 insertions(+), 27 deletions(-)
diff --git a/cpu-exec.c b/cpu-exec.c
index 041f8b7..63d739a 100644
--- a/cpu-exec.c
+++ b/cpu-exec.c
@@ -309,34 +309,18 @@ static TranslationBlock *tb_find_
On Wed, 2016-08-24 at 20:39 +0200, Hervé Poussineau wrote:
> Hi,
>
> Following patch regresses Linux boot on PReP machine:
Where do I find the source for that kernel ?
Cheers,
Ben.
> commit a2e71b28e832346409efc795ecd1f0a2bcb705a3
> Author: Benjamin Herrenschmidt
> Date: Tue Jun 21 23:48:46
Signed-off-by: Emilio G. Cota
---
cpu-exec.c | 1 +
include/exec/exec-all.h | 5 +++
linux-user/main.c | 89 +
linux-user/syscall.c| 1 +
4 files changed, 96 insertions(+)
diff --git a/cpu-exec.c b/cpu-exec.c
index 63d739a
On Thu, Aug 18, 2016 at 09:41:59AM -0700, Neo Jia wrote:
> Hi libvirt experts,
>
> I am starting this email thread to discuss the potential solution / proposal
> of
> integrating vGPU support into libvirt for QEMU.
>
> Some quick background, NVIDIA is implementing a VFIO based mediated device
>
On Thu, Aug 04, 2016 at 12:33:54AM +0530, Kirti Wankhede wrote:
> diff --git a/Documentation/vfio-mediated-device.txt
> b/Documentation/vfio-mediated-device.txt
> new file mode 100644
> index ..029152670141
> --- /dev/null
> +++ b/Documentation/vfio-mediated-device.txt
> @@ -0,0 +1,235
On Wed, Aug 24, 2016 at 21:39:01 +0100, Peter Maydell wrote:
> So I encountered this test failure running 'make check' on
> 32-bit ARM:
>
> MALLOC_PERTURB_=${MALLOC_PERTURB_:-$((RANDOM % 255 + 1))} gtester -k
> --verbose -m=quick tests/test-qht
> TEST: tests/test-qht... (pid=15763)
> /qht/mode/d
On 25 August 2016 at 00:44, Emilio G. Cota wrote:
> On Wed, Aug 24, 2016 at 21:39:01 +0100, Peter Maydell wrote:
>> So I encountered this test failure running 'make check' on
>> 32-bit ARM:
>>
>> MALLOC_PERTURB_=${MALLOC_PERTURB_:-$((RANDOM % 255 + 1))} gtester -k
>> --verbose -m=quick tests/test-
On Wed, 2016-08-24 at 20:39 +0200, Hervé Poussineau wrote:
> Hi,
>
> Following patch regresses Linux boot on PReP machine:
>
> commit a2e71b28e832346409efc795ecd1f0a2bcb705a3
> Author: Benjamin Herrenschmidt
> Date: Tue Jun 21 23:48:46 2016 +0200
>
> ppc: Fix rfi/rfid/hrfi/... emulation
On Tue, Aug 23, 2016 at 08:57:44AM +, Gaohaifeng (A) wrote:
> Hi Daniel & Paolo,
>
> Commit 9894dc0c "char: convert from GIOChannel to QIOChannel", about
>
> the below code segment:
>
> -static gboolean tcp_chr_read(GIOChannel *chan, GIOCondition cond, void
> *opaque)
> +static gboolean tcp
Public bug reported:
Qemu-kvm version : QEMU emulator version 1.5.3 (qemu-kvm-1.5.3-105.el7),
Copyright (c) 2003-2008 Fabrice Billard
Qemu version: Virsh command line tool of libvirt 1.2.17
I have the VM stuck in bios (efi shell), but i don't see the watchdog in
the host bringing it down?
Coupl
Hi~~ Jason.
If you have time, can you give me some feedback for this series?
Thanks
Zhang Chen
On 08/17/2016 04:10 PM, Zhang Chen wrote:
COLO-compare is a part of COLO project. It is used
to compare the network package to help COLO decide
whether to do checkpoint.
Filter-rewriter is a part
This series adds Mediated device support to Linux host kernel. Purpose
of this series is to provide a common interface for mediated device
management that can be used by different devices. This series introduces
Mdev core module that create and manage mediated devices, VFIO based driver
for mediate
Design for Mediated Device Driver:
Main purpose of this driver is to provide a common interface for mediated
device management that can be used by different drivers of different
devices.
This module provides a generic interface to create the device, add it to
mediated bus, add device to IOMMU grou
VFIO MDEV driver registers with MDEV core driver. MDEV core driver creates
mediated device and calls probe routine of MPCI VFIO driver. This driver
adds mediated device to VFIO core module.
Main aim of this module is to manage all VFIO APIs for each mediated
device. Those are:
- get VFIO device inf
VFIO IOMMU drivers are designed for the devices which are IOMMU capable.
Mediated device only uses IOMMU APIs, the underlying hardware can be
managed by an IOMMU domain.
Aim of this change is:
- To use most of the code of TYPE1 IOMMU driver for mediated devices
- To support direct assigned device
Add file Documentation/vfio-mediated-device.txt that include details of
mediated device framework.
Signed-off-by: Kirti Wankhede
Signed-off-by: Neo Jia
Change-Id: I137dd646442936090d92008b115908b7b2c7bc5d
Reviewed-on: http://git-master/r/1182512
Reviewed-by: Automatic_Commit_Validation_User
---
On 2016年08月25日 11:44, Zhang Chen wrote:
Hi~~ Jason.
If you have time, can you give me some feedback for this series?
Thanks
Zhang Chen
Yes, a little busy this week, will do it next week.
Thanks
On 08/17/2016 04:10 PM, Zhang Chen wrote:
COLO-compare is a part of COLO project. It is u
On Thu, 2016-08-25 at 11:31 +1000, Benjamin Herrenschmidt wrote:
> On Wed, 2016-08-24 at 20:39 +0200, Hervé Poussineau wrote:
> >
> > Hi,
> >
> > Following patch regresses Linux boot on PReP machine:
> >
> > commit a2e71b28e832346409efc795ecd1f0a2bcb705a3
> > Author: Benjamin Herrenschmidt
> >
On Thu, 2016-08-25 at 11:31 +1000, Benjamin Herrenschmidt wrote:
>
> Interesting, the problem is only with 603, not 604. I think I might
> have broken something with the 603 SW TLB loading stuff which is
> a bit weird, I'll have a look. Thanks.
This fixes it to some extent... It gets to "press en
>>> Markus Armbruster 2016/8/17 星期三 下午 2:52 >>>
>"Lin Ma" writes:
>
> Marc-André Lureau 8/17/2016 1:25 上午 >>>
>[...]
>>>How different is it from the list in qemu -help ? Why duplicate that list
>>>with less informations (arguments and details) ? Do you expect it to be
>>>easily machine rea
Hi Richard,
Migration fails on arm64 with these patches.
On the destination VM, follow errors are appearing.
qemu-system-aarch64: VQ 0 size 0x400 Guest index 0x0 inconsistent with
Host index 0x1937: delta 0xe6c9
qemu-system-aarch64: error while loading state for instance 0x0 of
device 'virtio-m
Am 17.08.2016 um 21:30 schrieb Michael Roth:
Hi everyone,
I am pleased to announce that the QEMU v2.6.1 stable release is now
available:
http://wiki.qemu.org/download/qemu-2.6.1.tar.bz2
v2.6.1 is now tagged in the official qemu.git repository,
and the stable-2.6 branch has been updated acco
101 - 159 of 159 matches
Mail list logo
