On Jul 17, 2015, at 3:19 AM, Marc Zyngier marc.zyng...@arm.com wrote:
On 17/07/15 11:15, Christoffer Dall wrote:
On Fri, Jul 17, 2015 at 10:56:39AM +0100, Marc Zyngier wrote:
On 17/07/15 10:33, Christoffer Dall wrote:
On Fri, Jul 03, 2015 at 11:10:09AM +0100, Marc Zyngier wrote:
On
On Jun 29, 2015, at 10:52 AM, Marc Zyngier marc.zyng...@arm.com wrote:
On 29/06/15 18:38, Peter Maydell wrote:
On 29 June 2015 at 18:30, Marc Zyngier marc.zyng...@arm.com wrote:
On 29/06/15 18:13, Chalamarla, Tirumalesh wrote:
Will this also prevents migrating between same implementations
On Jun 26, 2015, at 2:53 AM, Christoffer Dall christoffer.d...@linaro.org
wrote:
On Thu, Jun 25, 2015 at 02:49:08PM +0100, Peter Maydell wrote:
On 25 June 2015 at 14:44, Marc Zyngier marc.zyng...@arm.com wrote:
It should always be possible to emulate a known CPU on a generic host,
and it
[mailto:will.dea...@arm.com]
Sent: Friday, June 27, 2014 1:47 AM
To: Alex Williamson
Cc: Chalamarla, Tirumalesh; Joerg Roedel; kvm@vger.kernel.org; open list;
stuart.yo...@freescale.com; io...@lists.linux-foundation.org;
t...@virtualopensystems.com; kvm...@lists.cs.columbia.edu; moderated list:ARM
Forgive me if this discussion is not relative here, but I thought it is.
How is VFIO restricting devices from writing to MSI/MSI-X,
Is all the vector area is mapped by VFIO to trap the accesses. I am asking
this because we might need to emulate ITS somewhere either in KVM or VFIO to
provide
When I say emulating ITS, I mean translating guest ITS commands to physical ITS
commands and placing them in physical queue.
Regards,
Tirumalesh.
-Original Message-
From: kvmarm-boun...@lists.cs.columbia.edu
[mailto:kvmarm-boun...@lists.cs.columbia.edu] On Behalf Of Chalamarla
Sorry there was a type,
The question is:
How is VFIO restricting software from writing to MSI/MSI-X vectors
of the device.
-Original Message-
From: Chalamarla, Tirumalesh
Sent: Thursday, June 26, 2014 11:16 AM
To: Chalamarla, Tirumalesh; Joerg Roedel; Will Deacon
Cc: kvm
-
From: Alex Williamson [mailto:alex.william...@redhat.com]
Sent: Thursday, June 26, 2014 12:00 PM
To: Chalamarla, Tirumalesh
Cc: Joerg Roedel; Will Deacon; kvm@vger.kernel.org; open list;
stuart.yo...@freescale.com; io...@lists.linux-foundation.org;
t...@virtualopensystems.com; kvm
-Original Message-
From: kvmarm-boun...@lists.cs.columbia.edu
[mailto:kvmarm-boun...@lists.cs.columbia.edu] On Behalf Of Andre Przywara
Sent: Thursday, June 19, 2014 2:46 AM
To: linux-arm-ker...@lists.infradead.org; kvm...@lists.cs.columbia.edu;
kvm@vger.kernel.org
Cc:
-Original Message-
From: kvmarm-boun...@lists.cs.columbia.edu
[mailto:kvmarm-boun...@lists.cs.columbia.edu] On Behalf Of Andre Przywara
Sent: Thursday, June 19, 2014 2:46 AM
To: linux-arm-ker...@lists.infradead.org; kvm...@lists.cs.columbia.edu;
kvm@vger.kernel.org
Cc:
Again what is the need for vgic-v3.emul.c when we have vgic-v3.c ?
-Original Message-
From: kvmarm-boun...@lists.cs.columbia.edu
[mailto:kvmarm-boun...@lists.cs.columbia.edu] On Behalf Of Andre Przywara
Sent: Thursday, June 19, 2014 2:46 AM
To: linux-arm-ker...@lists.infradead.org;
-Original Message-
From: kvmarm-boun...@lists.cs.columbia.edu
[mailto:kvmarm-boun...@lists.cs.columbia.edu] On Behalf Of Andre Przywara
Sent: Thursday, June 19, 2014 2:46 AM
To: linux-arm-ker...@lists.infradead.org; kvm...@lists.cs.columbia.edu;
kvm@vger.kernel.org
Cc:
12 matches
Mail list logo
