On 15/09/2015 18:13, Cornelia Huck wrote:
> On Tue, 15 Sep 2015 17:07:55 +0200
> Paolo Bonzini wrote:
>
>> On 15/09/2015 08:41, Jason Wang wrote:
>>> +With KVM_CAP_FAST_MMIO, a zero length mmio eventfd is allowed for
>>> +kernel to ignore the length of guest write and get
On Tue, 15 Sep 2015 18:29:49 +0200
Paolo Bonzini wrote:
> On 15/09/2015 18:13, Cornelia Huck wrote:
> > On Tue, 15 Sep 2015 17:07:55 +0200
> > Paolo Bonzini wrote:
> >
> >> On 15/09/2015 08:41, Jason Wang wrote:
> >>> +With KVM_CAP_FAST_MMIO, a zero
On Tue, Sep 15, 2015 at 05:08:49PM +0200, Paolo Bonzini wrote:
>
>
> On 15/09/2015 08:41, Jason Wang wrote:
> > Hi:
> >
> > This series fixes two issues of fast mmio eventfd:
> >
> > 1) A single iodev instance were registerd on two buses: KVM_MMIO_BUS
> >and KVM_FAST_MMIO_BUS. This will
Hi all
I wonder if there is (relative) new ToDo/open projects list for kvm.
Th one on the www.linux-kvm.org/page/TODO seems to be a little bit old
Best
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at
> do you get normal speed?
Nope, still slow... I somehow missed that svm_set_msr() calls
svm_set_guest_pat() as well, it does seem to properly change g_pat. The only
thing that catches my eyes is that later on all WT entries in g_pat are
replaced by WC (0x0007040600070406 ->
On Mon, 2015-04-13 at 02:32 +0300, Nadav Amit wrote:
> Due to old Seabios bug, QEMU reenable LINT0 after reset. This bug is long gone
> and therefore this hack is no longer needed. Since it violates the
> specifications, it is removed.
>
> Signed-off-by: Nadav Amit
>
Hello,
On Tue, Sep 15, 2015 at 11:11:45PM +0200, Christian Borntraeger wrote:
> > In fact, I would say that any userspace-controlled call to *_expedited()
> > is a bug waiting to happen and a bad idea---because userspace can, with
> > little effort, end up calling it in a loop.
>
> Right. This
On Tue, Sep 15, 2015 at 05:26:22PM -0400, Tejun Heo wrote:
> Hello,
>
> On Tue, Sep 15, 2015 at 11:11:45PM +0200, Christian Borntraeger wrote:
> > > In fact, I would say that any userspace-controlled call to *_expedited()
> > > is a bug waiting to happen and a bad idea---because userspace can,
Am 15.09.2015 um 18:42 schrieb Paolo Bonzini:
>
>
> On 15/09/2015 15:36, Christian Borntraeger wrote:
>> I am wondering why the old code behaved in such fatal ways. Is there
>> some interaction between waiting for a reschedule in the
>> synchronize_sched writer and some fork code actually
On (Tue) 15 Sep 2015 [14:26:06], David Gibson wrote:
> On Mon, Sep 14, 2015 at 08:32:36AM +0200, Thomas Huth wrote:
> > On 14/09/15 04:15, David Gibson wrote:
> > > On Fri, Sep 11, 2015 at 11:17:01AM +0200, Thomas Huth wrote:
> > >> The PAPR interface defines a hypercall to pass high-quality
> >
https://bugzilla.kernel.org/show_bug.cgi?id=104581
Bug ID: 104581
Summary: BUG: quattro stagioni
Product: Virtualization
Version: unspecified
Kernel Version: 4.3.0-0.rc1.git0.1.fc24.x86_64+debug
Hardware: x86-64
OS: Linux
Juan Quintela wrote:
> Hi
>
> Please, send any topic that you are interested in covering.
>
> At the end of Monday I will send an email with the agenda or the
> cancellation of the call, so hurry up.
>
> After discussions on the QEMU Summit, we are going to have always open a
On 15/09/2015 15:36, Sander Klein wrote:
> On 2015-09-15 15:24, Paolo Bonzini wrote:
>>
>> What kernel runs in the host?
>
> The host is the standard Debian Jessie kernel, 3.16.7-ckt11-1+deb8u3.
Please try a more recent kernel (3.19 or newer).
Paolo
--
To unsubscribe from this list: send the
Hello,
On Tue, Sep 15, 2015 at 03:36:34PM +0200, Christian Borntraeger wrote:
> >> The problem seems to be that the newly used percpu_rwsem does a
> >> rcu_synchronize_sched_expedited for all write downs/ups.
> >
> > Can you try:
> >
> >
On Tue, Sep 15, 2015 at 02:05:14PM +0200, Christian Borntraeger wrote:
> Tejun,
>
>
> commit d59cfc09c32a2ae31f1c3bc2983a0cd79afb3f14 (sched, cgroup: replace
> signal_struct->group_rwsem with a global percpu_rwsem) causes some noticably
> hickups when starting several kvm guests (which libvirt
On 15/09/2015 12:57, Sander Klein wrote:
>
> I'm running Debian Jessie with KVM 2.1 on 6 nodes with an NFS3 back-end
> and sometimes when I migrate a VM it suddenly 'hangs'. The KVM process
> is running on the new node, eating up all it's CPU cycles but it does
> not respond to anything
On 2015-09-15 15:24, Paolo Bonzini wrote:
What kernel runs in the host?
The host is the standard Debian Jessie kernel, 3.16.7-ckt11-1+deb8u3.
Sander
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at
Am 15.09.2015 um 15:05 schrieb Peter Zijlstra:
> On Tue, Sep 15, 2015 at 02:05:14PM +0200, Christian Borntraeger wrote:
>> Tejun,
>>
>>
>> commit d59cfc09c32a2ae31f1c3bc2983a0cd79afb3f14 (sched, cgroup: replace
>> signal_struct->group_rwsem with a global percpu_rwsem) causes some noticably
>>
On 15/09/2015 12:30, Wanpeng Li wrote:
> + if (!nested) {
> + vpid = find_first_zero_bit(vmx_vpid_bitmap, VMX_NR_VPIDS);
> + if (vpid < VMX_NR_VPIDS) {
> vmx->vpid = vpid;
> __set_bit(vpid, vmx_vpid_bitmap);
> + }
> + } else
101 - 119 of 119 matches
Mail list logo