> -----Original Message-----
> From: Anthony Liguori [mailto:aligu...@us.ibm.com]
> Sent: Tuesday, March 26, 2013 10:28 AM
> To: Satoru Moriya; qemu-devel@nongnu.org
> Cc: Jan Kiszka; dle-deve...@lists.sourceforge.net; Seiji Aguchi; Paolo 
> Bonzini; mtosa...@redhat.com;
> Tomoki Sekiyama; satoru.moriya...@hitachi.com
> Subject: Re: [Qemu-devel] [PATCH v3] Add option to mlock qemu and guest memory
> 
> Satoru Moriya <satoru.mor...@hds.com> writes:
> 
> > ChangeLog:
> > v3
> >  - Modify os_mlock() to return error code
> >  - Update configure_realtime() to handle return value from os_mlock()
> >  - Change the variable name from is_mlock to enable_mlock in
> > configure_realtime()
> >  - Rebase qemu version 1.4.50
> >
> > v2
> >  - Change option name from -mlock to -realtime mlock=on|off
> >  - Rebase qemu version 1.3.91
> >  - Update patch description
> >
> > We have some plans to migrate legacy enterprise systems which require
> > low latency (10 msec order) to kvm virtualized environment. In our
> > usecase, the system runs with other untrusted guests and so locking
> > memory which is used by the system is needed to avoid latency impacts
> > from other guests' memory activity.
> >
> > ---
> 
> By putting this here, you're going to mess up the commit message.
> Everything below '---' gets chopped off.
> 
> You want to move the changelog below the --- and the commit message above it.
> 
> Please submit a v4 with a corrected commit message.

Thanks.

I'll post v4 soon.

Regards,
Satoru

Reply via email to