public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Ingo Molnar <mingo@kernel.org>,
	Konrad Rzeszutek Wilk <konrad@kernel.org>,
	Borislav Petkov <bp@alien8.de>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [GIT PULL] x86/cpu changes for v3.9
Date: Tue, 19 Feb 2013 13:26:13 -0500	[thread overview]
Message-ID: <5123C3C5.9090100@oracle.com> (raw)
In-Reply-To: <5123C28F.50405@zytor.com>

On 02/19/2013 01:21 PM, H. Peter Anvin wrote:
> On 02/19/2013 10:19 AM, Boris Ostrovsky wrote:
>> On 02/19/2013 12:57 PM, Konrad Rzeszutek Wilk wrote:
>>> On Tue, Feb 19, 2013 at 06:47:58PM +0100, Borislav Petkov wrote:
>>>> On Tue, Feb 19, 2013 at 09:38:31AM -0800, H. Peter Anvin wrote:
>>>>> My fault... I was tracking the fix and lost track of the thread.
>>>>>
>>>>> The problem is that the fix is necessary but not sufficient, as it
>>>>> introduces an undesirable host-guest dependency.  In order to allow
>>>>> neerw guests to work on older hosts we also should use the
>>>>> {rd,wr}msr_safe() functions to manipulate this MSR, with a comment
>>>>> as to why.
>>>>>
>>>>> Boris, could you prepare such a patch, please?
>>>> I don't think Boris O. is at AMD anymore. Want me to add that to my 
>>>> fix
>>>> for kvm or prep a separate patch?
>>> CC-ing Boris.
>>
>> BorisP's patch is what I should have done. Can you take it?
>>
>
> As I stated:
>
> >>>> The problem is that the fix is necessary but not sufficient, as it
> >>>> introduces an undesirable host-guest dependency. In order to allow
> >>>> neerw guests to work on older hosts we also should use the
> >>>> {rd,wr}msr_safe() functions to manipulate this MSR, with a comment
> >>>> as to why.

Ah, sorry --- I missed that part.

-boris


      reply	other threads:[~2013-02-19 18:26 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-19 15:25 [GIT PULL] x86/cpu changes for v3.9 Ingo Molnar
2013-02-19 15:36 ` Borislav Petkov
2013-02-19 15:47   ` Ingo Molnar
2013-02-19 17:38     ` H. Peter Anvin
2013-02-19 17:47       ` Borislav Petkov
2013-02-19 17:51         ` H. Peter Anvin
2013-02-19 18:33           ` [PATCH 1/2] x86, CPU, AMD: Fix WC+ workaround for older hosts Borislav Petkov
2013-02-19 18:33             ` [PATCH 2/2] x86, kvm: Add MSR_AMD64_BU_CFG2 to the list of ignored MSRs Borislav Petkov
2013-02-19 19:30               ` [tip:x86/cpu] " tip-bot for Borislav Petkov
2013-02-19 19:29             ` [tip:x86/cpu] x86, cpu, amd: Fix WC+ workaround for older virtual hosts tip-bot for Borislav Petkov
2013-02-19 17:57         ` [GIT PULL] x86/cpu changes for v3.9 Konrad Rzeszutek Wilk
2013-02-19 18:01           ` Borislav Petkov
2013-02-19 18:19           ` Boris Ostrovsky
2013-02-19 18:21             ` H. Peter Anvin
2013-02-19 18:26               ` Boris Ostrovsky [this message]

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=5123C3C5.9090100@oracle.com \
    --to=boris.ostrovsky@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=bp@alien8.de \
    --cc=hpa@zytor.com \
    --cc=konrad@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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