public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo-X9Un+BFzKDI@public.gmane.org>
To: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
	Laurent Vivier <Laurent.Vivier-6ktuUTfB/bM@public.gmane.org>,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	borntraeger-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org
Subject: Re: [PATCH] move kvm_guest_exit() after local_irq_enable()
Date: Mon, 22 Oct 2007 10:57:03 +0200	[thread overview]
Message-ID: <20071022085703.GA2781@elte.hu> (raw)
In-Reply-To: <471C647A.50908-atKUWr5tajBWk0Htik3J/w@public.gmane.org>


* Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org> wrote:

> Ingo Molnar wrote:
> >* Laurent Vivier <Laurent.Vivier-6ktuUTfB/bM@public.gmane.org> wrote:
> >
> >  
> >>According comments from Avi, we can clear PF_VCPU in kvm_guest_exit if 
> >>we move it after local_irq_enable().
> >>
> >>http://lkml.org/lkml/2007/10/15/114
> >>
> >>To simplify s390 port, we don't clear it in account_system_time().
> >>
> >>http://lkml.org/lkml/2007/10/15/183
> >>    
> >
> >thanks - i have picked your patch up.
> >
> >  
> 
> Note the kvm part is already in my 2.6.24 queue.

ok, then please push the whole patch to Linus, the scheduler bits are:

  Acked-by: Ingo Molnar <mingo-X9Un+BFzKDI@public.gmane.org>

	Ingo

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/

  parent reply	other threads:[~2007-10-22  8:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <47135D1B.1060004@bull.net>
     [not found] ` <11926264852739-git-send-email-Laurent.Vivier@bull.net>
     [not found]   ` <11926264852739-git-send-email-Laurent.Vivier-6ktuUTfB/bM@public.gmane.org>
2007-10-18 12:39     ` Use virtual cpu accounting if available for guest times Christian Borntraeger
     [not found]       ` <200710181439.10390.borntraeger-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org>
2007-10-18 12:41         ` Avi Kivity
2007-10-19 16:57       ` [kvm-devel] " Hollis Blanchard
2007-10-19 17:18         ` Hollis Blanchard
2007-10-18 13:19 ` [PATCH] move kvm_guest_exit() after local_irq_enable() Laurent Vivier
     [not found]   ` <11927135412363-git-send-email-Laurent.Vivier-6ktuUTfB/bM@public.gmane.org>
2007-10-18 13:32     ` Avi Kivity
2007-10-18 13:49       ` [kvm-devel] " Laurent Vivier
2007-10-22  8:26     ` Ingo Molnar
     [not found]       ` <20071022082604.GA28528-X9Un+BFzKDI@public.gmane.org>
2007-10-22  8:51         ` Avi Kivity
     [not found]           ` <471C647A.50908-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-22  8:57             ` Ingo Molnar [this message]
     [not found]               ` <20071022085703.GA2781-X9Un+BFzKDI@public.gmane.org>
2007-10-22  9:10                 ` Avi Kivity

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=20071022085703.GA2781@elte.hu \
    --to=mingo-x9un+bfzkdi@public.gmane.org \
    --cc=Laurent.Vivier-6ktuUTfB/bM@public.gmane.org \
    --cc=avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
    --cc=borntraeger-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox