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: Sun, 09 Sep 2007 10:58:24 +0300 [thread overview]
Message-ID: <46E3A7A0.90203@qumranet.com> (raw)
In-Reply-To: <37E52D09333DE2469A03574C88DBF40FA9C206-wq7ZOvIWXbM/UvCtAeCM4rfspsVTdybXVpNB7YpNyf8@public.gmane.org>
He, Qing wrote:
> Avi,
> During the rebase to lapic6, I saw two patches missing in this branch. Please see the attachments.
>
> For the p1 patch, it was Sheng's patch to fix x86_64 windows booting. I believe the commit 948a4b9e4b in kernel side (disable tpr/cr8 sync when in-kernel APIC is used) also addresses this issue, but from code point of view, this user mode patch is just OK, I see no reason to remove it. (btw., my original update on the patch is unnecessary, you can just drop that update).
>
> For the p2 patch, it was applied by you, and it's necessary for kernel apic SMP. Please reapply it to lapic6, and it can be folded and merged with kvm-userspace commit 314694c464 (conditionally bypass user level init/sipi handling).
>
> There is also a regression on SMP introduced by hrtimer migration. We are currently working on it and will send it out later as separate patch set.
>
>
Applied both, thanks.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
prev parent reply other threads:[~2007-09-09 7:58 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
[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 [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=46E3A7A0.90203@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.