From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:36064) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UsWKU-0001Rv-VO for qemu-devel@nongnu.org; Fri, 28 Jun 2013 06:55:03 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UsWKT-0001Fl-C6 for qemu-devel@nongnu.org; Fri, 28 Jun 2013 06:55:02 -0400 Received: from smtp.eu.citrix.com ([46.33.159.39]:54051) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UsWKT-0001Ex-7T for qemu-devel@nongnu.org; Fri, 28 Jun 2013 06:55:01 -0400 From: Ian Jackson MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-ID: <20941.27523.823994.805482@mariner.uk.xensource.com> Date: Fri, 28 Jun 2013 11:54:59 +0100 In-Reply-To: <51CD41CB.50303@redhat.com> References: <51CD41CB.50303@redhat.com> Subject: Re: [Qemu-devel] [PATCH v2] xen_disk: support "direct-io-safe" backend option List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini Cc: xen-devel@lists.xensource.com, qemu-devel@nongnu.org, Anthony Liguori , Stefano Stabellini Paolo Bonzini writes ("Re: [PATCH v2] xen_disk: support "direct-io-safe" backend option"): > Il 27/06/2013 20:16, Stefano Stabellini ha scritto: > > The original proposal for a "cache" backend option has been dropped > > because it was believed too wide, especially considering that at the > > moment the backend doesn't have a way to tell the toolstack that it is > > capable of supporting it. > > Given how rusty my xenstore-fu is, I'll ask the obvious: the frontend > cannot write to it, can it? No, the backend directory is writeable only by the toolstack and driver domains. Ian. From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Jackson Subject: Re: [PATCH v2] xen_disk: support "direct-io-safe" backend option Date: Fri, 28 Jun 2013 11:54:59 +0100 Message-ID: <20941.27523.823994.805482@mariner.uk.xensource.com> References: <51CD41CB.50303@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <51CD41CB.50303@redhat.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org Sender: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org To: Paolo Bonzini Cc: xen-devel@lists.xensource.com, qemu-devel@nongnu.org, Anthony Liguori , Stefano Stabellini List-Id: xen-devel@lists.xenproject.org Paolo Bonzini writes ("Re: [PATCH v2] xen_disk: support "direct-io-safe" backend option"): > Il 27/06/2013 20:16, Stefano Stabellini ha scritto: > > The original proposal for a "cache" backend option has been dropped > > because it was believed too wide, especially considering that at the > > moment the backend doesn't have a way to tell the toolstack that it is > > capable of supporting it. > > Given how rusty my xenstore-fu is, I'll ask the obvious: the frontend > cannot write to it, can it? No, the backend directory is writeable only by the toolstack and driver domains. Ian.