https://bugzilla.kernel.org/show_bug.cgi?id=102301
--- Comment #3 from Michael Long ---
Created attachment 197251
--> https://bugzilla.kernel.org/attachment.cgi?id=197251=edit
Backtrace taken with kernel 4.3.0
--
You are receiving this mail because:
You are watching the
https://bugzilla.kernel.org/show_bug.cgi?id=102301
--- Comment #4 from Michael Long ---
Created attachment 197261
--> https://bugzilla.kernel.org/attachment.cgi?id=197261=edit
Backtrace taken with kernel 4.4-rc
--
You are receiving this mail because:
You are watching the
https://bugzilla.kernel.org/show_bug.cgi?id=102301
--- Comment #5 from Michael Long ---
I'm also affected by this problem but haven't found a pattern to reproduce the
problem yet.
My observation is, that in former kernel versions, the shutdown problem was on
every 10th
On 2015/12/14 5:28, Alexander Duyck wrote:
This patch set is meant to be the guest side code for a proof of concept
involving leaving pass-through devices in the guest during the warm-up
phase of guest live migration. In order to accomplish this I have added a
new function called dma_mark_dirty
On Sun, Dec 13, 2015 at 6:27 PM, Yang Zhang wrote:
> On 2015/12/14 5:28, Alexander Duyck wrote:
>>
>> This patch set is meant to be the guest side code for a proof of concept
>> involving leaving pass-through devices in the guest during the warm-up
>> phase of guest live
On 2015/12/14 12:54, Alexander Duyck wrote:
On Sun, Dec 13, 2015 at 6:27 PM, Yang Zhang wrote:
On 2015/12/14 5:28, Alexander Duyck wrote:
This patch set is meant to be the guest side code for a proof of concept
involving leaving pass-through devices in the guest
On 12/11/2015 1:16 AM, Alexander Duyck wrote:
On Thu, Dec 10, 2015 at 6:38 AM, Lan, Tianyu wrote:
On 12/10/2015 7:41 PM, Dr. David Alan Gilbert wrote:
Ideally, it is able to leave guest driver unmodified but it requires the
hypervisor or qemu to aware the device
On Sun, Dec 13, 2015 at 7:47 AM, Lan, Tianyu wrote:
>
>
> On 12/11/2015 1:16 AM, Alexander Duyck wrote:
>>
>> On Thu, Dec 10, 2015 at 6:38 AM, Lan, Tianyu wrote:
>>>
>>>
>>>
>>> On 12/10/2015 7:41 PM, Dr. David Alan Gilbert wrote:
>
>
>
This change essentially does two things. First it folds the swiotlb_unmap
and swiotlb_sync calls into their callers. The goal behind this is three
fold. First this helps to reduce execution time and improves performance
since we aren't having to call into as many functions. Second it allows us
This change essentially does two things. First it folds the swiotlb_unmap
and swiotlb_sync calls into their callers. The goal behind this is three
fold. First this helps to reduce execution time and improves performance
since we aren't having to call into as many functions. Second it allows us
This patch set is meant to be the guest side code for a proof of concept
involving leaving pass-through devices in the guest during the warm-up
phase of guest live migration. In order to accomplish this I have added a
new function called dma_mark_dirty that will mark the pages associated with
the
This patch is meant to provide the guest with a way of flagging DMA pages
as being dirty to the host when using a direct-assign device within a
guest. The advantage to this approach is that it is fairly simple, however
It currently has a singificant impact on device performance in all the
On Sun, Dec 13, 2015 at 9:22 PM, Yang Zhang wrote:
> On 2015/12/14 12:54, Alexander Duyck wrote:
>>
>> On Sun, Dec 13, 2015 at 6:27 PM, Yang Zhang
>> wrote:
>>>
>>> On 2015/12/14 5:28, Alexander Duyck wrote:
This patch set is meant
On 2015/12/14 13:46, Alexander Duyck wrote:
On Sun, Dec 13, 2015 at 9:22 PM, Yang Zhang wrote:
On 2015/12/14 12:54, Alexander Duyck wrote:
On Sun, Dec 13, 2015 at 6:27 PM, Yang Zhang
wrote:
On 2015/12/14 5:28, Alexander Duyck wrote:
14 matches
Mail list logo