All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>, Kechen Lu <kechenl@nvidia.com>
Cc: "suravee.suthikulpanit@amd.com" <suravee.suthikulpanit@amd.com>,
	Somdutta Roy <somduttar@nvidia.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"qemu-discuss@nongnu.org" <qemu-discuss@nongnu.org>
Subject: Re: Optimized clocksource with AMD AVIC enabled for Windows guest
Date: Wed, 03 Feb 2021 10:15:51 +0100	[thread overview]
Message-ID: <878s85pl4o.fsf@vitty.brq.redhat.com> (raw)
In-Reply-To: <5688445c-b9c8-dbd6-e9ee-ed40df84f8ca@redhat.com>

Paolo Bonzini <pbonzini@redhat.com> writes:

> On 03/02/21 07:40, Kechen Lu wrote:
>> From the above observations, trying to see if there's a way for
>> enabling AVIC while also having the most optimized clock source for
>> windows guest.
>> 
>
> You would have to change KVM, so that AVIC is only disabled if Auto-EOI 
> interrupts are used.
>

(I vaguely recall having this was discussed already but apparently no
changes were made since)

Hyper-V TLFS defines the following bit:

CPUID 0x40000004.EAX 
Bit 9: Recommend deprecating AutoEOI.

But this is merely a recommendation and older Windows versions may not
know about the bit and still use it. We need to make sure the bit is
set/exposed to Windows guests but we also must track AutoEOI usage and
inhibit AVIC when detected.

-- 
Vitaly


  reply	other threads:[~2021-02-03  9:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-03  6:40 Optimized clocksource with AMD AVIC enabled for Windows guest Kechen Lu
2021-02-03  7:58 ` Paolo Bonzini
2021-02-03  9:15   ` Vitaly Kuznetsov [this message]
2021-02-04  2:05     ` Kechen Lu
2021-02-04 12:24       ` Vitaly Kuznetsov
2021-02-04 13:35         ` Paolo Bonzini
2021-02-04 15:01           ` Vitaly Kuznetsov
2021-02-04 15:19             ` Vitaly Kuznetsov
2021-02-05  5:38               ` Kechen Lu
2021-02-17 20:41                 ` Kechen Lu
2021-02-25 10:25                   ` Vitaly Kuznetsov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=878s85pl4o.fsf@vitty.brq.redhat.com \
    --to=vkuznets@redhat.com \
    --cc=kechenl@nvidia.com \
    --cc=kvm@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=qemu-discuss@nongnu.org \
    --cc=somduttar@nvidia.com \
    --cc=suravee.suthikulpanit@amd.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.