[Qemu-devel] [PATCH] hw/audio/intel-hda: Fix MSI capability address

2014-07-27 Thread Jan Kiszka
From: Jan Kiszka jan.kis...@siemens.com According to ICH9 spec, the MSI capability is located at 0x60. This is important for guest drivers that do not parse the capability chain and use absolute addresses instead. Signed-off-by: Jan Kiszka jan.kis...@siemens.com --- hw/audio/intel-hda.c | 2 +-

[Qemu-devel] [PATCH] pci: Use bus master address space for delivering MSI/MSI-X messages

2014-07-27 Thread Jan Kiszka
From: Jan Kiszka jan.kis...@siemens.com The spec says (and real HW confirms this) that, if the bus master bit is 0, the device will not generate any PCI accesses. MSI and MSI-X messages fall among these, so we should use the corresponding address space to deliver them. This will prevent delivery

[Qemu-devel] [PATCH v2 0/3] intel-iommu: introduce Intel IOMMU (VT-d) emulation to q35 chipset

2014-07-27 Thread Le Tan
Hi, These patches are intended to introduce Intel IOMMU (VT-d) emulation to q35 chipset. The major job in these patches is to add support for emulating Intel IOMMU according to the VT-d specification, including basic responses to CSRs accesses, the logic of DMAR (DMA remapping) and DMA memory

[Qemu-devel] [PATCH v2 1/3] intel-iommu: introduce Intel IOMMU (VT-d) emulation

2014-07-27 Thread Le Tan
Add support for emulating Intel IOMMU according to the VT-d specification for the q35 chipset machine. Implement the logic for DMAR (DMA remapping) without PASID support. Use register-based invalidation for context-cache invalidation and IOTLB invalidation. Basic fault reporting and caching are

[Qemu-devel] [PATCH v2 2/3] intel-iommu: add DMAR table to ACPI tables

2014-07-27 Thread Le Tan
Expose Intel IOMMU to the BIOS. If object of TYPE_INTEL_IOMMU_DEVICE exists, add DMAR table to ACPI RSDT table. For now the DMAR table indicates that there is only one hardware unit without INTR_REMAP capability on the platform. Signed-off-by: Le Tan tamlokv...@gmail.com --- hw/i386/acpi-build.c

Re: [Qemu-devel] [PATCH] [RFC] Add machine type pc-1.0-qemu-kvm for live migrate compatibility with qemu-kvm

2014-07-27 Thread Alex Bligh
Andreas, On 27 Jul 2014, at 15:10, Andreas Färber afaer...@suse.de wrote: Hi Alex, + quintela, mst, libvirt Thanks for your comments! This sounds like a really cool feature that SUSE would probably be interested in extending back to 0.14 and 0.15, but I see a fundamental flaw: libvirt

Re: [Qemu-devel] [PATCH] [RFC] Add machine type pc-1.0-qemu-kvm for live migrate compatibility with qemu-kvm

2014-07-27 Thread Alex Bligh
On 22 Jul 2014, at 19:43, Alex Bligh a...@alex.org.uk wrote: Testing has been light to date (i.e. can I migrate it inbound with -S without anything complaining). I've given this quite a bit more testing today. It works fine qemu-kvm 1.0 - qemu-2.0+patch (cirrus vga) It works fine

Re: [Qemu-devel] [PATCH v3 1/7] bootindex: add modify_boot_device_path function

2014-07-27 Thread Gonglei (Arei)
-Original Message- From: 陈梁 [mailto:chenliang0...@icloud.com] Sent: Sunday, July 27, 2014 11:51 AM Subject: Re: [Qemu-devel] [PATCH v3 1/7] bootindex: add modify_boot_device_path function Hi +if (bootindex = 0) { +node = g_malloc0(sizeof(FWBootEntry)); +

[Qemu-devel] [qemu-devel] Is sse2 implemented with host hardware support ?

2014-07-27 Thread 邓尧
Hello, I need to optimize a Linux program running under qemu-system-i386. qemu is compiled with KVM support. File /proc/cpuinfo in the guest shows that SSE2 is supported. If SSE2 is backed with host hardware, using SSE2 may improve my program's performance significantly. The host is x86_64 Linux.