On Fri, May 30, 2014 at 09:34:39AM +0200, Peter Zijlstra wrote:
> On Thu, May 29, 2014 at 06:12:06PM -0700, Andi Kleen wrote:
>
> > Note: in very rare cases with exotic events this may lead to spurious PMIs
> > in the guest.
>
> Qualify that statement so that if someone runs into it we at least
On Thu, May 29, 2014 at 06:12:06PM -0700, Andi Kleen wrote:
> Note: in very rare cases with exotic events this may lead to spurious PMIs
> in the guest.
Qualify that statement so that if someone runs into it we at least know
it is known/expected.
--
To unsubscribe from this list: send the line
On Thu, May 29, 2014 at 06:12:06PM -0700, Andi Kleen wrote:
Note: in very rare cases with exotic events this may lead to spurious PMIs
in the guest.
Qualify that statement so that if someone runs into it we at least know
it is known/expected.
--
To unsubscribe from this list: send the line
On Fri, May 30, 2014 at 09:34:39AM +0200, Peter Zijlstra wrote:
On Thu, May 29, 2014 at 06:12:06PM -0700, Andi Kleen wrote:
Note: in very rare cases with exotic events this may lead to spurious PMIs
in the guest.
Qualify that statement so that if someone runs into it we at least know
it
From: Andi Kleen
With PEBS virtualization the PEBS record gets delivered to the guest,
but the host sees the PMI. This would normally result in a spurious
PEBS PMI that is ignored. But we need to inject the PMI into the guest,
so that the guest PMI handler can handle the PEBS record.
Check for
From: Andi Kleen a...@linux.intel.com
With PEBS virtualization the PEBS record gets delivered to the guest,
but the host sees the PMI. This would normally result in a spurious
PEBS PMI that is ignored. But we need to inject the PMI into the guest,
so that the guest PMI handler can handle the PEBS
6 matches
Mail list logo