On Mon, May 14, 2018 at 07:37:49PM +0100, Peter Maydell wrote:
> On 14 May 2018 at 19:29, Michael S. Tsirkin wrote:
> > On Mon, May 14, 2018 at 04:10:42PM +0100, Peter Maydell wrote:
> >> On 14 May 2018 at 14:07, Michael S. Tsirkin wrote:
> >> > It turns out that we have unistd.h and kvm headers
On Mon, May 14, 2018 at 07:37:49PM +0100, Peter Maydell wrote:
> On 14 May 2018 at 19:29, Michael S. Tsirkin wrote:
> > On Mon, May 14, 2018 at 04:10:42PM +0100, Peter Maydell wrote:
> >> On 14 May 2018 at 14:07, Michael S. Tsirkin wrote:
> >> > It turns out that we have unistd.h and kvm headers
On 14 May 2018 at 19:29, Michael S. Tsirkin wrote:
> On Mon, May 14, 2018 at 04:10:42PM +0100, Peter Maydell wrote:
>> On 14 May 2018 at 14:07, Michael S. Tsirkin wrote:
>> > It turns out that we have unistd.h and kvm headers for some
>> > architectures but not others. We are thus unable to use
On Mon, May 14, 2018 at 04:10:42PM +0100, Peter Maydell wrote:
> On 14 May 2018 at 14:07, Michael S. Tsirkin wrote:
> > It turns out that we have unistd.h and kvm headers for some
> > architectures but not others. We are thus unable to use e.g. usefaultfd
> > on these systems unless system header
On 14 May 2018 at 14:07, Michael S. Tsirkin wrote:
> It turns out that we have unistd.h and kvm headers for some
> architectures but not others. We are thus unable to use e.g. usefaultfd
> on these systems unless system headers have been updated.
>
> Fix up update-linux-headers.sh to make sure we
It turns out that we have unistd.h and kvm headers for some
architectures but not others. We are thus unable to use e.g. usefaultfd
on these systems unless system headers have been updated.
Fix up update-linux-headers.sh to make sure we auto-updates
all architectures which have linux-headers/
(un