On 01/08/2010 02:30 PM, Bryan Donlan wrote:
On Fri, Jan 8, 2010 at 2:24 PM, Rik van Riel wrote:
On 01/08/2010 11:18 AM, Marcelo Tosatti wrote:
- Limit the number of queued async pf's per guest ?
This is automatically limited to the number of processes
running in a guest :)
Only if the gue
On Fri, Jan 8, 2010 at 2:24 PM, Rik van Riel wrote:
> On 01/08/2010 11:18 AM, Marcelo Tosatti wrote:
>
>> - Limit the number of queued async pf's per guest ?
>
> This is automatically limited to the number of processes
> running in a guest :)
Only if the guest is nice and plays by the rules. What
On 01/08/2010 11:18 AM, Marcelo Tosatti wrote:
- Limit the number of queued async pf's per guest ?
This is automatically limited to the number of processes
running in a guest :)
--
All rights reversed.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message
On Fri, Jan 08, 2010 at 02:18:28PM -0200, Marcelo Tosatti wrote:
> On Tue, Jan 05, 2010 at 04:12:42PM +0200, Gleb Natapov wrote:
> > KVM virtualizes guest memory by means of shadow pages or HW assistance
> > like NPT/EPT. Not all memory used by a guest is mapped into the guest
> > address space or
On Tue, Jan 05, 2010 at 04:12:42PM +0200, Gleb Natapov wrote:
> KVM virtualizes guest memory by means of shadow pages or HW assistance
> like NPT/EPT. Not all memory used by a guest is mapped into the guest
> address space or even present in a host memory at any given time.
> When vcpu tries to acc
On Wed, Jan 06, 2010 at 07:17:30PM +0900, Jun Koi wrote:
> On Wed, Jan 6, 2010 at 1:04 AM, Avi Kivity wrote:
> > On 01/05/2010 05:05 PM, Jun Koi wrote:
> >>
> >> Is it true that to make this work, we will need a (PV) kernel driver
> >> for each guest OS (Windows, Linux, ...)?
> >>
> >>
> >
> > It'
On Wed, Jan 6, 2010 at 1:04 AM, Avi Kivity wrote:
> On 01/05/2010 05:05 PM, Jun Koi wrote:
>>
>> Is it true that to make this work, we will need a (PV) kernel driver
>> for each guest OS (Windows, Linux, ...)?
>>
>>
>
> It's partially usable even without guest modifications; while servicing a
> ho
On 01/05/2010 05:05 PM, Jun Koi wrote:
Is it true that to make this work, we will need a (PV) kernel driver
for each guest OS (Windows, Linux, ...)?
It's partially usable even without guest modifications; while servicing
a host page fault we can still deliver interrupts to the guest (whic
On 01/05/2010 10:05 AM, Jun Koi wrote:
On Tue, Jan 5, 2010 at 11:12 PM, Gleb Natapov wrote:
KVM virtualizes guest memory by means of shadow pages or HW assistance
like NPT/EPT. Not all memory used by a guest is mapped into the guest
address space or even present in a host memory at any given ti
On Tue, Jan 5, 2010 at 11:12 PM, Gleb Natapov wrote:
> KVM virtualizes guest memory by means of shadow pages or HW assistance
> like NPT/EPT. Not all memory used by a guest is mapped into the guest
> address space or even present in a host memory at any given time.
> When vcpu tries to access memo
KVM virtualizes guest memory by means of shadow pages or HW assistance
like NPT/EPT. Not all memory used by a guest is mapped into the guest
address space or even present in a host memory at any given time.
When vcpu tries to access memory page that is not mapped into the guest
address space KVM is
11 matches
Mail list logo
