qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: Seiji Aguchi <seiji.aguchi@hds.com>,
	"!(03/30/2013-Mitsumasa Inagaki)Satoru Moriya"
	<satoru.moriya@hds.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: "dle-develop@lists.sourceforge.net"
	<dle-develop@lists.sourceforge.net>,
	"satoru.moriya.br@hitachi.com" <satoru.moriya.br@hitachi.com>,
	Jan Kiszka <jan.kiszka@siemens.com>,
	"mtosatti@redhat.com" <mtosatti@redhat.com>,
	Tomoki Sekiyama <tomoki.sekiyama@hds.com>,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v4] Add option to mlock qemu and guest memory
Date: Tue, 02 Apr 2013 14:12:20 -0500	[thread overview]
Message-ID: <87hajovjaj.fsf@codemonkey.ws> (raw)
In-Reply-To: <A5ED84D3BB3A384992CBB9C77DEDA4D41AF80315@USINDEM103.corp.hds.com>

Seiji Aguchi <seiji.aguchi@hds.com> 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 <satoru.moriya@hds.com> 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 <satoru.moriya@hds.com>
>> > > Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
>> > > Reviewed-by: Marcelo Tosatti <mtosatti@redhat.com>
>> >
>> > 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

  reply	other threads:[~2013-04-02 19:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-26 15:05 [Qemu-devel] [PATCH v4] Add option to mlock qemu and guest memory Satoru Moriya
2013-03-27 15:18 ` Anthony Liguori
2013-03-28  4:43   ` Satoru Moriya
2013-04-02 15:03     ` Seiji Aguchi
2013-04-02 19:12       ` Anthony Liguori [this message]
2013-04-03  7:57       ` Markus Armbruster
2013-04-22 18:38 ` Anthony Liguori
  -- strict thread matches above, loose matches on Subject: below --
2013-04-22  5:16 Chegu Vinod
2013-04-23  3:47 ` Satoru Moriya

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87hajovjaj.fsf@codemonkey.ws \
    --to=aliguori@us.ibm.com \
    --cc=dle-develop@lists.sourceforge.net \
    --cc=jan.kiszka@siemens.com \
    --cc=mtosatti@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=satoru.moriya.br@hitachi.com \
    --cc=satoru.moriya@hds.com \
    --cc=seiji.aguchi@hds.com \
    --cc=tomoki.sekiyama@hds.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).