Date: Tue, 04 Apr 2017 19:07:08 -0600 From: Jaguar DaRocha <jaguar.darocha@yandex.com> To: Eric McCorkle <eric@metricspace.net> Cc: "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org>, Dimitry Andric <dim@freebsd.org> Subject: Re:Source of QEMU woes: CPUTYPE Message-ID: <4098801491354428@web45g.yandex.ru> In-Reply-To: <25c71912-7eec-a174-9d9f-50280c3435e8@metricspace.net> References: <ee20545b-9937-bbfd-ea33-ca7d4d3deb46@metricspace.net> <A5077163-17D6-4416-B52C-325027E5BBEB@FreeBSD.org> <25c71912-7eec-a174-9d9f-50280c3435e8@metricspace.net>
next in thread | previous in thread | raw e-mail | index | archive | help
There is a mailing list for qemu. Have you tried there? > On 04/04/2017 14:31, Dimitry Andric wrote: > >> On 4 Apr 2017, at 14:34, Eric McCorkle <eric@metricspace.net> wrote: >> >> Out of interest, what does "llvm-tblgen -version | grep 'Host CPU'" >> show? (This is a simple way to see what LLVM auto-detects.) > > broadwell > >>> I'm posting this here, as it's somewhat non-obvious, and probably ought >>> to be documented somewhere. >> >> I usually find it clearer to specify the exact CPU type myself, for >> example CPUTYPE?=core-avx2 (which is an alias for "haswell"). You can >> also specify a lower CPUTYPE to build the world that you are going to >> run inside QEMU. > > I have a standard config for my laptops, so that's why it has > CPUTYPE?=native
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4098801491354428>