On 11/20/14 00:32, Mario Smarduch wrote:
> Hi Laszlo,
>
> couple observations.
>
> I'm wondering if access from qemu and guest won't
> result in mixed memory attributes and if that's acceptable
> to the CPU.
Normally this would be a problem I think (Jon raised the topic of live
migration).
VT-d Posted-Interrupts is an enhancement to CPU side Posted-Interrupt.
With VT-d Posted-Interrupts enabled, external interrupts from
direct-assigned devices can be delivered to guests without VMM
intervention when guest is running in non-root mode.
You can find the VT-d Posted-Interrtups Spec. in
This API returns the host irq for the MSI/MSI-X interrrupts.
Signed-off-by: Feng Wu
---
drivers/vfio/pci/vfio_pci.c | 10 ++
include/linux/vfio.h|2 ++
2 files changed, 12 insertions(+), 0 deletions(-)
diff --git a/drivers/vfio/pci/vfio_pci.c b/drivers/vfio/pci/vfio_pci.c
Add new group KVM_DEV_VFIO_INTERRUPT and command
KVM_DEV_VFIO_DEVIE_POSTING_IRQ related to it.
This is used for VT-d Posted-Interrupts setup.
Signed-off-by: Feng Wu
---
Documentation/virtual/kvm/devices/vfio.txt |8
include/uapi/linux/kvm.h | 14 ++
"Suresh E. Warrier" writes:
> This patch adds trace points in the guest entry and exit code and also
> for exceptions handled by the host in kernel mode - hypercalls and page
> faults. The new events are added to /sys/kernel/debug/tracing/events
> under a new subsystem called kvm_hv.
>
The next code fragment "list_for_each_entry" is not depend on "minor". With this
patch, the free of "minor" in "list_for_each_entry" can be reduced, and there is
no functional change.
Signed-off-by: Zhen Lei
---
drivers/vfio/vfio.c | 13 ++---
1 file changed, 6 insertions(+), 7 deletions
Am 10.11.2014 um 22:07 schrieb Linus Torvalds:
[...]
> So before blacklisting any compilers, let's first see if
>
> (a) we can actually make it a real rule that we only use ACCESS_ONCE on
> scalars
> (b) we can somehow enforce this with a compiler warning/error for mis-uses
>
> For example, th
On 19.11.14 22:54, Suresh E. Warrier wrote:
>
>
> On 11/14/2014 04:56 AM, Alexander Graf wrote:
>>
>>
>>
>>> Am 14.11.2014 um 00:29 schrieb Suresh E. Warrier
>>> :
>>>
>>> This patch adds trace points in the guest entry and exit code and also
>>> for exceptions handled by the host in kernel mo
On 20.11.14 11:40, Aneesh Kumar K.V wrote:
> "Suresh E. Warrier" writes:
>
>> This patch adds trace points in the guest entry and exit code and also
>> for exceptions handled by the host in kernel mode - hypercalls and page
>> faults. The new events are added to /sys/kernel/debug/tracing/events
2014-11-19 22:05+0100, Paolo Bonzini:
> KVM for ia64 has been marked as broken not just once, but twice even,
> and the last patch from the maintainer is now roughly 5 years old.
> Time for it to rest in piece.
>
> Signed-off-by: Paolo Bonzini
> ---
Nice, if only every diffstat was like that!
I
ia64 does not need them anymore.
Signed-off-by: Paolo Bonzini
---
arch/x86/include/asm/kvm_host.h | 16
arch/x86/kvm/Makefile | 5 ++---
{virt => arch/x86}/kvm/ioapic.c | 0
{virt => arch/x86}/kvm/ioapic.h | 1 -
{virt => arch/x86}/kvm/irq_comm.c | 4 ++--
On 20/11/2014 14:38, Radim Krčmář wrote:
> I propose another removal.
> (The reasoning below wasn't confirmed with ia64 compiler.
> I'd remove the ioctls even if they worked.)
Checked and applied, thanks.
Paolo
> ---8<---
> KVM: remove buggy ia64 specific ioctls
>
> IA64 is no longer present
On Thu, 20 Nov 2014 13:10:12 +0100
Alexander Graf wrote:
>
>
> On 20.11.14 11:40, Aneesh Kumar K.V wrote:
> > "Suresh E. Warrier" writes:
> >
> >> This patch adds trace points in the guest entry and exit code and also
> >> for exceptions handled by the host in kernel mode - hypercalls and pag
On Wed, Nov 12, 2014 at 5:49 PM, Alex Williamson
wrote:
>
> On Wed, 2014-11-12 at 11:05 +0100, Eric Auger wrote:
> > Hi Antonios,
> >
> > On 10/27/2014 07:07 PM, Antonios Motakis wrote:
> > > This patch forms the common skeleton code for platform devices support
> > > with VFIO. This will include
On Wed, Nov 12, 2014 at 5:36 PM, Alex Williamson
wrote:
> On Wed, 2014-11-12 at 11:32 +0100, Eric Auger wrote:
>> On 10/27/2014 07:07 PM, Antonios Motakis wrote:
>> > A VFIO userspace driver will start by opening the VFIO device
>> > that corresponds to an IOMMU group, and will use the ioctl inter
On Thu, Nov 13, 2014 at 9:05 AM, Hongbo Zhang wrote:
> On 12 November 2014 17:57, Antonios Motakis
> wrote:
>> Hello Hongbo,
>>
>> On Wed, Nov 12, 2014 at 10:52 AM, Hongbo Zhang
>> wrote:
>>> On 28 October 2014 02:07, Antonios Motakis
>>> wrote:
Enable building the VFIO PLATFORM driv
On 11/20/2014 03:10 PM, Antonios Motakis wrote:
> On Wed, Nov 12, 2014 at 5:36 PM, Alex Williamson
> wrote:
>> On Wed, 2014-11-12 at 11:32 +0100, Eric Auger wrote:
>>> On 10/27/2014 07:07 PM, Antonios Motakis wrote:
A VFIO userspace driver will start by opening the VFIO device
that corre
On Wed, Nov 19, 2014 at 8:59 PM, Christoffer Dall
wrote:
> On Tue, Nov 11, 2014 at 02:48:25PM +0530, Anup Patel wrote:
>> Hi All,
>>
>> I have second thoughts about rebasing KVM PMU patches
>> to Marc's irq-forwarding patches.
>>
>> The PMU IRQs (when virtualized by KVM) are not exactly
>> forward
On Thu, 2014-11-20 at 19:25 +0800, Zhen Lei wrote:
> The next code fragment "list_for_each_entry" is not depend on "minor". With
> this
> patch, the free of "minor" in "list_for_each_entry" can be reduced, and there
> is
> no functional change.
A reasonable micro-optimization, but I'm curious if
On Thu, 2014-11-20 at 17:05 +0800, Feng Wu wrote:
> Add new group KVM_DEV_VFIO_INTERRUPT and command
> KVM_DEV_VFIO_DEVIE_POSTING_IRQ related to it.
>
> This is used for VT-d Posted-Interrupts setup.
Eric proposed an interface for ARM forwarded interrupts[1] using group
KVM_DEV_VFIO_DEVICE with a
On 11/20/2014 04:53 PM, Alex Williamson wrote:
> On Thu, 2014-11-20 at 17:05 +0800, Feng Wu wrote:
>> Add new group KVM_DEV_VFIO_INTERRUPT and command
>> KVM_DEV_VFIO_DEVIE_POSTING_IRQ related to it.
>>
>> This is used for VT-d Posted-Interrupts setup.
>
> Eric proposed an interface for ARM forwar
On Thu, 2014-11-20 at 17:05 +0800, Feng Wu wrote:
> This API returns the host irq for the MSI/MSI-X interrrupts.
>
> Signed-off-by: Feng Wu
> ---
> drivers/vfio/pci/vfio_pci.c | 10 ++
> include/linux/vfio.h|2 ++
> 2 files changed, 12 insertions(+), 0 deletions(-)
>
> dif
On 11/20/2014 05:05 PM, Alex Williamson wrote:
> On Thu, 2014-11-20 at 17:05 +0800, Feng Wu wrote:
>> This API returns the host irq for the MSI/MSI-X interrrupts.
>>
>> Signed-off-by: Feng Wu
>> ---
>> drivers/vfio/pci/vfio_pci.c | 10 ++
>> include/linux/vfio.h|2 ++
>> 2 f
Fenghua,
I got KVM (v3.17) crashing on a machine that supports XRSTORS - It appears to
get a #GP when it is trying to load the guest FPU.
One reason for the #GP is that XCOMP_BV[63] is zeroed on the guest_fpu, but I
am not sure it is the only problem.
Was KVM ever tested with XRSTORS?
Thanks,
N
On 11/18/2014 9:57 AM, Eric S. Johansson wrote:
That's great to know. I will spin up a version of Windows 7 and give
it a try given that I'm not looking at it, I can strip it down to the
barest user interface elements and improve performance significantly.
I tried it and it took me approxim
On 05.11.14 02:21, Paul Mackerras wrote:
> From: "Aneesh Kumar K.V"
>
> In kvm_test_clear_dirty(), if we find an invalid HPTE we move on to the
> next HPTE without unlocking the invalid one. In fact we should never
> find an invalid and unlocked HPTE in the rmap chain, but for robustness
> we
On 03.11.14 16:35, Cédric Le Goater wrote:
> When being restored from qemu, the kvm_get_htab_header are in native
> endian, but the ptes are big endian.
>
> This patch fixes restore on a KVM LE host. Qemu also needs a fix for
> this :
>
> http://lists.nongnu.org/archive/html/qemu-ppc/2014
Hi,
On Fri, Oct 31, 2014 at 12:39:32PM -0700, Peter Feiner wrote:
> On Fri, Oct 31, 2014 at 11:29:49AM +0800, zhanghailiang wrote:
> > Agreed, but for doing live memory snapshot (VM is running when do
> > snapsphot),
> > we have to do this (block the write action), because we have to save the
>
On 03.11.14 05:51, Paul Mackerras wrote:
> From: Mahesh Salgaonkar
>
> When we get an HMI (hypervisor maintenance interrupt) while in a
> guest, we see that guest enters into paused state. The reason is, in
> kvmppc_handle_exit_hv it falls through default path and returns to
> host instead of
Hi,
I've almost finished the ARMv8 guest debug support but I have one
problem left to solve. userspace needs to know how many hardware debug
registers are available for GDB to use. This information is available
from the ID_AA64DFR0_EL1 register. Currently I abuse GET_ONE_REG to
fetch it's value ho
On 03.11.14 05:52, Paul Mackerras wrote:
> From: "Suresh E. Warrier"
>
> The kvmppc_vcore_blocked() code does not check for the wait condition
> after putting the process on the wait queue. This means that it is
> possible for an external interrupt to become pending, but the vcpu to
> remain as
On 03.11.14 05:51, Paul Mackerras wrote:
> Here are fixes for five bugs which were found in the testing of our
> PowerKVM product. The bugs range from guest performance issues to
> guest crashes and memory corruption. Please apply.
Thanks, applied patches 1-4 to kvm-ppc-queue.
Alex
--
To uns
Hi,
On Thu, Nov 20, 2014 at 10:54:29AM +0800, zhanghailiang wrote:
> Yes, you are right. This is what i really want, bypass all non-present faults
> and only track strict wrprotect faults. ;)
>
> So, do you plan to support that in the userfault API?
Yes I think it's good idea to support wrprotec
On 11/20/2014 12:08 AM, Laszlo Ersek wrote:
> On 11/20/14 00:32, Mario Smarduch wrote:
>> Hi Laszlo,
>>
>> couple observations.
>>
>> I'm wondering if access from qemu and guest won't
>> result in mixed memory attributes and if that's acceptable
>> to the CPU.
>
> Normally this would be a pro
On 20 November 2014 18:35, Mario Smarduch wrote:
> I think beyond consistency, there should be no double mappings with
> conflicting attributes at any time or CPU state is undefined.
The situation is not so bleak as this. See section B2.9 "Mismatched
memory attributes" in the ARMv8 ARM ARM (DDI04
On 11/20/2014 10:40 AM, Peter Maydell wrote:
> On 20 November 2014 18:35, Mario Smarduch wrote:
>> I think beyond consistency, there should be no double mappings with
>> conflicting attributes at any time or CPU state is undefined.
>
> The situation is not so bleak as this. See section B2.9 "Mism
On 11/20/2014 11:36 AM, Alexander Graf wrote:
>
>
> On 03.11.14 05:52, Paul Mackerras wrote:
>> From: "Suresh E. Warrier"
>>
>> The kvmppc_vcore_blocked() code does not check for the wait condition
>> after putting the process on the wait queue. This means that it is
>> possible for an externa
On 11/20/2014 01:40 PM, Peter Maydell wrote:
> On 20 November 2014 18:35, Mario Smarduch wrote:
>> I think beyond consistency, there should be no double mappings with
>> conflicting attributes at any time or CPU state is undefined.
>
> The situation is not so bleak as this. See section B2.9 "Mism
On 20 November 2014 19:49, Jon Masters wrote:
> On 11/20/2014 01:40 PM, Peter Maydell wrote:
>> The situation is not so bleak as this. See section B2.9 "Mismatched
>> memory attributes" in the ARMv8 ARM ARM (DDI0487A.d), which lays
>> out in some detail what the results of mismatched attributes ar
On Thu, Nov 20, 2014 at 3:39 AM, Christian Borntraeger
wrote:
>
> So It looks like we could make a change to ACCESS_ONCE. Would something like
>
> CONFIG_ARCH_SCALAR_ACCESS_ONCE be a good start?
No, if it's just a handful of places to be fixed, let's not add config
options for broken cases.
> Th
On 11/20/14 21:10, Peter Maydell wrote:
> On 20 November 2014 19:49, Jon Masters wrote:
>> On 11/20/2014 01:40 PM, Peter Maydell wrote:
>>> The situation is not so bleak as this. See section B2.9 "Mismatched
>>> memory attributes" in the ARMv8 ARM ARM (DDI0487A.d), which lays
>>> out in some detai
On 20/11/2014 17:28, Eric S. Johansson wrote:
> I'm accustomed to lesser performance on virtual machines. That's the
> hazard of a running on old and slow laptop (dell e6400 (2.2ghz core
> duo, 8gb ram)[1]) but even virtual box is not this slow. So what am I
> doing wrong? It would be nice to u
On 20 November 2014 21:13, Laszlo Ersek wrote:
> On 11/20/14 21:10, Peter Maydell wrote:
>> I think in practice for a well-behaved guest we can arrange
>> that everything is fine (roughly, the guest has to treat
>> DMA-capable devices as doing coherent-dma, which we can tell
>> them to do via DT b
> From: Nadav Amit [mailto:nadav.a...@gmail.com]
> Sent: Thursday, November 20, 2014 8:34 AM
> To: Paolo Bonzini; Yu, Fenghua
> Cc: kvm list
> Subject: KVM causes #GP on XRSTORS
>
> Fenghua,
>
> I got KVM (v3.17) crashing on a machine that supports XRSTORS - It appears
> to get a #GP when it is t
On 11/20/2014 4:48 PM, Paolo Bonzini wrote:
On 20/11/2014 17:28, Eric S. Johansson wrote:
I'm accustomed to lesser performance on virtual machines. That's the
hazard of a running on old and slow laptop (dell e6400 (2.2ghz core
duo, 8gb ram)[1]) but even virtual box is not this slow. So what
When being restored from qemu, the kvm_get_htab_header are in native
endian, but the ptes are big endian.
This patch fixes restore on a KVM LE host. Qemu also needs a fix for
this :
http://lists.nongnu.org/archive/html/qemu-ppc/2014-11/msg8.html
Signed-off-by: Cédric Le Goater
Cc: Pau
Hi Nadav,
On Thu, Nov 20, 2014 at 06:34:04PM +0200, Nadav Amit wrote:
>Fenghua,
>
>I got KVM (v3.17) crashing on a machine that supports XRSTORS - It appears to
>get a #GP when it is trying to load the guest FPU.
>One reason for the #GP is that XCOMP_BV[63] is zeroed on the guest_fpu, but I
>am n
> On Nov 21, 2014, at 02:10, Wanpeng Li wrote:
>
> Hi Nadav,
> On Thu, Nov 20, 2014 at 06:34:04PM +0200, Nadav Amit wrote:
>> Fenghua,
>>
>> I got KVM (v3.17) crashing on a machine that supports XRSTORS - It appears
>> to get a #GP when it is trying to load the guest FPU.
>> One reason for the
On 2014/11/20 23:37, Alex Williamson wrote:
> On Thu, 2014-11-20 at 19:25 +0800, Zhen Lei wrote:
>> The next code fragment "list_for_each_entry" is not depend on "minor". With
>> this
>> patch, the free of "minor" in "list_for_each_entry" can be reduced, and
>> there is
>> no functional change.
>
Hi Tang,
On Fri, Nov 21, 2014 at 02:41:57PM +0800, Tang Chen wrote:
>Hi Wanpeng,
>
>Sorry, it is about this problem again.
>
>I booted 3.18.0-rc2, without Paolo's patch. lockdep and RCU debug
>were all opened.
>
>Then I started a qemu vm with the following options:
>
>/usr/libexec/qemu-kvm -hda rhe
On 2014/11/21 1:38, Andrea Arcangeli wrote:
Hi,
On Thu, Nov 20, 2014 at 10:54:29AM +0800, zhanghailiang wrote:
Yes, you are right. This is what i really want, bypass all non-present faults
and only track strict wrprotect faults. ;)
So, do you plan to support that in the userfault API?
Yes I
51 matches
Mail list logo
