From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:52351) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UK9qE-0003ea-Pf for qemu-devel@nongnu.org; Mon, 25 Mar 2013 12:01:51 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UK9q9-0006Al-La for qemu-devel@nongnu.org; Mon, 25 Mar 2013 12:01:46 -0400 Received: from mx4-phx2.redhat.com ([209.132.183.25]:58583) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UK9q9-0006AV-Bq for qemu-devel@nongnu.org; Mon, 25 Mar 2013 12:01:41 -0400 Date: Mon, 25 Mar 2013 11:59:33 -0400 (EDT) From: Paolo Bonzini Message-ID: <1728727938.13211675.1364227173610.JavaMail.root@redhat.com> In-Reply-To: <51506ACB.1090506@linux.vnet.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [RFC 10/12] Add qemu_put_buffer_no_copy List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Michael R. Hines" Cc: Orit Wasserman , quintela@redhat.com, chegu vinod , qemu-devel@nongnu.org, mst@redhat.com > Right, the header's not used - but, are we certain that > put_buffer_copy() will *always* be used for RAM in the future? I think you should not make any assumption and proceed as if this series didn't exist. Paolo