On Thu, 23 Nov 2017 19:01:46 +0100
Christian Borntraeger wrote:
> On 11/23/2017 06:44 PM, Auger Eric wrote:
> > Hi Cornelia, Peter,
> >
> > On 23/11/17 18:14, Cornelia Huck wrote:
> >> On Thu, 23 Nov 2017 17:01:32 +
> >> Peter Maydell wrote:
> >>
> >>> On 23 November 2017 at 16:05, Auge
Hi,
On 23/11/17 19:01, Christian Borntraeger wrote:
>
>
> On 11/23/2017 06:44 PM, Auger Eric wrote:
>> Hi Cornelia, Peter,
>>
>> On 23/11/17 18:14, Cornelia Huck wrote:
>>> On Thu, 23 Nov 2017 17:01:32 +
>>> Peter Maydell wrote:
>>>
On 23 November 2017 at 16:05, Auger Eric wrote:
On 11/23/2017 06:44 PM, Auger Eric wrote:
> Hi Cornelia, Peter,
>
> On 23/11/17 18:14, Cornelia Huck wrote:
>> On Thu, 23 Nov 2017 17:01:32 +
>> Peter Maydell wrote:
>>
>>> On 23 November 2017 at 16:05, Auger Eric wrote:
When using update-linux-headers.sh I get suspicious errors at th
Hi Cornelia, Peter,
On 23/11/17 18:14, Cornelia Huck wrote:
> On Thu, 23 Nov 2017 17:01:32 +
> Peter Maydell wrote:
>
>> On 23 November 2017 at 16:05, Auger Eric wrote:
>>> When using update-linux-headers.sh I get suspicious errors at the end:
>>> grep: /tmp/tmp.A5NjLtHOij/include/asm/kvm_v
On Thu, 23 Nov 2017 17:01:32 +
Peter Maydell wrote:
> On 23 November 2017 at 16:05, Auger Eric wrote:
> > When using update-linux-headers.sh I get suspicious errors at the end:
> > grep: /tmp/tmp.A5NjLtHOij/include/asm/kvm_virtio.h: No such file or
> > directory
> > sed: can't read /tmp/tmp.
On 23 November 2017 at 16:05, Auger Eric wrote:
> When using update-linux-headers.sh I get suspicious errors at the end:
> grep: /tmp/tmp.A5NjLtHOij/include/asm/kvm_virtio.h: No such file or
> directory
> sed: can't read /tmp/tmp.A5NjLtHOij/include/asm/kvm_virtio.h: No such
> file or directory
>
>
Hi Peter,
On 23/11/17 16:19, Peter Maydell wrote:
> On 23 November 2017 at 14:56, Eric Auger wrote:
>> At the moment the ITS is not properly reset. On System reset or
>> reboot, previous ITS register values and caches are left
>> unchanged. Some of the registers might point to some guest RAM
>> t
On 23 November 2017 at 14:56, Eric Auger wrote:
> At the moment the ITS is not properly reset. On System reset or
> reboot, previous ITS register values and caches are left
> unchanged. Some of the registers might point to some guest RAM
> tables which are not valid anymore. This leads to state
>
At the moment the ITS is not properly reset. On System reset or
reboot, previous ITS register values and caches are left
unchanged. Some of the registers might point to some guest RAM
tables which are not valid anymore. This leads to state
inconsistencies that are detected by the kernel save/restor
