On Tue, May 05, 2020 at 08:09:39AM +0200, Cornelia Huck wrote:
> External email: Use caution opening links or attachments
>
>
> On Mon, 4 May 2020 17:03:54 -0600
> Alex Williamson wrote:
>
> > On Mon, 4 May 2020 15:08:08 -0700
> > Neo Jia wrote:
> >
>
On Mon, May 04, 2020 at 12:52:53PM -0600, Alex Williamson wrote:
> External email: Use caution opening links or attachments
>
>
> On Mon, 4 May 2020 18:09:16 +0200
> Cornelia Huck wrote:
>
> > On Fri, 01 May 2020 15:41:24 -0600
> > Alex Williamson wrote:
> >
> > > There is no PCI spec defined
On Thu, Mar 07, 2019 at 04:56:23PM -0700, Alex Williamson wrote:
> On Thu, 7 Mar 2019 00:44:54 -0800
> Neo Jia wrote:
>
> > On Fri, Feb 22, 2019 at 10:19:27AM +0800, Lu Baolu wrote:
> > > This adds the support to determine the isolation type
> > > of a mediated
On Fri, Feb 22, 2019 at 10:19:27AM +0800, Lu Baolu wrote:
> This adds the support to determine the isolation type
> of a mediated device group by checking whether it has
> an iommu device. If an iommu device exists, an iommu
> domain will be allocated and then attached to the iommu
> device. Otherw
On Thu, Nov 17, 2016 at 02:25:15PM -0700, Alex Williamson wrote:
> On Thu, 17 Nov 2016 02:16:12 +0530
> Kirti Wankhede wrote:
> >
> > Documentation/ABI/testing/sysfs-bus-vfio-mdev | 111 ++
> > Documentation/vfio-mediated-device.txt| 399 +++
> > MAINTAINERS
On Wed, Jul 06, 2016 at 10:22:59AM +0800, Xiao Guangrong wrote:
>
>
> On 07/05/2016 11:07 PM, Neo Jia wrote:
> >This is kept there in case the validate_map_request() is not provided by
> >vendor
> >driver then by default assume 1:1 mapping. So if validate_map_reque
On Wed, Jul 06, 2016 at 10:35:18AM +0800, Xiao Guangrong wrote:
>
>
> On 07/06/2016 10:18 AM, Neo Jia wrote:
> >On Wed, Jul 06, 2016 at 10:00:46AM +0800, Xiao Guangrong wrote:
> >>
> >>
> >>On 07/05/2016 08:18 PM, Paolo Bonzini wrote:
> >>>
&
On Wed, Jul 06, 2016 at 10:00:46AM +0800, Xiao Guangrong wrote:
>
>
> On 07/05/2016 08:18 PM, Paolo Bonzini wrote:
> >
> >
> >On 05/07/2016 07:41, Neo Jia wrote:
> >>On Thu, Jun 30, 2016 at 03:01:49PM +0200, Paolo Bonzini wrote:
> >>>The vGPU folks
On Tue, Jul 05, 2016 at 05:02:46PM +0800, Xiao Guangrong wrote:
>
> >
> >It is physically contiguous but it is done during the runtime, physically
> >contiguous doesn't mean
> >static partition at boot time. And only during runtime, the proper HW
> >resource will be requested therefore
> >the ri
On Tue, Jul 05, 2016 at 02:18:28PM +0200, Paolo Bonzini wrote:
>
>
> On 05/07/2016 07:41, Neo Jia wrote:
> > On Thu, Jun 30, 2016 at 03:01:49PM +0200, Paolo Bonzini wrote:
> >> The vGPU folks would like to trap the first access to a BAR by setting
> >> vm_ops o
On Tue, Jul 05, 2016 at 02:26:46PM +0800, Xiao Guangrong wrote:
>
>
> On 07/05/2016 01:16 PM, Neo Jia wrote:
> >On Tue, Jul 05, 2016 at 12:02:42PM +0800, Xiao Guangrong wrote:
> >>
> >>
> >>On 07/05/2016 09:35 AM, Neo Jia wrote:
> >>>On Tue,
On Thu, Jun 30, 2016 at 03:01:49PM +0200, Paolo Bonzini wrote:
> The vGPU folks would like to trap the first access to a BAR by setting
> vm_ops on the VMAs produced by mmap-ing a VFIO device. The fault handler
> then can use remap_pfn_range to place some non-reserved pages in the VMA.
>
> KVM la
On Tue, Jul 05, 2016 at 12:02:42PM +0800, Xiao Guangrong wrote:
>
>
> On 07/05/2016 09:35 AM, Neo Jia wrote:
> >On Tue, Jul 05, 2016 at 09:19:40AM +0800, Xiao Guangrong wrote:
> >>
> >>
> >>On 07/04/2016 11:33 PM, Neo Jia wrote:
> >>
> >
On Tue, Jul 05, 2016 at 09:19:40AM +0800, Xiao Guangrong wrote:
>
>
> On 07/04/2016 11:33 PM, Neo Jia wrote:
>
> >>>
> >>>Sorry, I think I misread the "allocation" as "mapping". We only delay the
> >>>cpu mapping, not the al
On Mon, Jul 04, 2016 at 06:16:46PM +0800, Xiao Guangrong wrote:
>
>
> On 07/04/2016 05:16 PM, Neo Jia wrote:
> >On Mon, Jul 04, 2016 at 04:45:05PM +0800, Xiao Guangrong wrote:
> >>
> >>
> >>On 07/04/2016 04:41 PM, Neo Jia wrote:
> >>>On Mon,
On Mon, Jul 04, 2016 at 04:45:05PM +0800, Xiao Guangrong wrote:
>
>
> On 07/04/2016 04:41 PM, Neo Jia wrote:
> >On Mon, Jul 04, 2016 at 04:19:20PM +0800, Xiao Guangrong wrote:
> >>
> >>
> >>On 07/04/2016 03:53 PM, Neo Jia wrote:
> >>>On Mon,
On Mon, Jul 04, 2016 at 04:19:20PM +0800, Xiao Guangrong wrote:
>
>
> On 07/04/2016 03:53 PM, Neo Jia wrote:
> >On Mon, Jul 04, 2016 at 03:37:35PM +0800, Xiao Guangrong wrote:
> >>
> >>
> >>On 07/04/2016 03:03 PM, Neo Jia wrote:
> >>>On Mon,
On Mon, Jul 04, 2016 at 03:37:35PM +0800, Xiao Guangrong wrote:
>
>
> On 07/04/2016 03:03 PM, Neo Jia wrote:
> >On Mon, Jul 04, 2016 at 02:39:22PM +0800, Xiao Guangrong wrote:
> >>
> >>
> >>On 06/30/2016 09:01 PM, Paolo Bonzini wrote:
> >>>T
On Mon, Jul 04, 2016 at 02:39:22PM +0800, Xiao Guangrong wrote:
>
>
> On 06/30/2016 09:01 PM, Paolo Bonzini wrote:
> >The vGPU folks would like to trap the first access to a BAR by setting
> >vm_ops on the VMAs produced by mmap-ing a VFIO device. The fault handler
> >then can use remap_pfn_range
On Thu, Jun 30, 2016 at 03:01:49PM +0200, Paolo Bonzini wrote:
> The vGPU folks would like to trap the first access to a BAR by setting
> vm_ops on the VMAs produced by mmap-ing a VFIO device. The fault handler
> then can use remap_pfn_range to place some non-reserved pages in the VMA.
Hi Paolo,
All,
These days, I am trying to debug the kernel (2.6.9) on x86_64 SMP. But
the Kprobes and UML cannot work probably for my case, due to the patch
file for x86_64 arch.
Is there anyone who is working on the same topic? Any hint and help
would be appreciated!
Thanks,
Neo
--
I would remembe
21 matches
Mail list logo
