All of lore.kernel.org
 help / color / mirror / Atom feed
From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: VPMU backports for 4.6
Date: Wed, 20 Jan 2016 12:36:51 -0500	[thread overview]
Message-ID: <569FC5B3.9050304@oracle.com> (raw)
In-Reply-To: <569FCE5E02000078000C94CC@prv-mh.provo.novell.com>

On 01/20/2016 12:13 PM, Jan Beulich wrote:
>>>> On 20.01.16 at 17:12, <boris.ostrovsky@oracle.com> wrote:
>> There two patches need to be backported to 4.6
>>
>> fb424bf x86/VPMU: don't allow any non-zero writes to MSR_IA32_PEBS_ENABLE
>> 31af0d7 x86/VPMU: check more carefully which bits are allowed to be
>> written to MSRs
> "Need to be" is pretty strong for an unsupported subsystem. In fact
> I had already considered those and then decided not to take them.
> So with you asking for them I'm not really sure what to do...

"Need to" may indeed have been a bit too much.

Since there is a potential for crashing the hypervisor I think we should 
have those two in 4.6, even if we don't officially support VPMU.

(As a side --- XSA-163 says that VPMU is "unsupported security-wise". Do 
we make any distinction between a feature being generally or 
security-wise unsupported?)

-boris

  reply	other threads:[~2016-01-20 17:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-20 16:12 VPMU backports for 4.6 Boris Ostrovsky
2016-01-20 17:13 ` Jan Beulich
2016-01-20 17:36   ` Boris Ostrovsky [this message]
2016-01-21  7:35     ` Jan Beulich
2016-01-21 10:10       ` Ian Campbell

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=569FC5B3.9050304@oracle.com \
    --to=boris.ostrovsky@oracle.com \
    --cc=JBeulich@suse.com \
    --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 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.