On 12/22/2017 01:18 PM, George Dunlap wrote:
> On Fri, Dec 22, 2017 at 10:41 AM, Sergej Proskurin
> wrote:
>> Hi George,
>>
>> Thank you for your reply.
>>
>> On 12/22/2017 11:26 AM, George Dunlap wrote:
>>> On Thu, Dec 21, 2017 at 2:42 PM, Sergej Proskurin
>>> wrote:
Hi all,
For
On Fri, Dec 22, 2017 at 10:41 AM, Sergej Proskurin
wrote:
> Hi George,
>
> Thank you for your reply.
>
> On 12/22/2017 11:26 AM, George Dunlap wrote:
>> On Thu, Dec 21, 2017 at 2:42 PM, Sergej Proskurin
>> wrote:
>>> Hi all,
>>>
>>> For the sake of completeness: the solution to the issue stated i
Hi George,
Thank you for your reply.
On 12/22/2017 11:26 AM, George Dunlap wrote:
> On Thu, Dec 21, 2017 at 2:42 PM, Sergej Proskurin
> wrote:
>> Hi all,
>>
>> For the sake of completeness: the solution to the issue stated in my
>> last email was deactivating Intel's Turbo Boost technology direc
On Thu, Dec 21, 2017 at 2:42 PM, Sergej Proskurin
wrote:
> Hi all,
>
> For the sake of completeness: the solution to the issue stated in my
> last email was deactivating Intel's Turbo Boost technology directly in
> UEFI (deactivating Turbo Boost through xenpm was not enough). Apparently
> Turbo Bo
Hi all,
For the sake of completeness: the solution to the issue stated in my
last email was deactivating Intel's Turbo Boost technology directly in
UEFI (deactivating Turbo Boost through xenpm was not enough). Apparently
Turbo Boost affects Linux and KVM differently than Xen, which led to the
phon
Hi all,
I have a question concerning a 'correct' Xen configuration to measure
performance, as I am currently experiencing a quite unexpected behavior.
My overall setup comprises a Skylake micro-architecture based system
with a Debian Buster and Linux kernel 4.13.16 running on top of Xen
v4.8. For
