Re: [Qemu-devel] [V6 0/4] AMD IOMMU

2016-03-02 Thread Michael S. Tsirkin
On Thu, Mar 03, 2016 at 12:17:27AM +0300, David Kiarie wrote: > > > On 01/03/16 16:48, Jan Kiszka wrote: > >On 2016-03-01 14:07, Michael S. Tsirkin wrote: > >>On Sun, Feb 21, 2016 at 09:10:56PM +0300, David Kiarie wrote: > >>>Hello there, > >>> > >>>Repost, AMD IOMMU patches version 6. > >>> > >>

Re: [Qemu-devel] [V6 0/4] AMD IOMMU

2016-03-02 Thread David Kiarie
On 01/03/16 16:48, Jan Kiszka wrote: On 2016-03-01 14:07, Michael S. Tsirkin wrote: On Sun, Feb 21, 2016 at 09:10:56PM +0300, David Kiarie wrote: Hello there, Repost, AMD IOMMU patches version 6. Changes since version 5 -Fixed macro formating issues -changed occurences of IO MMU to IOMM

Re: [Qemu-devel] [V6 0/4] AMD IOMMU

2016-03-01 Thread Michael S. Tsirkin
On Tue, Mar 01, 2016 at 10:23:55PM +0100, Jan Kiszka wrote: > On 2016-03-01 21:39, Michael S. Tsirkin wrote: > > On Tue, Mar 01, 2016 at 09:17:58PM +0100, Jan Kiszka wrote: > >> On 2016-03-01 21:11, Michael S. Tsirkin wrote: > >>> > >>> What this seems to call for is a new kind of protection > >>>

Re: [Qemu-devel] [V6 0/4] AMD IOMMU

2016-03-01 Thread Jan Kiszka
On 2016-03-01 21:39, Michael S. Tsirkin wrote: > On Tue, Mar 01, 2016 at 09:17:58PM +0100, Jan Kiszka wrote: >> On 2016-03-01 21:11, Michael S. Tsirkin wrote: >>> >>> What this seems to call for is a new kind of protection >>> where yes PTE is write protected, but instead of >>> making PTE writeabl

Re: [Qemu-devel] [V6 0/4] AMD IOMMU

2016-03-01 Thread Michael S. Tsirkin
On Tue, Mar 01, 2016 at 09:17:58PM +0100, Jan Kiszka wrote: > On 2016-03-01 21:11, Michael S. Tsirkin wrote: > > On Tue, Mar 01, 2016 at 03:00:09PM +0100, Jan Kiszka wrote: > >> On 2016-03-01 14:48, Jan Kiszka wrote: > >>> There is likely no way around write-protecting the IOMMU page tables (in > >

Re: [Qemu-devel] [V6 0/4] AMD IOMMU

2016-03-01 Thread Jan Kiszka
On 2016-03-01 21:11, Michael S. Tsirkin wrote: > On Tue, Mar 01, 2016 at 03:00:09PM +0100, Jan Kiszka wrote: >> On 2016-03-01 14:48, Jan Kiszka wrote: >>> There is likely no way around write-protecting the IOMMU page tables (in >>> KVM mode) once we evaluated and cached them somewhere. >> >> I mean

Re: [Qemu-devel] [V6 0/4] AMD IOMMU

2016-03-01 Thread Michael S. Tsirkin
On Tue, Mar 01, 2016 at 03:00:09PM +0100, Jan Kiszka wrote: > On 2016-03-01 14:48, Jan Kiszka wrote: > > There is likely no way around write-protecting the IOMMU page tables (in > > KVM mode) once we evaluated and cached them somewhere. > > I mean, when in kvm mode AND having something that caches

Re: [Qemu-devel] [V6 0/4] AMD IOMMU

2016-03-01 Thread Jan Kiszka
On 2016-03-01 15:30, Michael S. Tsirkin wrote: > On Tue, Mar 01, 2016 at 03:18:05PM +0100, Jan Kiszka wrote: >> On 2016-03-01 15:12, Jan Kiszka wrote: >>> On 2016-03-01 14:55, Michael S. Tsirkin wrote: On Tue, Mar 01, 2016 at 02:48:19PM +0100, Jan Kiszka wrote: > On 2016-03-01 14:07, Micha

Re: [Qemu-devel] [V6 0/4] AMD IOMMU

2016-03-01 Thread Michael S. Tsirkin
On Tue, Mar 01, 2016 at 03:18:05PM +0100, Jan Kiszka wrote: > On 2016-03-01 15:12, Jan Kiszka wrote: > > On 2016-03-01 14:55, Michael S. Tsirkin wrote: > >> On Tue, Mar 01, 2016 at 02:48:19PM +0100, Jan Kiszka wrote: > >>> On 2016-03-01 14:07, Michael S. Tsirkin wrote: > On Sun, Feb 21, 2016 a

Re: [Qemu-devel] [V6 0/4] AMD IOMMU

2016-03-01 Thread Michael S. Tsirkin
On Tue, Mar 01, 2016 at 03:12:40PM +0100, Jan Kiszka wrote: > On 2016-03-01 14:55, Michael S. Tsirkin wrote: > > On Tue, Mar 01, 2016 at 02:48:19PM +0100, Jan Kiszka wrote: > >> On 2016-03-01 14:07, Michael S. Tsirkin wrote: > >>> On Sun, Feb 21, 2016 at 09:10:56PM +0300, David Kiarie wrote: >

Re: [Qemu-devel] [V6 0/4] AMD IOMMU

2016-03-01 Thread Jan Kiszka
On 2016-03-01 15:12, Jan Kiszka wrote: > On 2016-03-01 14:55, Michael S. Tsirkin wrote: >> On Tue, Mar 01, 2016 at 02:48:19PM +0100, Jan Kiszka wrote: >>> On 2016-03-01 14:07, Michael S. Tsirkin wrote: On Sun, Feb 21, 2016 at 09:10:56PM +0300, David Kiarie wrote: > Hello there, > >

Re: [Qemu-devel] [V6 0/4] AMD IOMMU

2016-03-01 Thread Jan Kiszka
On 2016-03-01 14:55, Michael S. Tsirkin wrote: > On Tue, Mar 01, 2016 at 02:48:19PM +0100, Jan Kiszka wrote: >> On 2016-03-01 14:07, Michael S. Tsirkin wrote: >>> On Sun, Feb 21, 2016 at 09:10:56PM +0300, David Kiarie wrote: Hello there, Repost, AMD IOMMU patches version 6.

Re: [Qemu-devel] [V6 0/4] AMD IOMMU

2016-03-01 Thread Jan Kiszka
On 2016-03-01 14:48, Jan Kiszka wrote: > There is likely no way around write-protecting the IOMMU page tables (in > KVM mode) once we evaluated and cached them somewhere. I mean, when in kvm mode AND having something that caches enabled, of course. Besides vfio, we also still have the question ho

Re: [Qemu-devel] [V6 0/4] AMD IOMMU

2016-03-01 Thread Michael S. Tsirkin
On Tue, Mar 01, 2016 at 02:48:19PM +0100, Jan Kiszka wrote: > On 2016-03-01 14:07, Michael S. Tsirkin wrote: > > On Sun, Feb 21, 2016 at 09:10:56PM +0300, David Kiarie wrote: > >> Hello there, > >> > >> Repost, AMD IOMMU patches version 6. > >> > >> Changes since version 5 > >> -Fixed macro format

Re: [Qemu-devel] [V6 0/4] AMD IOMMU

2016-03-01 Thread Jan Kiszka
On 2016-03-01 14:07, Michael S. Tsirkin wrote: > On Sun, Feb 21, 2016 at 09:10:56PM +0300, David Kiarie wrote: >> Hello there, >> >> Repost, AMD IOMMU patches version 6. >> >> Changes since version 5 >> -Fixed macro formating issues >> -changed occurences of IO MMU to IOMMU for consistency >> -F

Re: [Qemu-devel] [V6 0/4] AMD IOMMU

2016-03-01 Thread Michael S. Tsirkin
On Sun, Feb 21, 2016 at 09:10:56PM +0300, David Kiarie wrote: > Hello there, > > Repost, AMD IOMMU patches version 6. > > Changes since version 5 > -Fixed macro formating issues > -changed occurences of IO MMU to IOMMU for consistency > -Fixed capability registers duplication > -Rebased to cu

Re: [Qemu-devel] [V6 0/4] AMD IOMMU

2016-02-22 Thread Jan Kiszka
On 2016-02-22 12:05, David Kiarie wrote: > On Mon, Feb 22, 2016 at 10:29 AM, Jan Kiszka wrote: >> On 2016-02-22 06:57, David Kiarie wrote: >>> On Sun, Feb 21, 2016 at 11:20 PM, Jan Kiszka wrote: On 2016-02-21 19:10, David Kiarie wrote: > Hello there, > > Repost, AMD IOMMU patches

Re: [Qemu-devel] [V6 0/4] AMD IOMMU

2016-02-22 Thread David Kiarie
On Mon, Feb 22, 2016 at 10:29 AM, Jan Kiszka wrote: > On 2016-02-22 06:57, David Kiarie wrote: >> On Sun, Feb 21, 2016 at 11:20 PM, Jan Kiszka wrote: >>> On 2016-02-21 19:10, David Kiarie wrote: Hello there, Repost, AMD IOMMU patches version 6. Changes since version 5 >>>

Re: [Qemu-devel] [V6 0/4] AMD IOMMU

2016-02-21 Thread Jan Kiszka
On 2016-02-22 06:57, David Kiarie wrote: > On Sun, Feb 21, 2016 at 11:20 PM, Jan Kiszka wrote: >> On 2016-02-21 19:10, David Kiarie wrote: >>> Hello there, >>> >>> Repost, AMD IOMMU patches version 6. >>> >>> Changes since version 5 >>> -Fixed macro formating issues >>> -changed occurences of IO

Re: [Qemu-devel] [V6 0/4] AMD IOMMU

2016-02-21 Thread David Kiarie
On Sun, Feb 21, 2016 at 11:20 PM, Jan Kiszka wrote: > On 2016-02-21 19:10, David Kiarie wrote: >> Hello there, >> >> Repost, AMD IOMMU patches version 6. >> >> Changes since version 5 >> -Fixed macro formating issues >> -changed occurences of IO MMU to IOMMU for consistency >> -Fixed capability

Re: [Qemu-devel] [V6 0/4] AMD IOMMU

2016-02-21 Thread Jan Kiszka
On 2016-02-21 19:10, David Kiarie wrote: > Hello there, > > Repost, AMD IOMMU patches version 6. > > Changes since version 5 > -Fixed macro formating issues > -changed occurences of IO MMU to IOMMU for consistency > -Fixed capability registers duplication > -Rebased to current master I suspe

[Qemu-devel] [V6 0/4] AMD IOMMU

2016-02-21 Thread David Kiarie
Hello there, Repost, AMD IOMMU patches version 6. Changes since version 5 -Fixed macro formating issues -changed occurences of IO MMU to IOMMU for consistency -Fixed capability registers duplication -Rebased to current master David Kiarie (4): hw/i386: Introduce AMD IOMMU hw/core: Add AM