public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: "He, Qing" <qing.he-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [RFC][PATCH 0/7] guest SMP with in-kernel APIC
Date: Mon, 03 Sep 2007 17:22:12 +0300	[thread overview]
Message-ID: <46DC1894.7050100@qumranet.com> (raw)
In-Reply-To: <37E52D09333DE2469A03574C88DBF40FA9C1E8-wq7ZOvIWXbM/UvCtAeCM4rfspsVTdybXVpNB7YpNyf8@public.gmane.org>

He, Qing wrote:
> Hi,
>
> This patch set enables guest SMP when using in-kernel APIC. It is
> independent from the partial kernel apic SMP patch from Avi. We are
> posting it here for comments and possible merging with that patch. The
> patch set is based on:
> 	KVM: lapic5 branch: e9ddfaf472 (Remove dead code) with a patch
> that undoes 34735648ce (apic: implement init/sipi, work in progress),
> see the attachment in [PATCH 0/7].
> 	kvm-userspace: lapic5 branch: 206d1aa22f (qemu: prevent set
> wrong cr8 when using irqchip).
>
> btw, I can't find the cr8 patch in kvm-userspace from kvm-userspace.git,
> but it is in kvm-commits mailing list. Is there anything happened when
> kvm-userspace relocates on kernel.org or am I missing anything?
>
> The patch set is:
> 	[PATCH 0/7] :this post, and a temporary sipi/init undo patch
> 	[PATCH 1/7] is a preparation patch for userspace
> 	[PATCH 2/7] and [PATCH 3/7] are bug fixes for kernel
> 	[PATCH 4/7] modifies the PIC interrupt routing for SMP
> 	[PATCH 5/7] enables round robin for the apic lowest priority
> delivery
> 	[PATCH 6/7] is the main patch for SMP support. It handles
> SIPI/INIT in the kernel
> 	[PATCH 7/7] is the usermode part for SMP support, which disables
> userleve SIPI/INIT handling
>
>
> I have tested some situation, 32bit SMP Windows xp/srv2k3 and Linux
> 2.6.9/2.6.18 all works fine using in-kernel apics. User mode APICs also
> works fine. Test for other environments is ongoing.
>
> [PATCH 6/7] and [PATCH 7/7] have additional comments, please see the
> corresponding post.
>   

Applied all to lapic6 (with minor style modification).  Did not apply 
the bios change; will do it later through cmos nvram.

I will do some folding later on (will try out git rebase --interactive) 
and merge to master.

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


-------------------------------------------------------------------------
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-09-03 14:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-30  9:02 [RFC][PATCH 0/7] guest SMP with in-kernel APIC He, Qing
     [not found] ` <37E52D09333DE2469A03574C88DBF40FA9C1E8-wq7ZOvIWXbM/UvCtAeCM4rfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-09-03 14:22   ` Avi Kivity [this message]
     [not found]     ` <46DC1894.7050100-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-09-06  7:33       ` He, Qing
     [not found]         ` <37E52D09333DE2469A03574C88DBF40FA9C206-wq7ZOvIWXbM/UvCtAeCM4rfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-09-09  7:58           ` 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=46DC1894.7050100@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=qing.he-ral2JQCrhuEAvxtiuMwx3w@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