Hi Peter,
While vfio with virtio-iommu I observed one issue, When virtio-iommu device
exists but guest kernel does not have virtio-iommu driver (not enabled in
Config) then IOMMU faults are reported on host.
This is because no mapping is created in IOMMU, not even default guest-physical
to re
This patch implements what I've been working towards over the past few
months in order to get a more realistic Ultra 5 model for the sun4u
machine. The basic change is that devices are no longer plugged into the
PCI root bus, but behind PCI busA for in-built devices and PCI busB for all
other devic
This patch updates the sun4u model to being much closer to a real Ultra 5
by moving devices behind the 2 simba PCI bridges (A and B) as found on real
hardware.
The most noticeable change introduced by this patchset is that in-built devices
are no longer attached to the PCI root bus, but instead be
Default replay does not work with virtio-iommu,
so this patch provide virtio-iommu replay functionality.
Signed-off-by: Bharat Bhushan
---
v3->v4:
- Replay functionality moved in separate patch
- No other changes
hw/virtio/trace-events | 1 +
hw/virtio/virtio-iommu.c | 38 +
On Tue, Sep 26, 2017 at 10:29:36AM +0200, Igor Mammedov wrote:
> On Tue, 26 Sep 2017 09:19:28 +0200
> Greg Kurz wrote:
>
> > On Tue, 26 Sep 2017 12:57:39 +1000
> > David Gibson wrote:
> >
> > > On Mon, Sep 25, 2017 at 11:47:33AM +0200, Greg Kurz wrote:
> > > > The CPU core abstraction belongs
Finally add notify_flag_changed() to for memory-region
access flag iommu flag change notifier
Finally add the memory notifier
Signed-off-by: Bharat Bhushan
---
v3->v4:
- notify_flag_changed functionality moved in separate patch
- No other changes
hw/virtio/trace-events | 2 ++
hw/virtio/v
On Tue, Sep 26, 2017 at 09:19:28AM +0200, Greg Kurz wrote:
> On Tue, 26 Sep 2017 12:57:39 +1000
> David Gibson wrote:
>
> > On Mon, Sep 25, 2017 at 11:47:33AM +0200, Greg Kurz wrote:
> > > The CPU core abstraction belongs to the machine code. This also gets
> > > rid of some code duplication.
> >
Translate msi address if device is behind virtio-iommu.
This logic is similar to vSMMUv3/Intel iommu emulation.
This RFC patch does not handle the case where both vsmmuv3 and
virtio-iommu are available.
Signed-off-by: Eric Auger
Signed-off-by: Bharat Bhushan
---
v3->v4
- No changes
target/ar
iommu-notifier are called when a device is attached
or detached to as address-space.
This is needed for VFIO.
Signed-off-by: Bharat Bhushan
Signed-off-by: Eric Auger
---
v3->v4:
Follwoig fixes by Eric
- Return "false" from virtio_iommu_mapping_unmap/map()
- Calling virtio_iommu_notify_unmap/m
This patch series integrates VFIO/VHOST with virtio-iommu.
This version is mainly about rebasing on v4 version on
virtio-iommu device framework from Eric Augur and
addresing review comments.
This patch series allows PCI pass-through using virtio-iommu.
This series is based on:
- virtio-iommu
This patch extends VIRTIO_IOMMU_T_MAP/UNMAP request to
notify registered iommu-notifier.
This is needed for VFIO support,
Signed-off-by: Bharat Bhushan
Signed-off-by: Eric Auger
---
v3->v4:
Follwoig fixes by Eric
- Calling virtio_iommu_notify_map() for all device in AS
- virtio_iommu_notify_u
On Tue, 09/26 08:48, Eric Blake wrote:
> On 09/26/2017 06:01 AM, Fam Zheng wrote:
> > Report error and exit upon compiling error, otherwise the iotests output
> > will be pure noise.
> >
> > Signed-off-by: Fam Zheng
> > ---
> > tests/docker/test-block | 2 +-
> > 1 file changed, 1 insertion(+),
On Tue, 09/26 13:17, Philippe Mathieu-Daudé wrote:
> On 09/26/2017 10:36 AM, Alex Bennée wrote:
> > The usual behaviour of /etc/profile is to set the default PATH for
> > users. This runs into problems when we have updated PATH in our
> > dockerfile e.g. to access a cross-compiler in a non-standard
在 2017/9/26 下午9:36, Christian Borntraeger 写道:
@@ -557,6 +557,12 @@ static void kvm_s390_flic_realize(DeviceState *dev, Error
**errp)
test_attr.group = KVM_DEV_FLIC_CLEAR_IO_IRQ;
flic_state->clear_io_supported = !ioctl(flic_state->fd,
KV
On 26.09.2017 22:35, Stefan Weil wrote:
> Am 26.09.2017 um 21:30 schrieb Michael S. Tsirkin:
>> On Fri, Sep 22, 2017 at 05:06:57AM +0200, Thomas Huth wrote:
>>> If QEMU has been compiled with the flags --enable-tcg-interpreter and
>>> --enable-debug, the guest is running incredibly slow. The pxe bo
在 2017/9/26 下午10:06, Christian Borntraeger 写道:
On 09/26/2017 03:43 PM, David Hildenbrand wrote:
+/* try enable the AIS facility */
+test_attr.group = KVM_DEV_FLIC_AISM_ALL;
+if (!ioctl(flic_state->fd, KVM_HAS_DEVICE_ATTR, test_attr)) {
+kvm_vm_enable_cap(kvm_state, KVM
[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1706866
Title:
migrate: a
On Tue, Sep 26, 2017 at 07:13:43PM +0800, Fam Zheng wrote:
> On Tue, 09/26 17:11, Peter Xu wrote:
> > If glib unset the flag after calling the destructor, it'll be fine.
> > But it's not doing it that way. And with above implementation of
> > glib, I don't see a good way to solve this problem via
On Thu, Jul 20, 2017 at 05:22:31PM +1000, Alexey Kardashevskiy wrote:
> This uses new kernel KVM_CAP_SPAPR_TCE_VFIO capability to enable
> in-kernel acceleration of TCE update requests which will go via
> the VFIO KVM device.
>
> Signed-off-by: Alexey Kardashevskiy
> Reviewed-by: David Gibson
I
Public bug reported:
Since booting could potentially take a lot of time and warnings are
likely to indicate that something is wrong, it would be useful to have a
command line flag which would abort the boot if there are any warnings.
An example might be network configuration. The following output
Hi Halil,
On 2017/9/15 23:59, Halil Pasic wrote:
>
>
> On 09/11/2017 03:12 AM, Longpeng(Mike) wrote:
>> From: Gonglei
>>
>> The virtio crypto device is a virtual crypto device (ie. hardware
>> crypto accelerator card). Currently, the virtio crypto device provides
>> the following crypto servic
Hi,
This series seems to have some coding style problems. See output below for
more information:
Type: series
Message-id: 20170916023417.14599-1-richard.hender...@linaro.org
Subject: [Qemu-devel] [PATCH v3 0/6] TCG vectorization and example conversion
=== TEST SCRIPT BEGIN ===
#!/bin/bash
BASE=
Richard Henderson writes:
> Signed-off-by: Richard Henderson
Reviewed-by: Alex Bennée
> ---
> target/arm/translate-a64.c | 216
> ++---
> 1 file changed, 143 insertions(+), 73 deletions(-)
>
> diff --git a/target/arm/translate-a64.c b/target/arm/tran
On 09/26/2017 11:33 AM, David Hildenbrand wrote:
> David Hildenbrand (6):
> s390x/tcg: fix checking for invalid memory check
> s390x/tcg: add MMU for real addresses
> s390x/tcg: make lura(g) use the new _real mmu.
> s390x/tcg: make stora(g) use the new _real mmu
> s390x/tcg: make testbloc
This will allow the test code to be improved to test multiple
devices in a single run.
Signed-off-by: Eduardo Habkost
---
scripts/device-crash-test | 29 ++---
1 file changed, 14 insertions(+), 15 deletions(-)
diff --git a/scripts/device-crash-test b/scripts/device-crash
When running device_add tests, test all devices in a single run
instead of restarting QEMU every time.
There's a plug_all testcase argument that can be used to make the
test code plug all devices at once. I'm adding this mode because
there's a crash that was detected while testing the script
with
Add a 'method' testcase argument that will test the device using
device_add instead of -device. A new device_add_error whitelist
key is now supported, to catch device_add errors.
Signed-off-by: Eduardo Habkost
---
scripts/device-crash-test | 38 +-
1 file cha
If we're running on quick mode, we won't wait for the full test
run, and will exit immediately if a fatal failure is found.
Signed-off-by: Eduardo Habkost
---
scripts/device-crash-test | 4
1 file changed, 4 insertions(+)
diff --git a/scripts/device-crash-test b/scripts/device-crash-test
i
Instead of making checkOneCase() return None on success, return
detailed info even if no problems were found. This will make
handling of device_add errors simpler, and improve debug output.
As logFailure() won't handle only failures, rename it to
logResult() and make it a bit more flexible about
This series implements device_add testing on device-crash-test.
The new test mode will be enabled by default in addition to the
old test cases, but if only device_add testing is wanted, it can
be specified using the '-t' command-line option, e.g.:
$ ./scripts/device-crash-test -t method=device_a
Allow test results without the 'log' and 'exitcode' keys. The
new device_add code won't report exitcode/log because multiple
devices will be tested on a single QEMU run.
Signed-off-by: Eduardo Habkost
---
scripts/device-crash-test | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff
Richard Henderson writes:
> Signed-off-by: Richard Henderson
Signed-off-by: Alex Bennée
> ---
> target/arm/cpu.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/target/arm/cpu.h b/target/arm/cpu.h
> index 98b9b26fd3..c346bd148f 100644
> --- a/target/arm/cpu.h
> +++
Richard Henderson writes:
> Signed-off-by: Richard Henderson
Other than live comments:
Reviewed-by: Alex Bennée
> ---
> Makefile.target | 2 +-
> accel/tcg/tcg-runtime.h | 24 ++
> tcg/tcg-gvec-desc.h | 49 +++
> tcg/tcg-op-gvec.h| 143
>
Now that we have query-device-info, we don't need to parse "info
qdm" output to find out if a device is user-creatable.
Signed-off-by: Eduardo Habkost
---
scripts/device-crash-test | 19 ++-
1 file changed, 2 insertions(+), 17 deletions(-)
diff --git a/scripts/device-crash-test
Add a command that returns QOM type information that is specific
to device types and is not returned by qom-list-types.
The returned DeviceTypeInfo struct inherits from ObjectTypeInfo,
so fields returned by qom-list-types are also included.
Signed-off-by: Eduardo Habkost
---
qapi-schema.json |
Extract the code that fills ObjectTypeInfo fields to a
qom_type_get_info() helper. It will be reused in other QMP
commands.
Signed-off-by: Eduardo Habkost
---
qmp.c | 14 ++
1 file changed, 10 insertions(+), 4 deletions(-)
diff --git a/qmp.c b/qmp.c
index e8c303116a..dec4bd843b 100
This series implements a new 'query-device-type' command, that
can be used to query TYPE_DEVICE-specific information that is not
returned by qom-list-types.
The new field can be used instead of "info qdm" parsing by the
device-crash-test script. It can be also used by hotplug test
cases, to skip
Extract device type lookup code from qmp_device_list_properties()
to a get_device_class() helper. It will be reused by other QMP
commands.
Signed-off-by: Eduardo Habkost
---
qmp.c | 24 ++--
1 file changed, 18 insertions(+), 6 deletions(-)
diff --git a/qmp.c b/qmp.c
index d
test introduced in 382176b4d78e070d119af8e0dcd00884c11bbec2
Signed-off-by: Carlo Marcelo Arenas Belón
Reviewed-by: Eric Blake
---
tests/.gitignore | 1 +
1 file changed, 1 insertion(+)
diff --git a/tests/.gitignore b/tests/.gitignore
index cf6d99c91e..53cb2efaee 100644
--- a/tests/.gitignore
+
On 26 September 2017 at 07:14, Michael Tokarev wrote:
> This is a resend of yesterday's pull request, with two patches
> removed:
> filter-mirror: segfault when specifying non existent device
> (causes testsuite to fail)
> dma/i82374: avoid double creation of i82374 device
> (better ve
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: 20170926201427.2833-1-richard.hender...@linaro.org
Subject: [Qemu-devel] [PATCH v3 0/9] Support the C
On 09/26/2017 03:25 PM, Carlo Marcelo Arenas Belón wrote:
Worth mentioning in the commit message body that it was introduced in
commit 382176b4.
> Signed-off-by: Carlo Marcelo Arenas Belón
> ---
> tests/.gitignore | 1 +
> 1 file changed, 1 insertion(+)
Reviewed-by: Eric Blake
>
> diff --gi
Am 26.09.2017 um 21:30 schrieb Michael S. Tsirkin:
> On Fri, Sep 22, 2017 at 05:06:57AM +0200, Thomas Huth wrote:
>> If QEMU has been compiled with the flags --enable-tcg-interpreter and
>> --enable-debug, the guest is running incredibly slow. The pxe boot test
>> can take up to 400 seconds when te
Signed-off-by: Carlo Marcelo Arenas Belón
---
tests/.gitignore | 1 +
1 file changed, 1 insertion(+)
diff --git a/tests/.gitignore b/tests/.gitignore
index cf6d99c91e..53cb2efaee 100644
--- a/tests/.gitignore
+++ b/tests/.gitignore
@@ -6,6 +6,7 @@ check-qdict
check-qnum
check-qjson
check-qlis
Even though there is only one monitor, and thus no race on this
global data object, there is also no point in having it. We can
just as well record the decision in the read_memory_function that
we select.
Reviewed-by: Alex Bennée
Signed-off-by: Richard Henderson
---
disas.c | 16 --
Tested-by: Alex Bennée
Reviewed-by: Alex Bennée
Signed-off-by: Richard Henderson
---
disas.c | 3 +++
target/arm/cpu.c | 21 ++---
2 files changed, 21 insertions(+), 3 deletions(-)
diff --git a/disas.c b/disas.c
index 1c44514254..23c4742f8d 100644
--- a/disas.c
+++ b/
Do not require the submodule, but use it if present (in preference
even to a system copy). This will allow us to easily use capstone
in older systems for which a package is not available, and also
easily track bug fixes from upstream.
Signed-off-by: Richard Henderson
---
Makefile| 4
On 09/13/2017 12:03 PM, Eric Blake wrote:
> We are gradually converting to byte-based interfaces, as they are
> easier to reason about than sector-based. Convert another internal
> type (no semantic change), and rename it to match the corresponding
> public function rename.
>
> Signed-off-by: E
Signed-off-by: Richard Henderson
---
disas.c | 4
target/ppc/translate_init.c | 6 ++
2 files changed, 10 insertions(+)
diff --git a/disas.c b/disas.c
index 23c4742f8d..0d212f2ac5 100644
--- a/disas.c
+++ b/disas.c
@@ -449,6 +449,10 @@ void disas(FILE *out, void *cod
On 09/13/2017 12:03 PM, Eric Blake wrote:
> We are gradually converting to byte-based interfaces, as they are
> easier to reason about than sector-based. Convert another internal
> function (no semantic change); and as with its public counterpart,
> rename to bdrv_co_block_status() to make the c
Now that every target is using the disas_set_info hook,
the flags argument is unused. Remove it.
Reviewed-by: Alex Bennée
Signed-off-by: Richard Henderson
---
include/disas/disas.h | 4 ++--
include/exec/log.h| 4 ++--
disas.c | 15 ---
m
Reviewed-by: Alex Bennée
Signed-off-by: Richard Henderson
---
disas.c | 33 -
monitor.c | 5 -
target/ppc/translate.c | 5 +
target/ppc/translate_init.c | 21 +
4 files changed, 22 insertions
Reviewed-by: Alex Bennée
Signed-off-by: Richard Henderson
---
disas.c | 4
target/i386/cpu.c | 7 +++
2 files changed, 11 insertions(+)
diff --git a/disas.c b/disas.c
index 746d76c07d..1c44514254 100644
--- a/disas.c
+++ b/disas.c
@@ -439,9 +439,13 @@ void disas(FILE *out, vo
If configured, prefer this over our rather dated copy of the
GPLv2-only binutils. This will be especially apparent with
the proposed vector extensions to TCG, as disas/i386.c does
not handle AVX.
Signed-off-by: Richard Henderson
---
include/disas/bfd.h | 4 +
include/disas/capstone.h |
Reviewed-by: Alex Bennée
Signed-off-by: Richard Henderson
---
disas.c | 22 ++
monitor.c | 21 -
target/i386/cpu.c | 12
target/i386/translate.c | 8 +---
4 files changed, 15 insertions(+), 48 deletions
Changes since v2:
* Fix a minor buglet in the monitor disassembly
* Add capstone as a submodule, preferring that when present.
The submodule idea came from discussion with PMM. The idea is that
we would potentially remove the old binutils code, and libvxil, and
rely on capstone entirely. Whi
On 09/26/2017 02:39 PM, John Snow wrote:
>> -int64_t bdrv_get_block_status(BlockDriverState *bs,
>> - int64_t sector_num,
>> - int nb_sectors, int *pnum,
>> - BlockDriverState **file)
>> +int64_t bdrv_block_statu
On 09/13/2017 12:03 PM, Eric Blake wrote:
> We are gradually moving away from sector-based interfaces, towards
> byte-based. In the common case, allocation is unlikely to ever use
> values that are not naturally sector-aligned, but it is possible
> that byte-based values will let us be more prec
On 26 September 2017 at 20:31, Michael S. Tsirkin wrote:
> On Mon, Sep 25, 2017 at 12:06:40AM +0300, Michael Tokarev wrote:
>> 22.09.2017 06:06, Thomas Huth wrote:
>> > If QEMU has been compiled with the flags --enable-tcg-interpreter and
>> > --enable-debug, the guest is running incredibly slow.
On Mon, Sep 25, 2017 at 12:06:40AM +0300, Michael Tokarev wrote:
> 22.09.2017 06:06, Thomas Huth wrote:
> > If QEMU has been compiled with the flags --enable-tcg-interpreter and
> > --enable-debug, the guest is running incredibly slow. The pxe boot test
> > can take up to 400 seconds when testing t
On Fri, Sep 22, 2017 at 05:06:57AM +0200, Thomas Huth wrote:
> If QEMU has been compiled with the flags --enable-tcg-interpreter and
> --enable-debug, the guest is running incredibly slow. The pxe boot test
> can take up to 400 seconds when testing the pseries ppc64 machine. While
> we should still
On 09/26/2017 03:18 PM, Eric Blake wrote:
> On 09/26/2017 01:51 PM, John Snow wrote:
>>
>>
>> On 09/13/2017 12:03 PM, Eric Blake wrote:
>>> In the process of converting sector-based interfaces to bytes,
>>> I'm finding it easier to represent a byte count as a 64-bit
>>> integer at the block layer
Richard Henderson writes:
> Nothing uses or enables them yet.
>
> Signed-off-by: Richard Henderson
> ---
> tcg/tcg-op.h | 26 +++
> tcg/tcg-opc.h | 37 ++
> tcg/tcg.h | 34 +
> tcg/tcg-op.c | 234
> ++
> tcg/
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: 20170926110628.2705-1-kra...@redhat.com
Subject: [Qemu-devel] [PULL 0/2] Fw 20170926 patches
On 09/26/2017 01:51 PM, John Snow wrote:
>
>
> On 09/13/2017 12:03 PM, Eric Blake wrote:
>> In the process of converting sector-based interfaces to bytes,
>> I'm finding it easier to represent a byte count as a 64-bit
>> integer at the block layer (even if we are internally capped
>> by SIZE_MAX
On 09/13/2017 12:03 PM, Eric Blake wrote:
> We are gradually converting to byte-based interfaces, as they are
> easier to reason about than sector-based. Continue by converting
> an internal function (no semantic change), and simplifying its
> caller accordingly.
>
> Signed-off-by: Eric Blake
On 09/13/2017 12:03 PM, Eric Blake wrote:
> We are gradually converting to byte-based interfaces, as they are
> easier to reason about than sector-based. Change the internal
> loop iteration of zeroing a device to track by bytes instead of
> sectors (although we are still guaranteed that we iter
Am 26.09.2017 um 20:29 hat Eric Blake geschrieben:
> On 09/26/2017 12:59 PM, Kevin Wolf wrote:
> > This was the easy part. Then I started looking at the code and found a
> > few a bit more interesting questions:
> >
> > * The old block-commit command decides between an "actual" commit job
> >
On 09/13/2017 12:03 PM, Eric Blake wrote:
> We are gradually converting to byte-based interfaces, as they are
> easier to reason about than sector-based. Convert another internal
> function (no semantic change), and rename it to is_zero() in the
> process.
>
> Signed-off-by: Eric Blake
> Revie
On 09/13/2017 12:03 PM, Eric Blake wrote:
> In the process of converting sector-based interfaces to bytes,
> I'm finding it easier to represent a byte count as a 64-bit
> integer at the block layer (even if we are internally capped
> by SIZE_MAX or even INT_MAX for individual transactions, it's
>
On 25 September 2017 at 23:16, Richard Henderson
wrote:
> Just one patch, but should make stable 2.10.1 this week.
>
>
> r~
>
>
> The following changes since commit 460b6c8e581aa06b86f59eebd9e52edfe7adf417:
>
> Merge remote-tracking branch 'remotes/bonzini/tags/for-upstream' into
> staging (201
On 26.09.2017 18:20, Cornelia Huck wrote:
> d32bd032d8 ("s390x/ccw: create s390 phb conditionally") made
> creating the s390 phb dependant on the zpci facility. This broke
> migration from pre-cpu model machines which was fixed with
> 8ad9087c4a ("s390x/ccw: create s390 phb for compat reasons as we
We don't wrap addresses in the mmu for the _real case, therefore the
behavior should be unchanged.
Signed-off-by: David Hildenbrand
---
target/s390x/mem_helper.c | 9 +
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/target/s390x/mem_helper.c b/target/s390x/mem_helper.c
ind
Low address protection checks will be moved into the mmu later.
Signed-off-by: David Hildenbrand
---
target/s390x/mem_helper.c | 12 ++--
1 file changed, 2 insertions(+), 10 deletions(-)
diff --git a/target/s390x/mem_helper.c b/target/s390x/mem_helper.c
index 34ffc282bf..4cf4f29171 1006
As we properly handle the return address now, we can drop
potential_page_fault().
Signed-off-by: David Hildenbrand
---
target/s390x/mem_helper.c | 8 ++--
target/s390x/translate.c | 2 --
2 files changed, 2 insertions(+), 8 deletions(-)
diff --git a/target/s390x/mem_helper.c b/target/s390x
This makes it easy to access real addresses (prefix) and in addition
checks for valid memory addresses, which is missing when using e.g.
stl_phys().
We can later reuse it to implement low address protection checks (then
we might even decide to introduce yet another MMU for absolute
addresses, just
Looks like, lurag was not loading 64bit but only 32bit.
As we properly handle the return address now, we can drop
potential_page_fault().
Signed-off-by: David Hildenbrand
---
target/s390x/mem_helper.c | 7 ++-
target/s390x/translate.c | 2 --
2 files changed, 2 insertions(+), 7 deletions(-
It should have been a >=, but let's directly perform a proper access
check to also be able to deal with hotplugged memory later.
Signed-off-by: David Hildenbrand
---
target/s390x/excp_helper.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/target/s390x/excp_helper.c b/tar
Conny reported that a guest Linux currently spits out:
"The s390-virtio transport is deprecated. Please switch to a modern host
providing virtio-ccw."
This is strange, because we have no legacy virtio transport in QEMU :)
Main problem is, that a page is tested for acccess, and the test does n
On 09/13/2017 12:03 PM, Eric Blake wrote:
> Not all callers care about which BDS owns the mapping for a given
> range of the file. In particular, bdrv_is_allocated() cares more
> about finding the largest run of allocated data from the guest
> perspective, whether or not that data is consecutive
On 09/26/2017 12:59 PM, Kevin Wolf wrote:
> Hi,
>
> as the next step after my commit block job fixes, I'm trying to
> implement a new, clean version of the QMP command, which I'm calling
> blockdev-commit for consistency with all the other "modern" QMP
> commands.
>
> I'll start with the schema t
On 26.09.2017 20:05, Christian Borntraeger wrote:
> We disabled ais for 2.10 lets also remove it from the z14 default model.
>
> Fixes: 3f2d07b3b01e s390x/ais: for 2.10 stable: disable ais facility
> Signed-off-by: Christian Borntraeger
> ---
> target/s390x/gen-features.c | 1 -
> 1 file change
On 09/19/2017 08:03 AM, Richard Henderson wrote:
> +while (1) {
> +/* We want to read memory for one insn, but generically we do not
> + know how much memory that is. We have a small buffer which is
> + known to be sufficient for all supported targets. Try to not
>
On 09/19/2017 07:45 PM, Michael Roth wrote:
> Hi everyone,
>
> The following new patches are queued for QEMU stable v2.10.1:
>
> https://github.com/mdroth/qemu/commits/stable-2.10-staging
>
> The release is planned for 2017-10-02:
>
> https://wiki.qemu.org/Planning/2.10
>
> Please respond
CC: qemu-sta...@nongnu.org
On 08/29/2017 07:27 AM, Stefan Hajnoczi wrote:
> The following segfault is encountered if the NBD server closes the UNIX
> domain socket immediately after negotiation:
>
> Program terminated with signal SIGSEGV, Segmentation fault.
...
> Note this only happens with UN
On 25 September 2017 at 14:41, Eric Blake wrote:
> The following changes since commit 460b6c8e581aa06b86f59eebd9e52edfe7adf417:
>
> Merge remote-tracking branch 'remotes/bonzini/tags/for-upstream' into
> staging (2017-09-23 12:55:40 +0100)
>
> are available in the git repository at:
>
> git:/
On 26 September 2017 at 18:27, Thomas Huth wrote:
> On 25.09.2017 19:59, Eduardo Habkost wrote:
>> On Mon, Sep 25, 2017 at 07:42:13PM +0200, Thomas Huth wrote:
>> "make check" found a few candidates:
>> https://travis-ci.org/ehabkost/qemu/jobs/278743999
>>
>> Initialization of device dpcd failed
Hi,
as the next step after my commit block job fixes, I'm trying to
implement a new, clean version of the QMP command, which I'm calling
blockdev-commit for consistency with all the other "modern" QMP
commands.
I'll start with the schema that I have so far:
{ 'command': 'blockdev-commit',
'dat
We disabled ais for 2.10 lets also remove it from the z14 default model.
Fixes: 3f2d07b3b01e s390x/ais: for 2.10 stable: disable ais facility
Signed-off-by: Christian Borntraeger
---
target/s390x/gen-features.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/target/s390x/gen-features.c b/tar
Am 25.09.2017 um 21:38 hat Eric Blake geschrieben:
> On 09/25/2017 07:28 AM, Kevin Wolf wrote:
> > This changes the commit block job to support operation in a graph where
> > there is more than a single active layer that references the top node.
> >
> > This involves inserting the commit filter no
On Fri, Sep 22, 2017 at 8:14 AM, Peter Maydell wrote:
> On 22 September 2017 at 16:11, Abhijit Ray Chaudhury
> wrote:
>> Hi Peter,
>>
>> Thanks for your prompt response. I have gone through target
>> description xml format for gdb
>> (https://sourceware.org/gdb//onlinedocs/gdb/ARM-Features.html#A
On 25.09.2017 19:59, Eduardo Habkost wrote:
> On Mon, Sep 25, 2017 at 07:42:13PM +0200, Thomas Huth wrote:
>> On 25.09.2017 17:26, Peter Maydell wrote:
>>> On 25 September 2017 at 16:19, Thomas Huth wrote:
Not sure whether this works for the virtio-xxx-device devices,
though, since they
On 09/26/2017 12:13 PM, Alistair Francis wrote:
>> +#if (WINDBG_DEBUG_ON)
>> +
>> +# define WINDBG_DEBUG(...) do {\
>> +printf("Debug: " __VA_ARGS__); \
>> +printf("\n"); \
>> +} while (false)
>> +
>> +# define WINDBG_ERROR(...) do {\
>> +printf("Error: " __VA_
On Tue, Sep 26, 2017 at 4:04 AM, Mihail Abakumov
wrote:
> We made the debugger module WinDbg (like GDB) for QEMU. This is the
> replacement of the remote stub in Windows kernel. Used for remote Windows
> kernel debugging without debugging mode.
>
> WinDbg is a multipurpose debugger for the Micro
On Tue, Sep 26, 2017 at 4:04 AM, Mihail Abakumov
wrote:
> Added chardev for listening to windbg. Target device is a parameter in the
> '-windbg' option.
>
> Signed-off-by: Mihail Abakumov
> Signed-off-by: Pavel Dovgalyuk
> Signed-off-by: Dmitriy Koltunov
Acked-by: Alistair Francis
Thanks,
A
Am 26.09.2017 um 18:13 hat Jan Dakinevich geschrieben:
> The command is intended for exposing device specific virtio feature bits
> and their negotiation status. It is convenient and useful for debug
> purpose.
>
> Names of features are taken from a devices via get_feature_name() within
> VirtioDe
On Tue, Sep 26, 2017 at 4:04 AM, Mihail Abakumov
wrote:
> Added definition of the WindbgState struct and its initialization.
>
> Signed-off-by: Mihail Abakumov
> Signed-off-by: Pavel Dovgalyuk
> Signed-off-by: Dmitriy Koltunov
> ---
> windbgstub.c | 26 ++
> 1 file ch
On 26 September 2017 at 18:03, Alistair Francis
wrote:
> On Tue, Sep 26, 2017 at 9:52 AM, Thomas Huth wrote:
>> On 26.09.2017 18:36, Alistair Francis wrote:
>>> On Tue, Sep 26, 2017 at 8:51 AM, Thomas Huth wrote:
The device uses serial_hds in its realize function and thus can't be
used
On Tue, Sep 26, 2017 at 4:04 AM, Mihail Abakumov
wrote:
> Added some helper features for windbgstub.
>
> Signed-off-by: Mihail Abakumov
> Signed-off-by: Pavel Dovgalyuk
> Signed-off-by: Dmitriy Koltunov
> ---
> include/exec/windbgstub-utils.h | 46
> +++
>
On Tue, Sep 26, 2017 at 4:04 AM, Mihail Abakumov
wrote:
> This option starts windbg server.
>
> Signed-off-by: Mihail Abakumov
> Signed-off-by: Pavel Dovgalyuk
> Signed-off-by: Dmitriy Koltunov
Acked-by: Alistair Francis
Thanks,
Alistair
> ---
> qemu-options.hx |8
> vl.c
1 - 100 of 309 matches
Mail list logo