All of lore.kernel.org
 help / color / mirror / Atom feed
From: George Dunlap <george.dunlap@eu.citrix.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Jan Beulich <JBeulich@suse.com>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	Eddie Dong <eddie.dong@intel.com>,
	Donald D Dugger <donald.d.dugger@intel.com>,
	Dietmar Hahn <dietmar.hahn@ts.fujitsu.com>,
	Jun Nakajima <jun.nakajima@intel.com>,
	Haitao Shan <maillists.shan@gmail.com>
Subject: Re: [PATCH] Intel/vpmu: Use Intel VPMU quirk on all family 6 processors
Date: Thu, 30 May 2013 17:38:12 +0100	[thread overview]
Message-ID: <51A78074.9020608@eu.citrix.com> (raw)
In-Reply-To: <51A77F5B.3090508@oracle.com>

On 05/30/2013 05:33 PM, Boris Ostrovsky wrote:
> On 05/16/2013 08:30 AM, Jan Beulich wrote:
>>>>> On 10.05.13 at 11:46, George Dunlap <George.Dunlap@eu.citrix.com>
>>>>> wrote:
>>> On Thu, May 9, 2013 at 9:45 PM, Boris Ostrovsky
>>> <boris.ostrovsky@oracle.com> wrote:
>>>> On 05/09/2013 04:34 PM, Boris Ostrovsky wrote:
>>>>> Currently only a few Intel models have VPMU workaround turned on. It
>>>>> appears, however, that this issue exists on more models than what is
>>>>> covered by check_pmc_quirk(). Since we don't know exactly which cpus
>>>>> are affected we should turn this workaround on for all family 6
>>>>> processors.
>>>>
>>>> Haitao,
>>>>
>>>> A few weeks ago we had an email thread about this issue
>>>> (http://lists.xen.org/archives/html/xen-devel/2013-03/msg02618.html)
>>>> Did you have a chance to clarify with your HW folks what this is?
>>>>
>>>> We kept hitting this on various models which is why I am suggesting
>>>> this
>>>> patch (and I think it should be considered for 4.3).
>>> In principle it's a bug fix, and fine for 4.3.  But it would be good
>>> to get some feedback from someone at Intel.
>> Intel, anyone???
>>
>> Thanks, Jan
>>
>
> I haven't seen any responses from Intel folks about this issue.
>
> Do we wait for post-4.3?

Our goals at this point:
- Bug-free release
- Awesome release
- On-time release

I take it that the main risk here is that vcpu for some models which 
would have otherwise worked will not work anymore?

But at his point you *know* many models which don't work without it; so 
on the whole I'm inclined to say that it's an "accept" on the 
cost/benefits analysis.

  -George

  reply	other threads:[~2013-05-30 16:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-09 20:34 [PATCH] Intel/vpmu: Use Intel VPMU quirk on all family 6 processors Boris Ostrovsky
2013-05-09 20:45 ` Boris Ostrovsky
2013-05-10  9:46   ` George Dunlap
2013-05-16 12:30     ` Jan Beulich
2013-05-30 16:33       ` Boris Ostrovsky
2013-05-30 16:38         ` George Dunlap [this message]
2013-05-30 16:44           ` Boris Ostrovsky
2013-05-30 16:44         ` Jan Beulich
2013-05-30 16:50           ` Dugger, Donald D
  -- strict thread matches above, loose matches on Subject: below --
2013-05-31  3:53 Auld, Will
2013-05-31  8:04 ` Jan Beulich
2013-05-31  8:11   ` Auld, Will

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=51A78074.9020608@eu.citrix.com \
    --to=george.dunlap@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=dietmar.hahn@ts.fujitsu.com \
    --cc=donald.d.dugger@intel.com \
    --cc=eddie.dong@intel.com \
    --cc=jun.nakajima@intel.com \
    --cc=konrad.wilk@oracle.com \
    --cc=maillists.shan@gmail.com \
    --cc=xen-devel@lists.xensource.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 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.