From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:54241) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UN6dK-0004eK-Du for qemu-devel@nongnu.org; Tue, 02 Apr 2013 15:12:39 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UN6dJ-00055N-0Y for qemu-devel@nongnu.org; Tue, 02 Apr 2013 15:12:38 -0400 Received: from e23smtp08.au.ibm.com ([202.81.31.141]:38780) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UN6dI-000554-G5 for qemu-devel@nongnu.org; Tue, 02 Apr 2013 15:12:36 -0400 Received: from /spool/local by e23smtp08.au.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Wed, 3 Apr 2013 05:10:25 +1000 Received: from d23relay03.au.ibm.com (d23relay03.au.ibm.com [9.190.235.21]) by d23dlp02.au.ibm.com (Postfix) with ESMTP id DDD8B2BB0051 for ; Wed, 3 Apr 2013 06:12:28 +1100 (EST) Received: from d23av03.au.ibm.com (d23av03.au.ibm.com [9.190.234.97]) by d23relay03.au.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r32JCNLG66781378 for ; Wed, 3 Apr 2013 06:12:24 +1100 Received: from d23av03.au.ibm.com (loopback [127.0.0.1]) by d23av03.au.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id r32JCRig026428 for ; Wed, 3 Apr 2013 06:12:27 +1100 From: Anthony Liguori In-Reply-To: References: <8631DC5930FA9E468F04F3FD3A5D00721AFE9AE6@USINDEM103.corp.hds.com> <87mwto98if.fsf@codemonkey.ws> <8631DC5930FA9E468F04F3FD3A5D00721AFEA7A0@USINDEM103.corp.hds.com> Date: Tue, 02 Apr 2013 14:12:20 -0500 Message-ID: <87hajovjaj.fsf@codemonkey.ws> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: [Qemu-devel] [PATCH v4] Add option to mlock qemu and guest memory List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Seiji Aguchi , "!(03/30/2013-Mitsumasa Inagaki)Satoru Moriya" , "qemu-devel@nongnu.org" Cc: "dle-develop@lists.sourceforge.net" , "satoru.moriya.br@hitachi.com" , Jan Kiszka , "mtosatti@redhat.com" , Tomoki Sekiyama , Paolo Bonzini Seiji Aguchi writes: > Anthony, > >> Currently my company doesn't allow me to use git-send-email to send a email. >> So now I'm trying to find work around with IT. > > Satoru and I still talk if we can use git-send-email with my company IT. > But, it seems to take a long time... > > So, I attached Satoru's patch. > Could you please apply it to your tree? Even attached, the patch still has carriage returns. I don't have a lot of confidence in accept a patch if it cannot be submitted in the correct fashion at least. Regards, Anthony Liguori > > Seiji > >> -----Original Message----- >> From: Satoru Moriya >> Sent: Thursday, March 28, 2013 12:43 AM >> To: Anthony Liguori; qemu-devel@nongnu.org >> Cc: Jan Kiszka; mtosatti@redhat.com; Paolo Bonzini; Seiji Aguchi; Tomoki Sekiyama; dle-develop@lists.sourceforge.net; >> satoru.moriya.br@hitachi.com >> Subject: RE: [Qemu-devel] [PATCH v4] Add option to mlock qemu and guest memory >> >> > -----Original Message----- >> > From: Anthony Liguori [mailto:aliguori@us.ibm.com] >> > Sent: Wednesday, March 27, 2013 11:18 AM >> > To: Satoru Moriya; qemu-devel@nongnu.org >> > Cc: Jan Kiszka; mtosatti@redhat.com; Paolo Bonzini; Seiji Aguchi; >> > Tomoki Sekiyama; dle- develop@lists.sourceforge.net; >> > satoru.moriya.br@hitachi.com >> > Subject: Re: [Qemu-devel] [PATCH v4] Add option to mlock qemu and >> > guest memory >> > >> > Satoru Moriya writes: >> > >> > > In certain scenario, latency induced by paging is significant and >> > > memory locking is needed. Also, in the scenario with untrusted >> > > guests, latency improvement due to mlock is desired. >> > > >> > > This patch introduces a following new option to mlock guest and qemu >> > > memory: >> > > >> > > -realtime mlock=on|off >> > > >> > > Signed-off-by: Satoru Moriya >> > > Reviewed-by: Paolo Bonzini >> > > Reviewed-by: Marcelo Tosatti >> > >> > This patch doesn't apply because you're sending it MIME encoded and >> > the patch has carriage returns in it. I think your mailer is badly munging the patch. >> > >> > Please send it via git-send-email directly from the repository. >> >> I'm sorry for bothering you... >> >> Currently my company doesn't allow me to use git-send-email to send a email. >> So now I'm trying to find work around with IT. >> >> Once it is solved, I re-post the patch. >> >> Regards, >> Satoru