From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:34955) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gKrWk-0005Ox-Ig for qemu-devel@nongnu.org; Thu, 08 Nov 2018 16:07:50 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gKrQ4-0004JT-FW for qemu-devel@nongnu.org; Thu, 08 Nov 2018 16:00:56 -0500 Received: from mx1.redhat.com ([209.132.183.28]:58212) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1gKrQ3-0004HO-UZ for qemu-devel@nongnu.org; Thu, 08 Nov 2018 16:00:52 -0500 Date: Thu, 8 Nov 2018 19:00:47 -0200 From: Eduardo Habkost Message-ID: <20181108210047.GU12503@habkost.net> References: <20181107192414.GH12503@habkost.net> <20181108130648.GJ12503@habkost.net> <95a93d53-f87d-bd96-9363-582c4eae4160@redhat.com> <20181108171437.GM12503@habkost.net> <20181108184242.GQ12503@habkost.net> <2f4793c3-5509-1def-3157-02bc0d9bbe26@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2f4793c3-5509-1def-3157-02bc0d9bbe26@redhat.com> Subject: Re: [Qemu-devel] QEMU and Kconfig List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini Cc: Thomas Huth , Samuel Ortiz , "Zhong, Yang" , Peter Maydell , QEMU Developers On Thu, Nov 08, 2018 at 09:28:06PM +0100, Paolo Bonzini wrote: > Oops. :) > > On 08/11/2018 19:42, Eduardo Habkost wrote: > >>> Keeping in mind that I might be talking about extra challenges we > >>> won't address right now (no cart before the horse), I have new > >>> questions: > >>> > >>> Why you say backends are not a target configuration and > >>> accelerators are? What's the definition of "target > >>> configuration"? > > Something that affects the hardware seen by the guest is target > configuration. > > Backends do not affect what hardware the guest sees. Boards and devices > do; accelerators do, but that's more of a side-effect than something > intended. Understood. My interpretation of "target" was just "a QEMU binary". In other words, I thought we were talking about anything that could be compiled in/out from a specific QEMU binary. Do you have a specific reason to restrict the scope to only guest-visible effects? Is this just a way to reduce the effort required for the task, or there are other caveats I'm missing? -- Eduardo