From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Juergen Gross <jgross@suse.com>,
linux-kernel@vger.kernel.org, x86@kernel.org
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH v2 1/3] xen/pv: allow pmu msr accesses to cause GP
Date: Tue, 4 Oct 2022 15:46:36 -0400 [thread overview]
Message-ID: <25d4aa73-ee2c-9890-164a-89fddcbe133e@oracle.com> (raw)
In-Reply-To: <20221004084335.2838-2-jgross@suse.com>
On 10/4/22 4:43 AM, Juergen Gross wrote:
>
> bool pmu_msr_read(unsigned int msr, uint64_t *val, int *err)
> {
> - if (boot_cpu_data.x86_vendor != X86_VENDOR_INTEL) {
> - if (is_amd_pmu_msr(msr)) {
> - if (!xen_amd_pmu_emulate(msr, val, 1))
> - *val = native_read_msr_safe(msr, err);
> - return true;
> - }
> - } else {
> - int type, index;
> + int type, index;
> + bool emulated;
>
> - if (is_intel_pmu_msr(msr, &type, &index)) {
> - if (!xen_intel_pmu_emulate(msr, val, type, index, 1))
> - *val = native_read_msr_safe(msr, err);
> - return true;
> - }
> + if (is_amd_pmu_msr(msr))
> + emulated = xen_amd_pmu_emulate(msr, val, 1);
> + else if (is_intel_pmu_msr(msr, &type, &index))
> + emulated = xen_intel_pmu_emulate(msr, val, type, index, 1);
> + else
> + return false;
> +
> + if (!emulated) {
You can factor this out even further I think by moving if/elseif/esle into a separate routine and then have 'if (!xen_emulate_pmu_msr(msr, val, 1))' (and pass zero from pmu_msr_write())
-boris
next prev parent reply other threads:[~2022-10-04 19:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-04 8:43 [PATCH v2 0/3] xen/pv: sanitize xen pv guest msr accesses Juergen Gross
2022-10-04 8:43 ` [PATCH v2 1/3] xen/pv: allow pmu msr accesses to cause GP Juergen Gross
2022-10-04 10:58 ` Jan Beulich
2022-10-04 15:22 ` Juergen Gross
2022-10-04 15:50 ` Jan Beulich
2022-10-04 19:46 ` Boris Ostrovsky [this message]
2022-10-04 8:43 ` [PATCH v2 2/3] xen/pv: refactor msr access functions to support safe and unsafe accesses Juergen Gross
2022-10-04 11:03 ` Jan Beulich
2022-10-04 15:33 ` Juergen Gross
2022-10-04 8:43 ` [PATCH v2 3/3] xen/pv: support selecting safe/unsafe msr accesses Juergen Gross
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=25d4aa73-ee2c-9890-164a-89fddcbe133e@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xenproject.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