From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: kevin.tian@intel.com, keir@xen.org,
suravee.suthikulpanit@amd.com, andrew.cooper3@citrix.com,
tim@xen.org, dietmar.hahn@ts.fujitsu.com,
xen-devel@lists.xen.org, Aravind.Gopalakrishnan@amd.com,
jun.nakajima@intel.com, dgdegra@tycho.nsa.gov
Subject: Re: [PATCH v13 for-xen-4.5 07/21] x86/VPMU: Handle APIC_LVTPC accesses
Date: Mon, 13 Oct 2014 14:05:26 -0400 [thread overview]
Message-ID: <543C1466.6050309@oracle.com> (raw)
In-Reply-To: <543BE970020000780003E4BD@mail.emea.novell.com>
On 10/13/2014 09:02 AM, Jan Beulich wrote:
>>>> On 03.10.14 at 23:40, <boris.ostrovsky@oracle.com> wrote:
>> @@ -706,10 +693,6 @@ static int core2_vpmu_do_interrupt(struct cpu_user_regs *regs)
>> return 0;
>> }
>>
>> - /* HW sets the MASK bit when performance counter interrupt occurs*/
>> - vpmu->hw_lapic_lvtpc = apic_read(APIC_LVTPC) & ~APIC_LVT_MASKED;
>> - apic_write_around(APIC_LVTPC, vpmu->hw_lapic_lvtpc);
> So why is simply deleting this correct? The comment makes pretty
> clear why it was being done here. All I could see being valid without
> further explanation is the removal of the middle of the three lines.
It is expected that PMU interrupt will set the mask bit so whoever is
using PMU hardware (bare-metal or virtualized) is expected to clear it.
Therefore there is no reason for the hypervisor to do this.
I can add a note about it in the commit message.
-boris
next prev parent reply other threads:[~2014-10-13 18:05 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-03 21:40 [PATCH v13 for-xen-4.5 00/21] x86/PMU: Xen PMU PV(H) support Boris Ostrovsky
2014-10-03 21:40 ` [PATCH v13 for-xen-4.5 01/21] common/symbols: Export hypervisor symbols to privileged guest Boris Ostrovsky
2014-10-03 21:40 ` [PATCH v13 for-xen-4.5 02/21] x86/VPMU: Manage VPMU_CONTEXT_SAVE flag in vpmu_save_force() Boris Ostrovsky
2014-10-03 21:40 ` [PATCH v13 for-xen-4.5 03/21] x86/VPMU: Set MSR bitmaps only for HVM/PVH guests Boris Ostrovsky
2014-10-03 21:40 ` [PATCH v13 for-xen-4.5 04/21] x86/VPMU: Make vpmu macros a bit more efficient Boris Ostrovsky
2014-10-03 21:40 ` [PATCH v13 for-xen-4.5 05/21] intel/VPMU: Clean up Intel VPMU code Boris Ostrovsky
2014-10-03 21:40 ` [PATCH v13 for-xen-4.5 06/21] vmx: Merge MSR management routines Boris Ostrovsky
2014-10-03 21:40 ` [PATCH v13 for-xen-4.5 07/21] x86/VPMU: Handle APIC_LVTPC accesses Boris Ostrovsky
2014-10-13 13:02 ` Jan Beulich
2014-10-13 18:05 ` Boris Ostrovsky [this message]
2014-10-14 10:00 ` Jan Beulich
2014-10-03 21:40 ` [PATCH v13 for-xen-4.5 08/21] intel/VPMU: MSR_CORE_PERF_GLOBAL_CTRL should be initialized to zero Boris Ostrovsky
2014-10-03 21:40 ` [PATCH v13 for-xen-4.5 09/21] x86/VPMU: Add public xenpmu.h Boris Ostrovsky
2014-10-13 13:31 ` Jan Beulich
2014-10-13 18:31 ` Boris Ostrovsky
2014-10-14 10:03 ` Jan Beulich
2014-10-03 21:40 ` [PATCH v13 for-xen-4.5 10/21] x86/VPMU: Make vpmu not HVM-specific Boris Ostrovsky
2014-10-03 21:40 ` [PATCH v13 for-xen-4.5 11/21] x86/VPMU: Interface for setting PMU mode and flags Boris Ostrovsky
2014-10-13 13:51 ` Jan Beulich
2014-10-13 18:57 ` Boris Ostrovsky
2014-10-14 10:09 ` Jan Beulich
2014-10-03 21:40 ` [PATCH v13 for-xen-4.5 12/21] x86/VPMU: Initialize AND and Intel VPMU with __initcall Boris Ostrovsky
2014-10-13 13:58 ` Jan Beulich
2014-10-03 21:40 ` [PATCH v13 for-xen-4.5 13/21] x86/VPMU: Initialize PMU for PV(H) guests Boris Ostrovsky
2014-10-13 14:29 ` Jan Beulich
2014-10-03 21:40 ` [PATCH v13 for-xen-4.5 14/21] x86/VPMU: Save VPMU state for PV guests during context switch Boris Ostrovsky
2014-10-03 21:40 ` [PATCH v13 for-xen-4.5 15/21] x86/VPMU: When handling MSR accesses, leave fault injection to callers Boris Ostrovsky
2014-10-03 21:40 ` [PATCH v13 for-xen-4.5 16/21] x86/VPMU: Add support for PMU register handling on PV guests Boris Ostrovsky
2014-10-03 21:40 ` [PATCH v13 for-xen-4.5 17/21] x86/VPMU: Handle PMU interrupts for " Boris Ostrovsky
2014-10-13 15:29 ` Jan Beulich
2014-10-13 19:10 ` Boris Ostrovsky
2014-10-14 10:10 ` Jan Beulich
2014-10-03 21:40 ` [PATCH v13 for-xen-4.5 18/21] x86/VPMU: Merge vpmu_rdmsr and vpmu_wrmsr Boris Ostrovsky
2014-10-03 21:40 ` [PATCH v13 for-xen-4.5 19/21] x86/VPMU: Add privileged PMU mode Boris Ostrovsky
2014-10-13 15:32 ` Jan Beulich
2014-10-03 21:40 ` [PATCH v13 for-xen-4.5 20/21] x86/VPMU: NMI-based VPMU support Boris Ostrovsky
2014-10-13 15:43 ` Jan Beulich
2014-10-03 21:40 ` [PATCH v13 for-xen-4.5 21/21] x86/VPMU: Move VPMU files up from hvm/ directory Boris Ostrovsky
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=543C1466.6050309@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=Aravind.Gopalakrishnan@amd.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=dgdegra@tycho.nsa.gov \
--cc=dietmar.hahn@ts.fujitsu.com \
--cc=jun.nakajima@intel.com \
--cc=keir@xen.org \
--cc=kevin.tian@intel.com \
--cc=suravee.suthikulpanit@amd.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xen.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 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.