On Thu, Aug 09, 2018 at 05:37:58PM +0800, Peter Xu wrote:
> On Thu, Aug 09, 2018 at 12:23:43PM +0300, Michael S. Tsirkin wrote:
> > On Wed, Aug 08, 2018 at 11:45:43AM +0800, Peter Xu wrote:
> > > On Wed, Aug 08, 2018 at 12:58:32AM +0300, Michael S. Tsirkin wrote:
> > > > At least with VTD, it seems
On Thu, Aug 09, 2018 at 12:23:43PM +0300, Michael S. Tsirkin wrote:
> On Wed, Aug 08, 2018 at 11:45:43AM +0800, Peter Xu wrote:
> > On Wed, Aug 08, 2018 at 12:58:32AM +0300, Michael S. Tsirkin wrote:
> > > At least with VTD, it seems entirely possible to change e.g. a PMD
> > > atomically to point
On Wed, Aug 08, 2018 at 11:45:43AM +0800, Peter Xu wrote:
> On Wed, Aug 08, 2018 at 12:58:32AM +0300, Michael S. Tsirkin wrote:
> > At least with VTD, it seems entirely possible to change e.g. a PMD
> > atomically to point to a different set of PTEs, then flush.
> > That will allow removing memory
On Wed, Aug 08, 2018 at 04:23:04PM -0600, Alex Williamson wrote:
> So again, I think this comes down to new iommu driver support and new
> iommu apis and new vfio apis to enable some sort of atomic update
> interface,
Oh absolutely. My point is some guest OS can start using atomic updates
at any t
On Wed, 8 Aug 2018 11:45:43 +0800
Peter Xu wrote:
> On Wed, Aug 08, 2018 at 12:58:32AM +0300, Michael S. Tsirkin wrote:
> > At least with VTD, it seems entirely possible to change e.g. a PMD
> > atomically to point to a different set of PTEs, then flush.
> > That will allow removing memory at hig
On Wed, Aug 08, 2018 at 12:58:32AM +0300, Michael S. Tsirkin wrote:
> At least with VTD, it seems entirely possible to change e.g. a PMD
> atomically to point to a different set of PTEs, then flush.
> That will allow removing memory at high granularity for
> an arbitrary device without mdev or PASI
On Tue, Aug 07, 2018 at 04:40:33PM -0600, Alex Williamson wrote:
> Maybe some of these will evolve over time, SVA efforts are working on
> some of these interfaces, but apparently device assignment users have
> been getting along just fine without ballooning for many years.
But not any more I thin
On Wed, 8 Aug 2018 00:58:32 +0300
"Michael S. Tsirkin" wrote:
> On Tue, Aug 07, 2018 at 01:53:03PM -0600, Alex Williamson wrote:
> > On Tue, 7 Aug 2018 22:44:56 +0300
> > "Michael S. Tsirkin" wrote:
> >
> > > On Tue, Aug 07, 2018 at 01:31:21PM -0600, Alex Williamson wrote:
> > > > v3:
> > >
On Tue, Aug 07, 2018 at 01:53:03PM -0600, Alex Williamson wrote:
> On Tue, 7 Aug 2018 22:44:56 +0300
> "Michael S. Tsirkin" wrote:
>
> > On Tue, Aug 07, 2018 at 01:31:21PM -0600, Alex Williamson wrote:
> > > v3:
> > > - Drop "nested" term in commit log (David)
> > > - Adopt suggested wording in
On Tue, 7 Aug 2018 22:44:56 +0300
"Michael S. Tsirkin" wrote:
> On Tue, Aug 07, 2018 at 01:31:21PM -0600, Alex Williamson wrote:
> > v3:
> > - Drop "nested" term in commit log (David)
> > - Adopt suggested wording in ccw code (Cornelia)
> > - Explain balloon inhibitor usage in vfio common (Pet
On Tue, Aug 07, 2018 at 01:31:21PM -0600, Alex Williamson wrote:
> v3:
> - Drop "nested" term in commit log (David)
> - Adopt suggested wording in ccw code (Cornelia)
> - Explain balloon inhibitor usage in vfio common (Peter)
> - Fix to call inhibitor prior to re-using existing containers
>
v3:
- Drop "nested" term in commit log (David)
- Adopt suggested wording in ccw code (Cornelia)
- Explain balloon inhibitor usage in vfio common (Peter)
- Fix to call inhibitor prior to re-using existing containers
to avoid gap that pinning may have occurred in set container
ioctl (self)
12 matches
Mail list logo
