RE: RFC: vfio interface for platform devices (v2)

2013-07-16 Thread Yoder Stuart-B08248
> -Original Message- > From: Mario Smarduch [mailto:mario.smard...@huawei.com] > Sent: Thursday, July 04, 2013 9:45 AM > To: Yoder Stuart-B08248 > Cc: Alex Williamson; Alexander Graf; Wood Scott-B07421; k...@vger.kernel.org > list; Bhushan Bharat-R65777; > kvm-ppc@vger.kernel.org; virtua

RE: RFC: vfio interface for platform devices

2013-07-16 Thread Yoder Stuart-B08248
> -Original Message- > From: Wood Scott-B07421 > Sent: Wednesday, July 03, 2013 5:32 PM > To: Yoder Stuart-B08248 > Cc: Alex Williamson; Alexander Graf; Wood Scott-B07421; Bhushan > Bharat-R65777; Sethi Varun-B16395; > virtualizat...@lists.linux-foundation.org; Antonios Motakis; > k...@v

RE: RFC: vfio interface for platform devices (v2)

2013-07-16 Thread Yoder Stuart-B08248
(sorry for the delayed response, but I've been on PTO) > > 1. VFIO_GROUP_GET_DEVICE_FD > > > > User space knows by out-of-band means which device it is accessing > > and will call VFIO_GROUP_GET_DEVICE_FD passing a specific sysfs path > > to get the device information: > > > > fd = ioctl(

Re: RFC: vfio interface for platform devices

2013-07-16 Thread Scott Wood
On 07/16/2013 04:51:12 PM, Yoder Stuart-B08248 wrote: > > 3. VFIO_DEVICE_GET_REGION_INFO > > > >No changes needed, except perhaps adding a new flag. Freescale > > has some > >devices with regions that must be mapped cacheable. > > While I don't object to making the information available

RE: RFC: vfio interface for platform devices

2013-07-16 Thread Yoder Stuart-B08248
> -Original Message- > From: Wood Scott-B07421 > Sent: Tuesday, July 16, 2013 5:01 PM > To: Yoder Stuart-B08248 > Cc: Wood Scott-B07421; Alex Williamson; Alexander Graf; Bhushan > Bharat-R65777; Sethi Varun-B16395; > virtualizat...@lists.linux-foundation.org; Antonios Motakis; > k...@vg

Re: RFC: vfio interface for platform devices

2013-07-16 Thread Scott Wood
On 07/16/2013 05:41:04 PM, Yoder Stuart-B08248 wrote: > -Original Message- > From: Wood Scott-B07421 > Sent: Tuesday, July 16, 2013 5:01 PM > To: Yoder Stuart-B08248 > Cc: Wood Scott-B07421; Alex Williamson; Alexander Graf; Bhushan Bharat-R65777; Sethi Varun-B16395; > virtualizat...@l

Re: [PATCH 3/5] booke: define reset and shutdown hcalls

2013-07-16 Thread Scott Wood
On 07/16/2013 01:35:55 AM, Gleb Natapov wrote: On Mon, Jul 15, 2013 at 01:17:33PM -0500, Scott Wood wrote: > On 07/15/2013 06:30:20 AM, Gleb Natapov wrote: > >There is no much sense to share hypercalls between architectures. > >There > >is zero probability x86 will implement those for instance >

Re: [PATCH 5/5] powerpc: using reset hcall when kvm,has-reset

2013-07-16 Thread Alexander Graf
On 16.07.2013, at 00:23, Scott Wood wrote: > On 07/15/2013 03:55:08 PM, Alexander Graf wrote: >> On 15.07.2013, at 22:52, Scott Wood wrote: >> > On 07/15/2013 03:28:46 PM, Alexander Graf wrote: >> >> On 15.07.2013, at 20:21, Scott Wood wrote: >> >> > On 07/15/2013 10:16:41 AM, Bhushan Bharat-R657

Re: [PATCH 5/5] powerpc: using reset hcall when kvm,has-reset

2013-07-16 Thread Scott Wood
On 07/16/2013 06:21:51 PM, Alexander Graf wrote: On 16.07.2013, at 00:23, Scott Wood wrote: > Still, I'm not sure what sort of error you're thinking of. If the guest didn't support the hcall mechanism we would have returned from the function by that point. In fact, seeing kvm,has-reset on

Re: [PATCH 5/5] powerpc: using reset hcall when kvm,has-reset

2013-07-16 Thread Scott Wood
On 07/16/2013 06:26:40 PM, Scott Wood wrote: On 07/16/2013 06:21:51 PM, Alexander Graf wrote: On 16.07.2013, at 00:23, Scott Wood wrote: > Still, I'm not sure what sort of error you're thinking of. If the guest didn't support the hcall mechanism we would have returned from the function by