From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:56141) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RhkDX-0008Ar-Ur for qemu-devel@nongnu.org; Mon, 02 Jan 2012 10:54:32 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RhkDW-0001cI-Tt for qemu-devel@nongnu.org; Mon, 02 Jan 2012 10:54:31 -0500 Received: from mail-qy0-f173.google.com ([209.85.216.173]:45471) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RhkDW-0001cC-Rh for qemu-devel@nongnu.org; Mon, 02 Jan 2012 10:54:30 -0500 Received: by qcsd15 with SMTP id d15so9996550qcs.4 for ; Mon, 02 Jan 2012 07:54:29 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <4F01B542.8000800@suse.de> References: <87ehvis3uj.fsf@trasno.mitica> <4F01B542.8000800@suse.de> Date: Mon, 2 Jan 2012 15:54:29 +0000 Message-ID: From: Peter Maydell Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] KVM call agenda for Tuesday 3 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: =?UTF-8?Q?Andreas_F=C3=A4rber?= Cc: Chris Wright , Developers qemu-devel , KVM devel mailing list , quintela@redhat.com On 2 January 2012 13:46, Andreas F=C3=A4rber wrote: > * when can we expect to be able to model SoCs rather than CPUs? Will > this affect command line usage - are we going to have '-device > ti-tms570' rather than '-cpu cortex-r4' then, or -cpu overriding the > container's default? My initial inclination is to say that specifying the CPU on the command line is almost always the wrong thing for ARM platforms (now or in a future QOM world). For instance, if you start the vexpress-a9 board with something other than -cpu cortex-a9 it won't complain but it won't do the right thing either (you'll get the private peripherals for the A9 with whatever CPU core you asked for). I don't think you want to have the user specifying -device my-soc on the command line either -- the user should be selecting a board (machine) model, which will generally nail down which soc and cpu are used. -cpu foo is most useful for linux-user mode. > Are > CPU features being refactored (standardized) for QOM or should we copy > current x86 code for controlling ARM FPU? There's a patch to add cpu feature support here: https://github.com/jowinter/qemu-trustzone/commit/421a2a71daa141da50c549979= 48d2a6d23013bd4 which I'm hoping will be submitted upstream... -- PMM