linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Li,Rongqing" <lirongqing@baidu.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
	Jim Mattson <jmattson@google.com>,
	Sean Christopherson <sean.j.christopherson@intel.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	LKML <linux-kernel@vger.kernel.org>,
	kvm list <kvm@vger.kernel.org>,
	"the arch/x86 maintainers" <x86@kernel.org>,
	"H . Peter Anvin" <hpa@zytor.com>,
	"Borislav Petkov" <bp@alien8.de>, Ingo Molnar <mingo@redhat.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Joerg Roedel <joro@8bytes.org>,
	Wanpeng Li <wanpengli@tencent.com>,
	Vitaly Kuznetsov <vkuznets@redhat.com>
Subject: 答复: [PATCH] [RFC] kvm: x86: emulate APERF/MPERF registers
Date: Sun, 26 Apr 2020 03:24:13 +0000	[thread overview]
Message-ID: <fd2a8092edf54a85979e5781dc354690@baidu.com> (raw)
In-Reply-To: <ce51d5f9-aa7b-233b-883d-802d9b00e090@redhat.com>



> -----邮件原件-----
> 发件人: Paolo Bonzini [mailto:pbonzini@redhat.com]
> 发送时间: 2020年4月25日 0:30
> 收件人: Jim Mattson <jmattson@google.com>; Sean Christopherson
> <sean.j.christopherson@intel.com>
> 抄送: Peter Zijlstra <peterz@infradead.org>; Li,Rongqing
> <lirongqing@baidu.com>; LKML <linux-kernel@vger.kernel.org>; kvm list
> <kvm@vger.kernel.org>; the arch/x86 maintainers <x86@kernel.org>; H .
> Peter Anvin <hpa@zytor.com>; Borislav Petkov <bp@alien8.de>; Ingo Molnar
> <mingo@redhat.com>; Thomas Gleixner <tglx@linutronix.de>; Joerg Roedel
> <joro@8bytes.org>; Wanpeng Li <wanpengli@tencent.com>; Vitaly Kuznetsov
> <vkuznets@redhat.com>
> 主题: Re: [PATCH] [RFC] kvm: x86: emulate APERF/MPERF registers
> 
> On 24/04/20 18:25, Jim Mattson wrote:
> >> Assuming we're going forward with this, at an absolute minimum the
> >> RDMSRs need to be wrapped with checks on host _and_ guest support for
> >> the emulated behavior.  Given the significant overhead, this might
> >> even be something that should require an extra opt-in from userspace to
> enable.
> >
> > I would like to see performance data before enabling this unconditionally.
> 
> I wouldn't want this to be enabled unconditionally anyway, because you need to
> take into account live migration to and from processors that do not have
> APERF/MPERF support.
> 
> Paolo

I will add a kvm parameter to consider whether enable MPERF/APERF emulations, and make default value to false

Thanks

-Li


  reply	other threads:[~2020-04-26  3:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-24  5:08 [PATCH] [RFC] kvm: x86: emulate APERF/MPERF registers Li RongQing
2020-04-24 10:01 ` Peter Zijlstra
2020-04-24 14:46   ` Sean Christopherson
2020-04-24 16:25     ` Jim Mattson
2020-04-24 16:30       ` Paolo Bonzini
2020-04-26  3:24         ` Li,Rongqing [this message]
2020-04-27 17:30           ` Jim Mattson
2020-04-27 19:10             ` Paolo Bonzini
2020-04-26  3:22     ` 答复: " Li,Rongqing
2020-04-26  8:30   ` Li,Rongqing

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=fd2a8092edf54a85979e5781dc354690@baidu.com \
    --to=lirongqing@baidu.com \
    --cc=bp@alien8.de \
    --cc=hpa@zytor.com \
    --cc=jmattson@google.com \
    --cc=joro@8bytes.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peterz@infradead.org \
    --cc=sean.j.christopherson@intel.com \
    --cc=tglx@linutronix.de \
    --cc=vkuznets@redhat.com \
    --cc=wanpengli@tencent.com \
    --cc=x86@kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).