Re: [PATCH v3] KVM: x86: Fix potential preemption when get the current kvmclock timestamp

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: [PATCH v3] KVM: x86: Fix potential preemption when get the current kvmclock timestamp
From: Radim Krčmář <rkrcmar@xxxxxxxxxx>
Date: Fri, 19 May 2017 15:13:07 +0200
Cc: Paolo Bonzini <pbonzini@xxxxxxxxxx>, "linux-kernel@xxxxxxxxxxxxxxx" <linux-kernel@xxxxxxxxxxxxxxx>, kvm <kvm@xxxxxxxxxxxxxxx>, Wanpeng Li <wanpeng.li@xxxxxxxxxxx>, stable <stable@xxxxxxxxxxxxxxx>
Dmarc-filter: OpenDMARC Filter v1.3.2 mx1.redhat.com B774AC04B302
In-reply-to: <CANRm+CzLBNNrhcb1ssQgZze30sEPG56HPXZBrirnODsms2GjUg@mail.gmail.com>

2017-05-19 05:53+0800, Wanpeng Li:
> Ping,

Applying for 4.12-rc2, thanks.

References:
- Re: [PATCH v3] KVM: x86: Fix potential preemption when get the current kvmclock timestamp
  - From: Paolo Bonzini
- Re: [PATCH v3] KVM: x86: Fix potential preemption when get the current kvmclock timestamp
  - From: Wanpeng Li

Prev by Date: Re: [PATCH 1/2] nvme: fix race between removing and reseting failure
Next by Date: Re: [PATCH 2/2] nvme: avoid to hang in remove disk
Previous by thread: Re: [PATCH v3] KVM: x86: Fix potential preemption when get the current kvmclock timestamp
Next by thread: [PATCH] uwb: fix device quirk on big-endian hosts
Index(es):
- Date
- Thread

[Index of Archives] [Linux Kernel] [Kernel Development Newbies] [Linux USB Devel] [Video for Linux] [Linux Audio Users] [Yosemite Hiking] [Linux Kernel] [Linux SCSI]