From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=50773 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PD2tn-0003Eu-Vg for qemu-devel@nongnu.org; Mon, 01 Nov 2010 18:30:46 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PD2sG-0005gP-L7 for qemu-devel@nongnu.org; Mon, 01 Nov 2010 18:29:10 -0400 Received: from mail-iw0-f173.google.com ([209.85.214.173]:48575) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PD2sG-0005gL-Go for qemu-devel@nongnu.org; Mon, 01 Nov 2010 18:29:08 -0400 Received: by iwn36 with SMTP id 36so7854644iwn.4 for ; Mon, 01 Nov 2010 15:29:07 -0700 (PDT) Message-ID: <4CCF3F30.5080103@codemonkey.ws> Date: Mon, 01 Nov 2010 17:29:04 -0500 From: Anthony Liguori MIME-Version: 1.0 References: <1288623713-28062-1-git-send-email-agraf@suse.de> <1288623713-28062-29-git-send-email-agraf@suse.de> <4CCEE08F.4030403@codemonkey.ws> <4CCEE463.3090406@codemonkey.ws> <4CCF176F.2020600@redhat.com> <4CCF17EF.8090502@codemonkey.ws> <0A26E838-7FF5-4E4C-98EB-5EB0821460B9@suse.de> <4CCF23E9.8070404@codemonkey.ws> <4CCF357E.9010208@redhat.com> <4CCF386D.5020302@codemonkey.ws> <4CCF3A47.8050909@redhat.com> In-Reply-To: <4CCF3A47.8050909@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Re: [PATCH 28/40] xenner: libxc emu: evtchn List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini Cc: qemu-devel Developers , Gerd Hoffmann , Alexander Graf On 11/01/2010 05:08 PM, Paolo Bonzini wrote: > On 11/01/2010 11:00 PM, Anthony Liguori wrote: >> >> Okay, so does the same apply for xenstored? Does it make more sense to >> move that into the xenner kernel? > > I think no, because the backend devices do use xenstore, so they would > need a way to talk to the guest. Yeah, I was thinking fw_cfg but that's only after not thinking too much about it so that may be naive. Regards, Anthony Liguori > It's the same conceptually for the console, but in that case the > "way to talk to the guest" is the 8250A device model that already > exists. In the case of xenstore it would be yet another protocol to > devise and scrutinize. > > Paolo