All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Ingo Molnar <mingo-X9Un+BFzKDI@public.gmane.org>
Cc: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: [RFT] mmu optimizations branch
Date: Tue, 02 Jan 2007 19:09:01 +0200	[thread overview]
Message-ID: <459A91AD.9030309@qumranet.com> (raw)
In-Reply-To: <20070102170212.GB25271-X9Un+BFzKDI@public.gmane.org>

Ingo Molnar wrote:
> * Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org> wrote:
>
>   
>>> unfortunately 0xc011f7f3 is in native_write_msr(), which isnt very 
>>> helpful. (i have CONFIG_PARAVIRT enabled in the -rt guest and host 
>>> kernels) But the MSR values suggest that this is the NMI watchdog 
>>> thing again, trying to program MSR_ARCH_PERFMON_EVENTSEL0 and 
>>> MSR_ARCH_PERFMON_PERFCTR0, but this time Linux recovered due to a 
>>> more robust MSR handling. The guest disabled the NMI watchdog with:
>>>
>>>  Testing NMI watchdog ... CPU#0: NMI appears to be stuck (0->0)!
>>>
>>> the FC6 installer hang that i saw with earlier MMU-branch snapshots 
>>> is fixed.
>>>       
>> Good.  Handling the counter well would have been very difficult, 
>> especially if attempting to support cross migration.
>>     
>
> as far as the NMI watchdog goes, it's in fact better to keep it disabled 
> this way - it's not like the guest context could 'lock up' in an 
> undebuggable way. Any NMI activity in the guest context would be pretty 
> pointless. I'd suggest simulating a non-working performance counter: 
> i.e. dont inject a #GPF when doing the wrmsr, and maybe preserve the 
> values that were written into the MSR register, but otherwise dont try 
> to implement the functionality by injecting NMIs. Worst-case this could 
> result in user-space debugging tools seeing non-working 
> performance-counter functionality.
>
>   

My worry is that when emulating an msr incorrectly, software can fail 
without any clue as to what went wrong.  I'll add the emulation as you 
suggest bug with a printk() to warn that we're bending the rules.


-- 
error compiling committee.c: too many arguments to function


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

  parent reply	other threads:[~2007-01-02 17:09 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-01 10:32 [RFT] mmu optimizations branch Avi Kivity
     [not found] ` <4598E33B.608-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-01-02 16:11   ` Ingo Molnar
     [not found]     ` <20070102161117.GA3306-X9Un+BFzKDI@public.gmane.org>
2007-01-02 16:32       ` Avi Kivity
     [not found]         ` <459A8909.7020600-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-01-02 16:49           ` Ingo Molnar
     [not found]             ` <20070102164912.GA25271-X9Un+BFzKDI@public.gmane.org>
2007-01-02 17:07               ` Avi Kivity
2007-01-02 17:01           ` Michael Riepe
     [not found]             ` <459A8FE0.2030202-0QoEqw4nQxo@public.gmane.org>
2007-01-03  8:49               ` Avi Kivity
2007-01-02 17:02           ` Ingo Molnar
     [not found]             ` <20070102170212.GB25271-X9Un+BFzKDI@public.gmane.org>
2007-01-02 17:09               ` Avi Kivity [this message]
2007-01-03  2:22           ` Ingo Molnar
     [not found]             ` <20070103022241.GA13840-X9Un+BFzKDI@public.gmane.org>
2007-01-03  3:05               ` Anthony Liguori
     [not found]                 ` <459B1D8A.6040604-NZpS4cJIG2HvQtjrzfazuQ@public.gmane.org>
2007-01-03  8:35                   ` Avi Kivity
2007-01-03  8:32               ` Avi Kivity
     [not found]                 ` <459B6A15.4010208-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-01-03 10:02                   ` Ingo Molnar
     [not found]                     ` <20070103100235.GA17168-X9Un+BFzKDI@public.gmane.org>
2007-01-03 10:16                       ` Avi Kivity
     [not found]                         ` <459B8267.5080000-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-01-03 11:30                           ` Ingo Molnar

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=459A91AD.9030309@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=mingo-X9Un+BFzKDI@public.gmane.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.