From: Paolo Bonzini <pbonzini@redhat.com>
To: Jim Mattson <jmattson@google.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
kvm list <kvm@vger.kernel.org>,
Vitaly Kuznetsov <vkuznets@redhat.com>
Subject: Re: [PATCH v2] KVM: x86: omit absent pmu MSRs from MSR list
Date: Thu, 3 Oct 2019 19:37:59 +0200 [thread overview]
Message-ID: <f8e169a5-4cf6-8df7-86bb-f70a480c33ad@redhat.com> (raw)
In-Reply-To: <CALMp9eRFUeSB035VEC61CzAg6PY=aApjyiQoSnRydH788COL4w@mail.gmail.com>
On 03/10/19 19:20, Jim Mattson wrote:
> You've truncated the list I originally provided, so I think this need
> only go to MSR_ARCH_PERFMON_PERFCTR0 + 17. Otherwise, we could lose
> some valuable MSRs.
This is v2, so it was meant to replace the patch that truncates the
list. But I can include the other one too, perhaps even ask the x86
maintainers about decreasing INTEL_PMC_MAX_GENERIC to 18.
>> + if (msrs_to_save[i] - MSR_ARCH_PERFMON_PERFCTR0 >=
>> + min(INTEL_PMC_MAX_GENERIC, x86_pmu.num_counters_gp))
> Why involve INTEL_PMC_MAX_GENERIC here?
It's not really necessary, but I wanted to imitate how intel_pmu_refresh
initializes pmu->nr_arch_gp_counters.
Paolo
>> + continue;
>> + break;
>> + case MSR_ARCH_PERFMON_EVENTSEL0 ... MSR_ARCH_PERFMON_EVENTSEL0 + 31:
> Same as the two comments above.
>> + if (msrs_to_save[i] - MSR_ARCH_PERFMON_EVENTSEL0 >=
>> + min(INTEL_PMC_MAX_GENERIC, x86_pmu.num_counters_gp))
>> + continue;
next prev parent reply other threads:[~2019-10-03 17:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-03 10:10 [PATCH v2] KVM: x86: omit absent pmu MSRs from MSR list Paolo Bonzini
2019-10-03 17:20 ` Jim Mattson
2019-10-03 17:37 ` Paolo Bonzini [this message]
2019-10-03 18:23 ` Jim Mattson
2019-10-03 20:12 ` Paolo Bonzini
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=f8e169a5-4cf6-8df7-86bb-f70a480c33ad@redhat.com \
--to=pbonzini@redhat.com \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vkuznets@redhat.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 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).