public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Gregory Haskins" <ghaskins-Et1tbQHTxzrQT0dZR+AlfA@public.gmane.org>
To: "Avi Kivity" <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [PATCH 0/9] in-kernel APIC v8 (kernel side)
Date: Thu, 24 May 2007 11:12:18 -0400	[thread overview]
Message-ID: <465572E4.BA47.005A.0@novell.com> (raw)
In-Reply-To: <4655AA0C.9040108-atKUWr5tajBWk0Htik3J/w@public.gmane.org>

>>> On Thu, May 24, 2007 at 11:06 AM, in message <4655AA0C.9040108-atKUWr5tajBWk0Htik3J/w@public.gmane.org>,
Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org> wrote: 
> Gregory Haskins wrote:
>>
>> I bet it has something to do with the local_irq_disable vs clgi in the 
> kvm_run() code.
>>   
> 
> clgi() overrides local irq, so I don't see how that happens.

Im just grasping ;)  I only bring it up because I was less confident that I got that part correct than most of the other code.

-Greg


-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/

      parent reply	other threads:[~2007-05-24 15:12 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-24 13:22 [PATCH 0/9] in-kernel APIC v8 (kernel side) Gregory Haskins
     [not found] ` <20070524131917.11321.17746.stgit-sLgBBP33vUGnsjUZhwzVf9HuzzzSOjJt@public.gmane.org>
2007-05-24 13:22   ` [PATCH 1/9] KVM: Adds support for in-kernel mmio handlers Gregory Haskins
2007-05-24 13:22   ` [PATCH 2/9] KVM: VMX - fix interrupt checking on light-exit Gregory Haskins
2007-05-24 13:23   ` [PATCH 3/9] KVM: Add irqdevice object Gregory Haskins
2007-05-24 13:23   ` [PATCH 4/9] KVM: Adds ability to preempt an executing VCPU Gregory Haskins
     [not found]     ` <20070524132305.11321.61433.stgit-sLgBBP33vUGnsjUZhwzVf9HuzzzSOjJt@public.gmane.org>
2007-05-27 11:16       ` Avi Kivity
2007-05-24 13:23   ` [PATCH 5/9] KVM: Add support for in-kernel LAPIC model Gregory Haskins
2007-05-24 13:23   ` [PATCH 6/9] KVM: Adds support for real NMI injection on VMX processors Gregory Haskins
2007-05-24 13:23   ` [PATCH 7/9] KVM: Adds basic plumbing to support TPR shadow features Gregory Haskins
2007-05-24 13:23   ` [PATCH 8/9] KVM: Add statistics from interrupt subsystem Gregory Haskins
2007-05-24 13:23   ` [PATCH 9/9] KVM: Adds support for halting in the kernel Gregory Haskins
2007-05-24 14:50   ` [PATCH 0/9] in-kernel APIC v8 (kernel side) Avi Kivity
     [not found]     ` <4655A63E.7000505-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-05-24 14:58       ` Avi Kivity
     [not found]         ` <4655A80C.4000606-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-05-24 15:02           ` Gregory Haskins
     [not found]             ` <4655709E.BA47.005A.0-Et1tbQHTxzrQT0dZR+AlfA@public.gmane.org>
2007-05-24 15:06               ` Avi Kivity
     [not found]                 ` <4655AA0C.9040108-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-05-24 15:12                   ` Gregory Haskins [this message]

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=465572E4.BA47.005A.0@novell.com \
    --to=ghaskins-et1tbqhtxzrqt0dzr+alfa@public.gmane.org \
    --cc=avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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