On Jul 18, 2012, at 9:00 AM, Michael S. Tsirkin wrote:
> On Wed, Jul 18, 2012 at 11:53:38AM -0400, Christoph Hellwig wrote:
>> On Wed, Jul 18, 2012 at 08:42:21AM -0500, Anthony Liguori wrote:
>>>
>>> If you add support for a new command, you need to provide userspace
>>> a way to disable this com
On Jul 18, 2012, at 10:17 AM, Michael S. Tsirkin wrote:
>> You do have to pay very close attention to some things however. Don't change
>> the device identity in any way - even version information, otherwise a
>> Windows initiator will blue-screen. I made that mistake myself, so I
>> remember
On Jul 25, 2014, at 7:06 AM, Paolo Bonzini wrote:
> Il 25/07/2014 15:27, Jeff Kirsher ha scritto:
>> From: Mark Rustad
>>
>> Resolve shadow warnings that appear in W=2 builds. In this case,
>> a macro declared an inner local variable with the same name as an
>> outer one. This can be a serious
On Jul 31, 2014, at 4:50 AM, Paolo Bonzini wrote:
> Il 30/07/2014 23:18, Mark D Rustad ha scritto:
>> Resolve some missing-initializers warnings that appear in W=2
>> builds. They are resolved by adding the name as a parameter to
>> the macros and having the macro generate all four fields of the
Alex,
> On Sep 11, 2015, at 11:16 AM, Alex Williamson
> wrote:
>
> RFC - Is this something we should do?
Superficially this looks pretty good. I need to think harder to be sure of the
details.
> Should we consider providing
> similar emulation through PCI sysfs to allow lspci to also make us
> On Sep 11, 2015, at 6:11 PM, Rustad, Mark D wrote:
>
> Superficially this looks pretty good. I need to think harder to be sure of
> the details.
This is the first time I've looked at all at any of the vfio code, but this is
still looking good to me. Thanks for taking thi
