The hypertrace channel allows guest code to emit events in QEMU (the host) using
its tracing infrastructure (see "docs/trace.txt"). This works in both 'system'
and 'user' modes, is architecture-agnostic and introduces minimal noise on the
guest.
See first commit for a full description, use-cases a
Signed-off-by: Lluís Vilanova
---
docs/devel/tracing.txt |3 +
docs/hypertrace.txt| 225
2 files changed, 228 insertions(+)
create mode 100644 docs/hypertrace.txt
diff --git a/docs/devel/tracing.txt b/docs/devel/tracing.txt
index 5768a0b
Generates the "guest_hypertrace" event with a user-configurable number
of arguments.
Signed-off-by: Lluís Vilanova
---
Makefile |6 --
Makefile.objs |2 ++
configure | 34 ++
rules.mak |2 +-
trace-events | 11 +++
5 files
QEMU detects when the guest uses 'mmap' on hypertrace's control channel
file, and then uses 'mprotect' to detect accesses to it, which are used
to trigger tracing event "guest_hypertrace".
Signed-off-by: Lluís Vilanova
---
Makefile.objs|4
bsd-user/main.c | 17 ++
bsd
Uses a virtual device to trigger the hypertrace channel event.
Signed-off-by: Lluís Vilanova
---
hypertrace/Makefile.objs |4 +
hypertrace/softmmu.c | 237 ++
include/hw/pci/pci.h |2
3 files changed, 243 insertions(+)
create mode 10
Provides guest library "libqemu-hypertrace-guest.a" to abstract access
to the hypertrace channel.
Signed-off-by: Lluís Vilanova
---
Makefile |5 +
configure |2
hypertrace/guest/Makefile | 30
hypertrace/guest/common.c
when SMP VM start, AP may lost INIT because of receiving INIT between
kvm_vcpu_ioctl_x86_get/set_vcpu_events.
vcpu 0 vcpu 1
kvm_vcpu_ioctl_x86_get_vcpu_events
events->smi.latched_init=0
send INIT
Hi,
This series failed build test on FreeBSD host. Please find the details below.
Subject: [Qemu-devel] [PATCH v7 0/5] hypertrace: Lightweight guest-to-QEMU
trace channel
Type: series
Message-id: 150141363372.9857.9055094189388759132.st...@frigg.lan
=== TEST SCRIPT BEGIN ===
#!/bin/sh
# Testing
Hi,
This series seems to have some coding style problems. See output below for
more information:
Subject: [Qemu-devel] [PATCH v7 0/5] hypertrace: Lightweight guest-to-QEMU
trace channel
Message-id: 150141363372.9857.9055094189388759132.st...@frigg.lan
Type: series
=== TEST SCRIPT BEGIN ===
#!/b
2017-07-31 4:01 GMT+08:00 Peng Hao :
> when SMP VM start, AP may lost INIT because of receiving INIT between
> kvm_vcpu_ioctl_x86_get/set_vcpu_events.
>
>vcpu 0 vcpu 1
>kvm_vcpu_ioctl_x86_get_vcpu_events
>
no-reply writes:
> Hi,
> This series seems to have some coding style problems. See output below for
> more information:
> Subject: [Qemu-devel] [PATCH v7 0/5] hypertrace: Lightweight guest-to-QEMU
> trace channel
> Message-id: 150141363372.9857.9055094189388759132.st...@frigg.lan
> Type: series
no-reply writes:
> Hi,
> This series failed build test on FreeBSD host. Please find the details below.
> Subject: [Qemu-devel] [PATCH v7 0/5] hypertrace: Lightweight guest-to-QEMU
> trace channel
> Type: series
> Message-id: 150141363372.9857.9055094189388759132.st...@frigg.lan
> === TEST SCRI
Lluís Vilanova writes:
> no-reply writes:
>> Hi,
>> This series failed build test on FreeBSD host. Please find the details below.
>> Subject: [Qemu-devel] [PATCH v7 0/5] hypertrace: Lightweight guest-to-QEMU
>> trace channel
>> Type: series
>> Message-id: 150141363372.9857.9055094189388759132.s
The hypertrace channel allows guest code to emit events in QEMU (the host) using
its tracing infrastructure (see "docs/trace.txt"). This works in both 'system'
and 'user' modes, is architecture-agnostic and introduces minimal noise on the
guest.
See first commit for a full description, use-cases a
Signed-off-by: Lluís Vilanova
---
docs/devel/tracing.txt |3 +
docs/hypertrace.txt| 225
2 files changed, 228 insertions(+)
create mode 100644 docs/hypertrace.txt
diff --git a/docs/devel/tracing.txt b/docs/devel/tracing.txt
index 5768a0b
Generates the "guest_hypertrace" event with a user-configurable number
of arguments.
Signed-off-by: Lluís Vilanova
---
Makefile |6 --
Makefile.objs |2 ++
configure | 34 ++
rules.mak |2 +-
trace-events | 11 +++
5 files
QEMU detects when the guest uses 'mmap' on hypertrace's control channel
file, and then uses 'mprotect' to detect accesses to it, which are used
to trigger tracing event "guest_hypertrace".
Signed-off-by: Lluís Vilanova
---
Makefile.objs|4
bsd-user/main.c | 17 ++
bsd
Uses a virtual device to trigger the hypertrace channel event.
Signed-off-by: Lluís Vilanova
---
hypertrace/Makefile.objs |4 +
hypertrace/softmmu.c | 237 ++
include/hw/pci/pci.h |2
3 files changed, 243 insertions(+)
create mode 10
Provides guest library "libqemu-hypertrace-guest.a" to abstract access
to the hypertrace channel.
Signed-off-by: Lluís Vilanova
---
Makefile |5 +
configure |2
hypertrace/guest/Makefile | 30
hypertrace/guest/common.c
Hi,
This series seems to have some coding style problems. See output below for
more information:
Subject: [Qemu-devel] [PATCH v8 0/5] hypertrace: Lightweight guest-to-QEMU
trace channel
Message-id: 150142369849.12995.11229612194223213120.st...@frigg.lan
Type: series
=== TEST SCRIPT BEGIN ===
#!
On Sun, Jul 30, 2017 at 05:59:17AM +, Wang, Wei W wrote:
> On Sunday, July 30, 2017 12:23 PM, Michael S. Tsirkin wrote:
> > On Sat, Jul 29, 2017 at 08:47:08PM +0800, Wei Wang wrote:
> > > On 07/29/2017 07:08 AM, Michael S. Tsirkin wrote:
> > > > On Thu, Jul 27, 2017 at 10:50:11AM +0800, Wei Wan
On Sun, Jul 30, 2017 at 07:18:33PM +0300, Michael S. Tsirkin wrote:
> On Sun, Jul 30, 2017 at 05:59:17AM +, Wang, Wei W wrote:
> > On Sunday, July 30, 2017 12:23 PM, Michael S. Tsirkin wrote:
> > > On Sat, Jul 29, 2017 at 08:47:08PM +0800, Wei Wang wrote:
> > > > On 07/29/2017 07:08 AM, Michael
On 29.07.2017 21:34, Peter Maydell wrote:
> On 29 July 2017 at 14:50, Patrick Steinhardt wrote:
>> On Fri, Jul 28, 2017 at 02:20:49PM -0300, Philippe Mathieu-Daudé wrote:
>>> This is likely to break on BSD, but now than patchew has a NetBSD job
>>> you can trigger a build RESENDing this patch.
>
On 30 July 2017 at 17:51, Kamil Rytarowski wrote:
> On 29.07.2017 21:34, Peter Maydell wrote:
>> On 29 July 2017 at 14:50, Patrick Steinhardt wrote:
>>> On Fri, Jul 28, 2017 at 02:20:49PM -0300, Philippe Mathieu-Daudé wrote:
This is likely to break on BSD, but now than patchew has a NetBSD j
QEMU can only handle up to function key F15. These patches extend QEMU to F24.
John Arbuckle (2):
Add more function keys to QEMU
Add more function keys to cocoa.m
qapi-schema.json | 13 -
ui/cocoa.m| 5 +
ui/input-keymap.c | 9 +
3 files changed, 26 inserti
There are now keyboards that have 19 function keys. This patch extends QEMU so
these function keys can be used.
Signed-off-by: John Arbuckle
---
qapi-schema.json | 12 +++-
ui/input-keymap.c | 9 +
2 files changed, 20 insertions(+), 1 deletion(-)
diff --git a/qapi-schema.json
Enable the Cocoa front-end to be able to use function keys F16 to F20.
Signed-off-by: John Arbuckle
---
ui/cocoa.m | 5 +
1 file changed, 5 insertions(+)
diff --git a/ui/cocoa.m b/ui/cocoa.m
index 93e56d0..edc7a65 100644
--- a/ui/cocoa.m
+++ b/ui/cocoa.m
@@ -225,6 +225,11 @@ const int mac_t
On Thu, Jul 27, 2017 at 10:21:22AM +0200, Amador Pahim wrote:
> On Tue, Jul 25, 2017 at 9:51 PM, Eduardo Habkost wrote:
> > On Tue, Jul 25, 2017 at 07:10:11PM +0200, Amador Pahim wrote:
> >> The message contains the self._args, which has only part of the
> >> options used in the qemu command line
CCing Alex, the original author of load_multiboot(), and Kevin,
who touched multiboot code recently.
On Fri, Jul 28, 2017 at 02:28:34PM -0700, Anatol Pomozov wrote:
> Hi
>
> I am looking at x86 multiboot code and trying to add "ELF section
> header" info feature. This will let target to learn m
On 30.07.2017 20:23, Peter Maydell wrote:
> On 30 July 2017 at 17:51, Kamil Rytarowski wrote:
>> On 29.07.2017 21:34, Peter Maydell wrote:
>>> On 29 July 2017 at 14:50, Patrick Steinhardt wrote:
On Fri, Jul 28, 2017 at 02:20:49PM -0300, Philippe Mathieu-Daudé wrote:
> This is likely to b
On Fri, Jul 28, 2017 at 06:29:20PM +0300, Alexey Perevalov wrote:
> On 07/28/2017 10:06 AM, Alexey Perevalov wrote:
> >On 07/28/2017 09:57 AM, Peter Xu wrote:
> >>On Fri, Jul 28, 2017 at 09:43:28AM +0300, Alexey Perevalov wrote:
> >>>On 07/28/2017 07:27 AM, Peter Xu wrote:
> On Thu, Jul 27, 201
* Cornelia Huck [2017-07-28 14:58:19 +0200]:
[...]
> >
> > If I understand you correctly it ain't possible to handle these
> > in the host (and let the guest a simple 'non-real' virtual
> > channel path whose reliability depends on what the host does),
> > or?
>
> It is possible. Mapping to a
On Fri, Jul 28, 2017 at 12:30:35PM +0200, Greg Kurz wrote:
> On Fri, 28 Jul 2017 13:49:25 +1000
> David Gibson wrote:
>
> > On Tue, Jul 25, 2017 at 08:01:50PM +0200, Greg Kurz wrote:
> > > From: Michael Roth
> > >
> > > Signed-off-by: Michael Roth
> > > Reviewed-by: David Gibson
> > > Signed-
* Cornelia Huck [2017-07-27 13:59:10 +0200]:
> On Thu, 27 Jul 2017 03:54:18 +0200
> Dong Jia Shi wrote:
>
> > When a channel path is hot plugged into a CSS, we should generate
> > a channel path initialized CRW (channel report word). The current
> > code does not do that, instead it puts a stub
From: Greg Kurz
If object_property_add_alias() returns an error in realize(), we should
propagate it to the caller and certainly not unref the DRC.
Same thing goes for unrealize(). Since object_property_del() is the last
call, we can even get rid of the intermediate Error *.
And finally, unreal
This reverts commit b87680427e8a3ff682f66514e99a8344e7437247.
I thought this was a harmless preliminary for XIVE enablement patches
we expect later on. However, due to some subtle interactions between
qemu and SLOF (guest firmware) this breaks some things. Revert it for
now, we'll work out how t
The following changes since commit a588c4985eff363154d65aee8607d0a4601655f7:
Merge remote-tracking branch 'remotes/ericb/tags/pull-nbd-2017-07-28' into
staging (2017-07-28 18:17:44 +0100)
are available in the git repository at:
git://github.com/dgibson/qemu.git tags/ppc-for-2.10-20170731
f
Right now, all qemu-iotests output data into the same scratch directory,
and so each tests needs to be responsible for cleanup up its own files.
Have each test use 'scratch/$seq' as its temp directory, so the check
script can do simple cleanup of removing the whole temporary directory.
Signed-off
This series does 2 things:
1.) Sets TEST_DIR to a unique subdirectory for each test
2.) Has './check' be responsible for removing temporary files
3.) Add option to './check' to retain temporary files in case of error
A caveat is #3 is working currently only for Bash tests, as the Python tests
sti
Now that ./check takes care of cleaning up after each tests, it
can also selectively not clean up. Add option to leave all output from
tests intact if that test encountered an error.
Note: this currently only works for bash tests, as the python tests
still clean up after themselves manually.
Sig
All files for a given test are now self-contained in a subdirectory,
and therefore the "./check" script can do all file-related cleanup
without any help.
This removes file cleanups from the bash tests. The only cleanup left
is whatever is needed to kill any spawned processes; e.g. _cleanup_qemu.
Hi Anatol,
> Am 30.07.2017 um 23:42 schrieb Eduardo Habkost :
>
>
> CCing Alex, the original author of load_multiboot(), and Kevin,
> who touched multiboot code recently.
>
>
>> On Fri, Jul 28, 2017 at 02:28:34PM -0700, Anatol Pomozov wrote:
>> Hi
>>
>> I am looking at x86 multiboot code and
New VFIO sub region VFIO_REGION_SUBTYPE_INTEL_IGD_DEVICE_STATE is added
to fetch and restore the status of mdev device vGPU during the live migration.
Signed-off-by: Yulei Zhang
---
hw/vfio/pci.c | 13 -
hw/vfio/pci.h | 1 +
linux-headers/linux/vfio.h | 7
Summary
This series RFC would like to introduce the live migration capability
to vfio_mdev device.
As currently vfio_mdev device don't support migration, we introduce
a new vfio subtype region VFIO_REGION_SUBTYPE_INTEL_IGD_DEVICE_STATE
for Intel vGPU device, during the vfio device initializatio
Introduce vfio_device_put/vfio_device_get funtion for vfio device state
save/restore usage.
For VFIO pci device status migrate, on the source side with
funtion vfio_device_put to save the following states
1. pci configuration space addr0~addr5
2. pci configuration space msi_addr msi_data
3. pci de
New VFIO ioctl VFIO_IOMMU_GET_DIRTY_BITMAP is used to fetch the
bitmap of pinned memory in iommu container, we need copy those
memory to the target during the migration as they are dirtied by
mdev devices.
Signed-off-by: Yulei Zhang
---
hw/vfio/common.c | 32 +++
VM status change handler is added to change the vfio pci device
status during the migration, write the demanded device status
to the DEVICE STATUS subregion to stop the device on the source side
before fetch its status and start the deivce on the target side
after restore its status.
Signed-off-by
On Fri, Jul 28, 2017 at 08:20:57AM +0200, Thomas Huth wrote:
> On 28.07.2017 06:02, David Gibson wrote:
> > On Tue, Jul 25, 2017 at 08:03:06PM +0200, Greg Kurz wrote:
> >> The "phandle" property of the XICS node is referenced by the
> >> "interrupt-map"
> >> property of each PHB node. This is used
Hi,
This series seems to have some coding style problems. See output below for
more information:
Subject: [Qemu-devel] [RFC V2 0/4] vfio: Introduce Live migration capability to
vfio_mdev device
Message-id: 1494316727-15518-1-git-send-email-yulei.zh...@intel.com
Type: series
=== TEST SCRIPT BEGI
> From: Zhang, Yulei
> Sent: Tuesday, May 9, 2017 3:59 PM
>
> Summary
>
> This series RFC would like to introduce the live migration capability
> to vfio_mdev device.
>
> As currently vfio_mdev device don't support migration, we introduce
> a new vfio subtype region
> VFIO_REGION_SUBTYPE_INTEL_I
50 matches
Mail list logo
