Am 25.07.2013 16:46, schrieb Andreas Färber:
> Am 25.07.2013 12:14, schrieb Gleb Natapov:
>> On Wed, Jul 24, 2013 at 05:01:15PM +0200, Andreas Färber wrote:
>>> New msr_* fields would be candidates for X86CPU, but there's already one
>>> in CPUX86State. :/
>>>
>> Is this NAK?
>
> No, it was more a
Am 25.07.2013 12:14, schrieb Gleb Natapov:
> On Wed, Jul 24, 2013 at 05:01:15PM +0200, Andreas Färber wrote:
>> Am 24.07.2013 16:37, schrieb Paolo Bonzini:
>>> This requires kernel 3.10 but it is otherwise quite simple to do.
>>> The kernel pays attention to MSRs writes that are host initiated, and
Il 25/07/2013 12:14, Gleb Natapov ha scritto:
> On Wed, Jul 24, 2013 at 05:01:15PM +0200, Andreas Färber wrote:
>> Am 24.07.2013 16:37, schrieb Paolo Bonzini:
>>> This requires kernel 3.10 but it is otherwise quite simple to do.
>>> The kernel pays attention to MSRs writes that are host initiated,
On Wed, Jul 24, 2013 at 05:01:15PM +0200, Andreas Färber wrote:
> Am 24.07.2013 16:37, schrieb Paolo Bonzini:
> > This requires kernel 3.10 but it is otherwise quite simple to do.
> > The kernel pays attention to MSRs writes that are host initiated, and
> > disables all side effects of the PMU regi
Am 24.07.2013 16:37, schrieb Paolo Bonzini:
> This requires kernel 3.10 but it is otherwise quite simple to do.
> The kernel pays attention to MSRs writes that are host initiated, and
> disables all side effects of the PMU registers (e.g. the global status
> MSR can be written and global overflow c
This requires kernel 3.10 but it is otherwise quite simple to do.
The kernel pays attention to MSRs writes that are host initiated, and
disables all side effects of the PMU registers (e.g. the global status
MSR can be written and global overflow control MSR does not clear bits
in the global status
