public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Gregory Haskins <ghaskins-Et1tbQHTxzrQT0dZR+AlfA@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [PATCH 0/3] Usermode side patches for in-kernel APIC
Date: Mon, 07 May 2007 13:53:56 +0300	[thread overview]
Message-ID: <463F0544.5070609@qumranet.com> (raw)
In-Reply-To: <20070502214651.16845.19031.stgit-sLgBBP33vUGnsjUZhwzVf9HuzzzSOjJt@public.gmane.org>

Gregory Haskins wrote:
> Here is the patch series for the usermode side.  Note that the last patch is
> pretty much experimental, and doesnt appear to be working the way I intended.
> Please advise if you know of the right way to do that.  It doesnt seem to have
> affected anything that I was able to test so far, so I don't know if it
> matters or if there is a HALT race condition lurking in there until the signal
> handling is fixed.
>
> In any case, you can apply at least the first two and get "level-1" support
> running (in kernel LAPIC, QEMU based 8259/IOAPIC).
>
> Note that I abandoned my original patch that kicked off this whole party where
> I majorly re-worked QEMU.  I figured if that new qemu-irq stuff from QEMU
> upstream was coming soon we could just go the #if USE_KVM route for now.  We
> can make things more elegant when the new infrastructure is in place somewhere
> down the road.
>
> As with the kernel side changes, comments/feedback/bug-reports/patches
> welcome.
>
>   

These are fine.  Of course, new userspace has to work with 2.6.22, so 
you need to check feature availability.

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


-------------------------------------------------------------------------
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-07 10:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-02 21:53 [PATCH 0/3] Usermode side patches for in-kernel APIC Gregory Haskins
     [not found] ` <20070502214651.16845.19031.stgit-sLgBBP33vUGnsjUZhwzVf9HuzzzSOjJt@public.gmane.org>
2007-05-02 21:53   ` [PATCH 1/3] KVM: Updates for compiling in-kernel APIC support with external-modules Gregory Haskins
2007-05-02 21:53   ` [PATCH 2/3] KVM: in-kernel-apic modification to QEMU Gregory Haskins
     [not found]     ` <20070502215327.16845.64.stgit-sLgBBP33vUGnsjUZhwzVf9HuzzzSOjJt@public.gmane.org>
2007-05-09  8:16       ` Dor Laor
     [not found]         ` <64F9B87B6B770947A9F8391472E032160BBA5FCB-yEcIvxbTEBqsx+V+t5oei8rau4O3wl8o3fe8/T/H7NteoWH0uzbU5w@public.gmane.org>
2007-05-09 15:04           ` Gregory Haskins
2007-05-02 21:53   ` [PATCH 3/3] KVM-USER: Add support for in-kernel interrupts to wake-up QEMU Gregory Haskins
2007-05-07 10:53   ` Avi Kivity [this message]
     [not found]     ` <463F0544.5070609-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-05-07 15:13       ` [PATCH 0/3] Usermode side patches for in-kernel APIC Gregory Haskins

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=463F0544.5070609@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=ghaskins-Et1tbQHTxzrQT0dZR+AlfA@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