public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: "Dong, Eddie" <eddie.dong-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel
	<kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
	"He, Qing" <qing.he-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: Re: lapic3 branch rebased
Date: Tue, 14 Aug 2007 13:00:01 +0300	[thread overview]
Message-ID: <46C17D21.607@qumranet.com> (raw)
In-Reply-To: <10EA09EFD8728347A513008B6B0DA77A01E8E414-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>

Dong, Eddie wrote:
> Avi Kivity wrote:
>   
>> lapic3 has been rebased, compile tested, and pushed.  note that this
>> does not include the patch-folding work I'd like to do before merging
>> into master. 
>>
>>     
> Thanks and verified it is fine for RHEL5U, XPSP2, FC5, Win2003. So feel
> free to 
> fold the patches and wanna to see merging soon :-)
> thx,eddie
>   

Some progress -- I rebased lapic3 and folded some patches; new branch 
called lapic4, 100% equivalent to lapic3 in final result.

Patches folded:

 KVM: cleanups on user/kernel irqchip checking
 KVM: Fix state save bug
 KVM: remove status in kvm_lapic structure
 KVM: Restore apic_base to struct kvm_vcpu
 KVM: Fix crash due to apic being accessed beore initialization
 KVM: Add missing #include
 KVM: IOAPIC: Temporarily avoid reissuing irq on EOI
 KVM: IOAPIC: Avoid delivering apic messages to non-existent vcpus
 KVM: Rename KVM_CAP_PIC to KVM_CAP_IRQCHIP
 KVM: Fix minor warnings in lapic patch
 KVM: Fix oops destroying VM with virtual PIC

Patches kept:

 KVM: pending irq save/restore
 KVM: in-kernel LAPIC save and restore support
 KVM: in-kernel IOAPIC save and restore support
 KVM: Bypass irq_pending get/set when using in kernel irqchip
 KVM: Add get/set irqchip ioctls for in-kernel PIC live migration support
 KVM: Protect in-kernel pio using kvm->lock
 KVM: Emulate hlt in the kernel
 KVM: In-kernel I/O APIC model
 KVM: Emulate local APIC in kernel
 KVM: Define and use cr8 access functions
 KVM: Add support for in-kernel PIC emulation

I plan to do some minor renaming and code movement (to remove artifacts 
like a line being moved by a patch for no reason).  Will be in a new 
branch lapic5.

-- 
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-08-14 10:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-13 15:31 lapic3 branch rebased Avi Kivity
     [not found] ` <46C07949.6090001-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-08-14  3:28   ` Dong, Eddie
     [not found]     ` <10EA09EFD8728347A513008B6B0DA77A01E8E414-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-08-14  7:59       ` Avi Kivity
2007-08-14 10:00       ` Avi Kivity [this message]
     [not found]         ` <46C17D21.607-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-08-14 12:08           ` Avi Kivity
     [not found]             ` <46C19B51.9010502-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-08-16  8:36               ` Zhao, Yunfeng
2007-08-16  9:00               ` Zhao, Yunfeng
     [not found]                 ` <10EA09EFD8728347A513008B6B0DA77AA3F00B-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-08-19  7:52                   ` Avi Kivity
2007-08-18 10:32               ` Dong, Eddie
     [not found]                 ` <10EA09EFD8728347A513008B6B0DA77A01EE24C5-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-08-19  7:31                   ` 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=46C17D21.607@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=eddie.dong-ral2JQCrhuEAvxtiuMwx3w@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