On 04.12.19 16:33, Cornelia Huck wrote:
> On Wed, 4 Dec 2019 16:08:48 +0100
> David Hildenbrand wrote:
>
>> On 04.12.19 16:07, David Hildenbrand wrote:
>>> On 04.12.19 15:59, Cornelia Huck wrote:
On Tue, 3 Dec 2019 08:28:11 -0500
Janosch Frank wrote:
> Up to now we only h
On Wed, 4 Dec 2019 16:08:48 +0100
David Hildenbrand wrote:
> On 04.12.19 16:07, David Hildenbrand wrote:
> > On 04.12.19 15:59, Cornelia Huck wrote:
> >> On Tue, 3 Dec 2019 08:28:11 -0500
> >> Janosch Frank wrote:
> >>
> >>> Up to now we only had an ioctl to reset vcpu data QEMU couldn't re
On 04.12.19 16:07, David Hildenbrand wrote:
> On 04.12.19 15:59, Cornelia Huck wrote:
>> On Tue, 3 Dec 2019 08:28:11 -0500
>> Janosch Frank wrote:
>>
>>> Up to now we only had an ioctl to reset vcpu data QEMU couldn't reach
>>> for the initial reset, and that was also called for the clear
>>> res
On 04.12.19 15:59, Cornelia Huck wrote:
> On Tue, 3 Dec 2019 08:28:11 -0500
> Janosch Frank wrote:
>
>> Up to now we only had an ioctl to reset vcpu data QEMU couldn't reach
>> for the initial reset, and that was also called for the clear
>> reset. To be architecture compliant, we also need to c
On Tue, 3 Dec 2019 08:28:11 -0500
Janosch Frank wrote:
> Up to now we only had an ioctl to reset vcpu data QEMU couldn't reach
> for the initial reset, and that was also called for the clear
> reset. To be architecture compliant, we also need to clear local
> interrupts on a normal reset.
Do we
On Wed, 4 Dec 2019 10:00:45 +0100
Janosch Frank wrote:
> On 12/3/19 6:44 PM, Cornelia Huck wrote:
> > On Tue, 3 Dec 2019 08:28:11 -0500
> > Janosch Frank wrote:
> >
> >> Up to now we only had an ioctl to reset vcpu data QEMU couldn't reach
> >> for the initial reset, and that was also called
On 12/3/19 6:44 PM, Cornelia Huck wrote:
> On Tue, 3 Dec 2019 08:28:11 -0500
> Janosch Frank wrote:
>
>> Up to now we only had an ioctl to reset vcpu data QEMU couldn't reach
>> for the initial reset, and that was also called for the clear
>> reset. To be architecture compliant, we also need to
On Tue, 3 Dec 2019 08:28:11 -0500
Janosch Frank wrote:
> Up to now we only had an ioctl to reset vcpu data QEMU couldn't reach
> for the initial reset, and that was also called for the clear
> reset. To be architecture compliant, we also need to clear local
> interrupts on a normal reset.
>
> B
Up to now we only had an ioctl to reset vcpu data QEMU couldn't reach
for the initial reset, and that was also called for the clear
reset. To be architecture compliant, we also need to clear local
interrupts on a normal reset.
Because of this and the upcoming protvirt support we need to add
ioctls
