[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH v2 0/6] x86: Physical address limit patches
From: |
Paolo Bonzini |
Subject: |
Re: [Qemu-devel] [PATCH v2 0/6] x86: Physical address limit patches |
Date: |
Tue, 5 Jul 2016 12:59:42 +0200 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 |
On 05/07/2016 12:06, Michael S. Tsirkin wrote:
> > -m 2G,slots=16,maxmem=2T
> >
> > On a host with a 39bit physaddress limit do you error
> > on that or not? I think oVirt is currently doing something
> > similar to that, but I'm trying to get confirmation.
>
> That would only be a problem since pci is allocated above
> maxmem so 64 bit pci addresses aren't accessible.
> With my proposal we can actually force firmware to avoid
> using 64 bit memory for that config.
> Will work better than today.
So you would remove completely the 64-bit _CRS in this case?
How do you handle migration in the above scenario from say 46bit host to
39bit host, where the firmware has mapped (while running on the source)
a 64-bit BAR above the destination's maximum physical address?
Thanks,
Paolo
- Re: [Qemu-devel] [PATCH v2 5/6] x86: fix up 32 bit phys_bits case, (continued)
[Qemu-devel] [PATCH v2 6/6] x86: Add sanity checks on phys_bits, Dr. David Alan Gilbert (git), 2016/07/04
Re: [Qemu-devel] [PATCH v2 0/6] x86: Physical address limit patches, Michael S. Tsirkin, 2016/07/04
Re: [Qemu-devel] [PATCH v2 0/6] x86: Physical address limit patches, Dr. David Alan Gilbert, 2016/07/05
Re: [Qemu-devel] [PATCH v2 0/6] x86: Physical address limit patches, Michael S. Tsirkin, 2016/07/05
Re: [Qemu-devel] [PATCH v2 0/6] x86: Physical address limit patches, Daniel P. Berrange, 2016/07/05