On 8/6/14, 2:49 PM, William Tu wrote:
Try vfio-pci instead of pci-assign
Thanks Alex, William. Using vfio worked.
So does that mean pci-assign is being deprecated?
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More
Il 07/08/2014 03:31, Zhang, Yang Z ha scritto:
Let me give an example to see whether my concern is a real problem:
Guest allocates a vector and set it in IOAPIC entry to deliver
interrupt. Later it masks the IOAPIC entry(means stop the
corresponding device) and assign this vector to a MSI
Paolo Bonzini wrote on 2014-08-07:
Il 07/08/2014 03:31, Zhang, Yang Z ha scritto:
Let me give an example to see whether my concern is a real problem:
Guest allocates a vector and set it in IOAPIC entry to deliver
interrupt. Later it masks the IOAPIC entry(means stop the
corresponding device)
Hi Paolo,
On Wed, Aug 06, 2014 at 06:38:06AM +, Zhang, Yang Z wrote:
[...]
+
+ if (exec_control CPU_BASED_TPR_SHADOW) {
+ if (vmx-nested.virtual_apic_page)
+ nested_release_page(vmx-nested.virtual_apic_page);
+ vmx-nested.virtual_apic_page =
+
On 08/05/2014 08:14 PM, Christian Borntraeger wrote:
We currently track the pid of the task that runs the VCPU in
vcpu_load. Since we call vcpu_load for all kind of ioctls on a
CPU, this causes hickups due to synchronize_rcu if one CPU is
modified by another CPU or the main thread (e.g.
On 6 August 2014 18:18, Will Deacon will.dea...@arm.com wrote:
On Tue, Aug 05, 2014 at 09:49:55AM +0100, Anup Patel wrote:
Instead, of trying out each and every target type we should use
KVM_ARM_PREFERRED_TARGET vm ioctl to determine target type
for KVM ARM/ARM64.
We bail-out target type
On 6 August 2014 18:20, Will Deacon will.dea...@arm.com wrote:
On Tue, Aug 05, 2014 at 09:49:56AM +0100, Anup Patel wrote:
The __ARM64_SYS_REG() macro is already defined in uapi/asm/kvm.h
of Linux-3.16-rcX hence remove it from arm/aarch64/kvm-cpu.c
I've been carrying a similar patch in my
On 7 August 2014 09:44, Anup Patel anup.pa...@linaro.org wrote:
The KVM_ARM_PREFERRED_TARGET ioctl is available from 3.13 onwards.
I think we should first try KVM_ARM_PREFERRED_TARGET. If it fails then
we should fallback to old method of trying each and every target type.
You don't need to
On 6 August 2014 18:22, Will Deacon will.dea...@arm.com wrote:
On Tue, Aug 05, 2014 at 09:49:57AM +0100, Anup Patel wrote:
The VCPU target type KVM_ARM_TARGET_XGENE_POTENZA is available
in latest Linux-3.16-rcX or higher hence register aarch64 target
type for it.
This patch enables us to run
On 6 August 2014 18:23, Will Deacon will.dea...@arm.com wrote:
On Tue, Aug 05, 2014 at 09:49:58AM +0100, Anup Patel wrote:
The KVM_EXIT_SYSTEM_EVENT exit reason was added to define
architecture independent system-wide events for a Guest.
Currently, it is used by in-kernel PSCI-0.2 emulation
On 6 August 2014 18:26, Will Deacon will.dea...@arm.com wrote:
On Tue, Aug 05, 2014 at 09:49:59AM +0100, Anup Patel wrote:
If in-kernel KVM support PSCI-0.2 emulation then we should set
KVM_ARM_VCPU_PSCI_0_2 feature for each guest VCPU and also
provide arm,psci-0.2,arm,psci as PSCI compatible
On Thu, Aug 07, 2014 at 09:56:28AM +0100, Anup Patel wrote:
On 6 August 2014 18:22, Will Deacon will.dea...@arm.com wrote:
On Tue, Aug 05, 2014 at 09:49:57AM +0100, Anup Patel wrote:
The VCPU target type KVM_ARM_TARGET_XGENE_POTENZA is available
in latest Linux-3.16-rcX or higher hence
On 6 August 2014 19:54, Will Deacon will.dea...@arm.com wrote:
On Tue, Aug 05, 2014 at 10:24:11AM +0100, Anup Patel wrote:
A hypervisor will typically mask the overflow interrupt before
forwarding it to Guest Linux hence we need to re-enable the overflow
interrupt after clearing it in Guest
On Thu, Aug 07, 2014 at 10:03:58AM +0100, Anup Patel wrote:
On 6 August 2014 19:54, Will Deacon will.dea...@arm.com wrote:
On Tue, Aug 05, 2014 at 10:24:11AM +0100, Anup Patel wrote:
A hypervisor will typically mask the overflow interrupt before
forwarding it to Guest Linux hence we need to
On Thu, Aug 07, 2014 at 10:00:13AM +0100, Anup Patel wrote:
On 6 August 2014 18:26, Will Deacon will.dea...@arm.com wrote:
On Tue, Aug 05, 2014 at 09:49:59AM +0100, Anup Patel wrote:
If in-kernel KVM support PSCI-0.2 emulation then we should set
KVM_ARM_VCPU_PSCI_0_2 feature for each guest
On Thu, Aug 07, 2014 at 09:50:52AM +0100, Anup Patel wrote:
On 6 August 2014 18:20, Will Deacon will.dea...@arm.com wrote:
On Tue, Aug 05, 2014 at 09:49:56AM +0100, Anup Patel wrote:
The __ARM64_SYS_REG() macro is already defined in uapi/asm/kvm.h
of Linux-3.16-rcX hence remove it from
On Wed, Aug 06, 2014 at 02:35:29PM +0200, Paolo Bonzini wrote:
This doesn't build without CONFIG_KVM_XICS, so I had to apply a fixup
patch to move some code from being under CONFIG_HAVE_KVM_IRQCHIP or
unconditional, to being conditional on CONFIG_HAVE_KVM_IRQFD. I'll send
the patch shortly.
On 07/08/14 10:21, Raghavendra K T wrote:
On 08/05/2014 08:14 PM, Christian Borntraeger wrote:
We currently track the pid of the task that runs the VCPU in
vcpu_load. Since we call vcpu_load for all kind of ioctls on a
CPU, this causes hickups due to synchronize_rcu if one CPU is
modified by
Linus,
The following changes since commit 5167d09ffad5b16b574d35ce3047ed34caf1e837:
Merge tag 'arm64-upstream' of
git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux (2014-08-04 12:31:53
-0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/virt/kvm/kvm.git
On 2014/8/5 20:14, Zhangjie (HZ) wrote:
On 2014/8/5 17:49, Michael S. Tsirkin wrote:
On Tue, Aug 05, 2014 at 02:29:28PM +0800, Zhangjie (HZ) wrote:
Jason is right, the new order is not the cause of network unreachable.
Changing order seems not work. After about 40 times, the problem occurs
Il 05/08/2014 16:44, Christian Borntraeger ha scritto:
We currently track the pid of the task that runs the VCPU in
vcpu_load. Since we call vcpu_load for all kind of ioctls on a
CPU, this causes hickups due to synchronize_rcu if one CPU is
modified by another CPU or the main thread (e.g.
Il 07/08/2014 11:59, Christian Borntraeger ha scritto:
Paolo,
are you willing to apply to kvm/queue?
I asked a question, but anyway... not until the end of the merge window
and my small vacation. :)
Paolo
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a
Il 06/08/2014 08:38, Zhang, Yang Z ha scritto:
Paolo Bonzini wrote on 2014-08-05:
Il 05/08/2014 09:56, Zhang, Yang Z ha scritto:
Wanpeng Li wrote on 2014-08-04:
This patch fix bug
https://bugzilla.kernel.org/show_bug.cgi?id=61411
TPR shadow/threshold feature is important to speed up the
https://bugzilla.kernel.org/show_bug.cgi?id=81841
--- Comment #1 from Marti Raudsepp ma...@juffo.org ---
Created attachment 145421
-- https://bugzilla.kernel.org/attachment.cgi?id=145421action=edit
crash_netconsole.txt
--
You are receiving this mail because:
You are watching the assignee of
https://bugzilla.kernel.org/show_bug.cgi?id=81841
Bug ID: 81841
Summary: amd-iommu: kernel BUG lockup after shutting down KVM
guest using PCI passthrough/PCIe bridge
Product: Virtualization
Version: unspecified
Kernel Version:
https://bugzilla.kernel.org/show_bug.cgi?id=81841
--- Comment #2 from Marti Raudsepp ma...@juffo.org ---
Created attachment 145431
-- https://bugzilla.kernel.org/attachment.cgi?id=145431action=edit
startup_dmesg.txt
--
You are receiving this mail because:
You are watching the assignee of the
https://bugzilla.kernel.org/show_bug.cgi?id=81841
--- Comment #3 from Marti Raudsepp ma...@juffo.org ---
Created attachment 145441
-- https://bugzilla.kernel.org/attachment.cgi?id=145441action=edit
dmidecode.txt
--
You are receiving this mail because:
You are watching the assignee of the bug.
On Wed, 2014-08-06 at 23:12 -0700, Nishank Trivedi wrote:
On 8/6/14, 2:49 PM, William Tu wrote:
Try vfio-pci instead of pci-assign
Thanks Alex, William. Using vfio worked.
So does that mean pci-assign is being deprecated?
Yes, vfio is meant to replace pci-assign with a better device
https://bugzilla.kernel.org/show_bug.cgi?id=81841
Marti Raudsepp ma...@juffo.org changed:
What|Removed |Added
Kernel Version|3.13 (Ubuntu: |3.16.0 (originally Ubuntu
https://bugzilla.kernel.org/show_bug.cgi?id=81841
Alex Williamson alex.william...@redhat.com changed:
What|Removed |Added
CC|
Great. VirtIO works for me. Thanks for your help folks!
Is there is any other way to add virtual disk, more like a traditional
disk to qemu-system-aarch64? For example IDE disk or SATA disk or
maybe as a SCSI disk?
On Wed, Aug 6, 2014 at 9:48 AM, Joel Schopp joel.sch...@amd.com wrote:
It turns
virtio will get you the best performance so why would you want to use
something slower?
-Joel
On 08/07/2014 11:51 AM, Mathew Li wrote:
Great. VirtIO works for me. Thanks for your help folks!
Is there is any other way to add virtual disk, more like a traditional
disk to qemu-system-aarch64?
That's probably because you updated your guest kernel to one that
supports PSCI v0.2 and therefore ignores the incorrect function IDs in
the DT (as it should).
I've sent a fix to qemu-devel@ today:
http://lists.gnu.org/archive/html/qemu-devel/2014-08/msg01179.html
On Wed, Aug 6, 2014 at 6:48 PM,
Currently we only model a virtual machine board (the -machine
type=virt parameter) which has a UART, a flash, an RTC, and a bunch of
virtio-mmio channelse.
Once we either emulate a real aarch64 board (with whatever peripherals
it may have) or add a PCI controller to the virt board, then you can
https://bugzilla.kernel.org/show_bug.cgi?id=81841
--- Comment #6 from Marti Raudsepp ma...@juffo.org ---
(In reply to Alex Williamson from comment #5)
What if you use vfio-pci instead of pci-assign?
I run into the dreaded error:
vfio: error, group 9 is not viable, please ensure all devices
On 08/07/2014 12:53 PM, Christoffer Dall wrote:
Currently we only model a virtual machine board (the -machine
type=virt parameter) which has a UART, a flash, an RTC, and a bunch of
virtio-mmio channelse.
Once we either emulate a real aarch64 board (with whatever peripherals
it may have) or
https://bugzilla.kernel.org/show_bug.cgi?id=81841
--- Comment #7 from Alex Williamson alex.william...@redhat.com ---
(In reply to Marti Raudsepp from comment #6)
(In reply to Alex Williamson from comment #5)
What if you use vfio-pci instead of pci-assign?
I run into the dreaded error:
On 08/07/2014 12:53 PM, Christoffer Dall wrote:
Currently we only model a virtual machine board (the -machine
type=virt parameter) which has a UART, a flash, an RTC, and a bunch of
virtio-mmio channelse.
Once we either emulate a real aarch64 board (with whatever peripherals
it may have) or add
I'm trying to find out some hard data on TSC virtualization when using
qemu-kvm to run linux guests on Intel-based linux 3.4 hosts.
I've read
https://www.kernel.org/doc/Documentation/virtual/kvm/timekeeping.txt;
and looked at the code somewhat, but it's a bit tricky to figure out
exactly
The following events can lead to an incorrect KVM_EXIT_MMIO bubbling
up to userspace:
(1) Guest accesses gpa X without a memory slot. The gfn is cached in
struct kvm_vcpu_arch (mmio_gfn). On Intel EPT-enabled hosts, KVM sets
the SPTE write-execute-noread so that future accesses cause
https://bugzilla.kernel.org/show_bug.cgi?id=81841
--- Comment #8 from Marti Raudsepp ma...@juffo.org ---
(In reply to Alex Williamson from comment #7)
There are some proposed workarounds on the web
None of these remotely address the issue.
I see. This page claims so:
https://bugzilla.kernel.org/show_bug.cgi?id=81841
--- Comment #9 from Alex Williamson alex.william...@redhat.com ---
(In reply to Marti Raudsepp from comment #8)
(In reply to Alex Williamson from comment #7)
There are some proposed workarounds on the web
None of these remotely address the
On Thu, Aug 07, 2014 at 01:06:09PM -0500, Wei Huang wrote:
On 08/07/2014 12:53 PM, Christoffer Dall wrote:
Currently we only model a virtual machine board (the -machine
type=virt parameter) which has a UART, a flash, an RTC, and a bunch of
virtio-mmio channelse.
Once we either emulate a
On 08/08/2014 02:32 AM, David Matlack wrote:
The following events can lead to an incorrect KVM_EXIT_MMIO bubbling
up to userspace:
(1) Guest accesses gpa X without a memory slot. The gfn is cached in
struct kvm_vcpu_arch (mmio_gfn). On Intel EPT-enabled hosts, KVM sets
the SPTE
https://bugzilla.kernel.org/show_bug.cgi?id=81841
Joel Schopp joel.sch...@amd.com changed:
What|Removed |Added
CC||joel.sch...@amd.com
---
On Thu, 2014-08-07 at 12:47 +1000, Gavin Shan wrote:
The function is used by VFIO driver, which might be built as a
dynamic module. So it should be exported.
Signed-off-by: Gavin Shan gws...@linux.vnet.ibm.com
Acked-by: Benjamin Herrenschmidt b...@kernel.crashing.org
Alex, are you taking
Hi Zhang,
No I haven't seen such problem
Which kernel version are you running?
Host kernel: RHEL7-RC1(linux-3.10.0).
Does it include the latest lazy eli changes?
lazy eli or lazy eoi?
EOI
How to confirm whether lazy eli has been included?
not in linux-3.10.0
So, do you mean hv_vapic
On Thu, 2014-08-07 at 12:47 +1000, Gavin Shan wrote:
The patch adds one warning message in eeh_dev_open() in case the
PCI device can't be marked as passed through.
Suggested-by: Alexey Kardashevskiy a...@ozlabs.ru
Signed-off-by: Gavin Shan gws...@linux.vnet.ibm.com
---
Acked-by: Benjamin
On Fri, 2014-08-08 at 13:50 +1000, Benjamin Herrenschmidt wrote:
On Thu, 2014-08-07 at 12:47 +1000, Gavin Shan wrote:
The patch adds one warning message in eeh_dev_open() in case the
PCI device can't be marked as passed through.
Suggested-by: Alexey Kardashevskiy a...@ozlabs.ru
On Thu, Aug 7, 2014 at 6:36 PM, Xiao Guangrong
xiaoguangr...@linux.vnet.ibm.com wrote:
On 08/08/2014 02:32 AM, David Matlack wrote:
The following events can lead to an incorrect KVM_EXIT_MMIO bubbling
up to userspace:
(1) Guest accesses gpa X without a memory slot. The gfn is cached in
https://bugzilla.kernel.org/show_bug.cgi?id=72381
Zhou, Chao chao.z...@intel.com changed:
What|Removed |Added
CC||chao.z...@intel.com
---
https://bugzilla.kernel.org/show_bug.cgi?id=72381
--- Comment #4 from Zhou, Chao chao.z...@intel.com ---
this commit fixed the bug:
commit 9242b5b60df8b13b469bc6b7be08ff6ebb551ad3
Author: Bandan Das b...@redhat.com
Date: Tue Jul 8 00:30:23 2014 -0400
KVM: x86: Check for nested events if
Use device flag operation helper functions when check device
assignment status.
Signed-off-by: Ethan Zhao ethan.z...@oracle.com
---
drivers/pci/iov.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/pci/iov.c b/drivers/pci/iov.c
index cb6f247..4d109c0 100644
---
Use pci device flag operation helper functions when set device
to assigned or deassigned state.
Acked-by: David Vrabel david.vra...@citrix.com
Reviewed-by: Konrad Rzeszutek Wilk konrad.w...@oracle.com
Signed-off-by: Ethan Zhao ethan.z...@oracle.com
---
drivers/xen/xen-pciback/pci_stub.c |4
This patch introduced three helper functions to hide direct
device flag operation.
void pci_set_dev_assigned(struct pci_dev *pdev);
void pci_clear_dev_assigned(struct pci_dev *pdev);
bool pci_is_dev_assigned(struct pci_dev *pdev);
Signed-off-by: Ethan Zhao ethan.z...@oracle.com
---
v2: simplify
Use helper function instead of direct operation to pci device
flag when set device to assigned or deassigned.
Acked-by: Paolo Bonzini pbonz...@redhat.com
Signed-off-by: Ethan Zhao ethan.z...@oracle.com
---
virt/kvm/assigned-dev.c |2 +-
virt/kvm/iommu.c|4 ++--
2 files changed, 3
https://bugzilla.kernel.org/show_bug.cgi?id=72381
robert...@intel.com changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
This patch set introduces three PCI device flag operation helper functions
when set pci device PF/VF to assigned or deassigned status also check it.
and patch 2,3,4 apply these helper functions to KVM,XEN and PCI.
v2: simplify unnecessory ternary operation in function pci_is_dev_assigned().
v3:
https://bugzilla.kernel.org/show_bug.cgi?id=72381
robert...@intel.com changed:
What|Removed |Added
Status|RESOLVED|VERIFIED
--
You are receiving this
On Wed, Aug 06, 2014 at 02:35:29PM +0200, Paolo Bonzini wrote:
This doesn't build without CONFIG_KVM_XICS, so I had to apply a fixup
patch to move some code from being under CONFIG_HAVE_KVM_IRQCHIP or
unconditional, to being conditional on CONFIG_HAVE_KVM_IRQFD. I'll send
the patch shortly.
60 matches
Mail list logo
