On Tue, Dec 13, 2016 at 06:17:47AM -0700, Alex Williamson wrote:
> On Tue, 13 Dec 2016 14:12:12 +0800
> Peter Xu wrote:
>
> > On Mon, Dec 12, 2016 at 10:48:28PM -0700, Alex Williamson wrote:
> > > On Tue, 13 Dec 2016 13:24:29 +0800
> > > Peter Xu wrote:
> >
On Tue, 13 Dec 2016 14:12:12 +0800
Peter Xu wrote:
> On Mon, Dec 12, 2016 at 10:48:28PM -0700, Alex Williamson wrote:
> > On Tue, 13 Dec 2016 13:24:29 +0800
> > Peter Xu wrote:
> >
> > > On Mon, Dec 12, 2016 at 08:51:50PM -0700, Alex Williamson wrote:
>
On Mon, Dec 12, 2016 at 10:48:28PM -0700, Alex Williamson wrote:
> On Tue, 13 Dec 2016 13:24:29 +0800
> Peter Xu wrote:
>
> > On Mon, Dec 12, 2016 at 08:51:50PM -0700, Alex Williamson wrote:
> >
> > [...]
> >
> > > > > I'm not sure how the vIOMMU supporting 39 bits or 48
On Tue, 13 Dec 2016 13:24:29 +0800
Peter Xu wrote:
> On Mon, Dec 12, 2016 at 08:51:50PM -0700, Alex Williamson wrote:
>
> [...]
>
> > > > I'm not sure how the vIOMMU supporting 39 bits or 48 bits is directly
> > > > relevant to vfio, we're not sharing page tables. There is
On Tue, 13 Dec 2016 05:00:07 +
"Tian, Kevin" wrote:
> > From: Alex Williamson
> > Sent: Tuesday, December 13, 2016 3:36 AM
> >
> > On Mon, 12 Dec 2016 10:01:15 +0800
> > Peter Xu wrote:
> >
> > > On Sun, Dec 11, 2016 at 05:13:45AM +0200, Michael
On Mon, Dec 12, 2016 at 08:51:50PM -0700, Alex Williamson wrote:
[...]
> > > I'm not sure how the vIOMMU supporting 39 bits or 48 bits is directly
> > > relevant to vfio, we're not sharing page tables. There is already a
> > > case today, without vIOMMU that you can make a guest which has more
> From: Alex Williamson
> Sent: Tuesday, December 13, 2016 3:36 AM
>
> On Mon, 12 Dec 2016 10:01:15 +0800
> Peter Xu wrote:
>
> > On Sun, Dec 11, 2016 at 05:13:45AM +0200, Michael S. Tsirkin wrote:
> > > On Wed, Dec 07, 2016 at 01:52:45PM +0800, Peter Xu wrote:
> > > >
On Tue, 13 Dec 2016 11:33:41 +0800
Peter Xu wrote:
> On Mon, Dec 12, 2016 at 12:35:44PM -0700, Alex Williamson wrote:
> > On Mon, 12 Dec 2016 10:01:15 +0800
> > Peter Xu wrote:
> >
> > > On Sun, Dec 11, 2016 at 05:13:45AM +0200, Michael S. Tsirkin wrote:
On Mon, Dec 12, 2016 at 12:35:44PM -0700, Alex Williamson wrote:
> On Mon, 12 Dec 2016 10:01:15 +0800
> Peter Xu wrote:
>
> > On Sun, Dec 11, 2016 at 05:13:45AM +0200, Michael S. Tsirkin wrote:
> > > On Wed, Dec 07, 2016 at 01:52:45PM +0800, Peter Xu wrote:
> > > >
On Mon, 12 Dec 2016 10:01:15 +0800
Peter Xu wrote:
> On Sun, Dec 11, 2016 at 05:13:45AM +0200, Michael S. Tsirkin wrote:
> > On Wed, Dec 07, 2016 at 01:52:45PM +0800, Peter Xu wrote:
> > > Previously vt-d codes only supports 39 bits iova address width. It won't
> > > be hard
On Sun, Dec 11, 2016 at 05:13:45AM +0200, Michael S. Tsirkin wrote:
> On Wed, Dec 07, 2016 at 01:52:45PM +0800, Peter Xu wrote:
> > Previously vt-d codes only supports 39 bits iova address width. It won't
> > be hard to extend it to 48 bits.
> >
> > After enabling this, we should be able to map
On Wed, Dec 07, 2016 at 01:52:45PM +0800, Peter Xu wrote:
> Previously vt-d codes only supports 39 bits iova address width. It won't
> be hard to extend it to 48 bits.
>
> After enabling this, we should be able to map larger iova addresses.
>
> To check whether 48 bits aw is enabled, we can grep
On 2016年12月07日 13:52, Peter Xu wrote:
Previously vt-d codes only supports 39 bits iova address width. It won't
be hard to extend it to 48 bits.
After enabling this, we should be able to map larger iova addresses.
To check whether 48 bits aw is enabled, we can grep in the guest dmesg
with
Previously vt-d codes only supports 39 bits iova address width. It won't
be hard to extend it to 48 bits.
After enabling this, we should be able to map larger iova addresses.
To check whether 48 bits aw is enabled, we can grep in the guest dmesg
with line: "dmar: Host address width 48"
14 matches
Mail list logo