From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: "Tian, Kevin" <kevin.tian@intel.com>,
"andrew.cooper3@citrix.com" <andrew.cooper3@citrix.com>,
"jbeulich@suse.com" <jbeulich@suse.com>,
"Nakajima, Jun" <jun.nakajima@intel.com>
Cc: "dietmar.hahn@ts.fujitsu.com" <dietmar.hahn@ts.fujitsu.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH v2 2/3] x86/VPMU: No need to check whether VPMU quirk is needed on Intel
Date: Thu, 3 Dec 2015 10:46:37 -0500 [thread overview]
Message-ID: <566063DD.1030905@oracle.com> (raw)
In-Reply-To: <AADFC41AFE54684AB9EE6CBC0274A5D15F72B376@SHSMSX101.ccr.corp.intel.com>
On 12/03/2015 01:18 AM, Tian, Kevin wrote:
>> From: Boris Ostrovsky [mailto:boris.ostrovsky@oracle.com]
>> Sent: Wednesday, December 02, 2015 12:50 AM
>>
>> We only support family 6 so quirk handling is always needed.
> what about you adding other family support in the future then you'll
> add back below quirk check?
Yes.
-boris
next prev parent reply other threads:[~2015-12-03 15:46 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-01 16:50 [PATCH v2 0/3] VPMU fixes Boris Ostrovsky
2015-12-01 16:50 ` [PATCH v2 1/3] x86/VPMU: Support only versions 2 through 4 of architectural performance monitoring Boris Ostrovsky
2015-12-02 14:32 ` Jan Beulich
2015-12-04 1:29 ` Tian, Kevin
2015-12-01 16:50 ` [PATCH v2 2/3] x86/VPMU: No need to check whether VPMU quirk is needed on Intel Boris Ostrovsky
2015-12-03 6:18 ` Tian, Kevin
2015-12-03 15:46 ` Boris Ostrovsky [this message]
2015-12-04 1:31 ` Tian, Kevin
2015-12-01 16:50 ` [PATCH v2 3/3] MAINTAINERS: Restore original maintainership of arch VPMU files Boris Ostrovsky
2015-12-04 1:32 ` Tian, Kevin
2015-12-02 2:20 ` [PATCH v2 0/3] VPMU fixes Tian, Kevin
2015-12-02 9:21 ` Dietmar Hahn
2015-12-03 6:16 ` Tian, Kevin
2015-12-03 10:36 ` Jan Beulich
2015-12-03 10:46 ` Tian, Kevin
2015-12-03 11:02 ` Jan Beulich
2015-12-03 15:44 ` Boris Ostrovsky
2015-12-04 1:28 ` Tian, Kevin
2015-12-07 8:23 ` Tian, Kevin
2015-12-07 21:24 ` Kleen, Andi
2015-12-07 23:05 ` 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=566063DD.1030905@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=andrew.cooper3@citrix.com \
--cc=dietmar.hahn@ts.fujitsu.com \
--cc=jbeulich@suse.com \
--cc=jun.nakajima@intel.com \
--cc=kevin.tian@intel.com \
--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.