On Wed, Jul 17, 2013 at 06:19:28PM +0300, Gleb Natapov wrote:
> On Tue, Jul 16, 2013 at 04:42:38PM -0300, Eduardo Habkost wrote:
> > On Tue, Jul 16, 2013 at 09:24:30PM +0200, Paolo Bonzini wrote:
> > > Il 16/07/2013 20:11, Eduardo Habkost ha scritto:
> > > > For physical bit size, what about extend
On Tue, Jul 16, 2013 at 04:42:38PM -0300, Eduardo Habkost wrote:
> On Tue, Jul 16, 2013 at 09:24:30PM +0200, Paolo Bonzini wrote:
> > Il 16/07/2013 20:11, Eduardo Habkost ha scritto:
> > > For physical bit size, what about extending it in a backwards-compatible
> > > way? Something like this:
> > >
Il 17/07/2013 15:39, Eduardo Habkost ha scritto:
> On Wed, Jul 17, 2013 at 10:09:01AM +0200, Paolo Bonzini wrote:
>> Il 16/07/2013 21:42, Eduardo Habkost ha scritto:
>>> On Tue, Jul 16, 2013 at 09:24:30PM +0200, Paolo Bonzini wrote:
Il 16/07/2013 20:11, Eduardo Habkost ha scritto:
> For ph
On Wed, Jul 17, 2013 at 10:09:01AM +0200, Paolo Bonzini wrote:
> Il 16/07/2013 21:42, Eduardo Habkost ha scritto:
> > On Tue, Jul 16, 2013 at 09:24:30PM +0200, Paolo Bonzini wrote:
> >> Il 16/07/2013 20:11, Eduardo Habkost ha scritto:
> >>> For physical bit size, what about extending it in a backwa
Il 16/07/2013 21:42, Eduardo Habkost ha scritto:
> On Tue, Jul 16, 2013 at 09:24:30PM +0200, Paolo Bonzini wrote:
>> Il 16/07/2013 20:11, Eduardo Habkost ha scritto:
>>> For physical bit size, what about extending it in a backwards-compatible
>>> way? Something like this:
>>>
>>> *eax = 0x00030
On Tue, Jul 16, 2013 at 09:24:30PM +0200, Paolo Bonzini wrote:
> Il 16/07/2013 20:11, Eduardo Habkost ha scritto:
> > For physical bit size, what about extending it in a backwards-compatible
> > way? Something like this:
> >
> > *eax = 0x0003000; /* 48 bits virtual */
> > if (ram_size < 1T
Il 16/07/2013 20:11, Eduardo Habkost ha scritto:
> For physical bit size, what about extending it in a backwards-compatible
> way? Something like this:
>
> *eax = 0x0003000; /* 48 bits virtual */
> if (ram_size < 1TB) {
> physical_size = 40; /* Keeping backwards compatibility */
>
On Tue, Jul 16, 2013 at 07:46:14PM +0200, Paolo Bonzini wrote:
> Il 16/07/2013 19:38, Eduardo Habkost ha scritto:
> > On Tue, Jul 16, 2013 at 07:22:01PM +0200, Andrea Arcangeli wrote:
> >> Without this patch the guest physical bits are advertised as 40, not
> >> 44 or more depending on the hardware
-On Tue, Jul 16, 2013 at 07:48:27PM +0200, Paolo Bonzini wrote:
> Il 16/07/2013 19:46, Paolo Bonzini ha scritto:
> >>> >> (see PUD with bit >=40 set)
> >> >
> >> > I am not sure I understand what caused this: if we are advertising 40
> >> > physical bits to the guest, why are we ending up with a P
Il 16/07/2013 19:46, Paolo Bonzini ha scritto:
>>> >> (see PUD with bit >=40 set)
>> >
>> > I am not sure I understand what caused this: if we are advertising 40
>> > physical bits to the guest, why are we ending up with a PUD with
>> > bit >= 40 set?
> Because we create a guest that has bigger me
Il 16/07/2013 19:38, Eduardo Habkost ha scritto:
> On Tue, Jul 16, 2013 at 07:22:01PM +0200, Andrea Arcangeli wrote:
>> Without this patch the guest physical bits are advertised as 40, not
>> 44 or more depending on the hardware capability of the host.
>>
>> That leads to guest kernel crashes with
On Tue, Jul 16, 2013 at 07:22:01PM +0200, Andrea Arcangeli wrote:
> Without this patch the guest physical bits are advertised as 40, not
> 44 or more depending on the hardware capability of the host.
>
> That leads to guest kernel crashes with injection of page faults 9
> (see oops: 0009) as bits
Il 16/07/2013 19:22, Andrea Arcangeli ha scritto:
> Without this patch the guest physical bits are advertised as 40, not
> 44 or more depending on the hardware capability of the host.
>
> That leads to guest kernel crashes with injection of page faults 9
> (see oops: 0009) as bits above 40 in the
Without this patch the guest physical bits are advertised as 40, not
44 or more depending on the hardware capability of the host.
That leads to guest kernel crashes with injection of page faults 9
(see oops: 0009) as bits above 40 in the guest pagetables are
considered reserved.
exregion-0206 [32
14 matches
Mail list logo