From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:47619) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1flXNe-0002MO-BY for qemu-devel@nongnu.org; Fri, 03 Aug 2018 06:32:25 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1flXNa-00047B-Bi for qemu-devel@nongnu.org; Fri, 03 Aug 2018 06:32:22 -0400 Date: Fri, 3 Aug 2018 11:32:14 +0100 From: Stefan Hajnoczi Message-ID: <20180803103214.GA14905@stefanha-x1.localdomain> References: <20180725085944.11856-1-stefanha@redhat.com> <20180725085944.11856-7-stefanha@redhat.com> <20180802124345.GA25289@stefanha-x1.localdomain> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="azLHFNyN32YCQGCU" Content-Disposition: inline In-Reply-To: Subject: Re: [Qemu-devel] [PATCH v3 6/7] loader: Implement .hex file loader List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: Stefan Hajnoczi , Jim Mussared , Steffen =?iso-8859-1?Q?G=F6rtz?= , Su Hang , Liviu Ionescu , Alistair Francis , QEMU Developers , Subbaraya Sundeep , Steffen Gortz , qemu-arm , Joel Stanley , Julia Suvorova --azLHFNyN32YCQGCU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Aug 02, 2018 at 11:04:46PM +0100, Peter Maydell wrote: > On 2 August 2018 at 13:43, Stefan Hajnoczi wrote: > > On Mon, Jul 30, 2018 at 07:01:53PM +0100, Peter Maydell wrote: > >> I'm still not convinced we want to add another random > >> special case only-works-on-one-architecture-and-some-boards > >> feature to the -kernel command line option. > >> > >> Adding it to the "generic loader" device might be more plausible? > > > > I'm not sure I understand the purpose of the generic loader. > > > > As a user -kernel is easier than -device > > loader,file=3D,cpu-num=3D1. > > > > Can you explain the advantage to moving hex file loading to the generic > > loader? >=20 > It means we have a command line option for loading hex files > that works for every board and every CPU architecture. > (Similarly, if you want a way to load an ELF file that > works the same way for all boards and CPUs, the generic > loader is it -- -kernel will not reliably do the job. > You can also use it to load more than one ELF file or > to load different ELF files for different CPUs, neither > of which you can do with -kernel.) >=20 > -kernel, like all our legacy short options, is, yes, > easier to use; it's also a twisted mess of different > "do what I mean" functionality that varies depending > on the guest CPU architecture and subtype, the machine > being emulated, and other random things like "did the > user also tell us to start a BIOS image". It mostly means > "run a Linux kernel", with some extras wedged in on the > side where we thought we could do it without breaking the > kernel case. Oh, and we don't document anywhere what > it actually does. I'm reluctant to add yet another layer of > "do what I mean" to it that only has an effect on a subset > of Arm boards. Okay, I understand better now. Thanks! I'll resend with the generic loader instead of -kernel. Stefan --azLHFNyN32YCQGCU Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEcBAEBAgAGBQJbZC8uAAoJEJykq7OBq3PIPp8H/R2Aq4x/Mh26uXs8de8aeNBW HW10uD3wk8SjsQ2Qde4pVPHOUeyPapOVkRgCzLp6ejGUWHT+QehY7EtKjUsoWapW fY2+ZhY1Fa1AcGL6dC3aWUagcJoZ/tHGreIrfvEM/XqGZcT3LXeieh6vAqHreVA6 cIgZrN/KxPbWRKNv5h6IGAtxircw1wIoSRZTLwzSRmLgFFYM1+twSQp5aLmVshKn PfnYQFQdz9KgwZaXeGuTSShOFKIiUhH8qqb4eeEytMwfVe6Vn2PtIpq8BKdswi8G o7UgAtg2OYppmKcm4MxoqCGXl9z5ar0MdCpnrLDKrDadF2c47HZHcxSHGXBCkEI= =xC8R -----END PGP SIGNATURE----- --azLHFNyN32YCQGCU--