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/6] in-kernel APIC v5 (usermode side)
Date: Wed, 16 May 2007 15:03:28 +0300 [thread overview]
Message-ID: <464AF310.1060608@qumranet.com> (raw)
In-Reply-To: <20070515145843.15674.23622.stgit-sLgBBP33vUGnsjUZhwzVf9HuzzzSOjJt@public.gmane.org>
Gregory Haskins wrote:
> Changelog:
>
> 1) Incorporated Anthony's feedback regarding the missed use_kernel_apic()
> 2) Added a new patch to allow new userspace on old kernels
>
>
All good.
--
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/
prev parent reply other threads:[~2007-05-16 12:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-15 14:59 [PATCH 0/6] in-kernel APIC v5 (usermode side) Gregory Haskins
[not found] ` <20070515145843.15674.23622.stgit-sLgBBP33vUGnsjUZhwzVf9HuzzzSOjJt@public.gmane.org>
2007-05-15 14:59 ` [PATCH 1/6] KVM: Updates for compiling in-kernel APIC support with external-modules Gregory Haskins
2007-05-15 14:59 ` [PATCH 2/6] KVM-USER: Make the kvm_allowed flag always defined so we dont need #ifdefs Gregory Haskins
2007-05-15 14:59 ` [PATCH 3/6] KVM-USER: Add ability to specify APIC emulation type from the command-line Gregory Haskins
2007-05-15 15:00 ` [PATCH 4/6] KVM: in-kernel-apic modification to QEMU Gregory Haskins
2007-05-15 15:00 ` [PATCH 5/6] KVM-USER: Add support for listening for kernel-based interrupts Gregory Haskins
2007-05-15 15:00 ` [PATCH 6/6] KVM-USER: Check kvm extensions at runtime Gregory Haskins
2007-05-16 12:03 ` Avi Kivity [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=464AF310.1060608@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