On Wed, Apr 22, 2015 at 04:59:49PM +0200, Alexander Graf wrote:
> On 04/22/2015 04:23 PM, Eduardo Habkost wrote:
> >On Tue, Apr 21, 2015 at 04:15:14PM +0200, Alexander Graf wrote:
> >>On 04/21/2015 04:16 PM, Eduardo Habkost wrote:
> >>>On Tue, Apr 21, 2015 at 04:04:21PM +0200, Alexander Graf wrote:
On 04/22/2015 04:23 PM, Eduardo Habkost wrote:
On Tue, Apr 21, 2015 at 04:15:14PM +0200, Alexander Graf wrote:
On 04/21/2015 04:16 PM, Eduardo Habkost wrote:
On Tue, Apr 21, 2015 at 04:04:21PM +0200, Alexander Graf wrote:
The AMD Opteron family has different xlevel levels depending on the
gene
On Tue, Apr 21, 2015 at 04:15:14PM +0200, Alexander Graf wrote:
> On 04/21/2015 04:16 PM, Eduardo Habkost wrote:
> >On Tue, Apr 21, 2015 at 04:04:21PM +0200, Alexander Graf wrote:
> >>The AMD Opteron family has different xlevel levels depending on the
> >>generation. I looked up Gen1, Gen2 and Gen3
On 04/21/2015 04:16 PM, Eduardo Habkost wrote:
On Tue, Apr 21, 2015 at 04:04:21PM +0200, Alexander Graf wrote:
The AMD Opteron family has different xlevel levels depending on the
generation. I looked up Gen1, Gen2 and Gen3 hardware and adapted the
levels according to real silicon.
The reason th
On Tue, Apr 21, 2015 at 04:04:21PM +0200, Alexander Graf wrote:
> The AMD Opteron family has different xlevel levels depending on the
> generation. I looked up Gen1, Gen2 and Gen3 hardware and adapted the
> levels according to real silicon.
>
> The reason this came up is that there is a sanity che
The AMD Opteron family has different xlevel levels depending on the
generation. I looked up Gen1, Gen2 and Gen3 hardware and adapted the
levels according to real silicon.
The reason this came up is that there is a sanity check in KVM making
sure that SVM is only used when xlevel is high enough. Us
