All of lore.kernel.org
 help / color / mirror / Atom feed
From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: keir@xen.org, xen-devel@lists.xen.org
Subject: Re: [PATCH for-xen-4.5] x86/pvh/vpmu: Disable VPMU for PVH guests
Date: Tue, 25 Nov 2014 11:19:11 -0500	[thread overview]
Message-ID: <5474ABFF.1030306@oracle.com> (raw)
In-Reply-To: <5474A666020000780004AB9C@mail.emea.novell.com>

On 11/25/2014 09:55 AM, Jan Beulich wrote:
>
>> Regardless, do you think that disabling VPMU for PVH is worth anyway?
> That depends on what (bad) consequences not doing so has.

I haven't seen anything (besides VAPIC accesses) but I think it would be 
prudent to prevent any VPMU activity from happening. I can see, for 
example MSRs and APIC vector being written. All of which look benign on 
the first sight but who knows...

-boris

  reply	other threads:[~2014-11-25 16:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-24 19:49 [PATCH for-xen-4.5] x86/pvh/vpmu: Disable VPMU for PVH guests Boris Ostrovsky
2014-11-25  8:45 ` Jan Beulich
2014-11-25 14:38   ` Boris Ostrovsky
2014-11-25 14:55     ` Jan Beulich
2014-11-25 16:19       ` Boris Ostrovsky [this message]
2014-11-25 16:39         ` Jan Beulich
2014-11-25 17:54           ` Konrad Rzeszutek Wilk

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=5474ABFF.1030306@oracle.com \
    --to=boris.ostrovsky@oracle.com \
    --cc=JBeulich@suse.com \
    --cc=keir@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.