[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sun, 10 Oct 2010 14:48:03 +0200
From: Avi Kivity <avi@...hat.com>
To: Gleb Natapov <gleb@...hat.com>
CC: Gleb Natapov <gleb@...antech.com>,
Marcelo Tosatti <mtosatti@...hat.com>, kvm@...r.kernel.org,
linux-mm@...ck.org, linux-kernel@...r.kernel.org, mingo@...e.hu,
a.p.zijlstra@...llo.nl, tglx@...utronix.de, hpa@...or.com,
riel@...hat.com, cl@...ux-foundation.org
Subject: Re: [PATCH v6 04/12] Add memory slot versioning and use it to provide
fast guest write interface
On 10/07/2010 07:23 PM, Gleb Natapov wrote:
> On Thu, Oct 07, 2010 at 06:20:53PM +0200, Avi Kivity wrote:
> > On 10/07/2010 06:03 PM, Gleb Natapov wrote:
> > >> >
> > >> > Isn't SET_USER_MEMORY_REGION so slow that calling it 2^32 times
> > >> > isn't really feasible?
> > >>
> > >> Assuming it takes 1ms, it would take 49 days.
> > >>
> > >We may fail ioctl when max value is reached. The question is how much slot
> > >changes can we expect from real guest during its lifetime.
> > >
> >
> > A normal guest has a 30 Hz timer for reading the vga framebuffer,
> > multiple slots. Let's assume 100 Hz frequency, that gives 490 days
> > until things stop working.
> >
> And reading vga framebuffer needs slots changes because of dirty map
> tracking?
Yes.
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists