On 2020/6/29 0:14, Bjorn Helgaas wrote:
> On Sun, Jun 28, 2020 at 12:18:10PM +0800, Xiang Zheng wrote:
>> On 2020/6/26 7:24, Bjorn Helgaas wrote:
>>> On Wed, Jun 24, 2020 at 06:23:09PM -0500, Bjorn Helgaas wrote:
>>>> On Tue, Dec 10, 2019 at 11:15
On 2020/6/26 7:24, Bjorn Helgaas wrote:
> On Wed, Jun 24, 2020 at 06:23:09PM -0500, Bjorn Helgaas wrote:
>> On Tue, Dec 10, 2019 at 11:15:27AM +0800, Xiang Zheng wrote:
>>> 7ea7e98fd8d0 ("PCI: Block on access to temporarily unavailable pci
>>> device") sugge
Hi Bjorn,
Sorry for the late reply, I had Dragon Boat Festival these days.
On 2020/6/25 7:23, Bjorn Helgaas wrote:
> On Tue, Dec 10, 2019 at 11:15:27AM +0800, Xiang Zheng wrote:
>> 7ea7e98fd8d0 ("PCI: Block on access to temporarily unavailable pci
>> device") su
Hi Bjorn,
Could you spare a little time for reviewing the v3 patch?
I'm afraid you had missed it.
v3: https://lkml.org/lkml/2019/12/10/36
On 2020/6/24 3:43, James Puthukattukaran wrote:
> Xiang/Bjorn -
> Any timeline when this bug will make it upstream? We're running into this
> problem on
c5e6688752c25 ("vfio/type1: Add conditional rescheduling") missed
a "cond_resched()" in vfio_iommu_map if iommu map failed.
This is a very tiny optimization and the case can hardly happen.
Signed-off-by: Xiang Zheng
---
drivers/vfio/vfio_iommu_type1.c | 4 +++-
1 file c
On 2020/6/11 8:23, Yan Zhao wrote:
> On Wed, Jun 10, 2020 at 04:59:43PM +0800, Xiang Zheng wrote:
>> Hi Yan,
>>
>> few nits below...
>>
>> On 2020/5/18 10:53, Yan Zhao wrote:
>>> This driver intercepts all device operations as long as it's
Hi Yan,
few nits below...
On 2020/5/18 10:53, Yan Zhao wrote:
> This driver intercepts all device operations as long as it's probed
> successfully by vfio-pci driver.
>
> It will process regions and irqs of its interest and then forward
> operations to default handlers exported from vfio pci if
Hi Bjorn,
Thanks for your reply!
On 2019/10/18 21:58, Bjorn Helgaas wrote:
> [+cc Matthew]
>
> On Wed, Oct 16, 2019 at 09:36:23PM +0800, Xiang Zheng wrote:
>> Hi all,
>>
>> Recently I encountered a kernel panic while doing vfio-pci hot-plug/unplug
>> te
Hi all,
Recently I encountered a kernel panic while doing vfio-pci hot-plug/unplug test
repeatly on my Arm-KVM virtual machines.
See the call stack below:
[66628.697280] vfio-pci :06:03.5: enabling device ( -> 0002)
[66628.809290] vfio-pci :06:03.1: enabling device ( -> 0002)
will get hang for
handling these interrupts.
So update the sample_period of perf event if the counter value is
changed to avoid this case.
Signed-off-by: Xiang Zheng
---
virt/kvm/arm/pmu.c | 54 +-
1 file changed, 45 insertions(+), 9 deletions
10 matches
Mail list logo