Am Tue, 13 Aug 2019 11:16:44 +0100
schrieb Peter Maydell :
> On Tue, 9 Jul 2019 at 08:35, Thomas Huth wrote:
> >
> > It is likely still quite incomplete (e.g. mouse and interrupts are
> > not implemented yet), but it is good enough for keyboard input at
> > the firmware monitor.
> > This code has
On Fri, Aug 30, 2019 at 02:56:48PM -0300, Eduardo Habkost wrote:
> On Thu, Aug 29, 2019 at 11:31:25AM +1000, David Gibson wrote:
> > If I attempt to run "make check-acceptance" on my POWER9, RHEL8.1
> > machine when the openssl-devel package isn't installed, I get the
> > following very cryptic err
So detailed explanation, I got the point.
Thank you Alex!
Li Qiang
发件人: Alex Williamson
发送时间: 2019年8月31日 10:23
收件人: Li Qiang
抄送: Alex Williamson; qemu-devel@nongnu.org
主题: Re: [Qemu-devel] Questions about 'emulated_config_bits' in vfio pci
On Sat, 31 Aug 2019 09:31:59 +0800
Li Qiang wrote:
>
On Sat, 31 Aug 2019 09:31:59 +0800
Li Qiang wrote:
> Hi Alex and all,
>
> My understanding for ‘emulated_config_bits’ in ‘VFIOPCIDevice’ is
> that this is the mask for PCI config space. If the bits is set in ‘
> emulated_config_bits’ then we can just use the qemu’s
> ‘vdev->pdev.config’, it the
Currently, when doing './check -qcow2 098'. We can get following
asan output:
qemu-img: Could not empty blkdebug:TEST_DIR/blkdebug.conf:TEST_DIR/t.IMGFMT:
Input/output error
+
+=
+==60365==ERROR: LeakSanitizer: detected memory leaks
Hi Alex and all,
My understanding for ‘emulated_config_bits’ in ‘VFIOPCIDevice’ is that this is
the mask for PCI config space. If the bits is set in ‘ emulated_config_bits’
then we can just use the qemu’s ‘vdev->pdev.config’, it the bits is not set, we
need to ask the physical device.
But the
I can take over the series. I'll rebase the patch set, and update it to
address the SIGRTMIN - 1 issue. I should have an update sometime next week.
On Wed, Aug 28, 2019 at 10:31 AM Aleksandar Markovic
wrote:
> > From: Laurent Vivier
> > Sent: Wednesday, August 28, 2019 10:51 AM
> > To: Josh Kun
On Fri, Aug 30, 2019 at 03:51:39PM -0300, Eduardo Habkost wrote:
> On Fri, Aug 30, 2019 at 08:40:33PM +0200, Philippe Mathieu-Daudé wrote:
> > The paramiko Python module has many dependencies. Some of them
> > are not pure Python, such cryptography module which requires to
> > be built and linked w
Hi Gerd,
Memory leak is observed in zrle_compress_data when we are doing some
AddressSanitizer tests. The leak stack is as bellow:
=
==47887==ERROR: LeakSanitizer: detected memory leaks
Direct leak of 29760 byte(s) in 5 object(s)
On 8/30/19 1:07 PM, Vladimir Sementsov-Ogievskiy wrote:
> 23.08.2019 17:37, Eric Blake wrote:
>> Commit fe0480d6 and friends added BDRV_REQ_NO_FALLBACK as a way to
>> avoid wasting time on a preliminary write-zero request that will later
>> be rewritten by actual data, if it is known that the write
On 8/30/19 6:10 PM, Eric Blake wrote:
> On 8/30/19 1:00 PM, Vladimir Sementsov-Ogievskiy wrote:
>> 23.08.2019 17:37, Eric Blake wrote:
>>> When creating a read-only image, we are still advertising support for
>>> TRIM and WRITE_ZEROES to the client, even though the client should not
>>> be issuing
On 8/30/19 1:00 PM, Vladimir Sementsov-Ogievskiy wrote:
> 23.08.2019 17:37, Eric Blake wrote:
>> When creating a read-only image, we are still advertising support for
>> TRIM and WRITE_ZEROES to the client, even though the client should not
>> be issuing those commands. But seeing this requires lo
On Tue, Aug 27, 2019 at 8:12 AM Bin Meng wrote:
>
> At present each hart's hartid in a RISC-V hart array is assigned
> the same value of its index in the hart array. But for a system
> that has multiple hart arrays, this is not the case any more.
>
> Add a new "hartid-base" property so that hartid
Note that currently I add tests 300-302, which are
placeholders to ease the rebase. In final version
of these patches I will update these.
Signed-off-by: Maxim Levitsky
---
tests/qemu-iotests/087.out | 6 +-
tests/qemu-iotests/134.out | 2 +-
tests/qemu-iotests/158.out |
Currently only for changing crypto parameters
Signed-off-by: Maxim Levitsky
---
block/qcow2.c| 71
qapi/block-core.json | 4 +--
2 files changed, 73 insertions(+), 2 deletions(-)
diff --git a/block/qcow2.c b/block/qcow2.c
index 8dff4c6b5f..3
Signed-off-by: Maxim Levitsky
---
block/crypto.c | 86 +---
qapi/block-core.json | 4 +--
2 files changed, 68 insertions(+), 22 deletions(-)
diff --git a/block/crypto.c b/block/crypto.c
index dbd95a99ba..9cb668ff0e 100644
--- a/block/crypto.c
+++ b/
---
block/qcow2.c | 79 ---
1 file changed, 63 insertions(+), 16 deletions(-)
diff --git a/block/qcow2.c b/block/qcow2.c
index 376bb416fd..8dff4c6b5f 100644
--- a/block/qcow2.c
+++ b/block/qcow2.c
@@ -171,6 +171,25 @@ static ssize_t qcow2_crypto_hdr
Signed-off-by: Maxim Levitsky
---
block/Makefile.objs | 2 +-
block/amend.c | 116 ++
include/block/block_int.h | 23 ++--
qapi/block-core.json | 26 +
qapi/job.json | 4 +-
5 files changed, 163 insertions(+)
Signed-off-by: Maxim Levitsky
---
block.c | 4 +++-
block/qcow2.c | 1 +
include/block/block.h | 1 +
include/block/block_int.h | 1 +
qemu-img-cmds.hx | 4 ++--
qemu-img.c| 8 +++-
qemu-img.texi | 6 +-
7 files change
Signed-off-by: Maxim Levitsky
---
crypto/block-luks.c | 366 +++-
1 file changed, 364 insertions(+), 2 deletions(-)
diff --git a/crypto/block-luks.c b/crypto/block-luks.c
index ba20d55246..21325fbc79 100644
--- a/crypto/block-luks.c
+++ b/crypto/block-luks
Now you can specify which slot to put the encryption key to
Plus add 'active' option which will let user erase the key secret
instead of adding it.
Check that it is true for creation
Signed-off-by: Maxim Levitsky
---
block/crypto.c | 2 ++
block/crypto.h | 16 ++
This patch series is continuation of my work to add encryption
key managment to luks/qcow2 with luks.
This patch series is based on patch series I sent earlier
called 'RFC crypto/luks: preparation for encryption key managment'
Let me hear what you think. This is still an RFC, so please
don't kill
This implements the encryption key management
using the generic code in qcrypto layer
(currently only for qemu-img amend)
This code adds another 'write_func' because the initialization
write_func works directly on the underlying file,
because during the creation, there is no open instance
of the l
This adds the qcrypto_amend_options and corresponding
crypto driver callbacks for the for encrypted
key managedment
Signed-off-by: Maxim Levitsky
---
crypto/block.c | 31 +++
crypto/blockpriv.h | 8
include/crypto/block.h | 22 ++
On Wed, Aug 28, 2019 at 11:14 PM John Snow wrote:
>
>
> On 8/27/19 2:59 PM, Nir Soffer wrote:
> > While working on 4k support, I noticed that there is lot of code using
> > BDRV_SECTOR_SIZE (512) for checking alignment. I wonder how this can
> work with
> > 4k storage.
> >
> > Lets start by clean
On Fri, Aug 30, 2019 at 08:40:33PM +0200, Philippe Mathieu-Daudé wrote:
> The paramiko Python module has many dependencies. Some of them
> are not pure Python, such cryptography module which requires to
> be built and linked with OpenSSL.
>
> When native libraries and header are missing on the hos
This allows to receive mouse and keyboard events from
a Barrier server.
This is enabled by adding the following parameter on the
command line
... -object input-barrier,id=$id,name=$name ...
Where $name is the name declared in the screens section of barrier.conf
The barrier server (barriers)
On 08/30/19 16:48, Igor Mammedov wrote:
> (01) On boot firmware maps and initializes SMI handler at default SMBASE
> (3)
> (using dedicated SMRAM at 3 would allow us to avoid save/restore
> steps and make SMM handler pointer not vulnerable to DMA attacks)
>
> (02) QEMU hotplug
On Fri, Aug 30, 2019 at 10:30:56AM +0100, Stefan Hajnoczi wrote:
> Neither stat(2) nor lseek(2) report the size of Linux devdax pmem
> character device nodes. Commit 314aec4a6e06844937f1677f6cba21981005f389
> ("hostmem-file: reject invalid pmem file sizes") added code to
> hostmem-file.c to fetch
On Fri, Aug 30, 2019 at 2:06 AM Alex Bennée wrote:
>
>
> Alistair Francis writes:
>
> > On Thu, Aug 29, 2019 at 5:05 AM liuzhiwei wrote:
> >>
> >> On 2019/8/29 上午5:34, Alistair Francis wrote:
> >> > On Wed, Aug 28, 2019 at 12:04 AM liuzhiwei wrote:
> >> >> Change-Id: I3cf891bc400713b95f47ecca82
23.08.2019 17:37, Eric Blake wrote:
> The server side is fairly straightforward: we can always advertise
> support for detection of fast zero, and implement it by mapping the
> request to the block layer BDRV_REQ_NO_FALLBACK.
>
> Signed-off-by: Eric Blake
Reviewed-by: Vladimir Sementsov-Ogievskiy
The paramiko Python module has many dependencies. Some of them
are not pure Python, such cryptography module which requires to
be built and linked with OpenSSL.
When native libraries and header are missing on the host, the
error reported is not very helpful:
$ make check-venv
VENVtests/ve
23.08.2019 17:37, Eric Blake wrote:
> The client side is fairly straightforward: if the server advertised
> fast zero support, then we can map that to BDRV_REQ_NO_FALLBACK
> support. A server that advertises FAST_ZERO but not WRITE_ZEROES
> is technically broken, but we can ignore that situation a
On 8/30/19 6:07 AM, Christophe de Dinechin wrote:
>
> John Snow writes:
>
>> On 8/29/19 12:45 PM, Christophe de Dinechin wrote:
>>>
> [...]
>
>>> Sorry for catching up late, this mail thread happened during my PTO.
>>>
>>> I remember bringing up at the time [1] that the correct solution needs
23.08.2019 17:37, Eric Blake wrote:
> Commit fe0480d6 and friends added BDRV_REQ_NO_FALLBACK as a way to
> avoid wasting time on a preliminary write-zero request that will later
> be rewritten by actual data, if it is known that the write-zero
> request will use a slow fallback; but in doing so, co
23.08.2019 17:37, Eric Blake wrote:
> When creating a read-only image, we are still advertising support for
> TRIM and WRITE_ZEROES to the client, even though the client should not
> be issuing those commands. But seeing this requires looking across
> multiple functions:
>
> All callers to nbd_ex
On Thu, Aug 29, 2019 at 11:31:25AM +1000, David Gibson wrote:
> If I attempt to run "make check-acceptance" on my POWER9, RHEL8.1
> machine when the openssl-devel package isn't installed, I get the
> following very cryptic error:
>
> VENV/home/dwg/qemu/build/rhel8/tests/venv
> PIP /hom
On 8/30/19 3:21 AM, Richard Henderson wrote:
> On 8/29/19 10:26 AM, Philippe Mathieu-Daudé wrote:
>>> -wp->hitaddr = vaddr;
>>> +wp->hitaddr = MAX(addr, wp->vaddr);
>>
>> When is addr > wp->vaddr?
>
> Both the watchpoint and the access are arbitrary ranges.
>
> wp:[
This seems related to this change:
commit ef96e3ae9698d6726a8113f448c82985a9f31ff5
Author: Mark Cave-Ayland
Date: Wed Jan 2 09:14:22 2019 +
target/ppc: move FP and VMX registers into aligned vsr register array
The VSX register array is a block of 64 128-bit registers where the
On Fri, 30 Aug 2019 17:34:13 +0100
Daniel P. Berrangé wrote:
> On Fri, Aug 30, 2019 at 06:13:45PM +0200, Laurent Vivier wrote:
> > When we hotplug a CPU on memory-less/cpu-less node, the linux kernel
> > crashes.
> >
> > This happens because linux kernel needs to know the NUMA topology at
> > st
On Fri, 30 Aug 2019 10:06:56 +0200
Auger Eric wrote:
> Hi Alex,
>
> On 8/29/19 8:14 PM, Alex Williamson wrote:
> > On Thu, 29 Aug 2019 11:01:41 +0200
> > Eric Auger wrote:
> >
> >> As of today, VFIO only works along with vIOMMU supporting
> >> caching mode. The SMMUv3 does not support this m
On Fri, 30 Aug 2019 14:44:07 +0530
Aravinda Prasad wrote:
> This patch adds support in QEMU to handle "ibm,nmi-register"
> and "ibm,nmi-interlock" RTAS calls and sets the default
> value of SPAPR_CAP_FWNMI_MCE to SPAPR_CAP_ON for machine
> type 4.2.
>
> The machine check notification address is
vandersonmr writes:
> Adding "info cfg id depth" commands to HMP.
> This command allow the exploration a TB
> neighbors by dumping [and opening] a .dot
> file with the TB CFG neighbors colorized
> by their hotness.
>
> The goal of this command is to allow the dynamic exploration
> of TCG behavi
vandersonmr writes:
> These commands allow the exploration of TBs
> generated by the TCG. Understand which one
> hotter, with more guest/host instructions...
> and examine their guest, host and IR code.
>
> The goal of this command is to allow the dynamic exploration
> of TCG behavior and code
After backup-top filter appearing it's not possible to see dirty
bitmaps in top node, so use node-name instead.
Signed-off-by: Vladimir Sementsov-Ogievskiy
---
tests/qemu-iotests/124| 83
tests/qemu-iotests/257| 49 ++---
tests/qemu-iotests/257.out| 364 +++
Backup-top filter caches write operations and does copy-before-write
operations.
The driver will be used in backup instead of write-notifiers.
Signed-off-by: Vladimir Sementsov-Ogievskiy
---
block/backup-top.h | 37 +++
block/backup-top.c | 244 +++
On Fri, Aug 30, 2019 at 06:13:45PM +0200, Laurent Vivier wrote:
> When we hotplug a CPU on memory-less/cpu-less node, the linux kernel
> crashes.
>
> This happens because linux kernel needs to know the NUMA topology at
> start to be able to initialize the distance lookup table.
>
> On pseries, th
Drop write notifiers and use filter node instead.
= Changes =
1. Add filter-node-name argument for backup qmp api. We have to do it
in this commit, as 257 needs to be fixed.
2. There are no more write notifiers here, so is_write_notifier
parameter is dropped from block-copy paths.
3. Intersecti
On Fri, 30 Aug 2019 08:06:32 +
"Tian, Kevin" wrote:
> > From: Tian, Kevin
> > Sent: Friday, August 30, 2019 3:26 PM
> >
> [...]
> > > How does QEMU handle the fact that IOVAs are potentially dynamic while
> > > performing the live portion of a migration? For example, each time a
> > > gue
We need to fix comment style around block-copy functions before further
moving them to separate file to satisfy checkpatch. But do more: fix
all comments style. Also, seems like doubled first asterisk is not
forbidden, but drop it too for consistency.
Signed-off-by: Vladimir Sementsov-Ogievskiy
-
When we hotplug a CPU on memory-less/cpu-less node, the linux kernel
crashes.
This happens because linux kernel needs to know the NUMA topology at
start to be able to initialize the distance lookup table.
On pseries, the topology is provided by the firmware via the existing
CPUs and memory inform
On Fri, 30 Aug 2019 07:25:59 +
"Tian, Kevin" wrote:
> > From: Alex Williamson [mailto:alex.william...@redhat.com]
> > Sent: Thursday, August 29, 2019 4:51 AM
> >
> > On Tue, 27 Aug 2019 00:25:41 +0530
> > Kirti Wankhede wrote:
> >
> > > - Defined MIGRATION region type and sub-type.
> > >
SCSI devices are unused in test, drop them.
Signed-off-by: Vladimir Sementsov-Ogievskiy
Reviewed-by: Max Reitz
---
tests/qemu-iotests/257 | 8 ---
tests/qemu-iotests/257.out | 44 --
2 files changed, 52 deletions(-)
diff --git a/tests/qemu-iotests/2
On 30.08.19 11:41, Igor Mammedov wrote:
> On Thu, 29 Aug 2019 14:41:13 +0200
> Christian Borntraeger wrote:
>
>> On 29.08.19 14:31, Igor Mammedov wrote:
>>> On Thu, 29 Aug 2019 14:07:44 +0200
>>> Christian Borntraeger wrote:
>>>
On 29.08.19 14:04, Igor Mammedov wrote:
> On Thu,
Split block_copy to separate file, to be cleanly shared with backup-top
filter driver in further commits.
It's a clean movement, the only change is drop "static" from interface
functions.
Signed-off-by: Vladimir Sementsov-Ogievskiy
Reviewed-by: Max Reitz
---
include/block/block-copy.h | 67 ++
Split out do_wait_serialising_requests with additional possibility to
not actually wait but just check, that there is something to wait for.
Signed-off-by: Vladimir Sementsov-Ogievskiy
Reviewed-by: Max Reitz
---
block/io.c | 24
1 file changed, 16 insertions(+), 8 delet
After previous commit Drive.device is actually unused. Drop it together
with .name property. While being here reuse .node in qmp commands
instead of writing 'drive0' twice.
Signed-off-by: Vladimir Sementsov-Ogievskiy
Reviewed-by: Max Reitz
---
tests/qemu-iotests/257 | 37 +++---
Split copying logic which will be shared with backup-top filter.
Signed-off-by: Vladimir Sementsov-Ogievskiy
---
block/backup.c | 47 ---
1 file changed, 32 insertions(+), 15 deletions(-)
diff --git a/block/backup.c b/block/backup.c
index 16ca9a3944..
Introduce lock/unlock range functionality, based on serialized
requests. This is needed to refactor backup, dropping local
tracked-request-like synchronization.
Signed-off-by: Vladimir Sementsov-Ogievskiy
Reviewed-by: Max Reitz
---
include/block/block_int.h | 4
block/io.c
We shouldn't try to copy bytes beyond EOF. Fix it.
Signed-off-by: Vladimir Sementsov-Ogievskiy
Reviewed-by: Max Reitz
---
block/backup.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/block/backup.c b/block/backup.c
index 2baf7bed65..16ca9a3944 100644
--- a/block/backup.c
+
Split copying code part from backup to "block-copy", including separate
state structure and function renaming. This is needed to share it with
backup-top filter driver in further commits.
Notes:
1. As BlockCopyState keeps own BlockBackend objects, remaining
job->common.blk users only use it to ge
Teach bdrv_debug_breakpoint and bdrv_debug_remove_breakpoint skip
filters with backing. This is needed to implement and use in backup job
it's own backup_top filter driver (like mirror already has one), and
without this improvement, breakpoint removal will fail at least in 55
iotest.
Signed-off-by
Hi all!
These series introduce backup-top driver. It's a filter-node, which
do copy-before-write operation. Mirror uses filter-node for handling
guest writes, let's move to filter-node (from write-notifiers) for
backup too.
v10 (mostly by Max's comments):
01: - s/MIN(end - start, job->len - star
Signed-off-by: Vladimir Sementsov-Ogievskiy
---
block/backup.c | 15 ---
1 file changed, 12 insertions(+), 3 deletions(-)
diff --git a/block/backup.c b/block/backup.c
index 8c19a265b2..abb5099fa3 100644
--- a/block/backup.c
+++ b/block/backup.c
@@ -764,9 +764,18 @@ BlockJob *backup_j
On 8/30/19 3:09 AM, David Hildenbrand wrote:
> Let's return a host pointer from probe_access() if possible and provide
> probe_access(). s390x will soon make use of probe_access() and use the
> provided host pointer.
>
> v1 -> v2:
> - Rebased to tcg-next
> - "tcg: Make probe_write() return a point
On 8/30/19 3:09 AM, David Hildenbrand wrote:
> Let's also allow to probe other access types.
>
> Signed-off-by: David Hildenbrand
> ---
> accel/tcg/cputlb.c | 43 ++---
> accel/tcg/user-exec.c | 26 +++--
> include/exec/exec-all.h |
On 8/30/19 3:09 AM, David Hildenbrand wrote:
> ... similar to tlb_vaddr_to_host(); however, allow access to the host
> page except when TLB_NOTDIRTY or TLB_MMIO is set.
>
> Signed-off-by: David Hildenbrand
> ---
> accel/tcg/cputlb.c | 21 -
> accel/tcg/user-exec.c | 6
vandersonmr writes:
> Adding tb_stats [start|pause|stop|filter] command to hmp.
> This allows controlling the collection of statistics.
> It is also possible to set the level of collection:
> all, jit, or exec.
>
> tb_stats filter allow to only collect statistics for the TB
> in the last_search
On Thu, 29 Aug 2019 19:01:35 +0200
Laszlo Ersek wrote:
> On 08/27/19 20:31, Igor Mammedov wrote:
> > On Sat, 24 Aug 2019 01:48:09 +
> > "Yao, Jiewen" wrote:
>
> >> (05) Host CPU: (OS) Port 0xB2 write, all CPUs enter SMM (NOTE: New CPU
> >> will not enter CPU because SMI is disabled)
Le 30/08/2019 à 16:36, Alex Bennée a écrit :
> Just passing NULL means we end up ignoring the bad dfilter spec
> instead of reporting it and exiting as we should.
>
> Signed-off-by: Alex Bennée
> ---
> linux-user/main.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/li
vandersonmr writes:
> -d tb_stats[[,level=(+all+jit+exec+time)][,dump_limit=]]
>
> "dump_limit" is used to limit the number of dumped TBStats in
> linux-user mode.
>
> [all+jit+exec+time] control the profilling level used
> by the TBStats. Can be used as follow:
>
> -d tb_stats
> -d tb_stats,l
Just passing NULL means we end up ignoring the bad dfilter spec
instead of reporting it and exiting as we should.
Signed-off-by: Alex Bennée
---
linux-user/main.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/linux-user/main.c b/linux-user/main.c
index 47917bbb20f..50a03152
Michal Privoznik writes:
> On 8/29/19 3:12 PM, Eric Blake wrote:
>> On 8/29/19 8:04 AM, Michal Privoznik wrote:
>>
> A bit of background: up until very recently libvirt used qemu-ga
> in all or nothing way. It didn't care why a qemu-ga command
> failed. But very recently a new API was
Jing Liu writes:
> Hi Sergio,
>
> On 8/29/2019 11:46 PM, Sergio Lopez wrote:
>>
>> Jing Liu writes:
>>
>>> Hi Sergio,
>>>
>>> The idea is interesting and I tried to launch a guest by your
>>> guide but seems failed to me. I tried both legacy and normal modes,
>>> but the vncviewer connected and
Markus Armbruster writes:
> Commands and events can define their argument type inline (default) or
> by referring to another type ('boxed': true, since commit c818408e44
> "qapi: Implement boxed types for commands/events", v2.7.0). The
> unboxed inline definition is an (anonymous) struct type.
This patch is part of Google Summer of Code (GSoC) 2019.
More about the project can be found in:
https://wiki.qemu.org/Internships/ProjectIdeas/TCGCodeQuality
This adds --perf command-line option to dump Linux Perf
jitdump files. These files are used to enhant Perf report
and to be able to analyze
On Sat, 06 Jul 2019 12:22:27 +0200
Christian Schoenebeck via Qemu-devel wrote:
> On Mittwoch, 3. Juli 2019 13:13:26 CEST Christian Schoenebeck wrote:
> > To support multiple devices on the 9p share, and avoid
> > qid path collisions we take the device id as input
> [snip]
> > - Fixed v9fs_do
On Fri, 30 Aug 2019 14:43:40 +0530
Aravinda Prasad wrote:
> Introduce the KVM capability KVM_CAP_PPC_FWNMI so that
> the KVM causes guest exit with NMI as exit reason
> when it encounters a machine check exception on the
> address belonging to a guest. Without this capability
> enabled, KVM redir
@Philippe, thank you for spending the time to find a compiler that works with
the testcase. I've been operating on RHEL 8 primarily:
gcc version 8.2.1 20180905 (Red Hat 8.2.1-3) (GCC)
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
h
On Thu, 29 Aug 2019 18:25:17 +0200
Laszlo Ersek wrote:
> On 08/28/19 14:01, Igor Mammedov wrote:
> > On Tue, 27 Aug 2019 22:11:15 +0200
> > Laszlo Ersek wrote:
> >
> >> On 08/27/19 18:23, Igor Mammedov wrote:
> >>> On Mon, 26 Aug 2019 17:30:43 +0200
> >>> Laszlo Ersek wrote:
> >>>
>
Adding TBStatistics information to linux perf TB's symbol names.
This commit depends on the following PATCH:
[PATCH v5 00/10] Measure Tiny Code Generation Quality
Signed-off-by: Vanderson M. do Rosario
---
accel/tcg/perf/jitdump.c | 16 +++-
1 file changed, 15 insertions(+), 1 delet
On 8/30/19 8:29 AM, Michal Privoznik wrote:
> If a command is disabled an error is reported. But due to usage
> of error_setg() the class of the error is GenericError which does
> not help callers in distinguishing this case from a case where a
> qmp command fails regularly due to other reasons. Us
Hi Peng,
On 12/12/18 2:54 AM, peng.h...@zte.com.cn wrote:
>>> v11 --> v12
>>> realize pvpanic as a pci device and use the mmio of pci device.
>>
>> Do you have a pointer to the kernel patches?
>>
>> Thanks,
>>> drew
>>
> I'm still sorting out the code for the kernel part, and I haven't submit
On Thu, 22 Aug 2019 21:33:37 +0200
Christian Schoenebeck wrote:
> 'warn' (default): Only log an error message (once) on host if more than one
> device is shared by same export, except of that just ignore this config
> error though. This is the default behaviour for not breaking existing
> install
vandersonmr writes:
> Replace all others CONFIG_PROFILER statistics and migrate it to
> TBStatistics system. However, TCGProfiler still exists and can
> be use to store global statistics and times. All TB related
> statistics goes to TBStatistics.
>
> Signed-off-by: Vanderson M. do Rosario
> -
Ok. I haven't change it before because I would like to be able to collect
information for already translated TBs when I, for instance, remove the
filter during execution. Having the TBStats already created guarantee this.
To guarantee this in your approach, we would need to tb_flush when changing
t
Vanderson Martins do Rosario writes:
> Ok. I haven't change it before because I would like to be able to collect
> information for already translated TBs when I, for instance, remove the
> filter during execution. Having the TBStats already created guarantee this.
> To guarantee this in your ap
On 8/30/19 1:52 PM, Markus Armbruster wrote:
Michal Privoznik writes:
On 8/29/19 3:12 PM, Eric Blake wrote:
On 8/29/19 8:04 AM, Michal Privoznik wrote:
A bit of background: up until very recently libvirt used qemu-ga
in all or nothing way. It didn't care why a qemu-ga command
failed. But ve
vandersonmr writes:
> If a TB has a TBS (TBStatistics) with the TB_JIT_STATS
> enabled then we collect statistics of its translation
> processes and code translation.
>
> Collecting the number of host instructions seems to be
> not simple as it would imply in having to modify several
> target s
This commit adds support to Linux Perf in order
to be able to analyze qemu jitted code and
also to able to see the TBs PC in it.
When using "-perf" qemu creates a jitdump file in
the current working directory. The file format
specification can be found in:
https://github.com/torvalds/linux/blob/ma
If a command is disabled an error is reported. But due to usage
of error_setg() the class of the error is GenericError which does
not help callers in distinguishing this case from a case where a
qmp command fails regularly due to other reasons. Use
CommandNotFound error class which is much closer t
vandersonmr writes:
> To store statistics for each TB, we created a TBStatistics structure
> which is linked with the TBs. TBStatistics can stay alive after
> tb_flush and be relinked to a regenerated TB. So the statistics can
> be accumulated even through flushes.
>
> The goal is to have all p
Add an API that takes QDict directly, so users could skip steps
of first building json dictionary and converting it back to
QDict in existing qtest_qmp_device_add() and instead use QDict
directly without intermediate conversion.
Signed-off-by: Igor Mammedov
---
tests/libqtest.h | 12
Commit bc1fb850a3 silently broke device_add test for CPU hotplug which
resulted in test successfully passing though it wasn't actually run.
Fix it by making sure that all non present CPUs reported
by "query-hotpluggable-cpus" are hotplugged instead of making up
and hardcoding values.
Use of query-
Fixes bc1fb850a3 (vl.c deprecate incorrect CPUs topology) that introduced
regression.
Igor Mammedov (2):
tests: add qtest_qmp_device_add_qdict() helper
tests: cpu-plug-test: fix device_add for pc/q35 machines
tests/libqtest.h | 12 +
tests/cpu-plug-test.c | 62 ++
vandersonmr writes:
> If a TB has a TBS (TBStatistics) with the TB_EXEC_STATS
> enabled, then we instrument the start code of this TB
> to atomically count the number of times it is executed.
> We count both the number of "normal" executions and atomic
> executions of a TB.
>
> The execution co
Let's return a host pointer from probe_access() if possible and provide
probe_access(). s390x will soon make use of probe_access() and use the
provided host pointer.
v1 -> v2:
- Rebased to tcg-next
- "tcg: Make probe_write() return a pointer to the host page"
-- Rephrase documentation
- "tcg: Fact
... similar to tlb_vaddr_to_host(); however, allow access to the host
page except when TLB_NOTDIRTY or TLB_MMIO is set.
Signed-off-by: David Hildenbrand
---
accel/tcg/cputlb.c | 21 -
accel/tcg/user-exec.c | 6 --
include/exec/exec-all.h | 4 ++--
3 files changed
Let's also allow to probe other access types.
Signed-off-by: David Hildenbrand
---
accel/tcg/cputlb.c | 43 ++---
accel/tcg/user-exec.c | 26 +++--
include/exec/exec-all.h | 9 +++--
3 files changed, 59 insertions(+), 19 deletio
John Snow writes:
> On 8/29/19 12:45 PM, Christophe de Dinechin wrote:
>>
[...]
>> Sorry for catching up late, this mail thread happened during my PTO.
>>
>> I remember bringing up at the time [1] that the correct solution needs
>> to take into account usage models that vary from
>>
>> - a work
1 - 100 of 120 matches
Mail list logo
