On Fri, Oct 19, 2012 at 4:27 PM, Christoffer Dall
wrote:
> On Fri, Oct 19, 2012 at 4:24 PM, Peter Maydell
> wrote:
>> On 19 October 2012 19:46, Christoffer Dall
>> wrote:
>>> On Wed, Oct 17, 2012 at 4:29 PM, Peter Maydell
>>> wrote:
This doesn't say whether userspace is allowed to make t
On Fri, Oct 19, 2012 at 4:24 PM, Peter Maydell wrote:
> On 19 October 2012 19:46, Christoffer Dall
> wrote:
>> On Wed, Oct 17, 2012 at 4:29 PM, Peter Maydell
>> wrote:
>>> This doesn't say whether userspace is allowed to make this ioctl
>>> multiple times for the same device. This could be any
On 19 October 2012 19:46, Christoffer Dall
wrote:
> On Wed, Oct 17, 2012 at 4:29 PM, Peter Maydell
> wrote:
>> This doesn't say whether userspace is allowed to make this ioctl
>> multiple times for the same device. This could be any of:
>> * undefined behaviour
>> * second call fails with some
On Wed, Oct 17, 2012 at 4:29 PM, Peter Maydell wrote:
> On 14 October 2012 01:04, Christoffer Dall
> wrote:
>> On ARM (and possibly other architectures) some bits are specific to the
>> model being emulated for the guest and user space needs a way to tell
>> the kernel about those bits. An examp
On 14 October 2012 01:04, Christoffer Dall
wrote:
> On ARM (and possibly other architectures) some bits are specific to the
> model being emulated for the guest and user space needs a way to tell
> the kernel about those bits. An example is mmio device base addresses,
> where KVM must know the ba
On ARM (and possibly other architectures) some bits are specific to the
model being emulated for the guest and user space needs a way to tell
the kernel about those bits. An example is mmio device base addresses,
where KVM must know the base address for a given device to properly
emulate mmio acce
